What Employers Look for in a CS Portfolio
One project they can open and use in about ten seconds, then proof you made the decisions yourself. Here is the order they apply, and the hosting detail that quietly decides whether they ever see it.
By Howard Davner
Quick Answer: One project they can open and use in about ten seconds. After that, in order: relevance to the specific role, evidence you made the decisions yourself, and code another person could read. Deployment comes first because it is the only item a reviewer can check without doing any work. An undeployed repository is the most common reason a solid CS portfolio gets passed over.
Ask most students what employers look for in a CS portfolio and the answer comes back as a list of properties: lots of projects, good GitHub activity, clean code.
None of that is wrong. It is just in the wrong order, and the order is the part that decides whether anyone gets as far as your code.
What employers look for, in order
Four things, ranked by how early each one is checked:
- Can they open it and use it. Deployed at a live URL, no setup. Checked in the first pass, by someone who is not an engineer.
- Is it relevant to this role. One project aimed at the job in front of them beats a general-purpose portfolio.
- Did you make the decisions. The stack, the data model, the edge cases. Checked in the interview, not before.
- Can another person read the code. Clear names, a README that says what it does and how to run it, a commit history that looks like work.
Employers describe this list in the opposite order, because code quality is the part they can talk about professionally and deployment sounds like a detail. Watch what actually happens to an application and the ranking inverts.
Why deployment outranks code quality
Because the two are judged at different moments by different people.
Code quality is assessed by an engineer, and an engineer only looks after somebody has already decided you are worth an engineer's half hour. Deployment is assessed in the first pass, by a reviewer with a pile of applications who is not going to clone a repository, install its dependencies and run it locally. Nobody does that during screening.
So the repository does not fail on quality. It fails on latency. It asks for effort before it produces any output, at the exact moment nobody has effort to spare. That is the whole argument for putting a deployed project on your resume, and it is a claim about timing rather than about your code.
This is also why a GitHub profile is not a portfolio on its own. A profile is a directory of names like ml-final and COMP3700-a2. A live URL is a thing already running.
Which free host keeps your demo awake
This is the part no employer will ever name and no portfolio guide mentions, and it decides whether the first item on the list above actually works.
You get one click. If the reviewer clicks and the page hangs, they do not conclude that your host is asleep. They conclude it is broken, and a broken demo is worse than no demo, because it is evidence against you rather than missing evidence.
So the hosting choice matters for a reason that has nothing to do with features. Read from each platform's own pricing and documentation pages on 2 October 2026:
- Vercel, Hobby plan. No cost, and it does not idle, so a cold link opens immediately. Runs static sites and Next.js or React apps. Its fair use guidelines restrict the plan to personal, non-commercial use, which a portfolio demo is.
- Render, free web services. Spins down after fifteen minutes without inbound traffic, and takes about a minute to come back up while the visitor watches a loading page. Capped at 750 free instance hours for each workspace in a calendar month, on 512 MB of memory and less than one CPU. Fine for a project you can warm up before you send the link. Risky for a link sitting in an application somebody opens on Tuesday.
- Hugging Face Spaces, CPU Basic. No cost, two shared vCPUs and 16 GB of memory. The natural home for a model demo.
- Railway. A thirty-day trial with five dollars of starting credit, after which the free option carries a one dollar monthly minimum. Workable, but it is a trial rather than an open-ended free plan, so plan for that before a recruiter finds out for you.
The practical rule: if your host sleeps, either move the project to one that does not, or hit the URL yourself the morning you send it and accept that the link decays.
What "real decisions" means to the person reading it
It means you can name a choice and defend it, which is a different thing from having built something complicated.
The projects that stand out are not technically ambitious. They are specific. "A tool that reads a job description and surfaces the keywords a resume is missing" names a problem, implies a solution, and shows you can frame a product. "An NLP project" tells a reviewer nothing at all, and tutorials and AI assistants are not the issue here. Using either is fine. The question is whether the decisions underneath were yours.
A useful test before you list a project: can you talk about it for ten minutes? What problem it solves, what you chose and why, what you would change, what broke. If you cannot, the project works against you in the interview rather than for you.
How reviewers check it is your work
Three cheap checks, and all three are fast.
- They open the link and use it. This is the entire first round. Anything that does not load ends here.
- They skim the commit history. Steady commits across days read as real work. A single upload titled "final project" reads as something else.
- They ask you about a decision. Why this stack, what breaks under load, what you would rebuild. Borrowed projects come apart on the third question, not the first.
All three pass on their own if you built the thing and chose the tools. None of them can be talked around with a better README.
Does a CS portfolio count without a CS degree
It counts for more. A degree and a certificate both have to be trusted. A live URL can be used, so without a degree on the page the project stops supporting your credentials and becomes the credential.
That raises the bar on exactly two things:
- It has to run. Every time, not on the day you deployed it. See the hosting section above.
- It has to be explainable end to end. The question that separates built-it from borrowed-it is never "what does it do". It is "why did you do it that way".
If you are weighing a course against building something, the comparison between an AI certificate and a project is the same argument with the numbers attached.
How many projects, and does school work count
One deployed, role-specific project beats ten undeployed ones, and a reviewer can only count the ones that open. That is why the number of projects on your resume matters less than how many of them run.
School projects count on one condition: they are deployed and some decision in them was yours. A project built to a prescribed brief with a prescribed stack demonstrates that you can follow a rubric. Take it past the assignment, choose something about it yourself, put it somewhere a stranger can use it, and it becomes evidence.
How long one takes
A weekend, for a narrow single-purpose project that is deployed at the end of it.
The code is not the time sink. Choosing what to build is, and so is the last mile of getting it online. Students who spend a month on a portfolio project usually spent three weeks choosing a topic and letting the scope grow. Two things stop that:
- Pick one narrow problem and build only what answers it.
- Deploy on day one, empty, so the URL exists before the features do.
What to build when nothing on your list fits the role
Start from the job description rather than from a list of impressive-sounding ideas.
The reason generic portfolios stall is that they are built for a category. "Software engineering" is a category. The posting in front of you is not: it names a stack, a domain, and a set of responsibilities, and the project that reads as evidence for it is usually the small, unglamorous task buried in that list. If none of your existing projects map to the roles you are applying to, AI project ideas for a resume covers how to pick one from a specific posting, and CS portfolio projects for internships breaks it down by the kind of internship you are chasing.
That gap between a posting and a working link is what Provieo's project builder exists to close. Paste in the job description, get project ideas scoped to that specific role, then build and deploy one with an AI Coach handling the parts you are stuck on. The output is a project running at a URL, plus a resume and cover letter that link to it.
Provieo is free and unlimited to use, and your first project build and deploy is free. After that it is a one-time $39 for unlimited deployed projects, with nothing recurring.
Related tools: ATS resume checker | AI cover letter generator | Interview questions generator
Try it free, no sign-up needed
Not sure your projects match the jobs you want? Paste a job description into Provieo's free Job Description Matcher and see example project directions for a role, with no account. Already applying? Run your resume through the free ATS Resume Checker to see what is getting filtered before a human sees it. Both are free.
Frequently Asked Questions
What do employers look for in a CS portfolio?+
Four things, and they are applied in this order. First, can they open it and use it immediately, which means it is deployed at a live URL rather than sitting in a repository. Second, is it relevant to the specific role they are hiring for. Third, can you explain the decisions you made, because that is what separates a project you built from one you followed. Fourth, is the code readable by another person. Deployment comes first because it is the only one of the four that can be checked without any effort from the reviewer.
Why does deployment matter more than code quality?+
Because of when each one gets checked. Code quality is assessed by an engineer, after someone has already decided you are worth an engineer's time. Deployment is assessed on the first pass through the application pile, by a person who will not clone a repository and set up an environment. A live URL produces evidence before the reviewer has decided whether to bother. Unreadable code loses you a later round. An undeployed project loses you the first one.
Which free hosting should I use for a portfolio project?+
Pick one that does not go to sleep, because you get one click. Vercel's Hobby plan runs static sites and Next.js or React apps and does not idle, though its fair use guidelines restrict it to personal, non-commercial use, which a portfolio demo is. Render's free web services spin down after fifteen minutes without traffic and take about a minute to come back, so a reviewer clicking a cold link sees a loading page first. Hugging Face Spaces runs machine learning demos on two shared CPUs and sixteen gigabytes of memory at no cost. Railway is a thirty-day trial rather than an open-ended free option, so budget for it or host elsewhere.
How many projects does a CS portfolio need?+
One deployed, role-specific project is worth more than ten undeployed ones. A reviewer can only count the projects they can actually open, so three repository links and no live URL reads as zero to the person making the first pass. Aim for one working project per type of role you are applying to, and add more only as you build them.
Do school projects count in a CS portfolio?+
Only if they are deployed and the decisions were yours. A class project built to a prescribed brief with a prescribed stack tells a reviewer that you can follow a rubric. The same project becomes evidence the moment you take it past the assignment, choose something about it yourself, and put it somewhere a stranger can use it. Undeployed and rubric-shaped is the weakest item you can list.
Does a CS portfolio matter without a CS degree?+
It matters more, not less. A degree and a certificate both have to be taken on trust. A live URL can be opened and used, so it is the only claim on the application a reviewer can verify for themselves in under a minute. Without a degree behind it, the project is the credential, which raises the bar on two things specifically: it has to run every time, and you have to be able to explain it end to end.
How do recruiters check that a portfolio project is your own work?+
Three cheap checks, in this order. They open the live URL and use it, which ends the process for anything that does not load. They skim the commit history, where steady work over days reads differently from one upload labelled final. Then they ask you about a decision in the interview, and the follow-up questions are where a borrowed project comes apart: why this database, what breaks under load, what you would rebuild. Nobody audits code line by line, and none of the three can be passed with a better README.
How long does a CS portfolio project take to build?+
A narrow, deployed, single-purpose project takes most students a weekend. The time is not spent on the code. It goes on choosing what to build and getting it online, which is why students who spend a month on one usually spent three weeks picking a topic and widening the scope. Deploy on day one so the URL exists before the features do.
How does Provieo help CS students build portfolio projects?+
Provieo takes a job description, generates project ideas matched to that specific role, and walks you through building and deploying one with an AI Coach. The output is a working project at a live URL, plus a tailored resume and cover letter that link to it. Provieo is free and unlimited to use, and your first project build and deploy is free.
Put a working link in your next application.
Paste the job you're applying to. Provieo designs a project against that exact listing and walks you through deploying it, so what a recruiter clicks is the work itself, not a description of it.
Free to use, and your first deployed project is free. Or tailor your resume to the same posting.