I've been running into a bit of a creative block lately, and I'd genuinely appreciate some advice from people who review resumes or have experience hiring for backend and systems engineering roles.
I keep hearing people say that finding real-world problems to solve is easy. Just look around, identify something inefficient in your day-to-day life, and build a solution. But I've been struggling with this.
Almost every problem I've come up with already has an established solution, sometimes even an entire product built around it. I've spent the last week hunting for project ideas, and I keep running into the same wall.
For some context, I've primarily built projects as a hobby, focusing entirely on backend engineering without relying on AI APIs.
A couple of things I've built:
1. File Management System for Educational Enterprises
A tool designed to organize large amounts of educational material, particularly in environments where files are poorly named using generic identifiers like dates, subject codes, etc.
It parses documents, extracts relevant information, identifies document types, renames files accordingly, and provides features for modular organization and arrangement.
2. Repository Change Visualization Tool
A developer-focused tool that visualizes changes within a Git repository. This goes beyond conventional diffs by tracking changes to JSON variables, mapping classes, and providing a more structured understanding of how a codebase evolves.
Both projects were built using my own understanding of backend technologies. No AI APIs or external AI-powered services involved.
Now, I feel like it's time to move towards building projects that actually align with the domain I want to pursue after graduation.
I'm interested in backend engineering, systems engineering, distributed systems, and related fields. I haven't settled on a particular specialization yet.
Here's where my dilemma begins.
When hunting for projects, I find myself stuck between two approaches:
Approach 1: Build something that already exists, but engineer it myself**.**
For example, something like a data recovery system or a recovery tool verifier. These are problems that already have enterprise-level solutions, but building a prototype myself could involve interesting engineering challenges, concurrency, fault tolerance, recovery mechanisms, etc.
Another example could be a ledger system for tracking natural resources at a municipal/local government level.
I feel like I have 1000 more ideas which I feel like with a little bit of dedication I can do it right and impressive.
Approach 2: Find a problem that hasn't been properly solved yet.
Instead of recreating something that already exists, I could hunt for a relatively unexplored problem and build a solution around it, even if the engineering complexity is comparatively average. Again is this the necessity right now given the job market?
My question is: Which of these approaches actually carries more weight when you're evaluating a candidate's resume?
Would you rather see a student build a technically complex prototype of an existing enterprise solution, or a relatively unexplored solution to a problem that hasn't received much attention?
I'm also curious about something a senior once told me:
Why are we always chasing solutions for individual users when we could be building solutions for enterprises?
The idea was that instead of building another consumer-facing application, perhaps I should look at smaller, overlooked enterprise problems and build tools that solve them.
I found that perspective interesting, but I'm still trying to understand how to approach it.
One last thing: I'm currently studying at a college I'd consider well below the 2.5-tier category. I know that puts me at a disadvantage when applying for internships, so I want my projects to genuinely stand out and demonstrate engineering ability rather than just add another CRUD application to my resume.
I'd especially appreciate perspectives from people who have reviewed technical resumes, interviewed candidates, or work in backend/systems engineering.
TL;DR: I'm a student interested in backend, systems engineering and distributed systems, trying to build projects that genuinely strengthen my resume for internships.
I've built two backend-focused projects without AI APIs, but I'm struggling to find what to build next.
My dilemma is whether I should:
- Build technically complex prototypes of problems that already have established enterprise solutions.
- Hunt for relatively unexplored problems and build solutions that don't already exist, even if the technical complexity is lower.
- Focus on overlooked enterprise problems rather than consumer-facing applications.
As someone reviewing a resume, what would impress you more: engineering depth, originality of the problem, or the practical value of the solution?
Coming from a lower-tier college, I want my projects to compensate for the lack of institutional advantage and actually demonstrate that I can engineer systems.
I am really sorry for the extremely long rant and ofc generated ai content.