Tell me about yourself.

This isn't an autobiography — it's the opening pitch that sets the tone for the rest of the interview. Don't use STAR here; use the Past–Present–Future structure.

Past (how you got here) — one or two sentences. "I came into QA from [a related background — support, dev, ops, or QA from day one]. What drew me in was [a specific aspect: the systems thinking, breaking things, helping users, …]." Avoid life history; pick the one or two facts that matter for this role.

Present (what you do now and what you're known for) — the meatiest section, 30-45 seconds. "Currently I'm a [role] at [team or domain]. My day-to-day is [concrete: writing automation, owning a release suite, leading test strategy for X]. The thing I get told I do well is [specific signature strength — e.g. 'I'm the person teams come to when a flake won't go away,' or 'I bridge developer and product conversations on testability']."

Future (why this role) — 15-20 seconds. "What I'm looking for next is [a substantive aspiration that matches the JD — bigger scope, deeper specialism, leadership, a problem domain that fascinates you]. Your role caught my attention because [a specific reason rooted in the company / team / tech stack]." This is where you connect the dots between your trajectory and this role.

Tone: confident but not boastful, specific not vague, professional but warm. Practise it out loud — written and spoken cadence are different. The interviewer is listening for whether you can structure thought under mild pressure as much as for the content.