Jo Harper · Round 2, live coding
Summary
every claim at its momentGrades
every quote from the recordIntegrity
context, never proofA person confirmed every grade shown.
One hire at Northwind Labs, from the job description to the decision. Every screen is Panelio as it runs.
Senior backend engineer, Payments
Northwind Labs · Remote, United States · Job PAY-214
You will own the reliability of the payout path: idempotent retries, ledger correctness, and on-call for the services that move money.
What you will do
What you bring
| # | Candidate | Fit | Strengths | Gaps | Upvotes | Next step |
|---|---|---|---|---|---|---|
| 1 | Candidate 03Jo Harperjo.harper@example.com | Strong | Payment reliability; Idempotent retries; Python and TypeScript | Mentoring | 0 | InviteHoldDecline |
| 2 | Candidate 01Tom Bennetttom.bennett@example.com | Strong | Ledger correctness; Postgres; On-call | AI-assisted development | 1 | InviteHoldDecline |
| 3 | Candidate 05Mary Ellismary.ellis@example.com | Likely | Payment reliability; Python | Ledger correctness | 0 | InviteHoldDecline |
| 4 | Candidate 02Becky Shawbecky.shaw@example.com | Likely | Postgres; TypeScript | Payment reliability; On-call | 0 | InviteHoldDecline |
| 5 | Candidate 06Aiko Tanakaaiko.tanaka@example.com | Partial | Python | Payment reliability; Ledger correctness | 0 | InviteHoldDecline |
| 6 | Candidate 04Sid Palmersid.palmer@example.com | Weak | None | Payment reliability; Idempotent retries; Postgres | 0 | InviteHoldDecline |
| Candidate | Correctness | Complexity reasoning | Communication | Testing | Rounds | Decision |
|---|---|---|---|---|---|---|
| Jo Harper | 4.0S.M. 4 · N.W. 4 | 3.0 | 4.5S.M. 4 · N.W. 5 · they differ | 3.0S.M. 2 · N.W. 4 · discuss | 4 of 4 | AdvanceN. Walker · Wed 12:20Send the candidate's note |
| Tom Bennett | 3.5 | 3.0 | 4.0 | 3.5 | 2 of 4 | No decision yet |
| Mary Ellis | 3.0 | n/a | 3.5 | 3.0 | 1 of 4 | HoldN. Walker · Tue 15:12 |
| Becky Shaw | 2.5 | 3.0 | 3.0 | n/a | 1 of 4 | No decision yet |
Senior backend engineer, Payments at Northwind Labs
A person confirmed every grade shown.
Northwind Labs asks whether you agree to a voice check during your interviews for the Senior backend engineer, Payments role. If you agree, Panelio, the interview tool Northwind Labs uses, makes a voiceprint from your voice while you speak in each round. A voiceprint is a set of numbers that describes how your voice sounds. It is not a recording: no audio of you is ever recorded or kept. A voiceprint is biometric information under the laws of some states, including Illinois, Texas and Washington.
What it is for. The voiceprint is used only to confirm that the same person joins every round of these interviews, and that no one else answers for you. It is not used to grade your answers, and it is never used to infer your emotions, your personality or anything else about you.
What is kept. The voiceprint from your first round with the voice check is kept, encrypted. In each later round a new voiceprint is made from that round, compared with it, and discarded. The people who interview you see only whether the voices match, never the voiceprint.
Who has it. Northwind Labs, and Panelio as Northwind Labs's service provider. Nobody else. It is never sold, leased, traded or shared, and it is never used for any other purpose, role or employer.
How long it is kept. It is deleted when Northwind Labs records its hiring decision for this role, and never later than one year after your last interview round for this role, whichever comes first. Panelio's retention schedule is public at panelio.ai/privacy.
If you say no. Nothing else changes, and saying no counts against nothing. You can change your answer on your invitation page before any round, and taking back your agreement deletes any voiceprint already made.
By ticking the box and choosing I agree, you sign this notice as your written release under the Illinois Biometric Information Privacy Act, and you give your explicit consent to this use of your voice.
Your interviewer asks the questions in the meeting.
Allow at most N requests per client in any rolling window of W seconds. Return whether a request is allowed. Explain the memory bound. Talk through your approach before you type if you like.
| Candidate | Correctness | Complexity reasoning | Communication | Testing | Rounds | Decision |
|---|---|---|---|---|---|---|
| Jo Harper | 4.0S.M. 4 · N.W. 4 | 3.0 | 4.5S.M. 4 · N.W. 5 · they differ | 3.0S.M. 2 · N.W. 4 · discuss | 4 of 4 | No decision yetRecord a decisionRecord with my name |
Jo Harper, Testing3.0, the average of 2 confirmed gradesClose
Round 2, live coding · Sara Mitchell · Mon 10:00
Nothing was suggested for this line.
24:10 "I think the edge bucket gets counted twice on the boundary."
2 runs. The last passed 6 of 7 tests.
Confirmed 2 of 5 by Sara Mitchell, Mon 11:04.
Nick Walker confirmed 4 of 5: named the edge to test before the fix.
The interviewers in this round differ on this line.
Open the replayOpen the pack
| ||||||
| Tom Bennett | 3.5 | 3.0 | 4.0 | 3.5 | 2 of 4 | No decision yet |
| Mary Ellis | 3.0 | n/a | 3.5 | 3.0 | 1 of 4 | HoldN. Walker · Tue 15:12 |