TL;DR
- The four paths - bootcamp, self-study, certifications, open source - are not equivalent. Which one works depends on your existing background, your budget, and who you want to hire you.
- FAANG hiring without a degree at entry level is outlier territory. Startups, agencies, and remote-first companies hire without degree requirements regularly.
- AI tools accelerate learning but cannot validate whether your work crosses a hiring bar. That requires a human who has been on a hiring committee.
- A hireable portfolio means one to two deployed projects with public GitHub repos - reviewed by at least two working engineers before you apply.
- Timeline reality: 9-18 months from zero to first junior role is realistic. Bootcamp marketing that promises 3-6 months typically omits the post-bootcamp job search and portfolio-validation time.
Is software engineering right for you?
The degree question is the wrong starting point. The right question is which employer tier you're targeting. I see people tie themselves in knots over "can I get hired without a degree?" - but that's not a yes/no question. At startups, agencies, and remote-first companies, hiring without a degree is common and documented. At FAANG and large enterprise, it's a different story at entry level. So before committing to a 9-18 month transition, calibrate your target.
You can read more about breaking into tech as broader context if you're still deciding whether this is the right field at all - but come back here once you've settled on software engineering specifically.
What software engineers actually earn without a degree
Entry-level software engineer roles in the US generally start in the $65,000-$85,000 range. Without a degree, you'll often land slightly below that band on first hire - more typically $60,000-$75,000, depending on the employer tier and geography. The gap converges within two to three years when you have demonstrated output. Senior engineers without degrees who have built track records at startups routinely earn equivalent salaries to degree-holding peers. The income trajectory is the same; the starting point is slightly compressed.
Wrong-fit signals - when not to make this transition now
Some people should hold off on this transition, not because they lack aptitude but because the conditions aren't right. Three situations where committing now will cost you 12 months and leave you in the same spot - or a worse one. None of these are permanent, but they matter enough that I'd tell you to address them before spending a dollar or a month on a learning path.
If you need income within 6-12 weeks and have no existing programming foundation, no credible path produces a hireable software engineer on that timeline. Consider QA, support engineering, or technical writing as an intermediate step - roles where prior domain knowledge matters more than coding depth, and where you can build proximity to engineering teams while you learn.
If your primary target is Google, Meta, or Amazon as your first role without a degree, your timeline is measured in years, not months. FAANG hiring at entry level without a degree is possible but requires exceptional prior work history and a strong referral network. Calibrate your first target to startups and remote-first companies - then use that experience as the credentialled bridge to larger companies.
If you're planning to complete a bootcamp and then begin applying without anyone with hiring-committee experience reviewing your portfolio, you're skipping the step that determines whether the bootcamp was worth it. Spending $15,000 on a bootcamp and not landing a role within 12 months is a real outcome - we see it in the applications of people who went through bootcamps without the external portfolio review step. The bootcamp is not the problem. The absence of hiring-side feedback is.
What software engineering actually does
Junior software engineering is less glamorous than most guides make it sound. The actual day-to-day: you get a ticket, you read through enough of the codebase to understand where the change needs to happen, you write the fix and test it locally, you submit a pull request, you address the review feedback from a senior engineer, and you merge. That cycle - ticket to PR to merge - is the first-year default. You're not architecting systems from scratch. You're building familiarity with a codebase that predates you, shipping small changes reliably, and proving you can work inside an existing engineering culture.
Employers who hire without a degree are concentrated in specific segments. Remote-first SaaS companies, digital agencies, and early-stage startups are where you'll find the most documented examples. Large enterprise and regulated industries - finance, healthcare, government contracting - remain credential-heavy. FAANG sits in its own category: technically possible without a degree, but practically rare at entry level.
The table below shows what the role actually requires versus what each learning path covers. Most guides skip this comparison:
| What the role requires | What a bootcamp teaches | What self-study covers | |
|---|---|---|---|
| Reading existing codebases | Yes - daily | Minimal | Depends on what you build |
| Writing tests | Yes - usually required for PRs | Some programs, not all | Rarely taught proactively |
| Responding to PR review feedback | Yes - core skill | Rarely practiced | Not at all, without a community |
| Stack knowledge for target employers | Varies by employer | Curriculum-fixed | You choose - for better or worse |
| Portfolio projects at the hiring bar | Required substitute for degree | Built during curriculum | Built independently - quality varies widely |
Both paths have gaps relative to what first-year junior work actually requires. What closes those gaps is having someone with hiring-committee experience review your work and tell you specifically what's missing.
How to transition into software engineering without a degree
Three inputs determine which path is right for you: your existing background, your budget, and your available hours per week. The path is a function of those three things, not a free-form choice. After facilitating over a thousand mentor-mentee matches, the consistent pattern in successful transitions is: internal clarity first, skill-gap mapping second, then external steps. Most people skip the first two and wonder why they're stuck six months in.
The bootcamp path
A bootcamp is worth it under specific conditions. If you have limited time, prefer structured learning with external accountability, and can find a program with a publicly documented hiring-partner record, it's a legitimate accelerant. If those conditions don't hold, you're paying for structure you could build elsewhere for less money.
Before committing to a bootcamp, you need answers to three questions. What is the bootcamp's publicly documented hiring-partner record - employer names, placement percentage, and median time-to-hire? Can you speak to a graduate placed in the last 12 months? Does the curriculum stack match your target employer's current job postings? If you can't answer all three, don't commit.
One thing most bootcamp reviews miss: completing a bootcamp doesn't close the portfolio-validation gap. Even after graduating, you still need someone with hiring-committee experience to review your final projects and tell you whether they cross the bar. That step is what determines whether the bootcamp investment converts to a hire. Bootcamp instructors are not the same as people who have made actual hiring decisions.
The self-study path
Self-study works - to a point. The ceiling is almost never skill. It's the moment when you've made real progress but have no one with hiring-side experience to tell you whether that progress crosses the bar. I see this in our applications constantly: six months of learning, a project or two built, and no signal on whether it's enough to get hired. More tutorials won't answer that question.
A growing share of people learning to code are doing it alongside AI tools - and hitting the same wall. The tools accelerate learning. They don't validate your output against what a hiring manager actually wants to see. I know this because we see it in our applications: someone has been learning to code with YouTube tutorials and AI assistants for months, has made real progress, and has reached a point where no tool can tell them whether their work is good enough to hire.
The self-study ceiling checkpoint: you've been learning for six or more months and have at least one deployed project. Has a working engineer - not a bootcamp instructor, not a classmate - reviewed it and told you specifically whether it crosses a hiring bar? If the answer is no, you have hit the ceiling. More tutorials won't move you forward. External technical feedback will. The pass state: at least one working engineer has given you specific, technical feedback on a deployed project and told you where it does or doesn't meet a hiring bar.
You can connect with a coding mentor for exactly this kind of structured review - someone who has hired or been hired in your target stack.
The certifications path
Certifications are supplements, not primary credentials. If you're coming from an IT support or network administration background with some scripting experience, a targeted certification can bridge the signal gap between "can manage systems" and "can write software." For someone starting from zero, a certification without portfolio work behind it doesn't move most hiring managers.
The categories with the strongest hiring signal in no-degree pathways: AWS Certified Developer for cloud-adjacent software engineering roles, and CompTIA A+ for readers moving from IT support into software. Both are most useful when they accompany deployed projects that demonstrate the skill in context, not as standalone credentials.
The open-source contribution path
Open-source is the strongest path for readers who already have some coding foundation and are targeting companies that visibly use open source in their stack. A merged PR to a recognized project is verifiable hiring evidence in a way that a personal project isn't - it's documented, publicly traceable, and shows you can work inside an existing codebase.
The timing caveat: a meaningful first contribution to a recognized project takes weeks to months. That includes the ramp-up time to understand the codebase and build enough standing in the community to get a PR reviewed and merged. If you're starting from zero with a tight timeline, open source is the wrong first choice. If you have three to six months of foundation and want a public work trail, it's a strong move.
Which path is right for you
| Your background | Your budget | Hours per week | Recommended path |
|---|---|---|---|
| No coding background, tight budget | Under $500 | 10-15 hrs | Self-study (free resources) + mentor for portfolio validation at the checkpoint |
| No coding background, flexible budget | $10,000-$15,000 | Limited (under 15 hrs) | Bootcamp - with hiring-partner vetting before you commit |
| IT or support background, some scripting | Under $1,000 | 10 hrs | Certifications (AWS/CompTIA) + portfolio work |
| Some prior coding (1-3 months), wants public work trail | Under $500 | 15+ hrs | Open source + mentor review |
Common roadblocks and how to get past them
The roadblock isn't usually skill. It's the absence of external validation at the right moments. The failure pattern is almost always the same: someone builds for six to twelve months, applies without having had their work reviewed by anyone with hiring-side experience, gets rejected repeatedly, and concludes they're not good enough. In most cases, they're close. The issue is that no one has told them specifically what's missing.
The portfolio validation gap matters more than most guides admit
How do you know if your software engineering portfolio is good enough? You ask someone who has been on a hiring committee - not a bootcamp instructor, not an AI tool. The only reliable signal is someone who has made a real hiring decision telling you directly whether your work crosses the bar or what's missing.
We see this in our applications constantly: someone who has built several projects, knows they need portfolio help, and wants a specific person to tell them what's missing and help them get there. That's the most common reason people come to MentorCruise at the portfolio stage.
The portfolio validation milestone: before you begin active job applications, you need at least two external technical reviews from working engineers. The pass state: you can name two working engineers who have reviewed at least one deployed project and given you specific feedback on whether it crosses the hiring bar. The fail state: you've only received feedback from bootcamp instructors, classmates, or no one.
The degree bias - where it's real and where it isn't
Not having a CS degree hurts your chances at FAANG and large enterprise, at entry level and without exceptional prior work history. At startups, agencies, and remote-first companies, the degree requirement is largely absent and well-documented. There's a compiled list of companies that explicitly hire programmers without degrees - including Shopify, Spotify, Proton, and Webflow (nocsdegree.com).
The practical implication: targeting the right employer tier is itself a solution to the degree-bias roadblock. Your first role doesn't have to be your last. A no-degree engineer who lands at a well-regarded startup, builds two years of documented output, and then applies to a larger company is in a fundamentally different position than a no-degree engineer applying to FAANG with six months of bootcamp experience and no external track record.
When you're ready to start applying to your calibrated employer tier, a technical interview mentor can help you position your portfolio specifically for the hiring bar at those companies.
Immigration and visa considerations
If visa sponsorship is part of your target - you're planning a trans-national move or targeting US-based employers who sponsor H-1B visas - the no-degree path adds specific complexity. H-1B sponsorship typically requires a degree or degree-equivalency documentation. Prior work history and portfolio evidence can demonstrate equivalency in some cases, but this requires employer willingness and documented evidence stronger than a typical no-degree portfolio.
If immigration-aware hiring is part of your scenario, find a mentor with that specific experience before you're deep into a job search. Getting the target-employer calibration wrong when visa sponsorship is in play costs months, not days.
Tools, mentors, and next steps
The tools that matter for a no-degree software engineering path are the ones that serve the actual bottlenecks: learning platforms for the chosen path, GitHub for public portfolio evidence, coding communities for peer feedback, and a mentor for portfolio validation at the right milestones.
For learning, freeCodeCamp and The Odin Project are the two free options I'd point you to for full-stack foundations. If you're frontend-focused, Scrimba's interactive format is better than reading docs cold. And if you want to go deeper before picking a specialization, CS50 from Harvard - also free - gives you the rigorous foundational layer most of the others skip.
For portfolio: GitHub is non-negotiable. Every project needs a public repo with a README that explains what it does, why you built it, and what technical decisions you made. Deployed, live links are stronger than repos alone - if someone can't click to see it running, it's harder to evaluate.
For feedback: local meetups, Discord coding communities, and open-source communities give peer feedback. Peer feedback is not the same as hiring-side feedback. It's a useful layer, not a substitute.
The single highest-leverage thing you can do if you're making this transition is find a mentor who has been on a hiring committee for entry-level engineers - specifically ones without degrees. They know which portfolio items actually cross the bar and which ones look impressive but don't.
Davide Pollicino came to MentorCruise as a mentee struggling to land that first role, worked with a mentor, and landed at Google. He now mentors others through the same path. We accept fewer than 5% of mentor applicants - so when you find someone on the platform, you're not getting a random person with a blog. Async document reviews mean portfolio feedback can happen on your schedule, not just in scheduled calls. If you're ready to stop guessing about whether your work is hireable, there's a 7-day free trial. Find a software engineering mentor
FAQs
Can you get a software engineering job without a degree?
Yes - at startups, agencies, and remote-first companies, which hire without degree requirements regularly. No - as a reliable path to FAANG and large enterprise at entry level. The honest answer is that "can I get hired without a degree?" is the wrong question. The right question is: which employers hire without a degree, and am I targeting them? Calibrate your employer target before treating this as a binary yes or no.
What is the best path to become a software engineer without a degree?
It depends on your background and budget. Bootcamp if you need structure, have the budget, and have vetted the hiring-partner record. Self-study if you have time and strong self-direction, with a plan to seek external validation at the six-month checkpoint. Certifications as supplements to portfolio work, especially if you're bridging from an IT role. Open source if you have some foundation and want publicly verifiable work.
How long does it take to become a software engineer without a degree?
9-18 months from zero to first junior role is realistic, depending on hours per week and prior background. Someone with analytical or technical-adjacent experience will compress that range. Someone starting from no technical foundation should plan for the longer end. Bootcamp marketing that promises 3-6 months typically omits the post-bootcamp job search and portfolio-validation period, which together add three to six months to any realistic timeline.
Is a coding bootcamp worth it without a degree?
Conditional. Worth it if the bootcamp has a publicly documented hiring-partner record with employer names and placement stats, the curriculum matches your target employer stack, and you can speak to a recent graduate placed in the last 12 months. Not worth it if you can't get clear answers to those three questions, or if you're planning to apply immediately after graduation without a mentored portfolio review. The bootcamp gets you to the starting line; an external review gets you through the door.
What should a software engineering portfolio contain without a degree?
Two to three deployed projects with public GitHub repos and READMEs that explain what each project does, what technical decisions you made, and why. At least one project that solves a real problem rather than following a tutorial pattern. You should be able to explain every line under interview conditions. Before you apply, the portfolio needs at least two external reviews from working engineers who have given you specific feedback on whether it crosses the hiring bar.
Do you need a CS degree to work at Google, Amazon, or Meta?
Practically, yes - at entry level without exceptional prior work history. FAANG hiring without a degree requires years of verifiable portfolio work, strong referral signals, and typically evidence of exceptional output - open-source contributions at scale, side projects with real users, or prior startup experience. Plan your first role at a startup or remote-first company, build two years of documented output, and use that as the bridge to larger companies.
