Ninety days won't turn you into a senior engineer. What it can realistically do is turn "I'm thinking about switching into tech" into "I have a portfolio, a clear direction, and I'm actively applying" — which is the actual bottleneck for most career-switchers, far more than raw skill.
Days 1–20: Pick a lane and stop researching
The biggest time-waster in this phase is comparing career paths indefinitely — frontend versus backend, data versus product, and so on. Pick one based on rough interest and realistic time investment, commit to it for the full ninety days, and revisit the decision only after you've actually tried it, not before.
- Choose one specific role (not a broad field) — e.g. "junior frontend developer," not "something in tech"
- Find three real job postings for that exact role and read their requirements closely — this becomes your actual curriculum
- Block a consistent daily or near-daily time slot for the next ninety days, even if it's short
Days 21–50: Build, don't just study
This is the phase most self-taught paths get wrong by staying too long in courses. Spend the first third of this window on focused learning tied directly to your chosen role, then shift the majority of your time to building one real project.
A finished, imperfect project beats an unfinished, ambitious one every time a hiring manager looks at your portfolio. Scope down until you can actually finish.
What "real project" means here
- Solves an actual problem, even a small one — not a copy of a tutorial's exact example
- Is deployed somewhere live, not just sitting in a local folder
- Has a short written explanation of what it does and why you built it this way
Days 51–70: Build proof of judgment, not just proof of code
Hiring managers screening career-switchers are often less worried about raw ability and more worried about judgment — can this person make reasonable decisions without hand-holding? Two projects with a short write-up of your decisions ("I chose X over Y because...") demonstrate this far better than five projects with no explanation.
This is also the window to start showing up publicly in a small way — sharing what you're building, asking specific technical questions, engaging with people already in the role you want. This isn't about self-promotion; it's about building the kind of visibility that turns into a referral later.
Days 71–90: Apply while still building
Waiting until you "feel ready" to apply is the single most common reason career-switches stall out. Start applying at day 71, not day 90 — applications, interviews, and feedback loops take time on their own, and running them in parallel with your final project work is far more efficient than doing everything sequentially.
A useful reframe: the goal of these ninety days isn't to become fully qualified. It's to become interview-ready — able to talk clearly and specifically about real work you've done.
What to expect honestly
Most career switches take longer than ninety days from first application to signed offer — that's normal, and it depends heavily on the market and role. What ninety days of focused work reliably produces is a real portfolio and enough momentum to keep going without starting over from scratch every time motivation dips.
Once your 90 days are up
Read our guides on how to land your first developer job in 2026 without 5 years of experience and building a developer portfolio that actually gets you interviews for the exact next steps.
Coming Soon From Altiora
Want a structured way to prepare once you're interview-ready? The Programming Interview Handbook — technical question patterns, a behavioral framework and a negotiation script — is in development.
See it on the Shop page
