Becoming an FDE Without a Computer Science Degree
Updated · Tech checked
FDE hiring weighs demonstrated delivery over degrees. A production portfolio, relevant assessment results where available, and strong discovery skills matter; expect to prove yourself through practical artifacts rather than credentials.
The short answer
No hard barrier: FDE interviews test what you can do in front of the customer and in production, not where you studied. Self-taught and bootcamp engineers do land these roles - the honest price is that your evidence burden is higher: you must show working systems because your resume can't lean on pedigree.
What replaces the degree
- A delivery portfolio (2-3 end-to-end projects with briefs, measurement, runbooks - format in the portfolio guide).
- Assessment results, where available. Forward Engineer publishes a proposed FDE Foundations blueprint, but no certification exam is currently offered.
- Open-source or freelance delivery with real users, however small: a CLI with 200 users teaches more customer truth than a certificate with 20 modules.
- Communication artifacts: write-ups that explain trade-offs to non-engineers.
Realistic timeline
From zero programming: 18-24 months to job-ready (be suspicious of anyone selling 12 weeks). With adjacent experience (IT, support, ops, data analysis): 9-15 months is common - your domain knowledge is a genuine asset in customer-facing work.
Interview reality check
- Nobody will ask you to derive algorithms from a whiteboard theory course; they will ask you to reason about a messy customer system - buildable skill.
- Degree filters, where they exist, concentrate in a few large enterprises; the services, startup, and AI-lab market mostly doesn't filter.
Avoid programs that sell "no degree? no problem" urgency pricing. The path is the same evidence stack as everyone else's - see the roadmap.
Continue: Full roadmap · FDE certifications, honestly