Mid QA/QC Engineer
About the Role
We are looking for a QA/QC Engineer who will be responsible for designing, implementing, and maintaining automated testing frameworks for web and mobile applications, while also ensuring the quality of our Python-based API. This individual will work closely with development teams and QA/QC team members to create scalable, automated testing solutions, conduct manual testing when necessary, and optimize the QA/QC pipeline within our CI/CD workflows.
Responsibilities
- Test Automation & CI/CD Integration
- Develop, implement, and maintain automated test frameworks for web and mobile applications using tools like QASE.
- Design and execute automated API tests for our Python-based API using tools like Postman, PyTest, or REST Assured.
- Integrate automated testing into CI/CD pipelines (GitLab CI, Jenkins, etc.) to ensure continuous testing .
- Identify opportunities for automation to improve efficiency, test coverage, and reliability.
- API Testing & Backend Validation
- Conduct thorough validation of API endpoints, ensuring correct request/response handling, data integrity, and performance.
- Perform load, security, and failure recovery testing on the API (Locust, JMeter, etc.).
- Work closely with engineering team to understand API requirements and ensure robust integration testing.
- Process Improvement & Documentation
- Define and document QA/QC best practices, ensuring consistency in testing methodologies.
- Continuously evaluate testing strategies, implementing improvements to enhance quality and reduce deployment risks.
- Collaborate with cross-functional teams to ensure that QA/QC processes align with development workflows.
Qualifications:
- Technical Skills & Experience
- 3+ years of experience in QA/QC testing for web and mobile applications.
- Strong experience with test automation tools such as Selenium, Cypress, Appium, or Playwright.
- Proficiency in Python for API testing, using frameworks like PyTest or REST Assured.
- Experience with CI/CD pipelines and integrating automated tests into deployment workflows.
- Familiarity with SQL/NoSQL databases for test data validation.
- Knowledge of security testing best practices for API and application security.
- Experience with testing in embedded devices is a plus, but not mandatory.
- Soft Skills & Mindset
- Strong problem-solving skills and attention to detail.
- Ability to work independently and collaboratively in a fast-paced team.
- Excellent communication skills, with the ability to document and explain testing processes effectively.
- Curious and eager to learn, staying up to date with new testing tools and methodologies.
- Preferred Qualifications:
- Experience with performance testing using tools like Locust, JMeter or Gatling.
- Familiarity with containerized test environments (Docker, Kubernetes).
Previous experience working in an Agile development environment.
How to Apply
Start your application with the word banana this helps us confirm that you’ve read the job description and understand the requirements.
To apply:
- Submit your resume.
- If you advance past the second interview, you’ll be asked to walk us through a project you’ve completed.
All interviews require your camera to be turned on.
Important:
Reading from any AI agent during the interview will immediately disqualify you. We fully embrace AI as a tool for engineers, but we need critical thinkers. Show us that you’re a great fit by demonstrating extreme ownership, strong teamwork, technical excellence, and problem-solving skills.
Equal Employment Opportunity Employer
We are proud to be a global team united by diverse perspectives, cultures, and experiences. Our commitment to inclusion and respect extends across every border, embracing the unique contributions that individuals bring from all walks of life and every corner of the world.
We are an equal opportunity employer and welcome everyone, regardless of race, color, religion, gender, gender identity, sexual orientation, age, national origin, disability, veteran status, or any other characteristic that makes you uniquely you. Your story matters, and we value the richness it adds to our shared journey.
We strive to create an environment where every team member—no matter where they are in the world—feels seen, heard, and empowered to succeed. From hiring to development, promotions, and beyond, we are dedicated to ensuring equity and fairness for all.
Together, we are building a global community where collaboration and respect drive innovation and belonging.
Application Prompt (Loom Video Required)
We’re looking for QA/QC Engineers who don’t just test—they engineer quality into everything they touch. In this short Loom video, we want to understand how you think, how you problem-solve, and how you communicate with both engineers and non-technical stakeholders.
Scenario
Your team is preparing for a production deployment of a new mobile feature that allows users to sync their wearable device to track biometric data (e.g., heart rate, steps). This feature interacts with:
- A new set of Python-based API endpoints
- A third-party wearable SDK
- A mobile interface (both Android and iOS)
During regression testing, your automated suite passes on web and Android, but you notice the following:
- On iOS, the sync flow intermittently crashes during onboarding.
- The API appears stable under unit and basic integration tests, but fails under concurrent load (500+ simultaneous requests).
- The Product team is expecting a greenlight by end of day to hit a marketing deadline.
In your Loom (4–6 minutes), walk us through:
- Your immediate response:
- How would you isolate the iOS crash and API underperformance?
- What tools would you use to debug and validate both layers (frontend and backend)?
- How would you isolate the iOS crash and API underperformance?
- Your communication strategy:
- What would you communicate to the developers, product team, and QA peers—especially with a time-sensitive launch?
- How would you ensure alignment without slowing momentum or compromising quality?
- What would you communicate to the developers, product team, and QA peers—especially with a time-sensitive launch?
- Your longer-term reflection:
- What changes would you propose to prevent these issues in future cycles (e.g., automation improvements, performance testing enhancements, better test data strategy, etc.)?
- What changes would you propose to prevent these issues in future cycles (e.g., automation improvements, performance testing enhancements, better test data strategy, etc.)?
Start your video by saying the word “pineapple” so we know you’ve read this fully.
Please submit your Loom link with your resume and any relevant project samples or GitHub links.