Describe a job you would like to do in the future

How to approach this cue card

This card is forward-looking, so the examiner is testing your ability to talk hypothetically and give reasons, not just describe facts about the present. The trap is answering with a one-line ambition (“I want to be a doctor because it’s a good job”) and then running out of things to say. A stronger approach picks a job you can describe in some real detail — what a typical day involves, what training or qualifications it needs, and a specific, personal reason it appeals to you, beyond salary or status alone.

You don’t need to have a fully formed career plan. A job you’re curious about, even one you’re still deciding on, gives you plenty to talk about as long as you can explain what draws you to it and what steps would realistically be involved in getting there, which directly answers the explain bullet.

Spend about 20 seconds naming the job, 30–40 seconds on the skills or qualities it requires, and the rest split between why it appeals to you and what you’d actually need to do to get it — that last part naturally invites future and conditional language, which is useful for showing grammatical range.

Vocabulary that lifts this answer

A one-minute plan

• job: something in product design, tech
• skills: creativity, attention to detail, some coding
• appeal: making things people actually use daily
• to get there: short course, build a portfolio, apply
• closing: current job is a stepping stone toward it

Sample answer

This is presented as one example of how to organise an answer here, not a script — your own career interests should shape the real content.

A job I’d genuinely like to do at some point in the future is something in product design, ideally for a technology company, designing the kind of apps or tools that ordinary people use every day. It’s not a field I’m formally trained in yet, but it’s something I’ve become increasingly interested in over the last couple of years, partly through a bit of self-teaching in my spare time. As far as I understand it, the role requires a mix of creativity and quite careful attention to detail, along with a basic understanding of how the technical side works, even if you’re not writing the code yourself.

What appeals to me most about it is the idea of making something that genuinely improves how people go about small parts of their day, rather than producing something abstract that nobody actually uses. My current job has some transferable skills — I already do a fair amount of problem-solving and working with feedback from colleagues — but to actually get into product design properly, I’d realistically need to do a short course to build up the technical basics and then put together a portfolio of practice projects, since that seems to matter more to employers in this field than formal qualifications alone. It would mean a fair amount of extra work outside my current job for a while, but I see my current role as something of a stepping stone rather than a final destination.

Common mistakes on this card

• Naming the job but giving no real reason beyond “it pays well” or “it’s interesting.”
• Ignoring the “skills it requires” bullet and jumping straight to personal appeal.
• Speaking entirely in the present tense about a job you don’t yet have.
• Leaving the explain bullet as a single vague sentence instead of realistic, concrete steps.