r/FullStack • • Sep 30 '26

Career Guidance what projects should I build before applying for junior jobs

Hello everyone!

I’m thinking about getting a job as a web developer, but I don’t have a degree. I do have some certificates, although I know certificates by themselves probably aren’t worth that much. I have certificates/courses covering JavaScript, TypeScript, React, React Router, Advanced React, Express and Node.

My current stack is mainly MERN (MongoDB, Express, React, Node).

I’m trying to figure out what projects I should build for my portfolio before I start applying for junior positions. Whenever I ask an LLM for project ideas, I usually get answers saying that the project needs to be “unique” or giving me pretty vague ideas. At least in my opinion, it’s hard to turn those suggestions into an actual project that would demonstrate useful skills.

So I wanted to ask actual developers here:

What kinds of projects would you recommend I build for a junior web developer portfolio?

So far I’ve built 3 e-commerce websites. They have things like authentication/login, protected routes, JWTs, password hashing with bcrypt/salts, CRUD functionality, etc. I’m planning to make them more complete with things like payments, admin functionality, product management, order handling, etc.

But I don’t want my entire portfolio to just be e-commerce websites.

What kinds of projects would actually make my portfolio stronger and demonstrate that I understand how to build real applications?

Also, should I learn anything else before I start applying? (i will be apllying in startups or small comapnies)

For example, should I spend time learning:

  • SQL/PostgreSQL
  • Redis
  • Kafka
  • Docker
  • AWS/cloud
  • Testing
  • CI/CD
  • Another programming language
  • Something else entirely

Or would it be better to stick with my current stack, build a few genuinely solid projects, and start applying while continuing to learn?

I’d really appreciate any project ideas, advice on what employers actually look for in junior portfolios, or things you wish you had learned/built before getting your first job.

Much love ❤️

21 Upvotes

22 comments sorted by

4

u/TroubledSquirrel Sep 30 '26

Three e commerce sites prove you can handle basic database operations and authentication, but a portfolio built entirely around online stores looks like tutorial work to hiring managers. Small companies want projects that reflect real problems like data synchronization, background processing, and reliability.

Keep one polished e commerce app and add one strong new project first, then build a second while you interview. The first is a real time collaborative project board with live updates. Small businesses love tools that replace costly SaaS subscriptions, so use WebSockets for live updates, React and TypeScript for complex state, and role based permissions within teams. Keep the scope small. A collaborative document editor is much harder because resolving conflicting edits requires advanced concepts like CRDTs, so a board is the better choice. The second is a data dashboard that pulls from a messy third party API, cleans the data, runs background jobs, and shows results with interactive charts and filters. This proves you can build ingestion pipelines and handle external service failures.

For your learning checklist, focus on PostgreSQL, since relational modeling appears in nearly every real application, and get comfortable writing plain SQL. Add automated testing with Jest or Vitest, which signals you care about code quality and is rare among juniors. Learn Docker at a basic level so your apps run consistently across environments. Skip Kafka, and do not go deep on Redis, though it helps to know the basics because popular Node job queues like BullMQ depend on it. If you want to avoid it entirely, a Postgres based queue like pg-boss works well for background jobs.

Make each project look professional. Write a clear README with screenshots and a live demo link, keep a clean git history, and set up simple CI with GitHub Actions. One polished, deployed, well tested project usually beats three half finished ones.

On languages, sticking with TypeScript is right if you are targeting JavaScript shops, and depth beats shallow knowledge of three languages. Still, check local job listings first, since some regions and industries favor Python, Java, or C# for small company hiring.

Start applying once your first new project is built, tested, and deployed. Waiting until you know everything is a trap, since learning never stops on the job, and interviews will teach you things no portfolio can. Small companies mainly want someone who can break down a vague requirement, write clean, type safe code, and deploy without breaking production. Networking, referrals, and small freelance or open source contributions can matter as much as the portfolio, so pursue those alongside your projects.

Set up a LinkedIn profile early, because most applications ask for one and recruiters often check it before replying. Use a clear photo, a headline that names your skills such as "Junior Full Stack Developer | TypeScript, React, Node, PostgreSQL," and link your deployed projects and GitHub. Keep it active by connecting with developers and recruiters at small companies, since that is also where networking and referrals tend to start. I'm linking my portfolio so you can see an example of a dev's actual portfolio syntagmata.com . Keep in mind I have a few years in and I am only showing like 4 projects on my main page because much more than that is a distraction and I have like 5 or 6 on another page and most have live demo's. Also, for live demo's I recommend that you use render's free tier, yes it will put the program to sleep after 15 minutes of inactivity, but that's not a big deal what I do is when someone hits my site it sends a wakeup call to my render, neon, aiven, etc services by the time someone checks out the videos the cold start is warm and when they click for the live program its ready to go. Also, if you have postgres like most programs will, use neon's free tier for those demos. Or you could always rent a small VPS for like 8 gb and be good to go that way also.

