Senior QA Engineer
AI summary
Watu Credit is hiring a Senior QA Engineer to be embedded in a squad as the senior technical authority on quality. The role involves owning test architecture, leading performance and load testing, defining acceptance criteria, and mentoring QA Engineers across the chapter. This is a senior individual-contractor role based in Nairobi, working remotely.
- Senior individual-contributor role, not management
- Own test architecture and performance/load testing for your squad
- Mentor QA Engineers and represent squad in QA Guild
- Requires CS/IT Degree and 5+ years QA experience
- Salary open; deadline 05/10/2026
AI job guide
Use this guide to check salary signals, requirements, documents, application steps and safety before you apply.
AI salary guide
Source salary availableThe source lists Open. Confirm the final pay, benefits, contract terms and allowances directly with the employer before accepting an offer.
Can you qualify for this role?
- Required5+ years of relevant experienceThe job post includes a minimum experience signal.
- RequiredEducation or certification mentioned in the postThe captured text mentions education, a diploma, certificate, or licence.
- PreferredPractical evidence in internship, restaurante, technologyThe tags and summary point to skills connected with this role.
- RequiredAvailability to work in Not specifiedThe vacancy is associated with this location.
- UnclearComfort with the Remote contract termsConfirm hours, duration, probation and benefits at the original source.
Documents to prepare
- Likely requiredUpdated CV
- Role specificCover letter or short employer message
- OptionalProfessional references
- Role specificAcademic or professional certificates
- VerifyID or passport only after verifying the employer
Application tips for this job
- Place your strongest Senior QA Engineer evidence in the first half of your CV.
- In your cover letter or employer message, connect your experience to Watu Credit and the role in Not specified.
- Add concrete examples related to internship, restaurante, technology, ideally with measurable outcomes or clear responsibilities.
- Follow the instructions from Corporate Staffing Kenya; avoid sending documents to unofficial contacts or copied links.
- Confirm the deadline, interview location and employer contact before sharing personal documents.
- Plan to submit before the listed deadline: 2026-10-05.
Source and safety check
- Corporate Staffing Kenya
- Original source link available
- Application method is clear
- Deadline is available: 2026-10-05
- No major risk signal was detected in the captured text.
Never pay for interviews, shortlisting, medical checks, uniforms, or job placement. Confirm every application at the original source before sharing personal documents. Report suspicious listing.
Interview preparation
- What experience makes you a strong fit for this Senior QA Engineer role in internship, restaurante?
- How have you handled responsibilities similar to those in this job post?
- Are you available to work in Not specified under the listed contract or schedule?
- Prepare examples with clear responsibilities, tools used and measurable outcomes.
- Review the source and research Watu Credit before the interview.
Ask what the first priorities will be in the role and how success will be measured.
Similar jobs to consider
Use AI to apply better
After confirming the original source, use Career Assistant to check role fit, tailor your CV and prepare a cover letter or employer message.
Original source description
Job Title: Senior QA Engineer
Date Posted: 25/09/2026
Job Type: Remote
Job Level: Management
Employer: Watu Credit
Industry: Quality Control
Salary: Open
Location: Nairobi
Country: Kenya
Deadline: 05/10/2026
Quality Control Jobs, Watu Credit Jobs. Senior QA Engineer designs comprehensive test cases, executes automated test suites, and ensures software quality across releases, requires a CS/IT Degree and 5+ years QA experience.
Job Summary
As a Senior QA Engineer at Watu, you are embedded in a squad – the senior technical authority on quality within it. You do everything a QA Engineer does – ceremonies, acceptance criteria, automated test suites, the Definition of Done – but you also own the harder problems: test architecture, performance and load testing, contract testing, and the squad’s most complex integration surfaces.
You report to your squad’s Tech Lead for day-to-day work. For QA standards and tooling, you sit in the QA Chapter led by the QA Chapter Lead, who reports to the Head of Engineering. You are the natural deputy to the QA Chapter Lead – representing your squad in the QA Guild when needed, mentoring QA Engineers across the chapter, and often owning a specific chapter-wide initiative (a framework, a tooling migration, a testing discipline) end to end.
This is a senior individual-contributor role, not a management role. You lead through technical depth and example, not through authority over other QA engineers’ day-to-day work.
Key Responsibilities
- Attend all squad ceremonies – sprint planning, daily standup, review, retrospective – as a full member of the squad, not a downstream recipient of work.
- Define acceptance criteria with the Product Owner before each sprint, and push back on ambiguity before development starts, not after.
- Own test architecture for your squad’s domain – the structure of the test pyramid, how unit, integration, contract, and E2E tests fit together, and where the squad’s coverage gaps are.
- Lead performance and load testing for your squad – establishing baselines, identifying throughput and concurrency limits, and surfacing risk before it reaches production.
- Own the squad’s Definition of Done quality gate, and act as the final internal check before anything ships to staging or production.
- Mentor QA Engineers in your squad and across the chapter – reviewing their test design, raising the bar on automation quality, and helping them grow into the standards the Chapter Lead sets.
- Deputise for the QA Chapter Lead where needed – representing your squad’s QA practice in the monthly QA Guild, and contributing directly to chapter-wide standards, tooling decisions, and onboarding material.
- Own a chapter-level initiative – for example, the contract-testing framework, the performance-testing toolkit, or AI-assisted test generation – evaluating, implementing, and documenting it for the whole function.
- Triage the squad’s hardest test failures – distinguishing flaky tests from real regressions in complex, high-traffic, or high-risk areas of the system.
- Use AI/LLM tooling actively: test case generation, synthetic test data, regression triage, and documentation are all areas where AI accelerates QA work.
Requirements
- Essential
- 5+ years of QA engineering experience in a software product environment, with a track record of owning test strategy for a complex domain, not just executing within it.
- Strong automation engineering skills – you write test code to a production standard, in Java, Python, or JavaScript, and your suites are maintainable, readable, and stable in CI.
- API testing depth – REST API testing, contract testing, integration test design, HTTP semantics, and JSON schema validation.
- Experience with performance and load testing – you can design and run load tests, interpret throughput and concurrency results, and translate them into engineering action.
- Comfortable operating without a QA manager above you, and confident enough in your technical judgement to mentor others and represent QA practice beyond your own squad.
- Experience in Java-based backend environments – you can read Java code, understand the architecture, and write tests that reflect it accurately.
- Strongly preferred
- Experience in fintech, payments, or digital financial services – you understand the stakes of testing systems that move money.
- Experience with contract testing (Pact or equivalent) in a microservices environment.
- Mobile app testing experience – Android in particular, whether automation (Espresso, Appium) or structured manual testing with a regression framework.
- Experience mentoring other QA engineers, running internal training, or contributing to a QA chapter, guild, or community of practice.
- Familiarity with AI-assisted test generation tooling – test case generation, regression triage, and synthetic test data creation using LLMs.