Topic 6 — Planning your pivot

Goal: Choose the right role and set a realistic plan and expectations for breaking in.

Lesson 6.1 — Choosing the right role for you

Teodora — Teo to everyone who's met her — quit teaching geography in March and spent her first free Sunday doing something faintly embarrassing: typing "tech jobs no coding" into a search bar at 11pm. Forty browser tabs later she had Data Analyst, UX Designer, Product Manager, Customer Success, and Project Manager all open at once, and a worse problem than when she started. Everything looked plausible. Nothing felt like hers.

The thing she was missing has a name. Choosing your role is the single most important early decision in a pivot, and a good fit comes from matching three things at once — not one, all three.

• Your strengths and interests. What do you reach for without being asked? Love data and finding the pattern? → Data Analyst. Energized by people and relationships? → Sales, Customer Success, or Recruiting. Visual and quick to feel what a confused user feels? → Design. Naturally organized, the one who keeps everyone on track? → Project Management. Strategic and decisive, comfortable making the call? → Product.
• Your transferable background. Your old career already points somewhere. Finance or bookkeeping → Analyst. Teaching → Customer Success (you explain things for a living) or Design (you read confusion fast). Any sales or front-desk job → tech sales. You're not starting from zero; you're starting from over there.
• The market. Some roles open their doors wider to career-changers and hire more steadily than others. Every role this platform teaches was picked because it's a non-coding, realistic entry point — not because it sounded impressive.

Teo's three lined up on Customer Success and, more quietly, Product. Eight years of standing in front of thirty restless teenagers turns out to be relationship work and explaining-hard-things work, which is most of what those roles are.

The right role isn't the one with the best salary screenshot. It's the one where your strengths, your past, and the market overlap.

Lesson 6.2 — You don't need to be certain, you need to be aimed

Teo nearly froze here. What if I pick wrong? She messaged Davor — an ex-accountant from her cohort who'd started six weeks earlier and was already a junior data analyst — and asked how he'd been so sure.

He laughed. He hadn't been. He'd done two of the free intro topics, one in Data Analyst and one in Product, back to back over a weekend, and noticed that the analyst exercises felt like a puzzle he didn't want to put down, while the product ones felt like homework. That was the whole "decision."

Sampling a syllabus is a legitimate way to test fit, and it's cheaper than agonizing. The first topics in each track are free for exactly this. Try one. Notice what your attention does.

But there's a trap on the other side: sampling forever. Six tracks half-open, none finished, is how three months disappear with nothing to show. At some point you commit to one clear target, and committing is itself the productive move — it's what turns scattered effort into compounding effort.

You can always correct course later. Aimed-and-adjusting beats certain-and-frozen every time.

Lesson 6.3 — Setting honest expectations

Here's the lesson nobody puts on the inspirational poster, and the one that'll save you the most pain.

When Teo asked Renske, Brightwell's recruiter, how long this realistically takes, Renske didn't sugar-coat it. A pivot is months, not a weekend. Plan on roughly 3 to 6 months of focused learning to get job-ready in an entry role like Data Analyst, Customer Success, or PM, and a job search that commonly runs 6 to 12 months on top of or overlapping that, in a normal market. Steady beats heroic. The people who make it are rarely the fastest; they're the ones still going in month five.

Two more truths Renske laid out plainly:

• You'll likely start junior. Even with a decade behind you, you'll probably enter at an associate, junior, or entry-level title and climb from there. That's not a demotion — it's a doorway, and tech careers tend to move quickly once you're inside.
• Rejection is a numbers game. You will hear "no," often, and silence even more often. Renske reviews stacks of applications; passing on one is a filter doing its job, not a judgment on a person's worth. The ones who break in are simply the ones who kept applying after the no's.

Realistic expectations aren't pessimism. They're armor. They keep you walking through the hard middle — that stretch where the excitement's worn off and the offer hasn't come yet — which is exactly where most people quit, often just before it would have worked.

Lesson 6.4 — Your background is the asset, not the apology