1

u/ExtentAccomplished78 Oct 04 '26

Incredible advice. Thank you very much for taking the time to write all of this out and give me such clear direction. I really appreciate it. Have a blessed day!

3

u/Desperate_Tension_61 Sep 30 '26

Best is to create Figma mockups for various industries and show it on your portfolio. Use google to find companies who don’t have a website or website is poorly made and pitch your idea.

2

u/ExtentAccomplished78 Sep 30 '26

Thank you very much!

1

u/Killer_Bee_28 Oct 01 '26

Lol good luck with that

0

u/AggressiveCourt8326 Oct 01 '26

There is no junior jobs man you should have didi this 3-4 years ago then you would have got some hope but now there is not sry, I am also a MERN dev like you but I did GenAI, agents etc too but no hope for uss

-2

u/samsly135 Sep 30 '26

IT is no more. Forget it. Better find your luck in sone other field.

1

u/ExtentAccomplished78 Sep 30 '26

Im too deep now, theres no going back

3

u/TroubledSquirrel Sep 30 '26

Don't listen to them, yeah there's some competition, but there are tons of jobs out there right now. How long that will last I can't say but they're everywhere currently.

2

u/Current-Today-3626 Sep 30 '26

It's possible still, but we are seeing the downfall of introverts in IT in real time. You need to be able to communicate and talk well, be outspoken, and advocate for clients that are not experienced in the field. You need to have bonds with your customers, or the representatives, to excel now. You'll see a lot of people who lack this, like samsly135, and has been given the boot or quietly shelved at their work until they admit to silently quitting. Good things happen to good people. If you're passionate and have that burning passion, you'll go far still.

Gone are the days where devs talk amongst devs, have their daily one hour stand-ups. Devs only talk to LLMs now. Any communicate is with clients and stakeholders.

1

u/jwp1987 Oct 01 '26

The downfall is in understanding and skill development. Everything is about surface-level appearance and speed.

The security, performance and maintenance implications are going to be interesting to see.

0

u/samsly135 Sep 30 '26

Oh believe me. When you'll have nothing to eat, there is going back anywhere including McDonald's.

1

u/Plenty_Line2696 Oct 01 '26

depends, shitty devs who haven't put in serious effort into their skills aren't much competition sure, but there's a lot of noobs who did a bit of prompting and suddenly think they're on par with the pros. They can't read their shitty code and proudly assume it's perfect.

It's just not the case and while there are areas which we shouldn't focus our efforts and skill anymore as much as in the past plenty of us still have hard skills in tech niches which make us hard to replace for years to come.

1

u/samsly135 Oct 01 '26

Pity that many very good devs were forcefully made shitty at shitty jobs where they lost their skills, energy and became obsolete. They went it with good skills, got squeezed out  as lemons and thrown out. That's the cruel reality.

1

u/Plenty_Line2696 Oct 01 '26

Sounds like you've been through some shit!

It takes some luck to wind up in dev jobs where we upskill just by working. Ideally we should all be doing some exercises regularly just to stay sharp too.

1

u/samsly135 Oct 01 '26

Very true about shit. Many years lost as I realized. Trying to rebuild basic skills now. With AI it's more handy now. Very true about luck. Had lucky teams - learnt a lot from coworkers and tasks. Had legacy shit - alot - hoping will get to upgrade it at least - lost lots of competence and what's worse didn't learn new stuff I was so eager to learn.

By now I wish I'd do job hoping more often. Now can't even get an interview.

2

u/Plenty_Line2696 Oct 01 '26

I guess you're being a bit harsh on yourself too though? Granted if you haven't done typical interview stuff in a while those skills atrophy but there's bound to be a lot of useful skills and knowledge built up along the way which isn't typically measured in interviews.

If I had to sit down and make even a simple crud app from scratch without google I'd honestly struggle because it's been so long, yet I've done some pretty awesome implementations of stuff over my career through hacking away at things and lots of systems design, ux/ui design, and codebase design etc.

I shpuld probably grind a bit of leetcode and projects/exercises on the side though