What Do You Do for Work? Part 1 Answer (Band 9)

What do you do for work?

The opener of almost every Part 1. Answer in one breath: role, place, one color detail.

Band-9 sample answer (30 seconds)

"I'm a backend developer at a fintech startup here in the city. I mostly build payment systems — the invisible plumbing behind online transactions. I've been there about three years, and I still find the problem-solving genuinely absorbing."

Extended version (if asked to elaborate)

"What I enjoy most is the ownership. In a small team, my code ships to real users within days, so the feedback loop is tight — you see the impact of your work almost immediately. The trade-off is the pace: startup life means shifting priorities and the occasional late night before a release. But I'd take meaningful chaos over comfortable boredom any day."

Delivery tip

Name your role in words a non-specialist grasps instantly ("I build payment systems," not "I work in backend microservices architecture"). Examiners score language, not job prestige — clarity beats jargon.

Vocabulary to steal

fintech startup — financial technology new company
invisible plumbing — hidden infrastructure (vivid metaphor)
feedback loop — cycle of action and response
tight — fast, close (for timelines)
trade-off — exchange of advantages
meaningful chaos — busy but purposeful (memorable contrast)

Part 3 bridge

Work questions lead to Part 3 discussions of job satisfaction, automation, and work-life balance — your Part 1 job description becomes evidence there.

FAQs

How long should a Part 1 answer be?

Two to four sentences, roughly 20 to 30 seconds. Answer the question, add one detail or reason, then stop. Part 1 rewards concise completeness, not monologues.

Should I use my real job?

Yes, real details flow naturally. But a simplified version is fine: describe your role in plain words an examiner instantly understands.

More work questions in the Part 1 bank — next: do you enjoy your job.