The Apprenticeship Program for Engineers
An engineering apprenticeship program is a structured 90-day track for engineers who have real potential but limited production experience. Unlike internships, apprenticeships end with the person either hired or capable of shipping on their own. Unlike hiring seniors, apprenticeships give you access to underpriced talent that the resume-filtered hiring funnel misses entirely.
Written by Yashveer Singh, founder of Yashveer Labs.
What you actually need to know
- Apprenticeship programs produce hires that the standard resume-filtered funnel completely misses.
- The 90-day structure works: 30 days learning, 30 days contributing, 30 days shipping.
- Mentorship needs dedicated time carved out. It does not happen organically.
- Evaluation at the end should be specific: navigation, shipping, and communication.
- Apprentices should be paid. Unpaid programs exclude the people the program is supposed to reach.
| Program Type | Duration | Outcome | Cost vs Senior Hire |
|---|---|---|---|
| Internship (observation) | 8 to 12 weeks | Maybe a hire, often not | Low cost, low output |
| Apprenticeship (structured) | 90 days | Real hire or strong external candidate | Medium cost, high output |
| Bootcamp partnership | Ongoing | Pipeline of entry-level hires | Variable |
The core argument
The hiring funnel for engineers is broken in a specific way. It filters for credentials and formats resumes into ranked lists. It systematically undervalues people who did not follow the conventional path: degree, internship, junior role, mid role, senior role. The people who taught themselves, built things on the side, worked in adjacent fields, or came from non-traditional backgrounds often never get past the screening call because their experience does not fit the expected progression.
An apprenticeship program is a structured bet on those people. It says: we will take 90 days to find out if this person can do the work, and we will give them the scaffolding to do it well. If they can ship real code by the end, we hire them. If they cannot, they leave with more skills and a production reference. The risk is low. The upside is access to talent that every other company filtered out.
The program works best at companies where senior engineers have the interest and the time to mentor. That is the constraint. A good senior can carry one apprentice at a time without meaningfully reducing their own output. A bad mentorship setup, where the apprentice is expected to figure things out without structured guidance, produces nothing.
How to structure the 90 days
Month one: orientation and codebase navigation. The goal of the first 30 days is not shipping. It is understanding. The apprentice reads documentation, runs the application locally, traces flows from the UI through the API to the database, and asks every question they have in writing. A weekly written summary of what they learned that week builds the habit of written communication.
Month two: contributing to real features. The apprentice picks up tickets from the backlog with mentor support. Nothing that is on the critical path of a major launch. Everything that a senior would review before it ships. The feedback loop is tight. The mentor reviews code daily, not weekly.
Month three: shipping something independently. One feature or improvement, scoped by the apprentice with the mentor's guidance. The apprentice owns it from spec to production. The mentor is available but does not drive. By the end of this month, you know whether they can execute with confidence.
Common mistakes teams make
- Assigning the apprentice to a mentor who is already overloaded. Mentorship without time is abandonment.
- Putting apprentices on critical path work in month one. They need low-stakes space to make mistakes.
- Not evaluating at fixed milestones. Without checkpoints at 30 and 60 days, the final decision is harder and more emotional.
- Running the program without a written curriculum. Apprentices who do not know what they are expected to learn by week eight have no way to self-assess.
- Letting the program extend past 90 days without a decision. Extensions signal indecision and are unfair to the apprentice.
Where to start: a 3-step apprenticeship setup plan
Step 1: Find the mentor first. Before you post the program, identify which senior engineer has both the capacity and the desire to mentor. Have a conversation with them about what it will take. Block 20 percent of their calendar for the 90 days.
Step 2: Write the 90-day curriculum. What will the apprentice learn each month? What will they ship? What are the evaluation criteria at day 30, day 60, and day 90? Write this down before you talk to candidates. It becomes the program spec.
Step 3: Source through non-traditional channels. Post on communities for self-taught engineers, coding bootcamp alumni networks, and developer communities focused on underrepresented groups. The goal is to reach people the standard hiring funnel would filter out.
Related reading
Frequently asked
Why you should skip the agency and hire me instead
Agencies markup engineering work by three to five times. Yashveer Singh, founder of Yashveer Labs. I do the work directly. No project manager, no account manager, no overhead. The engineer you talk to is the engineer who writes the code. That changes the math on price, speed, and quality at the same time. If that sounds like the shape of project you have, we should talk.
Posts that line up with this one.
- Startup Technical Strategy
The CTO vs VP Engineering Distinction
The CTO and VP of Engineering are not the same role. Here is the difference and why getting it wrong costs founders team clarity and technical direction.
- Startup Technical Strategy
The Engineering Open Roles Page That Attracts Senior Talent
What senior engineers look for on a company's roles page and how to write job descriptions that signal the right things to experienced candidates.
- Startup Technical Strategy
The Engineering Internship Program at Startup Scale
How early-stage startups can run engineering internships that produce real value for both the company and the intern without derailing the team.
- Startup Technical Strategy
The Engineering Hiring Bar: How to Set and Hold It
How to define what good looks like for your engineering team, evaluate candidates against that standard, and avoid the most common failure modes.