I'm trying to land a backend development job, but I keep getting vague feedback that my GitHub projects aren't impressive enough. I've built a task queue system, an RTMP server from scratch, and a basic JSON-based SQL engine, yet people still tell me to build "something interesting" or "something that helps people" without explaining what that means.
I have around two years of data engineering experience, although I'd prefer to move into backend development. If my Python or FastAPI skills are outdated, or if employers expect technologies like CUDA, I'd rather know clearly so I can focus my time. What specific skills, projects, experience, or job-search strategies would make me more competitive for backend roles?
4 Answers
Your projects already sound more substantial than another basic CRUD application. The issue may be presentation and production readiness rather than originality. Pick one project and make it look like something a team could actually operate: add thorough tests, Docker, CI/CD, authentication, logging, metrics, deployment instructions, architecture notes, and a clear explanation of the tradeoffs you made. Then tailor your resume to the requirements in real job postings. CUDA is not a magic shortcut to employment; most backend roles value reliable production engineering much more.
The entry-level market is crowded, so networking can matter almost as much as technical ability. Try meetups, job fairs, alumni groups, former coworkers, friends, and companies in your area. Look for internships or internal transfers too, even if the role isn’t your ideal destination. When applying, learn what each company actually builds and become familiar with its domain and technology stack. There’s no guaranteed project that unlocks a job, but referrals and targeted applications can get your work in front of people who will evaluate it properly.
Don’t assume the answer is automatically another degree or a flashy specialization. If you already have professional data engineering experience, frame it as evidence that you’ve worked with real systems, deadlines, reliability, and stakeholders. Explain why you want backend work and connect your previous experience to the role. Also, apply broadly and keep an income source if necessary—the current market has a lot of randomness, and rejection doesn’t necessarily prove that your projects are inadequate.
Companies usually aren’t hiring someone simply because they can write code. They want someone who can build a useful product, understand requirements, explain technical decisions to nontechnical people, manage their work, and collaborate with a team. Consider specializing in a stack or product area that has consistent demand, such as cloud infrastructure, data platforms, enterprise systems, or a particular backend ecosystem. Make sure your portfolio demonstrates those broader skills instead of only showing source code.
That’s the part I struggle with: people say I need to stand out, but rarely explain what evidence they actually want to see. I’ll focus more on showing production quality and connecting my experience to specific job requirements.