What should Maya lead with?
Maya has a recruiter call for a customer-operations role. She needs to make the match clear.
The question
Maya and Northline are fictional. The role lists onboarding coordination and recurring issue reduction. Maya wants a role where she can own follow-through across customer and product teams.
- Onboarding
- coordinated account handoffs and trained colleagues on a checklist.
- Escalations
- tracked recurring billing issues and agreed owners with support and engineering.
- Ownership
- engineers made product changes; Maya owned the issue register, handoffs and follow-up.
“Choose your next move and explain it briefly.”
Not saved by this site. Your browser may restore text when you navigate back.
A strong answer, step by step
Open each step in turn. This is one strong answer, not the only one.
Step 1: What comes first?
What would you do here? Open the move you’d make.
Connect her work to this role
The strong move. A relevant summary gives the recruiter a reason to ask for detail.
Recite every job from the start of her career
Tempting, but it misses something. A full chronology uses the opening without showing why this role fits.
See how a strong candidate says it
“I coordinate customer issues across teams. I’m interested in this role because it combines onboarding with reducing recurring problems.”
Why it works: A relevant summary gives the recruiter a reason to ask for detail.
Step 2: Which proof point fits?
What would you do here? Open the move you’d make.
Name the handoff she owned
The strong move. A specific action is more useful than a broad claim about being collaborative.
Say she transformed the whole customer experience
Tempting, but it misses something. The packet supports a concrete handoff contribution, not ownership of every customer outcome.
See how a strong candidate says it
“I owned the handoff checklist and training; engineers owned the product changes. I can explain how the teams used that handoff.”
Why it works: A specific action is more useful than a broad claim about being collaborative.
Step 3: What should change?
The recruiter says the next six months focus on renewal escalations, rather than new-client onboarding.
What would you do here? Open the move you’d make.
Switch to the escalation example
The strong move. The recruiter has clarified which part of her experience matters now.
Continue the onboarding story because it was rehearsed
Tempting, but it misses something. That ignores the newly stated priority.
See how a strong candidate says it
“I’d lead with the billing escalations: I tracked the recurring issues, agreed owners and kept the follow-up moving.”
Why it works: The recruiter has clarified which part of her experience matters now.
Step 4: What is worth asking next?
The recruiter can arrange a hiring-manager call but cannot confirm who has final authority over escalation fixes.
What would you do here? Open the move you’d make.
Confirm the next stage and the open question
The strong move. The next stage can resolve a concrete responsibility question.
Treat the manager invitation as confirmation that she has the job
Tempting, but it misses something. An invitation advances the process; it does not settle hiring or role authority.
See how a strong candidate says it
“Please arrange the manager conversation. I’d like to ask how escalation authority is split between customer operations and engineering.”
Why it works: The next stage can resolve a concrete responsibility question.
The answer, in short
- Decision
- Continue to the manager conversation.
- Because
- Maya has relevant escalation work and a clear question about the role.
- What would change it
- A different responsibility split could change the match.
Common traps
- A polished story can still miss the role’s current priority.
- Team results do not make every action your own.
Check your answer
- I led with relevant work.
- I named my own contribution.
- I used the new role priority.
- I left with a clear next question.
Last reviewed Nov 10, 2026