A practice prompt we wrote. No company or candidate report names it, so it carries no company tag.
How to answer
When this question opens a recruiter screen, your answer sets what the rest of the call is about. One candidate reported, in June 2026, that the recruiter screen for an Anthropic Applied AI Architect role was an easy conversation about experience and motivation. Source 1Applied AI Architect AnthropicPublisherBlind (teamblind.com)Source typecandidate report on Blind Those are the two things this minute covers: what you have done, and why you want this. Write this answer as an argument, not a summary: every sentence should move the listener toward “and that’s why this role.”
The shape, in order.
- Now, in one sentence. Your current role, named in terms a stranger understands, with one concrete system: “I’m a senior backend engineer at a claims software company; I own the service that takes in new insurance claims.”
- Two beats of evidence. Pick the two moments that point at forward deployed work: a time you worked directly with a user or customer, and a time you built something under a real constraint. Give each a named system and a result. Leave out everything else.
- The bridge. The reason you want this work, grounded in something that happened: “The part I kept volunteering for was the on-site debugging.” Build it from an event, not an adjective.
- Land on the role. One sentence connecting your bridge to something specific in this posting. Stop there, and let them pick the thread.
If you come from another field, the bridge is your strongest sentence, not a gap to explain. Palantir’s Chief Architect said on a16z Deep Dives, in January 2026, that one archetype that stands out is someone from another field, such as a former physicist or electrical engineer, who has a reason for wanting this work. Source 2How Palantir Scaled: Why the Best Software Is Built Backwards (YouTube auto-generated English captions)Publishera16z Deep Dives, YouTubeSource typerecorded talk or interview The reason is the part to copy. A former physicist might say: “In the lab I was the one who kept going to the instrument to find out why the data looked wrong. That’s the job I want.” Then the two beats of evidence come from the lab, told for a stranger.
How to rehearse it. Write it out, read it aloud against a timer, and cut until it fits inside a minute with a breath to spare. Then practice it from bullet points, so it sounds said, not recited.
Reuse it at the onsite. If an onsite interviewer opens with a version of this, keep the first sentence and the bridge fixed, and swap the evidence for the person in front of you: the customer story for the hiring manager, the ugliest technical constraint for an engineer. End on the project you want them to dig into, not on “why this role”.
The trap is the chronological read-out. It spends the minute on your first job, and the reason for this role, the part the recruiter asked for, never arrives.
Follow-ups
What the interviewer may ask next, once your first answer is on the table.
- Why leave now?
- You said you want to be closer to customers. What part of that do you expect to dislike?
- Which of those projects would you want to go deeper on in the next round?
Where answers go wrong
- Reading the résumé in date order from your first job, so the reason for this role arrives after the listener has stopped listening, or never arrives.
- Replacing evidence with adjectives (“passionate about customers”, “fast learner”). The recruiter can’t write any of it down as evidence for the hiring manager.
Answer this in two minutes
Write the answer you would say out loud. The clock starts with your first word.
Compare with the model answer
Illustrative answer about a fictional project
Written in the first person to show the structure. Tell yours from your own work.
“I’m a senior backend engineer at a claims software company; I own the service that takes in new insurance claims.
“Two things explain why I’m here. At launch, our biggest customer’s adjusters were still retyping half of every claim. I sat in their call center for two days, found that callers give details in a different order than our form, and rebuilt the form that week. The retyping stopped, and entry time fell from eleven minutes to six.
“After that I took every integration nobody else wanted. The last was an insurer’s nightly drop of fixed-width files over SFTP; it was live in nine days and is now our team’s pattern.
“I do my best work with the customer’s problem in front of me. Your posting asks for someone who owns deployments end to end with the customer’s team. That’s the part of my job I’ve been volunteering for, and it’s why this role.”
What each part is doing. The first sentence gives a role and a system a stranger can picture, so the recruiter knows what to ask about next. The two stories are chosen for the role, not for impressiveness: one shows the speaker in front of a customer, the other shows speed on an ugly integration, and each ends in a result. The bridge, “my best work with the customer’s problem in front of me”, comes from the stories rather than from a list of adjectives, and the close points at a specific phrase in the posting.
What was left out. The degree, the first job, the language list and the team size. Each is true and none moves the argument. If the recruiter wants them, they’ll ask, and the answer has left them an easy question: which of those two stories to go deeper on.
Timing. The spoken part is about 150 words, which read aloud at a steady pace runs about a minute. If yours runs long, cut from the stories, never from the close.
The follow-ups that trip people. Two of them turn a good minute into a worry, so have the words ready.
- “Why leave now?” Give a pull, not a push: “Nothing’s wrong where I am. The customer work I’ve been volunteering for is a side job there, and it’s the whole job here.”
- “What part will you dislike?” Name a real cost and how you handle it: “Switching context between customers, and the travel weeks. I’ve done both in bursts, and I plan for them rather than hope they don’t happen.”