01
Apply
Send us your background, a link to your work, and an honest case for why you belong. We read everything — and invite only the candidates who clear a bar most applicants never reach.
Careers
The pipeline
Sixteen enter each cohort; four reach the final phase on a single project. We run 4 cohorts per year — 64 total slots annually — and the overwhelming majority never make it past the first gate.
We built SimuCorps to be small, senior, and impossible to bluff your way into. The pipeline is how we find people who belong: twelve weeks of real work, real competition, and real consequences at every gate. Not everyone who applies gets in. Not everyone who gets in finishes. The ones who do join a team that exceptional operators aspire to be part of.
We do not count hours — we count output. Finish what is due and you are done. That is how we work here, and that is how the pipeline runs.
- Cohort size
- 16
- Per quarter
- Final phase
- 4
- One project, one team
- Duration
- 12 wks
- Three phases
- Cohorts / year
- 4
- Sequential quarters
How it works
The only way in is through
We do not hire from job boards and hope for the best. The pipeline is a quarter-long proving ground — and for the few who make it through, a direct path onto one of the most selective teams in the industry.
02
Enter the cohort
Sixteen per quarter. You ship solo, survive the first cut, prove yourself again, and maybe — if you are exceptional — join the final four on one build. Most will not get that far.
03
Earn the seat
The pipeline ends with a full-time offer to those who proved they can operate at our level. Accept, and you join a team people fight to be part of. That is the whole point.
What you are competing for
A full-time role on a senior-led team that ships real systems for real operations — not slide decks, not benchwarming, not a logo on your LinkedIn. People do not end up at SimuCorps by accident. They get here by out-executing everyone else in the room.
The pipeline
16 people. 3 phases. One seat.
One quarter, three cuts. Sixteen enter each cohort; four reach the final phase on a single project. We run 4 cohorts per year — 64 total slots annually — and the overwhelming majority never make it past the first gate.
Phase 01
Weeks 1–4 · 16 interns
Individual build
Sixteen engineers per cohort. Everyone ships a solo project — scoped, finished, and reviewed against a real bar. No hand-holding. No busywork.
- Ship an individual software project from scratch
- Weekly reviews with senior SimuCorps operators
- Demonstrate craft, judgment, and the ability to finish
Half the cohort is cut. Eight interns and the strongest work advance.
Phase 02
Weeks 5–8 · 8 interns
Narrow the field
Eight remain. Projects consolidate and competition intensifies — you are proving the work can go further, not just that it exists.
- Advance the strongest projects from Phase 1
- Operate under tighter scope and higher scrutiny
- Show you can collaborate without losing individual accountability
Cut again. Four interns advance to the final phase on one project.
Phase 03
Weeks 9–12 · 4 interns
One team. One project.
The final four work as a single unit on the winning build — taking it to a standard we would stand behind publicly.
- Collaborate as a focused team of four
- Ship a final build ready for production scrutiny
- Present what you shipped to SimuCorps leadership
Earn a full-time offer. If what you ship is good enough, we may offer to adopt it with you and give you the tools and the team to take it even further.
Engineering
Build software that ships
The pipeline is engineering-only. Every phase is about writing, shipping, and hardening real software — not pitching it, not documenting it, not talking about it.
Software that ships
Phase 1 — solo
Build a working product or internal tool end to end — scoped, deployed, and demo-ready. We care about architecture, reliability, and whether you can finish.
Phase 2 — narrow
Push the strongest builds further: harden what works, cut what does not, and prove the project deserves a final-phase team.
Phase 3 — team
Ship the winning build as a four-person unit — production-grade, fully deployed, and finished. No demos. No prototypes. Done.
Example projects
- Internal ops dashboard
- Automation pipeline
- Customer-facing web app
Before you apply
Know what you are signing up for
This is not a résumé-padding exercise. It is a cutthroat filter — and joining SimuCorps on the other side is worth every cut along the way.
Extremely selective
Sixteen spots per cohort. Four per year. Most applicants never make it past the first review, and three quarters of each cohort is cut before the final phase. We are not trying to fill seats — we are trying to find the few who belong here.
Unpaid — output is the clock
There is no salary during the program, and we do not track hours. Finish the work and you are done for the day — if everything ships in the first hour, go home. We hire people who deliver, not people who log time.
Merit at every gate
Sixteen becomes eight becomes four. Projects get cut alongside people. Advancing is never automatic, and there is no consolation path to the final phase.
Prove it or go home
No one advances because they tried hard. You ship, you survive the cut, or you leave. The pipeline does not owe you a role, a reference, or a second chance — it owes you a fair shot to show what you can actually do.
A seat on this team is the prize
SimuCorps stays deliberately small: senior-led, mission-focused, and hard to get into. The pipeline exists because we will only hire people we have watched execute under pressure — and a full-time role here is something exceptional operators aspire to.
You compete with the best
Your cohort is your competition. Sixteen high-agency engineers, same clock, zero sympathy — pushing each other to a standard no one reaches alone. The final four are not lucky. They outbuilt everyone else.
Apply
Think you belong here?
Email us with the subject line “The Pipeline”. Include a link to your work and a direct answer to why you will outlast three quarters of your cohort. We respond to candidates who advance — not everyone gets a reply.