What full-stack project should I build for my portfolio?

November 17, 2026 4 answers
Asked by Rovexa.8j

I know React, FastAPI, and PostgreSQL, and I've built frontend projects before. I'm having trouble picking an idea and figuring out how to connect the frontend, API, database, and authentication.

What would be a useful first full-stack project for job applications? Should I focus on a traditional app first or add an AI feature?

Answers

_k53!mapgrommet.7

Pick something you already keep in notes or a spreadsheet. It doesn't need to be a brand new idea. A simple tracker for local shows, for example, gives you venues, events, dates, and a way to mark which ones you plan to attend.

Start with a user who can sign in, add and edit events, and filter the list. That gives you a reason to connect React to FastAPI, store related records in PostgreSQL, and deal with a real workflow. Once that works, add features one at a time.

Luka:

A small issue tracker or an app that replaces a spreadsheet works too. The subject matters less than having a workflow you can finish.

Reply to this answer
_v84~flickerwrench.2

Plan one complete path through the app before designing every screen. For a show tracker, that could be: sign in, create a venue, add an event at that venue, then see it in a filtered list.

Sketch the tables and their relationships first. A venue can have many events, so an event needs a venue reference. Then decide which API calls the screen needs, such as creating an event and fetching events with a filter. Build those endpoints and connect the React form and list to them.

Test the path with valid and invalid input, and make sure one user can't change another user's data. Deploy a working version someone else can open. You can expand the design after that instead of trying to solve the whole app up front.

Reply to this answer
_e42!cobblecrank.7

I wouldn't add an AI feature just because it's 2026. Get the ordinary app working first. If you later find a specific task where an LLM would actually help, add it as a separate feature and think about what happens when its output is wrong or the service is unavailable.

Reply to this answer
n.739!orbitwicket

Don't count on a project alone to get you an interview. It can still give you practice and something concrete to discuss, including the tradeoffs you made and problems you fixed.

People disagree about how closely application code gets reviewed, so if you put a repository on your resume, make it something you're comfortable showing. Clean up the confusing bits and include enough setup information for someone to understand and run it.

Reply to this answer

Add your answer

Answers are reviewed before publication.

Related Discussions