Performance Engineering Service Manager — Test Evidence Continuity, Interim

The mandate

A performance testing service needs a six-month manager while several retail and healthcare product releases continue through an established test calendar. The immediate need is ownership of a small team's priorities and the comparability of its evidence, not a missing technology strategy. The interim manager will keep the service usable, ensuring that changed test conditions, unfinished investigations and release limitations remain visible rather than disappearing behind completed test reports, and will hand the service back to the returning manager at the end of the term.

The assignment begins onsite in Hyderabad on 26 October 2026, requires five days each week and is fixed for six months with no extension. The incumbent's planned return defines the cover's endpoint, with neither a replacement search nor permanent conversion proposed. In the first ten working days, the interim will confirm the accepted request queue, available test environments, reference workloads and known evidence defects with the Engineering Quality Head and the current service's technical contributors.

Many misleading comparisons originate outside the code under review. Different dataset sizes, altered dependency behaviour, an unrecorded configuration change or competing use of the environment can make one release appear faster than another. The interim will require each run to carry an intelligible conditions record and will determine whether its result is comparable to the agreed baseline. Where a meaningful comparison cannot be made, the service must report that limitation and seek the missing input rather than issue an unsupported trend claim.

Day-to-day authority includes allocating five engineers, approving their analysis within the existing test method, setting investigation priorities and recommending performance readiness to release owners. Product teams decide functional acceptance, environment owners authorise infrastructure changes and the Engineering Quality Head approves material method or staffing departures. The interim cannot waive a release gate, hire permanent staff or commit to platform redesign. Clinical decisions, commercial campaign approvals and enterprise infrastructure replacement are outside this service-management assignment.

Handback is complete when the returning manager can independently operate the request queue, reproduce a selected baseline comparison and chair two evidence reviews with unresolved limitations correctly routed. The service's engineers must demonstrate access to the run records and maintenance instructions without relying on the interim's personal working files. The Engineering Quality Head and returning incumbent jointly accept the handover, including the named owner, next action and decision route for every material open investigation rather than requiring an artificially empty backlog.

What you will own

• Confirm the incoming test queue and reference baselines during the first ten working days, identifying requests that lack an agreed workload, environment condition or authorised readiness question.
• Allocate the five engineers against material release needs and investigation effort, recording changed priorities so product owners understand which evidence can be delivered and which remains outstanding.
• Establish a complete conditions record for each accepted run, including data characteristics, relevant configuration, dependency assumptions and concurrent environment use that may invalidate comparison.
• Decide whether a reported performance change is analytically supported within the service's method, requesting a controlled rerun when environment differences prevent a defensible conclusion.
• Present readiness recommendations to release owners with reproducible observations and explicit limitations, keeping functional acceptance and any exception decision with their authorised governance routes.
• Coach engineers in preserving investigation history and explaining contradictory results, so service continuity does not depend on the interim personally interpreting every test or working file.
• Conduct the returning manager's observed handback through queue operation, baseline replay and two chaired evidence reviews, obtaining joint acceptance of remaining investigations and their ownership.

Candidate qualifications

• Bring at least seven years of performance engineering or architectural practice, with direct responsibility for test design, result interpretation or a recurring performance review service. Explain a comparison you rejected because the conditions differed, the evidence that revealed the defect and the test that restored confidence. Relevant retail or healthcare technology context is useful; the essential proof is disciplined performance reasoning that remains understandable after the original analyst steps away.
• Show practical ability to organise a focused technical service through mentoring, work coordination, review leadership or small-team management. You must be able to prioritise requests, challenge incomplete inputs and develop another engineer's analysis while maintaining a clear decision queue. Previous executive leadership is unnecessary. Describe how you kept technical judgement accountable when several product teams wanted an immediate answer but the evidence supported different levels of confidence.
• Understand how test datasets, environment configuration, dependency conditions and measurement boundaries affect comparability. Demonstrate a reproducible run record and an approach to separating release changes from environmental noise. The assignment does not prescribe a particular language, infrastructure provider or testing product; you must learn the existing service's tools and controls quickly. Use approved test data and seek the relevant privacy or healthcare owner when an access or interpretation question exceeds engineering authority.
• Be available onsite from 26 October 2026 for five days weekly throughout the six-month fixed cover. Provide an example of knowledge transfer through observed practitioner use, technical review or a responsibility handback, explaining what the receiving owner could reproduce independently. Commit to a truthful record of unresolved work and to the returning incumbent's restored authority, with release exceptions and material service changes referred to the designated owners.

Application

Applications for this mandate are received in one way only: through the India Board Terminal's application process. It is automated end to end. Your Executive Passport travels to the mandate holder in its confidential form, your answers to the three questions below are read before anything else in your file, and every stage that follows is recorded on your applications page.

There is no address to write to and no intermediary to call. The mandate holder reads what the Terminal delivers and nothing else, which is what keeps the process the same for every applicant and keeps your name out of it until you release it. Applications close on 11 October 2026. Mandate reference CVU-INT-2026-IND-084.