Hiring managers don't reject career changers for lacking experience. They reject silence — when you can't explain your thinking under pressure, you look unready no matter what your resume says.

I taught high school math for nine years in the Seattle area, which meant I spent nearly a decade explaining reasoning out loud to teenagers who'd immediately tell me if an explanation didn't make sense. I assumed that skill would transfer directly when I enrolled in a coding bootcamp at 32. It didn't, not in the way I expected. I finished the bootcamp with a portfolio I was genuinely proud of — three projects, one using a public transit API that I still think was a clever idea — and heard almost nothing back for four months. Dozens of applications, a handful of online assessments, silence after nearly all of them. The one technical screen I did get, I froze completely. Not because I didn't know how to solve the problem, but because I'd never once practiced narrating my thinking out loud to a stranger while they watched me type and waited in silence. A former classmate from the bootcamp suggested we start mock-interviewing each other twice a week, cold, using real problems from actual interview loops we'd heard about from others. It was uncomfortable for about three sessions. By the fourth, I could talk through a problem without the fifteen-second silences that had killed my one real interview. I had three offers within six weeks of starting that routine, and I'm now a senior engineer at a logistics startup here in Seattle.

Bootcamps across the country — the twelve-week intensives in Seattle, Austin, and dozens of other cities — are generally good at teaching people to write working code. Almost none of them spend meaningful time on the specific, learnable skill of performing that code live for a stranger who's evaluating you in real time. That's a genuinely different skill from solving the same problem alone at 11 p.m. with a browser tab open for reference and no clock running. Career changers in particular get hurt by this gap, because they're already fighting the assumption that they're less technical than a traditional CS grad, and going quiet under pressure in an interview confirms exactly the bias they're trying to overcome in the first place. It's rarely a knowledge gap. It's an unpracticed-performance gap, and unlike years of missing experience, it's genuinely fixable in a few weeks of deliberate, uncomfortable practice.

What we cover inside:

In every mock interview, you talk through your understanding of the problem out loud before writing a single line of code, every single time, no exceptions. This one habit eliminates most of the dead-air moments that quietly sink real interviews, because the interviewer can follow your reasoning instead of watching you type in silence and guessing whether you're stuck or just thinking. Members who struggle with this at first almost always improve within two or three sessions once they get used to narrating instead of just solving.

Mock interviews happen live, on video, with an actual stranger watching you type in real time — not alone at your kitchen table, and not with unlimited time to second-guess every line. Comfort with that specific discomfort is the actual skill being trained here, and it only builds through repetition under conditions that feel uncomfortably close to the real thing. We rotate partners regularly so you're not just getting comfortable with one person's style.

A resume that erases nine years of teaching, or a decade in retail management, or a stint in the military, throws away real signal a hiring manager is actually looking for. We work on language that reframes prior experience as direct evidence of exactly what hiring managers say they can't find enough of — communication, ownership, working under pressure without falling apart. Members workshop these rewrites together line by line, not just once at the start.

A referral from someone already inside the company changes the odds of a callback dramatically compared to an application dropped into a portal alongside a thousand others. We treat the members' job leads board and referral network as a core part of the job search strategy itself, not a bonus feature tacked onto the end of it. Members who've recently landed offers regularly post openings at their own companies first.

Wednesdays are mock interview night — paired technical interviews with feedback on both your code and, more importantly, your communication while you write it, run live every single week without exception. Sundays are resume and portfolio review, where members who've landed offers recently help newer members translate their old career into language a hiring manager will actually read past the first line instead of skimming past it. Beyond the two weekly calls, the group includes short refreshers on the CS fundamentals that come up most often in interviews — the handful of data structures and complexity concepts that get asked about repeatedly, not the entire computer science curriculum crammed into a weekend — plus word-for-word salary negotiation scripts for when an offer finally comes in, and honest, member-written reviews of specific bootcamps, since so much bad information circulates online about which programs are actually worth the cost.

This is for bootcamp grads, self-taught developers, and anyone switching into tech from a different career, at any stage — still in a bootcamp, just finished, or six months into a discouraging job search with no callbacks. No CS degree is required or expected from anyone here. It's not for people who want to skip practicing out loud and just collect more study materials instead — the mock interviews are the core of what actually works here, and they only work if you show up and talk through problems in front of another person, uncomfortable as that is at first.

✅ Weekly live mock interviews with real feedback
✅ Resume templates that translate non-tech experience into hireable language
✅ A running job leads board shared by members who've already landed offers
✅ Salary negotiation scripts for when your first tech offer comes in

Members have gone from eighty rejected applications with zero interviews to two callbacks in a single week after just a few weeks of mock interview practice — the applications didn't change, the interview performance did. Others have used the referral board to skip the cold-application pile entirely and land a first conversation through a warm introduction instead. The transformation isn't more coding knowledge. It's the ability to show the knowledge you already have, live, under pressure. If you're ready to stop applying into the void, join the group.