r/developers • u/spbrothers33303 • 1d ago
Career & Advice Student developer looking for career advice, real-world problems to solve, and project ideas
Hey everyone!
I'm a student developer from India, currently working on improving my full-stack development skills and preparing myself for software engineering internships and entry-level jobs.
I have experience with TypeScript, JavaScript, React, Next.js, Node.js, and building applications with AI/LLMs. Instead of building another basic CRUD app or following tutorials, I want to work on something that solves a genuine real-world problem.
My goals are to:
- Become a better software engineer and build projects that demonstrate real problem-solving skills.
- Understand what problems professionals and small businesses actually face in their daily work.
- Build a useful project that I can showcase in my portfolio and discuss in interviews.
- Eventually turn a solution into a small business if people find it valuable.
I'd really appreciate advice from software engineers, hiring managers, freelancers, founders, and business owners.
A few questions I'd love your perspective on:
- As someone hiring junior developers, what skills or projects would make you take a fresher's application seriously?
- What frustrating, repetitive task do you deal with at work that existing software doesn't solve well?
- Are there any real-world problems you think a junior developer could realistically solve with a small but well-built application?
- What mistakes do you commonly see in junior developers' portfolios?
- If you were starting your software engineering career today, what would you focus on first?
I'm not trying to sell anything. I want to learn from people with real industry experience, improve my engineering skills, and build something genuinely useful.
Even a small piece of advice or an example from your own experience would mean a lot. Thank you!
1
u/Aromatic-Olive69 1d ago
One thing that always makes a portfolio stand out is having actual users and showing how you dealt with their feedback, not just a clean repo. A project where you had to fix a weird bug because three people complained tells me way more than another to-do app with perfect code.
Id pick someone who built a scrappy internal tool for a local shop over someone who followed a tutorial for a flashy dashboard. Talk to a few businesses around you, a bakery, a tutor, a small clinic, and ask what takes them way too long to do manually. Youll find scheduling nightmares, inventory tracking on paper, or messy client follow-ups that a simple web app could handle.
Junior portfolios usually make the same mistake of explaining what the tech does instead of what problem it solved. Dont tell me you used websockets, tell me you cut a manual update process from two hours to two minutes for a guy running a warehouse.
A lot of the frustrating stuff at work isnt a missing feature in big software, its the glue between them. Moving data from a slack message into a spreadsheet, or parsing a messy email thread into a task. Nobody builds that because its ugly and specific to one team, perfect for a small project.
If I started over today Id spend less time on framework of the week and more time shipping small ugly things to real people and watching where they struggle. The skill of figuring out what to cut and what actually matters to a user is the whole job.
•
u/AutoModerator 1d ago
Howdy u/spbrothers33303, and welcome to r/developers!
A few tips for a post that gets good answers:
- Use a clear, specific title (what are you actually asking or sharing?).
- Include code, the exact error, versions, and what you already tried.
- Heads-up: this sub does not allow external links in posts or comments.
Share code and details directly instead of linking out.Join the r/developers Discord!
I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.