Skip to main content

A sample report. Written by hand to show the shape. A free run has everything but the notes and the paid read.

Start your own

Support Engineer · 5 questions

  1. Not yet
  2. Close
  3. Ready
  4. Strong

You told real stories, but three of the five never said how they ended.

Pace
148
Words a minute. Easy to follow.
Fillers
11
About 2.1 a minute.
Time used
5:12
Of 6:00. 1 answer cut off by the timer.

Fix this one thing

Say how it ended in your first 20 seconds.

In question 2 you stopped at "we handed it off to the platform team." Nobody can ask what happened next, so the reviewer is left guessing.

What a reviewer has to go on

  • Troubleshooting production issuesShown

    “I pulled the logs for the failed webhook and saw the retries were stacking”

  • Working with engineeringShown

    “I wrote up the repro and sat with the on-call until they could see it”

  • Writing to customersMentioned

    “I kept them updated” No example of what you wrote.

  • SQL or log analysisNot shown

    It never came up. If you've done it, question 2 was the place.

Reviewer's notes

  1. Walk me through your background.

    Ready

    Clear arc. Ends on why support engineering.

  2. Tell me about a hard issue you debugged.

    Close

    Good detective work. Stops before the fix shipped. “we handed it off to the platform team”

  3. Tell me about a customer who was upset with you. Cut off by the timer.

    Not yet

    Timer ran out during the setup. “so just for some context, the account had been with us for a while”

  4. Tell me about a time you disagreed with an engineer.

    Close

    Real disagreement. No word on who was right or what changed.

  5. Why this role?

    Ready

    Specific to the product. “I've been the person reading those error messages”

Also in the paid read

What landed

  • You name what you did, not what the team did: "I wrote up the repro and sat with the on-call."
  • You tied the last answer to this job rather than to jobs in general.

Also worth fixing

  • Question 3: spend ten seconds on the setup, not ninety.
  • "Kept them updated" is a claim. Say one thing you actually wrote.

Say it like this

A customer's webhooks were failing. I pulled the logs and saw the retries were stacking. I wrote up the repro and sat with the on-call until they could see it. The fix shipped in [how long], and [what changed for the customer].

Question 2, built from your words.

Have an interview booked?

Get the week before it planned to your date, the questions that round will ask, and two full run-throughs out loud with feedback. $12 for this interview.

Get ready for it

No interview yet? Save this report with a free account. Your transcripts and report go with it.

How a person reading from a rubric could note these answers. It isn't any vendor's scoring, and it can't tell you whether you'd pass.

On the web, your phone, and in Chrome.Android appChrome extension