What projects should I show to get hired?

Ajay Jetty · Nov 22, 2026

Show two or three projects that look like the work the job actually involves, and that you can talk about in detail. A small project you understand completely will help you more than a big one where your part is hard to explain.

I think people get stuck here because they treat a portfolio like a storage box. They put everything in and hope someone finds the good part. The person hiring has a narrower question: can you do the kind of work my team needs done?

Start from the job, not from your past

Open three or four job posts you would be glad to get. Read what they ask for and write down the tasks that keep showing up. Those tasks are your filter.

Now look back at your work and ask which projects touch those tasks. If a role keeps mentioning customer research, your research project goes first, even if your favorite project was something else. You can love a project and still leave it out of this particular conversation.

What makes a project worth showing

A good project to show usually has most of these:

The last one surprises people. Saying what you would change often makes you sound more experienced, because anyone who has done real work has a list.

What to show for your kind of role

The format depends on the work, so here are some simple starting points.

If your best work is private

Most work belongs to an employer, so be careful. Do not share company files, customer names or anything confidential.

You can still describe the work. Remove the identifying details and explain the problem, your approach and what happened in general terms. You can also rebuild the idea using public or made-up data, as long as you say that is what you did.

If you have nothing to show yet

Make something small and useful. Fix a process for a local group, build a tool you wish existed, write a teardown of a product you use, or draft a plan for a company you admire. Be honest that it was self-directed. Finishing one modest thing tells an employer more than a long list of courses.

Write each project in a few lines

Before you share a project, try describing it in four short lines: the problem, what you did, what changed, what you learned. If you cannot do that, the project is not ready to show yet.

Those same lines can go straight into a note. Here is a made-up example:

Hi Daniel, I saw your team is hiring a backend engineer to work on billing. Last year I rebuilt a retry system for failed payments and wrote up what I got wrong the first time. Would it be useful if I sent you the short writeup?

One project, tied to their work, with an easy next step.

How Jobs Jetty helps

Once you know which project to lead with, you need someone to show it to. Jobs Jetty covers thousands of companies and their open roles in engineering, product, sales, marketing and recruiting.

Upload your resume once. It shows you who to write to and drafts a note from your resume. Edit it so your best project is in there, then Send with Gmail opens your own Gmail with the note filled in, and you send it. Free is 10 notes a day, and sharing gets you more.

Try it at jobs.openjetty.ai.

FAQ

How many projects should I show?

Two or three is plenty for most roles. Lead with the one closest to the job.

Can I show a group project?

Yes. Say clearly which part was yours, and be ready to talk about it in detail.

Do personal projects count?

They do, especially early in a career or during a career change. Say that it was a personal project and explain why you built it.

Do I need a portfolio website?

Not always. A clean document, a repo or a simple link can do the job if it is easy to open and read.

Sign in or sign up
AboutQuestionsHiring benchmarksJust fundedWho's hiringPay rangesMy storyBlogHow we verifyPrivacySign inTermsJobs Jetty, a closed community of job seekers helping each other.
What projects should I show to get hired? | Jobs Jetty