Bao, a senior PM at Brightwell who'd taken Teo's "can I buy you a coffee and ask dumb questions" message seriously, said the single most useful thing in their whole conversation: "Stop opening with what you're missing."

Teo had been doing it without noticing. Every practice intro started with some version of sorry, I don't have a tech background, but…. Your background is an asset, not a liability — and the way you frame it decides which one the listener hears.

Career-changers bring things a fresh graduate simply can't: maturity, real workplace experience, the calm of having handled hard rooms, and domain knowledge. Bao pointed out that Teo understands schools, teachers, and how students actually use a study planner — from the inside. Brightwell sells to schools. That's not a gap; that's a reason to hire her over a 22-year-old who's never set foot in a staff room.

The story is always "here's what I uniquely bring," never "sorry I'm new." Marisol, Brightwell's founder, was a teacher before she built the company — half the team came in sideways from somewhere else. Sideways is normal here. Sideways is, frequently, the point.

Lesson 6.5 — Run the pivot like a project, with proof

Teo's instinct, trained by years of lesson plans, saved her here: she stopped hoping to get into tech and started planning to. Treat the pivot like a project — a clear goal, a rough timeline, and tracked weekly steps.

Her plan fit on one index card:

• Goal + timeline. "Land an entry-level Customer Success role at an edtech company within 6 months." A named target focuses every decision underneath it.
• Skills. Work the chosen role's syllabus end to end, doing the exercises rather than only reading them.
• Materials & presence. LinkedIn, resume, and a sharp pivot story — the next three topics (7–9).
• The search. Networking and applications, consistent and tracked — Topics 8–10.

Then the part that does the heaviest lifting: portfolio proof. Demonstrable work beats claims, and for a career-changer with no relevant job title yet, proof is often the only thing standing between "screened out" and "let's talk." Build the kind your target role values:

• Data Analyst → a sample analysis or dashboard that ends in a recommendation rather than a bare chart.
• Product → a product teardown or a short case study of a decision.
• Sales → a mock outreach sequence.
• QA → a set of clean, reproducible sample bug reports.
• Design → a redesign of a real, flawed screen, with your reasoning shown.

One project that connects work to a real outcome beats five that just say "I cleaned a dataset." And you don't eat the whole goal at once — you break it into weekly actions: this week, finish 3 topics, rewrite my LinkedIn headline, message 2 people in the field. Small steps compound; a written plan beats vague hope every time.

A clear target, honest expectations, and a steady plan are what turn "I want to get into tech" into a date on the calendar.

Worked example — Teo writes her one-page plan

Six weeks in, Teo sat down and turned the whole vague wish into something she could actually check off.

Target: Customer Success at an edtech company (Brightwell is the dream, but not the only door), entry/associate level, within 6 months. She matched it deliberately — strengths (people, explaining), background (teaching → CS, plus real edtech domain knowledge), and market (CS hires career-changers and isn't coding-gated). All three boxes, not one.

Expectations, written down so panic can't rewrite them: months not weeks; a junior title is the door; "no" and silence are normal and not personal.

Proof: she didn't have a CS title, so she manufactured evidence. She wrote a two-page case study — "How I'd onboard a new school onto a study-planner app in its first 30 days" — using everything she knew from the teacher's side of the desk. It read like someone already doing the job.

Weekly card, week one: finish 3 Customer Success topics · rewrite LinkedIn headline from "Former Teacher" to "Customer Success | Edtech | ex-Educator" · message Davor and one CS person on LinkedIn · draft the case-study outline.

Then the test that separates the people who make it from the people who don't. Month three came. Teo had sent twenty-two applications and heard back from two. Discouraging — the exact texture of the hard middle. But she treated the silence as data, not a verdict: twenty applications, near-zero response, meant the targeting or the resume was off, not that she was unhireable. Renske had told her precisely this. She tightened her resume to foreground the edtech case study, narrowed her applications to edtech specifically, and the response rate climbed. She didn't try harder at the same thing — she read the signal and adjusted, and kept going.

That last move — feedback in, adjust, continue — is the engine of the whole pivot.