Senior QA Engineer at Wipfli (Chicago, IL)
Punchkick Interactive Inc.
Punchkick is comprised of a team of exceptional designers, developers, and strategists. We build products that we take pride in for clients we deeply respect. Punchkick runs flat, and our uncommonly close-knit structure helps us guide each other toward excellence. We’re seeking a talented and motivated self-starter to join our unique family.
What are we looking for?
Punchkick QA is responsible for ensuring all functional expectations come together as gracefully as possible. Boiled down, QA is a system of checks and balances and—within an agile environment, where waterfall conditions are not apparent—the checks and balances system has the potential to quickly break down. Time management, self-motivation, thinking outside the box, and working as an integral member of several project teams are all crucial qualities for a successful QA and we encourage all candidates with past QA experience to reach out.
The full-time Punchkick Senior QA Engineer job description can be broken down into three activities:
- Testing (Manual)
The core of this QA position lies in conducting manual test plans and bug logging to ensure a more end-user-friendly experience. Testing encompasses everything from ensuring Acceptance Criteria is functional per specification (across the span of a project’s development), ensuring test cases are created per spec, black box testing, smoke testing, regressions testing, and beyond.
High-level testing tasks, testing tools, and general expected understandings include:
- Document bugs/issues in Jira
- Test Case creation based on documented scenarios
- Xcode and Android Studio (to build commits/code to device and virtual tools)
- Browsers (ex. Chrome, Firefox, Safari, IE)
- iOS and Android devices (and have an understanding of the latest, minus 2, operating system versions per those platforms)
- Versioning (at ex. A commit level), regression, bug within a bug concept
- Distinguishing between a bug and UX decisions
Documentation is invaluable and often becomes a cyclical cycle of never-ending considerations. That said, documentation is important, and finding the right balance, per project, is part of the role. Most Punchkick QA documentation can be broken down into two major categories: logging bugs and creating test cases. Considerations for each include:
- For bug-logging, ensuring all bugs are logged with adequate, and enough detail.
- For Test Case creation, ensuring all functional features are accounted for, and assessing the potential volume of regressions, per project.
High-level Documentation tasks, tools, and general expected understandings include:
- Bug entry in Jira (a daily task)
- Test Case creation (a per Sprint cadence task)
- Excel, Google Sheets, LICEcap, Sketch, VMs, Charles, SourceTree
Meetings at Punchkick aim to serve a very specific purpose. Be it Sprint Planning, Sprint Retro, a 15 minute daily stand-up, the goal is to ensure the team regroups to assess specific projects. The open office environment runs parallel with this idea—being open and willing to converse with team members, in such an environment, is a must.
High-level Meeting tasks, tools, and general expected understandings include:
- Ensure Jira is updated daily
- Ensure Test Cases are updated (ideally, per a Sprint cadence)
- Come with answers and questions, and leave with answers (so, come prepared with an understanding of your projects at at least a Sprint level).
- Are comfortable (and capable) talking to clients, and all Punchkick team members (APs, SMs, Dev, Design, Marketing, Business)