FREE ACCESS
5,000–10,000 jobs/day
See all jobs on JobTailor
Search thousands of fresh jobs every day.
Discover
- Fresh listings
- Fast filters
- No subscription required
Create a free account and start exploring right away.
ATS Keywords
Tailor your resumeApplicant Tracking System Keywords
Tip: use these terms in your resume and cover letter to boost ATS matches.
Hard Skills
test automationexploratory testingfunctional testingREST APIsSQLCypressPlaywrightPostmanSeleniumtest pyramid
Soft Skills
collaborative attitudeautonomycritical thinkingclear communicationproactive improvementpair-testingproblem-solvingattention to detailadaptabilitycustomer focus
Tools & Technologies
Postman/NewmanRestAssuredtest environmentstest suitesauxiliary databasesproduction incident analysislogs and metricstest data setsdefect trackingversion control
Certifications & Qualifications
Bachelor's degree in Computer ScienceBachelor's degree in Software EngineeringBachelor's degree in Information SystemsBachelor's degree in Systems Analysis and Development
Industry Keywords
acceptance criteriaedge casesdata consistencyintegration testingE2E testingregression testingsmoke testingcritical flowsuser impactnonconformities
Tech Stack
Tools & technologiesCypressSeleniumSQL
About the role
Key responsibilities & impact- Participate in story refinement together with the PO, design and developers, proposing acceptance criteria, edge-case scenarios and questions that reduce ambiguity before the story enters development.
- Build test plans for squad stories and features, identifying risks, critical flows and what is worth automating vs what should only be validated manually.
- Configure local and test environments to run test suites (manual and automated), including dependencies, mocks and auxiliary databases.
- Prepare, maintain and manage representative test data sets, balancing happy paths, edge cases and error scenarios.
- Perform exploratory and functional testing during the sprint, in the same development cycle rather than as a final pipeline stage.
- Develop and maintain API and end-to-end test automation for critical flows, keeping the test suite healthy and reliable over time.
- Validate integrations with third-party APIs and asynchronous flows, including failure scenarios, retries and idempotency.
- Verify data consistency in the database by writing queries to compare persisted data with expected results.
- Report defects and nonconformities found both in requirement specifications and in implementation: provide reproduction steps, evidence, user impact and criticality assessed together with the PO.
- Support production incident analysis, helping reconstruct scenarios and design coverage to prevent recurrence.
- Analyze and follow up on customer tickets in production, translating recurrent issues into improvements in test coverage and process.
- Work in pair-testing with developers and review automated tests written by the team.
- Monitor production deliveries and the acceptance criteria developed.
Requirements
What you’ll need- Bachelor's degree in Computer Science, Software Engineering, Information Systems, Systems Analysis and Development, related fields, or equivalent proven practical experience.
- Fluent English for reading technical documentation.
- 2.5+ years of experience in software quality, with work in both exploratory/functional testing and automation.
- Solid experience testing REST APIs: authentication, headers, payloads, status codes, contracts and versioning.
- Experience building and maintaining test automation in at least one market stack (Cypress, Playwright, Postman/Newman, Karate, RestAssured, Selenium or equivalents), with an understanding of the trade-offs between them.
- SQL in relational databases: read and write queries to validate data, verify states and investigate scenarios.
- Ability to read logs and metrics in production to understand system behavior without relying on someone else to interpret what happened.
- Knowledge of the test pyramid and different types (unit, integration, contract, E2E, regression, smoke), with criteria to decide when to apply each.
- Careful handling of edge cases involving sensitive data: monetary values, dates, time zones, decimal precision, concurrency.
- Autonomy to unblock tasks: investigates before asking, but communicates blockers early when help is needed.
- Collaborative attitude: brings risks and scenarios to the table instead of only pointing out errors, and accepts feedback about their work without friction.
- Works closely with developers in refinement and pair-testing, rather than acting as an end-of-pipeline gate.
- Proactively proposes coverage or process improvements based on observations from the squad's day-to-day work.
- Operates in a horizontal, multidisciplinary team treating PMs, designers, developers and other analysts as peers in decision-making.
- Shares learnings through pair-testing, technical conversations or short documentation as a daily habit.
- Critical stance toward code and test scenarios generated by AI: reviews, questions and does not accept suggestions as truth.
- Genuine interest in the product: wants to understand the "why" before planning "how" to test.
- Tracks defects to root cause rather than closing tickets when the symptom disappears.
- Clear written communication in Portuguese, especially when describing defects (steps, evidence, impact, criticality).
Benefits
Comp & perks- Distributed QA culture: works closely with developers, contributes to refinement and reviews the team's automated tests.
- Familiarity with CI/CD pipelines in Azure DevOps or equivalents: understands where automation runs, reads execution results and investigates intermittent failures.
- Use of Grafana or equivalents for production observability: reading structured logs, metrics and alerts.
- Use of Docker in the local development workflow to spin up the application environment.
- Short, direct documentation of test scenarios, bug reports and coverage decisions.
- Use of AI tools with discernment in daily work, maintaining responsibility for what is validated and released.
- Awareness of security in sensitive flows: handling personal and financial data in tests, using controlled test data sets, and attention to credential leakage.
