Lensys
Suivez-nous

Test Analyst

A focused test analyst is needed to bring order to a complex backend quality landscape, turning scattered test coverage into a clear, actionable assurance strategy. The role blends deep analysis, environment coordination, and Agile collaboration to help a major public-facing organization ship with confidence.

CONTEXT

Our client, a major player in its sector, is modernizing a critical backend platform that supports high-volume public services. The platform has evolved through multiple delivery cycles, and legacy testing practices have left behind a complex web of partially covered flows, duplicated checks, and uncertain quality signals. The organization is not simply looking for someone to execute scripts; it needs a test analyst who can read the quality story hidden inside the backlog, understand where risk has accumulated, and help teams recover clarity without slowing delivery. This is a chance to join a structured Agile environment where quality is treated as a shared engineering responsibility, and where careful analysis can directly shape how future releases are planned, built, and validated.

ACTIVITIES

  • Map and manage testing debt across backend services, identifying where coverage is thin, outdated, duplicated, or disconnected from real business risk.
  • Perform detailed test coverage analyses and translate the findings into clear gap assessments, improvement plans, and prioritization proposals.
  • Execute test activities within an Agile SCRUM cadence, collaborating with product owners, developers, and fellow QA professionals to validate behavior and reduce release risk.
  • Coordinate test environments and data needs, ensuring the right configurations are available for functional, integration, and regression testing.
  • Facilitate quality assurance conversations across project teams, challenge assumptions, and promote shared ownership of testability and defect prevention.
  • Document test evidence and quality decisions in a way that remains useful to both technical teams and less technical stakeholders.

EXPECTED ACHIEVEMENTS

  • A measurable reduction in testing debt, with a clear roadmap showing which gaps have been closed and which risks remain.
  • Stronger visibility into test coverage, allowing delivery teams to make informed decisions about scope, quality, and release readiness.
  • More reliable and better coordinated test environments, reducing delays caused by configuration issues or missing data.
  • A culture of proactive quality assurance in which testing is understood as a design and risk-management activity, not a final checkpoint.
  • Confident, evidence-based releases for a major public-facing service, with fewer surprises and clearer accountability across the delivery chain.

ENVIRONMENT

  • Agile SCRUM delivery with cross-functional project teams and recurring ceremonies.
  • Backend services and integration layers requiring structured functional and regression testing.
  • Test management and defect tracking tools, coverage analysis practices, and environment coordination workflows.
  • A Dutch-speaking stakeholder context, with English used for technical collaboration.
  • A quality assurance mindset built around risk-based testing, test coverage analysis, improvement planning, and collaborative defect prevention.