Software Testing
Get through the interviewPremium · free during launch7 min readPublished November 12, 2026

Practical QA interview tasks: how to approach them

'Test this pen.' 'How would you test a login page?' 'Find bugs in this app in 30 minutes.' Practical tasks are where junior candidates win or lose. Here's a repeatable approach, worked examples and what interviewers are really looking for.

On this page

Key takeaways

  • Practical tasks test how you think, not whether you find the "right" list. Interviewers look for questions first, structure, prioritisation and clear communication.
  • Use a repeatable approach: clarify → structure → prioritise → test → report. Say your reasoning out loud.
  • For take-home assignments: follow the instructions exactly, keep it clear and concise, explain your choices, and submit on time.

What interviewers are really checking

They watch forWeak signStrong sign
CuriosityStarts listing tests immediatelyAsks who uses it and what it's for
StructureA random list of ideasGroups: functional, negative, boundaries, usability, performance, security
PrioritisationEverything is equally important"First I'd check X, because it's the biggest risk"
CommunicationSilent, then a long listThinks out loud; summarises
Bug reporting"It's broken"Steps, expected vs actual, impact

The approach: five steps

  1. Clarify. Ask about users, purpose, requirements, platforms and constraints. Two or three good questions are enough; don't interrogate.
  2. Structure. Group your test ideas: functional (happy path), negative, boundaries, usability and accessibility, performance, security, compatibility.
  3. Prioritise. Say what you'd test first and why: the core purpose and the highest risks.
  4. Test (if there's something to test). Explore systematically; take notes as you go.
  5. Report. Summarise what you tested, what you found (with severity), what you didn't have time for, and what you'd do next.

Task 1: "Test this pen"

The classic. It isn't about pens; it's about whether you ask before you test.

Clarify: "Who is it for: an office, children, astronauts? Is it a ballpoint, a gel pen, a premium gift? Are there requirements, like how long it should write or what it costs?"

Then structure your ideas:

  • Functional: does it write? Is the line consistent? Does the click mechanism retract and extend? Does the cap fit?
  • Boundaries and endurance: how many metres of line before the ink runs out? Writing at extreme angles, upside down, in cold or heat?
  • Negative: dropping it, sitting on it, leaving it uncapped for a day, writing on glossy paper.
  • Usability: comfortable grip for long writing? Left-handed users: does the ink smudge?
  • Safety: for children, can the cap be swallowed? Does it have an air hole?
  • Compatibility: different paper types, refills.

Prioritise: "For an office pen, I'd start with: does it write reliably, for how long, and does the mechanism survive thousands of clicks. Safety comes first if it's for children."

Task 2: "How would you test a login page?"

Clarify: "Username or email? Password rules? Is there 'remember me', 'forgot password', social login, two-factor authentication? Lockout after failed attempts? Web, mobile or both?"

Test ideas, structured:

AreaExamples
Happy pathValid credentials log in and land on the right page
NegativeWrong password, unknown user, empty fields, spaces before/after the email
BoundariesMinimum and maximum password length; very long email
SecurityLockout after N failed attempts; the error doesn't reveal whether the user exists; password masked; HTTPS; session ends on logout; the back button after logout doesn't show private pages
Usability and accessibilityClear error messages, keyboard-only use, screen reader labels, show/hide password, paste allowed
Other"Remember me" really remembers and expires; "Forgot password" flow; multiple tabs; different browsers and mobile

Prioritise: "First, valid login and the main error cases, because nobody can use the product without them. Then security checks like lockout and session handling, because the impact is high."

Task 3: "Find as many bugs as you can in 30 minutes"

  1. Spend 2–3 minutes understanding the app: what is it for, what are the main flows?
  2. Test the main flow first (sign up, search, buy) since bugs there matter most.
  3. Then try inputs: empty, very long, special characters, boundaries.
  4. Watch the DevTools Console and Network for errors you can't see on screen. See browser DevTools for testers.
  5. Write as you go: a title and steps for every bug, so you aren't reconstructing them at the end.
  6. Leave 5 minutes to rank your bugs by severity and summarise.

Five well-described, well-prioritised bugs make a better impression than twenty one-line notes.

Task 4: "Write test cases for this feature"

You'll get a short requirement or user story. Show test design techniques:

  • Identify partitions and boundaries (for example, a discount for orders of 100–500 lei: 99.99, 100, 500, 500.01).
  • Use a decision table if there are combinations of rules.
  • Include negative cases.
  • Write down the questions the requirement leaves open. Spotting ambiguity is a skill they're looking for.

Format each case clearly: ID, title, preconditions, steps, expected result. See how to write a good test case.

Task 5: technical mini-tasks

Take-home assignments

  • Read the instructions twice and follow them exactly: format, scope, deadline.
  • Time-box it. If they say "2–3 hours", don't spend two days. Note what you'd add with more time.
  • Explain your choices in a short README or summary: what you tested, why, what you'd do next.
  • Quality over quantity: clean, readable test cases and bug reports beat volume.
  • Submit on time, and be ready to walk through it in the next interview.
Real-world exampleThe candidate who asked first

In a junior QA interview (an illustrative example), the interviewer slid a coffee mug across the table: "Test this."

The first candidate listed 25 ideas in two minutes: drop it, fill it with boiling water, check the handle, microwave it. The second paused and asked: "Who's it for, and where? A café, an office, a children's set? Is it meant to be microwave-safe?"

The interviewer said: "It's a travel mug for commuters." The candidate then focused on leaks when tilted in a bag, keeping drinks hot for the length of a commute, one-handed use, fitting a car cup holder, and lid cleaning. She grouped the ideas and said she'd start with leaks, "because a leak in a bag ruins someone's laptop".

The second candidate got the job. Afterwards, the interviewer said that several candidates had covered more ideas; she was the only one who had found out what the product was for.

Lesson: the question before the test is what interviewers remember.

Do

Ask one or two clarifying questions, think out loud, group your ideas, say what you'd test first and why, and summarise at the end.

Don't

Fire off an unstructured list as fast as possible, or freeze in silence. Interviewers can only assess thinking they can hear.

Check yourself

You're asked to test a search box on an online shop in an interview. You have 5 minutes to talk. What would you say first?

Show answer

Start with one or two clarifying questions (search by name only, or also brand and category? Is there autocomplete?), then give a structure: happy path (exact name, partial name), negative (no results, empty search, special characters, very long text), relevance and sorting, performance with many results, usability on mobile, accessibility, and security (input reflected on the page safely). Then prioritise: "First I'd check that common searches return relevant results, since that's what drives sales."