Interview Panel

Published:
Atmospheric watercolor detail of two pens and muted monitor reflections

Candidate says "that's a good question" to Nemesis.

great. Validated.

Twenty minutes into systems design. distributed job scheduler. Ten million jobs, leases, at-least-once delivery. Candidate doing well.

Nemesis is shadowing me, but he won't shut up.

Nemesis asks how workers claim jobs. Candidate says leases and explains expiration. Correct.

I have been quiet for almost four minutes. Not frozen out. Giving space. Senior panel behavior.

Candidate starts drawing dispatch path.

"What happens if we lose a region?" I ask.

Nemesis glances over.

Candidate pauses. "Do jobs need to execute in a specific region?"

"You can decide."

Nemesis says "let's let him establish the base case, then we can add failures."

"Yeah, I was just stress testing the shape."

The shape?

Candidate says okay and goes back to partitioning.

I nod like this was productive. small thoughtful nod. Camera sees.

workers poll by scheduled time. Lease prevents double ownership. Candidate knows his stuff.

I ask about duplicate execution.

"Idempotency key on the job."

"Yep."

Had that.

Nemesis asks what happens when jobs fail. Candidate says exponential backoff.

I wait maybe one beat.

"Does it ever stop?"

"It should. Bounded retries and then a dead-letter queue. Otherwise a poison job keeps consuming workers."

Nemesis says "right, exactly" and writes something down.

Exactly what. I asked it.

Near the end Candidate points out our requirement is loose. At-least-once dispatch does not mean at-least-once completion.

"Good distinction," Nemesis says.

"Yeah that's kind of what I was pulling on with the region thing," I say.

Pulling on.

"Makes sense," Candidate says. Nice guy.

Interview ends. Feedback first so nobody anchors.

I read my notes twice.

Strong technically. clear communicator. Needed redirect early but recovered. Caught the completion thing himself. I select Hire.

Strong Hire available directly above it.

hover.

No. Strong Hire should mean something.

Submit.

Ratings unlock.

Nemesis: Strong Hire.

Four sentence writeup. Clear architecture. good under ambiguity. Strong failure reasoning. Would raise the bar.

Debrief starts.

"Strong hire for me," Nemesis says.

"Yeah, same."

My yellow Hire is visible to everyone.

"Same direction," I say. "I put Hire. Upper Hire."

Upper Hire is not a rating.

"I use Strong pretty narrowly, but no concerns. I'd be excited to work with him."

Recruiter says sounds like consensus.

"Fully," I say.

On screen Nemesis is green. I am yellow.

I hover mine.

Hire — positive signal

yes.