A degree used to be the default proof that you knew what you were doing. That has changed. Google, Apple, IBM, and dozens of other major companies have dropped degree requirements for technical roles. But dropping the requirement does not mean they stopped caring about proof. It means they want different proof.
The question is not whether you can get hired without a degree. You can. The question is what you show instead. Not all proof is equal. A link to a live project you built carries far more weight than a paragraph describing what you "know." Here are seven types of proof, ranked by how much trust they actually build with recruiters and hiring managers.
Yes. Many companies, including Google, Apple, and IBM, have dropped degree requirements for technical roles. What matters is proof that you can do the work. A deployed project, open source contributions, or a respected certification carries more weight than a diploma at most companies.
What is the best certification for getting a tech job without a degree?
It depends on your target role. For cloud engineering, AWS Solutions Architect or Google Cloud Professional are strong. For security, CompTIA Security+ is widely recognized. For data, the Google Data Analytics Certificate is a solid entry point. Pick the certification that matches the jobs you are applying for.
How do I show proof of skills on my resume?
Link directly to the proof. A GitHub profile, a live project URL, a certification verification page, or a portfolio site. Do not just list skills as words. Point to something the recruiter can click and verify in 30 seconds.
This is the strongest signal you can send. A project that is live, working, and accessible through a URL tells a hiring manager everything they need to know in about 60 seconds. They click the link, use the thing, and form an opinion based on real output. No guessing. No trust required.
Strong examples: a full-stack web app with authentication and a database, an API that other developers actually use, a data dashboard that pulls live data and updates on a schedule. Weak examples: a to-do app from a tutorial, a clone of a popular app with no original features, or anything that is just a README with screenshots but no working demo.
The difference between strong and weak is originality and scope. A to-do app shows you can follow instructions. A custom app that solves a real problem shows you can think, design, and ship. For more on presenting projects the right way, check out our guide on showing your code.
Best for: software engineers, frontend developers, data engineers, and anyone whose work can be seen in a browser.
2. Open Source Contributions
Contributing to open source projects is proof that you can work with other developers on real codebases. It shows you can read someone else's code, follow contribution guidelines, write clean pull requests, and respond to code review. These are exactly the skills companies test for in interviews.
A strong contribution is a merged PR on a well-known project that fixes a real bug or adds a real feature. A weak contribution is a typo fix in a README or an issue comment saying "I'd like to work on this."
You do not need to contribute to React or Kubernetes. Smaller projects with active maintainers are often better because your PR is more likely to get reviewed and merged. Look for repos with "good first issue" labels. One meaningful merged PR on a project with 500 stars is better than 20 cosmetic fixes.
Best for: backend engineers, systems programmers, and anyone targeting companies that value open source culture.
3. Industry Certifications
Certifications sit in an interesting spot. They are not as strong as deployed projects or open source work because they test knowledge, not applied skill. But they are standardized, verifiable, and widely recognized. A recruiter who sees "AWS Solutions Architect, Associate" knows exactly what that means.
The strongest certifications are the ones that match real job requirements. AWS, Google Cloud Professional, and Azure certifications are valued for cloud roles. CompTIA Security+ is a baseline for security positions. The Certified Kubernetes Administrator (CKA) is respected in DevOps. Cisco's CCNA still matters for networking.
Weak certifications are the ones from platforms nobody has heard of, or ones that only require watching videos with no real exam. If the cert does not have a proctored test or a hands-on component, it does not carry much weight.
What makes a cert strong
It comes from a recognized company (AWS, Google, Microsoft, CompTIA). It has a proctored exam that you can fail. And it maps directly to a job requirement listed in real postings. If a cert meets all three, it is worth getting.
Best for: cloud engineers, security analysts, network engineers, and anyone applying to companies with compliance requirements.
4. Bootcamp With a Capstone
A bootcamp completion alone is moderate proof. It says you spent 12 to 16 weeks learning a stack, but plenty of people complete bootcamps and still struggle in interviews. What makes a bootcamp meaningful is the capstone project.
A good capstone is a real application that you built, deployed, and can demo. If your bootcamp ended with a group project and you can clearly describe what you personally built (not what the team built), that is solid. If you can point to the live app, even better.
Be specific about what you learned. Instead of saying "Completed General Assembly Software Engineering Immersive," try: "Built a full-stack React/Node.js app with PostgreSQL that processes real-time transit data for 3 city bus routes. Deployed on AWS." The first version tells the recruiter you attended. The second tells them you can build things.
Paid work is proof, period. If someone gave you money to do the job, that is a strong signal that you can do the job. Freelance and contract work counts even if the client was small or the project was short.
The key is specificity. "Freelance web developer" on your resume means almost nothing. "Built a custom Shopify theme and checkout flow for a DTC brand processing 2,000 orders per month" means a lot. Name the technologies. Describe the scale. If the client will serve as a reference, mention that.
Platforms like Upwork and Toptal give you a verifiable track record with reviews and completed project counts. These are not as prestigious as a full-time role at a known company, but they are real proof that clients trusted you with their money and their product.
Best for: designers, frontend developers, mobile developers, and anyone building a portfolio through client work.
6. Technical Writing and Talks
Writing a technical blog post or giving a conference talk proves something deeper than skill. It proves understanding. You cannot clearly explain distributed systems or database indexing to other people unless you actually understand those topics yourself.
Strong examples: a blog post walking through how you solved a real debugging problem, a conference talk on a specific technical decision your team made, or a tutorial that other developers have bookmarked and shared. Weak examples: a post that summarizes documentation without adding anything, or a talk that is just a product demo.
The best technical writing is specific and experience-based. "How I reduced our API response time from 800ms to 120ms" is interesting. "An Introduction to REST APIs" is not. Recruiters and hiring managers share technical posts internally all the time. If your post shows up in a Slack channel before your resume does, that is a massive advantage.
Best for: senior engineers, developer advocates, and anyone targeting roles where communication matters as much as code.
7. Hackathons and Competitions
Winning a hackathon or placing in a coding competition is real proof, but it is the weakest type on this list because it is time-limited and context-dependent. A hackathon project is built in 24 to 48 hours. It is usually rough, unfinished, and not maintained after the event. That is fine for the hackathon. It is less convincing as lasting proof of skill.
What makes hackathon results strong is specificity and outcome. "Won first place at HackMIT 2025 for building a real-time sign language translation tool using MediaPipe and React" is meaningful. "Participated in a hackathon" is not.
Coding competitions like LeetCode contests, Advent of Code leaderboards, or Kaggle competitions carry weight in specific contexts. Kaggle rankings matter for data science roles. LeetCode contest ratings can be relevant for companies that do heavy algorithm interviews. But for most roles, a deployed project (#1) is a better use of your time than competitive coding.
Best for: students, early-career developers, and anyone applying to companies that run their own hackathons.
Putting All Your Proof Together
Having multiple types of proof is better than having just one. A deployed project plus a certification plus a couple of open source PRs tells a much stronger story than any single item alone. The challenge is presenting it in a way that is clean and easy to scan.
This is where a web profile helps. On a page like CVin.Bio, you can lay out your projects with live links, list your certifications with verification URLs, and link to your GitHub contributions all in one place. Instead of stuffing everything onto a one-page resume, put the highlights on paper and link to the full picture.
The proof stack
The strongest candidates without degrees typically have at least three types of proof: a live project they can demo, a recognized certification, and one more thing (open source, freelance work, or a technical blog). Stack your proof and make it all clickable.
Avoid the trap of listing skills as plain text without evidence. Writing "Python, AWS, Docker" in a skills section tells the recruiter nothing about your ability. Linking to a project built with those tools tells them everything. We wrote about this pattern in our piece on why generic skill bars hurt your resume.
Jordan M.