🎨 Agency & studio

// Round by round

2–3 rounds · typical sequence

1. 1
   Culture and portfolio screen— 45 min· Hiring manager or studio director

   Portfolio review: what projects have you worked on, which stacks, how varied is your experience? The HM is also evaluating energy and communication style — agencies are small teams and culture fit is a practical concern, not just a nice-to-have. Expect questions like: 'What is the most different project you have worked on from your usual stack?' and 'How do you communicate a technical defect to a non-technical designer?'

   Scored: Range of experience, communication energy, interest in the agency's client portfolio, adaptability.

2. 2
   Practical and process review— 45–60 min· Lead QA or tech lead

   Three parts: (1) A short live test design exercise — often a form or e-commerce checkout, no spec provided. (2) 'How would you set up testing on a new project in 48 hours with no documentation?' They want to hear a specific plan, not 'I would explore the app.' (3) Tool breadth questions — 'Which automation framework would you choose for a React + Node project and why?'

   Scored: Speed of structured thinking, adaptability, breadth of tools, fast ramp-up plan.

3. 3
   Team or stakeholder meet— 30 min· Creative director, PM, or designer

   Evaluating whether you will work well with people who are not engineering-literate. Agencies often have designers and PMs reviewing bug reports. They want to see you explain technical defects in plain language, ask about the client's goals (not just the tech), and show interest in how the project serves the end user — not just whether the build passes.

   Scored: Empathy, plain-language communication, client and user awareness, collaboration style.

// What they weight

The signals that distinguish strong candidates from average ones in this archetype.

• Fast project ramp-up: agencies cannot afford a QA who takes two weeks to be productive on a new stack. They want to see someone who can skim an app, identify the highest-risk flows, and have basic smoke coverage running by end of day one — without documentation or a senior to guide them.

• Cross-functional communication as a core skill: your bug reports will be read by designers, PMs, and clients — not just engineers. Agencies specifically reward QAs who can explain a defect in plain English with a clear reproduction path and propose a fix direction without jargon.

• Manual and automation balance: studios mix manual and automated testing depending on the project timeline and client budget. A QA who can only automate is a liability when the project budget does not allow for it; a QA who only tests manually cannot deliver the efficiency a tech-forward client expects.

• Multi-project context-switching without quality loss: handling 2–3 live projects simultaneously — each with different stacks, different CI setups, different release rhythms — requires strong personal organisation and ruthless prioritisation. The interview is partly evaluating whether you have that discipline.

// Question shapes to expect

These are question categories and formats — not leaked specific questions. Real questions vary by team and interviewer.

• 01

  Fast ramp scenario: 'You are joining a new project on Monday. The previous QA left no documentation. A release is scheduled for Friday. By Wednesday you need smoke tests for the checkout flow. Walk me through your approach.' Expect to be specific about what you would do hour by hour.

• 02

  Client communication test: 'A designer you work closely with has shipped a UI change that breaks three of your automated tests. How do you raise it without creating tension?' They are evaluating your communication style, not just your technical instinct.

• 03

  Tool-agnostic automation decision: 'The client is using React and Node, there are no existing tests, the budget is two weeks, and the project is a marketing campaign with a 6-week life. What do you automate first and with what?'

• 04

  Multi-project prioritisation: 'You have three active projects. All three have releases on Thursday. Monday morning you discover a regression in project A that affects project B. Walk me through how you triage and communicate.'

• 05

  Live bug report: they may show you a visual regression or a recorded session and ask you to write the bug report on the spot. Clear title, precise steps, screenshot reasoning, and no jargon.

// How to prepare

• ☐Build a breadth story: for each major framework you have used, prepare a two-sentence pitch — what project, what problem it solved, why that tool was the right choice at the time.
• ☐Practise the 48-hour ramp-up answer until it is concrete: which flows do you test first, which tool do you reach for by default, how do you handle having no environment documentation.
• ☐Practise writing a bug report for a visual defect in plain English — no jargon, clear reproduction steps, screenshot reasoning, and a suggested fix direction without promising a timeline.
• ☐Prepare multi-project prioritisation reasoning: how you decide where to spend limited time when three deadlines converge and one regression has knock-on effects.
• ☐Run both the manual QA mock and the Playwright/Cypress mock to keep both manual and automation skills sharp under interview conditions.

// Is this you?

Day-to-day reality of this role type — to help you self-select before investing in prep.

• Working across two to four client projects simultaneously — each at a different phase: one launching, one in regression, one in UAT, one being scoped.

• Writing bug reports that go directly to client stakeholders, not just into an internal engineering backlog.

• Setting up test environments and basic CI on a new project with minimal guidance, roughly every quarter.

• Balancing creative context (your colleague today might be a designer or UX researcher) with technical rigour (your next call is a CI pipeline debug).