Varden Pay interview brief and feedback record, week of Sep 28
Varden Pay interview brief and feedback record, week of Sep 28
Owner: Rafael Delaney. Updated Oct 1, 2026.
The week at a glance
What each Varden Pay panel received a day ahead of its interview, the five criteria every panel scores against, and the feedback recorded so far for the three interviews booked for the week of September 28, 2026. Prepared by Rafael Delaney, senior recruiter at Copperline Talent, for the Varden Pay interview panels and for Anders Sundqvist, head of platform engineering. Status on Thursday, October 1. No next step is taken on a candidate until scored feedback is recorded.
Candidate names and contact details stay in the submission record. This page identifies each interview by role and shows the summary the panel was given.
Five criteria, agreed before the first interview
Every panel scores every candidate on the same five criteria, whatever the role. A score of 1 means no evidence, 3 means the candidate meets the bar for the role, and 5 means strong evidence with examples. Each score carries one line of evidence. A chat message such as "strong maybe" is not feedback, because it cannot be compared across interviews.
| # | Criterion | What the panel looks for |
|---|---|---|
| 1 | Technical depth | Working knowledge of the core stack for the role, with one concrete example of work the candidate owned |
| 2 | System design and reliability | Designs that fail safely: retries, timeouts, backfills and recovery |
| 3 | Payments judgment | Care with money movement: idempotency, reconciliation and an audit trail |
| 4 | Collaboration | Explains trade-offs plainly, takes feedback and works across two offices |
| 5 | Ownership and on-call | Has run production, carried a pager and writes down what was learned |
One tab per interview
Tue Sep 29, backend engineer
Role and panel. Backend engineer, payments. Three Varden backend engineers; the panel lead is a senior backend engineer.
Candidate summary. Eight years building payment APIs in Go and Java, the last three on card settlement.
Focus in the brief. Retry and idempotency design, how the candidate found a reconciliation break, and a recent on-call incident.
-
- Technical depth: 4 of 5
-
- System design and reliability: 4 of 5
-
- Payments judgment: 3 of 5
-
- Collaboration: 5 of 5
-
- Ownership and on-call: 4 of 5
Panel recommendation. Advance to a second round. The panel wants one reconciliation scenario in round two, because payments judgment met the bar but did not stand out. Average of the five scores: 4.0.
Recruiter's reading, Rafael Delaney. Matches the panel's notes. The second round goes to the Thursday hiring sync on Oct 8 for Anders Sundqvist's decision.
Wed Sep 30, backend engineer
Role and panel. Backend engineer, payments. Three Varden backend engineers; the panel lead is a senior backend engineer.
Candidate summary. Six years on ledger and billing services in Java, with two years running a small team's on-call rota.
Focus in the brief. Schema changes on a live ledger, a time the candidate disagreed with a design, and how production incidents were written up.
-
- Technical depth: 3 of 5
-
- System design and reliability: 4 of 5
-
- Payments judgment: 4 of 5
-
- Collaboration: 4 of 5
-
- Ownership and on-call: 3 of 5
Panel recommendation. Advance with one focused question on production ownership. Technical depth and ownership each scored 3. Average of the five scores: 3.6.
Recruiter's reading, Rafael Delaney. A solid candidate with one gap to test. Put the ownership question to the candidate before the Oct 8 sync so the decision does not wait on it.
Mon Sep 28, data platform lead
Role and panel. Data platform lead. Panel led by Anders Sundqvist, head of platform engineering.
Candidate summary. Eleven years in data engineering, the last four leading a platform team that owned pipelines and storage choices.
Focus in the brief. Pipeline reliability, how the candidate sets team priorities, and data access controls in a regulated payments setting.
What was recorded. One chat message from the panel saying "strong maybe". No score on any of the five criteria and no line of evidence.
What this means. None of the five ratings can be shown, and the interview cannot be compared with the two backend interviews. The candidate also has another offer to answer.
Data platform lead: scored feedback is missing
Four days after the interview on Monday, September 28 (counting Monday to Thursday), the panel has sent only a chat message and no scores. Rafael Delaney has asked the panel lead for a score on each of the five agreed criteria, with one line of evidence each, before any next step. Owner: Anders Sundqvist as panel lead, target Friday, October 2. Consequence: the candidate must answer another offer on Tuesday, October 6. Without scores, Copperline cannot tell the candidate whether to wait, and Varden cannot weigh this interview against the other two.
I sent a chat message that said strong maybe. That is not a record. I will enter scores against the five criteria by Friday so Rafael can tell the candidate where we stand.
Before any next step
How quickly Varden answers, by role
Interview feedback is one gap. The other is the answer to a submission. The chart shows the median business days Varden took to answer, by role, from July to September, against an agreed window of two. Senior site reliability engineer is the longest at 7, and QA automation engineer is the only role at the window with 2. Data platform lead sits at 3 for the submission answer, so the delay after this interview is a separate gap, not a habit of that panel.
Rule for the next three interviews: the brief goes out one business day ahead, and the scores are due within 24 hours of the interview.
Who is on this record
Briefs prepared by and checked by
Demo client portal. Copperline Talent, Varden Pay, the people and every figure are fictional sample data. Built on FuseBase.