How much of the import failure can you own?
Eight customers cannot finish their import. You are the startup’s new generalist, and the engineer is in another meeting.
The question
RelayDesk and the incident are fictional. You may correct customer field mappings with their agreement and verify the import. Only the engineer may change or deploy connector code. A successful import is confirmed by the customer seeing all expected records.
| Customers | |
|---|---|
| Field-mapping issue | 5 |
| Connector-code issue | 3 |
The groups are disjoint. Each customer has one blocked import.
Give each customer an accurate next step today. You can coordinate the full issue even where another person must make the code change.
“Choose your next action and explain the trade-off.”
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 can you start now?
What would you do here? Open the move you’d make.
Start the safe fixes and route the rest
The strong move. Ownership includes action within authority and a clear handoff for the rest.
Wait for the engineer before doing any work.
Tempting, but it misses something. Five customers have a fix within your approved scope.
See how a strong candidate says it
“Contact the five mapping customers, agree the correction and verify each completed import. Send the engineer the evidence for the three connector cases.”
Why it works: Ownership includes action within authority and a clear handoff for the rest.
Step 2: How do you report progress?
What would you do here? Open the move you’d make.
Report verified imports
The strong move. Diagnosis is not a completed outcome; customer verification closes each fix.
Report 100% handled because every ticket has a category.
Tempting, but it misses something. Classifying a problem does not restore the customer’s import.
See how a strong candidate says it
“After the five customers verify success, report 5 of 8 restored, or 62.5%, with three still blocked.”
Why it works: Diagnosis is not a completed outcome; customer verification closes each fix.
Step 3: What changes after the review?
The engineer reviews the logs and reclassifies two of the remaining three cases as field-mapping errors. The last case needs a connector code change.
What would you do here? Open the move you’d make.
Update the diagnosis and verify
The strong move. Revise the diagnosis without losing track of the remaining blocked customer.
Keep all three cases with engineering to avoid changing the original report.
Tempting, but it misses something. That would leave two safe fixes waiting for no reason.
See how a strong candidate says it
“Two connector cases are mapping issues after all. Verify those fixes and report 7 of 8 restored, or 87.5%, once confirmed.”
Why it works: Revise the diagnosis without losing track of the remaining blocked customer.
Step 4: What still needs an owner?
What would you do here? Open the move you’d make.
Close the handoff loop
The strong move. Coordination can stay with you while deployment authority stays with the engineer.
Promise that you will deploy a fix before the engineer confirms it.
Tempting, but it misses something. You cannot approve the code change or invent its completion time.
See how a strong candidate says it
“Agree the last case’s fix owner and next update time with the engineer; tell the customer what is confirmed and what remains uncertain.”
Why it works: Coordination can stay with you while deployment authority stays with the engineer.
The answer, in short
- Decision
- Restore and verify seven imports; keep ownership of the final customer update.
- Because
- One remaining case needs an engineering change outside your authority.
- What would change it
- A verified code fix or a new diagnosis changes the remaining plan.
Common traps
- Assigning a ticket is not closing a customer problem.
- Ownership does not grant production access.
Check your answer
- I acted within the approved scope.
- I measured verified outcomes.
- I revised the diagnosis.
- I named the next owner and customer update.
Last reviewed Nov 10, 2026