Software Engineer In Test - SDET (Contractual)
About the Role
We’re looking for a Senior Developer in Test who sees quality as a shared responsibility—not a checkpoint at the end of delivery. This role goes well beyond executing test cases or logging defects. You’ll operate as a technical leader in quality, shaping how we design, build, test, and ship software.
You’ll be embedded in an Agile, DevOps-driven environment where automation, fast feedback, and engineering excellence are non-negotiable. Your mandate is simple but demanding: raise the reliability, predictability, and confidence of our software at scale.
You’ll challenge assumptions, influence architecture, and help the team push testing as far down the pyramid as possible—while still knowing when hands-on exploratory testing is the smartest move.
What You’ll Do
Engineering Quality at the Core
- Design, build, and evolve test automation frameworks from the ground up across UI, integration, end-to-end, and performance layers
- Write atomic, fast, and maintainable automated tests that provide meaningful signal—not noise
- Embed testing into the development lifecycle, ensuring quality is built in, not bolted on
- Ensure integration, regression, and end-to-end test suites run reliably and continuously
DevOps & CI/CD Enablement
- Keep the CI/CD pipeline green by ensuring the right testing tools, coverage, and practices are in place
- Integrate automated tests seamlessly into pipelines using modern CI/CD tooling
- Mock services and dependencies to remove bottlenecks and enable faster feedback loops
- Incorporate security and non-functional testing alongside functional validation
Agile Partnership & Influence
- Actively participate in the Three Amigos process, shaping acceptance criteria and ensuring testability from day one
- Support Product Owners by clarifying functional and non-functional requirements
- Translate acceptance criteria into meaningful automated tests that teams trust
- Advocate for pragmatic testing strategies aligned with business risk
Enablement & Continuous Improvement
- Coach engineers and testers on automation-first thinking and good testing practices
- Share insights from industry trends, tools, and evolving testing methodologies
- Promote a culture of metrics, observability, and data-driven improvement
- Collaborate closely with Operations to reinforce a strong DevOps culture
What We Consider Non-Negotiable
- Proven experience building test automation frameworks from scratch (UI, integration, E2E, performance)
- Strong hands-on background in integration and end-to-end testing
- Experience with UI automation tools such as Cypress, Selenium, or Playwright
- Solid software engineering foundation in one or more of: Java, .NET, Go, C#, PHP, Node.js, JavaScript, or Python
- Practical experience with manual testing, including positive and negative paths
- Deep understanding of Agile practices and how QA adds value within them
- Experience working in a DevOps-oriented, cloud-native environment
- Hands-on expertise in testing REST APIs and webhooks using tools like Postman, Swagger, Rest Assured, or similar
- Working knowledge of CI/CD tooling (Git, Jenkins, Maven, Terraform, Ansible, Cucumber, or equivalents)
- Comfortable operating across distributed teams and time zones
- Strong communicator who can influence without authority and educate without friction
Nice to Have
- Testing in Docker and Kubernetes environments
- Performance testing experience with JMeter or similar tools
- Exposure to AWS, ELK stack, and observability tooling
- Experience with BDD and Gherkin
- Security testing, accessibility testing, or TDD support
- Event-driven or streaming architecture testing
- Mobile automation using Appium or similar frameworks
- Contribution to open-source projects
What This Role Is Not
This is not a checkbox QA role.
It’s not about guarding quality from the sidelines or policing releases after the fact.
If you’re energized by ownership, influence, and building systems that scale quality across teams, you’ll thrive here. If you prefer rigid boundaries, narrow scopes, or purely manual execution, this won’t be the right environment.