Topic 10 — Interviewing and landing the offer

Goal: Master the universal interview skills that turn interviews into offers.

Lesson 10.1 — The interview is a staircase, not a single door

Teodora Vrabie has a first call with Brightwell on Thursday and she's been quietly terrifying herself all week. In her head it's one giant exam: she walks in, they decide, she lives or dies on forty-five minutes. That picture is wrong, and the wrong picture is half of why she's scared.

A tech hiring process is a staircase — a sequence of separate, predictable steps, each with its own purpose. Once you can name the steps, the surprise drains out. Here's the sequence almost every company runs, give or take a stair:

1. Recruiter screen — a short call (often 20–30 minutes) on basic fit, interest, logistics, and salary expectations. Renske Aldous, Brightwell's recruiter, runs these. She is checking that Teo is real, motivated, and roughly in budget — not grilling her on skills.
2. Hiring-manager interview — a deeper conversation about your background, your skills, and whether you'd fit the team. This is the person you'd actually report to.
3. Skills / role assessment — the role-specific stair: a case study, a take-home exercise, a portfolio review, or practical questions. (Your role's own syllabus covers exactly what this looks like for you.)
4. Team / final interviews — more people, often more senior, sometimes a panel. They're sanity-checking the earlier signal.
5. Offer — if it all lands, they make you one. That's its own conversation, and Lesson 10.5 is about it.

Renske told Teo something on that first call that reframed everything:

"Every stair runs both ways. We're deciding about you, and you're deciding about us. The candidates who do best treat it like that from the recruiter screen on."

So Teo is allowed — encouraged — to evaluate Brightwell the whole time. What's the team like? Is the work real? Does Marisol's vision hold up? An interview where you forget you have a vote is one where you perform instead of connect.

Lesson 10.2 — Tell it in STAR

The hiring-manager call comes, and the question Teo dreaded arrives: "Tell me about a time you handled a difficult situation." Her instinct is to ramble — to start in the middle, backfill context, trail off without a point. That instinct loses interviews.

The fix is a tiny four-part skeleton called the STAR method: Situation, Task, Action, Result. You set the scene, name your job in it, describe what you did, and land on what happened.

• Situation — two or three sentences. "In my last year teaching, our department's lesson-planning was scattered across a dozen private spreadsheets."
• Task — one sentence on your responsibility. "I volunteered to build us one shared system before the new term."
• Action — the heart of the answer, and most of your airtime. This is where you say I more than we: I mapped what every teacher needed, I built the shared planner, I ran two training sessions when people resisted it.
• Result — always end here, with a number if you possibly can. "By the end of term all eleven of us were using it, and planning time dropped from about three hours a week to under one."

The single most common mistake is spending forever on the Situation and almost no time on the Action. Flip it. The Action is the part the interviewer is actually scoring — it's the only section that reveals what you are like to work with. Aim for roughly 90–120 seconds per answer. Long enough to be a real story, short enough that they don't drift.

You don't improvise these in the room. Before the interview, Teo wrote out five to seven reusable real stories from her actual life: a challenge overcome, a clear success, a conflict with a colleague, a failure she learned from, a time she led or persuaded people. Those few stories, told in STAR, answer the large majority of behavioral questions any company throws — the wording changes, but they keep fishing for the same handful of things.

Lesson 10.3 — Think out loud

Davor Halász, the ex-accountant who's now a junior data analyst one step ahead of Teo, calls her after his final-round assessment, half-laughing. "They gave me a problem I couldn't fully solve. I got the offer anyway."

How? Because in a case or problem-solving question, the interviewer is not grading the final number. They're watching how you reason — and the only way they can see that is if you think out loud.

Davor's move was to narrate everything. "Okay, first I want to understand what 'churn' means here. Let me check the date range. My first guess is the drop is seasonal, so I'd want to compare it to last year — am I allowed to assume we have that data?" He talked through his structure, his assumptions, the path he'd take. He hit a wall, said so plainly, and described how he'd find his way around it.

A clear, reasoned wrong-ish path spoken aloud almost always beats a silent correct guess. Silence is the thing that sinks people, not being stuck.

For Teo this is a relief, not a threat. She doesn't have to be the fastest mind in the room. She has to be legible — structure the problem, voice her thinking, ask clarifying questions, and let the interviewer ride along inside her head. She's been doing exactly that for years explaining geography to teenagers, and it transfers cleanly.

Lesson 10.4 — Show up knowing them, and have questions ready

Two things make a career-changer stand out before they've proven a single technical skill. Both are completely in your control.

The first is doing your homework. Before her Brightwell calls, Teo spent an hour learning the company cold: what the study-planner app does, who it's for, that Marisol Ferreira founded it as an ex-teacher, that they'd just raised a Series A and were pushing into more school districts. So when Renske asked the inevitable "why Brightwell?", Teo didn't go generic — she tied her classroom past to their mission, with specifics. Research like this won't dazzle anyone; it's table stakes. Candidates who clearly researched the company stand out instantly, because so many clearly didn't.

The second is enthusiasm, coachability, and good questions. Near the end, almost every interviewer asks: "Any questions for us?" — and "no, I think you covered everything" is a quiet way to lose. Have three or four real ones ready, about the role, the team, the challenges ahead:

• "What does someone need to do in the first 90 days to be considered a success here?"
• "What's the hardest part of this role that isn't obvious from the job post?"
• "How does the team handle it when someone's still learning the ropes?"

Thoughtful questions signal genuine engagement — and they're how you evaluate them, the two-way street from Lesson 10.1 in action. Bao Trinh, the Brightwell PM mentoring Teo, put it bluntly: "For someone like you, we're hiring for potential and attitude, not the skills you have on day one. Show us you'll grow fast and you're easy to teach." Employers, especially for career-changers, bet on the trajectory.

Lesson 10.5 — Own your pivot, then play the long game

Sooner or later it comes: "So… why are you switching careers?" Teo's first instinct was to apologize — to explain herself, to treat being new as a confession. That instinct is poison.

Own your pivot. Your background is not a hole to apologize for; it's a strength to lead with. Teo learned to answer with her chin up: "Seven years of teaching means I explain hard things simply, stay calm with frustrated people, and find where someone's actually stuck — which is most of what this work is. I'm moving toward tech on purpose." Confident and positive, framed as an asset. Never "I know I don't have the typical background, but…" Davor calls this the pivot story, and he rehearsed his until it sounded like pride instead of an excuse — the version you believe is the version they believe.

Then the offer arrives — and the long game begins.

• Take your time and ask about the whole package. It's completely normal to ask for a day or two to consider. Look past the salary number at the role, the growth, the team, the benefits — the things that decide whether your first year is a launchpad or a dead end.
• Negotiating is normal and expected. Politely asking about pay or terms almost never costs you the offer — the first number usually assumes you'll ask, and a respectful negotiation almost never costs you the offer. The rare exception is aggressive, ultimatum-style demands or negotiating in bad faith, which can sour things (and at a very small startup, occasionally cost the offer) — so stay gracious and keep it a conversation, not a standoff. Research the typical pay range first so the conversation is informed, then ask. For a first tech role especially, weigh fit and growth over squeezing out the last bit of salary. A place where you'll learn fast is worth more than a slightly bigger number somewhere you'll stall.
• Persistence is the final ingredient. Interviewing is a skill that gets better every single time you do it. Rejection is normal — it's the cost of the search, not a verdict on you. Teo treats every interview that doesn't convert as a free rehearsal: she notes what landed, what didn't, and walks into the next one sharper. The people who break into tech are, overwhelmingly, the ones who kept showing up.

Worked example — Teo's run at Brightwell

Watch the whole staircase, one candidate, start to finish.

Recruiter screen. Renske calls — twenty minutes on why tech, why Brightwell, and salary. Teo has researched a rough pay range, so she gives a sensible band instead of freezing, stays warm and specific about the mission, and gets moved forward.

Hiring-manager interview. "Tell me about a time you handled conflict." Teo reaches for a prepared STAR story — the resistant-colleagues one — sets the scene in two sentences, spends most of her airtime on what she did, and lands on a result: eleven of eleven teachers adopted the system. Ninety seconds. Clean.

Skills assessment. A practical exercise with a problem she can't fully crack. Instead of going quiet, she thinks out loud — names her assumptions, structures her approach, flags where she's stuck and how she'd dig out. The reasoning is the deliverable.

Final interviews. A few more people, including Bao. "Why are you switching?" — she owns it: teaching as a strength, the move as deliberate. At "any questions for us?" she has four sharp ones ready about the first 90 days.

Offer. It comes. Teo asks for two days, asks about growth and the team, politely negotiates the salary up a little — and nobody flinches. She weighs fit over the last dollar, sees a real launchpad, and says yes.

One candidate. No tech background. A staircase climbed one prepared step at a time.