How to Get a Job at a FAANG Company Without a CS Degree

The Degree Question in 2026

Let's start with the facts. In 2018, Google officially dropped the four-year degree requirement for many of its positions. Apple, IBM, and others followed. By now, all of the major tech companies have roles where a CS degree isn't listed as a requirement.

But — and this is important — dropping the requirement doesn't mean they stopped caring. It means they're willing to look at other signals. You still need to demonstrate the same level of competence. You just need to do it differently.

I've watched people with English degrees land roles at Amazon and people with bootcamp certificates get into Meta. I've also watched plenty of talented self-taught developers apply to 200 FAANG positions and hear nothing back. The difference isn't talent. It's strategy.

The Self-Taught Path: What Actually Works

Every "how I got into Google without a degree" blog post makes it sound like the person casually learned Python over a weekend, built a side project, and got a recruiter call. That's not how it goes for most people.

The self-taught path that actually works looks more like this:

• 12-18 months of serious, structured learning — Not watching tutorials. Writing code every day. Building things that break and fixing them.
• Deep expertise in one area — Full-stack generalists are a dime a dozen. The people who get noticed are the ones who go deep. Pick a specialization: mobile development, ML engineering, cloud infrastructure, security.
• Public proof of work — GitHub contributions, blog posts, open source work, conference talks. Anything that lets a recruiter or hiring manager verify your skills without relying on a degree.

Someone I know spent 14 months teaching himself iOS development. He didn't just follow tutorials — he built three real apps, published them on the App Store, and wrote detailed blog posts about the technical challenges he faced. When he applied to Apple, his portfolio spoke louder than any degree could have.

The Bootcamp Reality Check

Bootcamps can work. But most bootcamp graduates don't end up at FAANG companies — at least not right away. Here's why.

A typical bootcamp is 12-16 weeks. In that time, you learn enough to build basic web applications. That's genuinely useful, and it can get you a junior developer job at a startup or mid-size company. But FAANG companies are looking for something more: data structures and algorithms knowledge, system design understanding, and depth in at least one technical area.

The bootcamp-to-FAANG path usually has a gap year in the middle. You graduate the bootcamp, get a job at a smaller company, spend 1-2 years building real experience, and then apply to FAANG. The bootcamp isn't the destination — it's the on-ramp.

Not all bootcamps are equal, either. App Academy, Hack Reactor, and Launch School have notably strong placement records. Some others are essentially expensive tutorial playlists. Do your research before spending $15-20K.

Building a Portfolio That Gets Noticed

Your portfolio is your resume replacement. It needs to do the same job a Stanford CS degree does: convince someone you can solve hard problems.

What doesn't work:

• Todo apps, weather apps, calculator apps — anything from a tutorial
• Projects with no README or documentation
• A GitHub full of forked repos you didn't actually contribute to

What works:

• Projects that solve real problems — "I built a tool that monitors my apartment building's water pressure because our landlord kept denying there was an issue" beats "I built a social media clone" every time
• Technical depth — Show that you made hard decisions. Why did you choose PostgreSQL over MongoDB? How did you handle rate limiting? What would you change if you rebuilt it?
• Scale or complexity — Projects that handle concurrent users, process real data, or integrate multiple systems signal engineering maturity

Open Source: The Great Equalizer

Contributing to open source is probably the single most effective thing you can do without a degree. It proves you can read other people's code, work with existing systems, collaborate through code reviews, and ship real changes that real users depend on.

Start small. Find a project you actually use — maybe a CLI tool, a library, or a framework. Look at their "good first issue" labels. Fix a bug. Improve documentation. Then gradually take on bigger contributions.

A former teacher I know contributed to the React Native codebase for eight months. She fixed accessibility bugs that nobody else wanted to touch. When she applied to Meta, she literally pointed to her merged PRs in their own codebase. She got the job.

Networking Without Being Gross About It

I hate the word "networking." It conjures images of forced small talk at meetups. But building genuine connections in the industry is massively important when you don't have a traditional background.

Here's what works without making you feel slimy:

1. Contribute to communities — Answer questions on Stack Overflow, participate in Discord servers for frameworks you use, help people in GitHub issues
2. Write about what you're learning — Technical blog posts attract people with shared interests. Some of the best connections happen when someone comments on your post
3. Go to local meetups — Not to hand out business cards. To learn something and meet people who care about the same technology you do
4. Get referrals — At FAANG companies, referred candidates get interviews at dramatically higher rates. One genuine connection inside the company is worth 50 cold applications

Roles Beyond Software Engineering

Here's what most "get into FAANG" guides miss: software engineering isn't the only path. There are roles at these companies that value different backgrounds and don't require you to invert binary trees.

Technical Program Manager (TPM) — Coordinates complex technical projects across teams. Values organizational skills, communication, and enough technical depth to understand what engineers are building. Former project managers, military officers, and operations people often thrive here.

Product Manager (PM) — Defines what gets built and why. Values business sense, user empathy, and analytical thinking. MBA backgrounds are common, but so are people from consulting, design, and journalism.

Solutions Architect / Solutions Engineer — Helps enterprise customers implement the company's products. Values deep product knowledge, communication skills, and technical troubleshooting. AWS, Google Cloud, and Azure all hire for these roles extensively.

Data Analyst — Works with data to drive decisions. Requires SQL and statistics but not necessarily a CS degree. People from economics, social sciences, and math backgrounds do well.

UX Research / UX Design — User experience roles that value psychology, design thinking, and research methodology over coding.

Which Companies Care Less About Degrees

Not all FAANG companies are equally open to non-traditional backgrounds:

• Google — Was the first to publicly drop degree requirements. Has multiple pathways for non-traditional candidates including the Google Career Certificates program
• Amazon — Leadership Principles-driven hiring means they weight how you think and what you've accomplished over credentials. Very open to non-traditional paths
• Apple — Varies a lot by team. Some teams are very degree-focused, others care entirely about what you can demonstrate
• Meta — Generally open to bootcamp grads and self-taught developers, especially for frontend and mobile roles
• Netflix — Hires almost exclusively experienced professionals. You'd typically need significant industry experience regardless of degree status

The Honest Timeline

If you're starting from zero — no coding experience, no technical background — here's a realistic timeline:

• Months 1-6: Learn fundamentals. Pick a language, build basic projects, understand how software works
• Months 6-12: Go deep in a specialization. Build your portfolio. Start contributing to open source
• Months 12-18: Get your first tech job. Not at FAANG — at a startup, agency, or mid-size company
• Months 18-36: Build real experience. Ship production code. Learn from senior engineers
• Month 36+: Start applying to FAANG with a track record of real work

Three years isn't what you want to hear. But it's honest. Some people do it faster — especially if they're transitioning from an adjacent field. But setting the expectation at 2-3 years prevents the burnout that comes from thinking it should happen in 6 months.

If you're on this path and want to start practicing for technical interviews and behavioral rounds, Craqly's interview prep tool gives you realistic mock interviews with AI feedback — so when the opportunity does come, you're ready for it.