Proof without a CS degree

Projects, contributions and writing that a stranger can check, built to use what you already know.

What: Evidence of skill that anyone can open and check, such as a deployed project, a data report, a merged pull request or a written case study, rather than a list of courses taken.
Why: Without a CS degree or tech job, proof is what lets a reviewer trust you. It answers "can you actually do this?" before anyone asks.

Watch out

A resume listing ten completed courses and no link to anything you built.

Also called project from your old field, old-field project

What: A project that solves a real problem from your previous degree or job: a tool, an automation, an analysis or a test plan for software used in that field.
Why: It is original, hard to copy, shows domain knowledge and gives you a story that interviewers remember.
Example: A civil engineer builds a small app to log site inspections with photos and export reports, replacing a paper form they used for years.

Watch out

Using real client or employer data; recreate the structure with fake records.

What: A project small enough to finish in a few weeks at your weekly hours, with a clear list of what it will and will not do.
Why: Finished small projects prove more than ambitious unfinished ones, and finishing is the skill employers most want to see.
Example: Version one: three screens, one user type, CSV export. Later ideas go in a "next" list, not into version one.

What: A small, accepted change to a public project: a documentation fix, a test, a translation or a labelled beginner issue.
Why: It shows you can read code you did not write, follow a project's process and take review feedback, which is daily work in any tech job.

Watch out

Opening pull requests that only change a word to collect contributions, which maintainers notice and dislike.

What: Sharing what you learn and build as you go: short posts, write-ups of problems you solved, or notes on a project's decisions.
Why: It builds a visible trail of progress, sharpens your understanding and brings people to you over time, including recruiters and fellow switchers.

Watch out

Posting daily motivation with no substance instead of occasional useful write-ups.

Also called certificate

What: Treating certificates as structured learning and a small signal, not as proof. They matter most in fields with recognised exams, such as IT support, cloud or security.
Why: Many people hold the same beginner certificate, so it rarely decides a hire. A project built with the skills tells a reviewer far more.

Watch out

Collecting certificates to feel ready instead of building something with what they taught.

Also called case study

What: A one-page account of a project: the problem, who it was for, what you built, decisions and trade-offs, results and what you would change.
Why: Career changers are often good communicators. A clear write-up shows judgement and communication, which code alone does not.
Example: Problem, users, approach, two key decisions, screenshot, result, next steps, link to code.

Go deeper