▲ 4 r/careerquestions+2 crossposts

Is it better to have many skills on a junior developer resume, or fewer skills with deeper knowledge?

I’m aiming for a junior Python backend/full-stack role and have been looking through a lot of resumes on Reddit. One thing I’ve noticed is that many people list a huge number of technologies,sometimes 20–30 skills like Docker, Kubernetes, AWS, Redis, Kafka, RabbitMQ, React, Next.js, MongoDB, PostgreSQL, etc.
This made me wonder:
Is it actually better to list as many relevant skills as possible for ATS and recruiters, or is it better to keep the list shorter and only include technologies you know well and can confidently discuss in an interview?
For those of you who interview candidates or have recently been hired:
What makes a stronger junior resume?
Do recruiters expect juniors to know all the technologies they list?
Have you ever rejected someone because they listed skills they clearly didn’t understand?
How much does ATS influence this decision?
I’d love to hear from recruiters, hiring managers, and developers who have been involved in hiring.

reddit.com
u/AnasKaithakoden — 4 days ago
▲ 50 r/careerquestions+2 crossposts

What backend projects would actually aid me stand out for a junior Python backend developer role?

Hi everyone,
I’m currently preparing for junior Python backend developer roles, mainly focusing on FastAPI, PostgreSQL, SQLAlchemy, Docker, Git, and REST APIs.
When I search online, I always see the same project recommendations:
Todo API
Blog API
Library Management System
Expense Tracker
URL Shortener
E-commerce API
My concern is that almost every beginner seems to build these projects. If recruiters have seen hundreds of them, do they still add value to a portfolio, or do they just blend in?
Would it be better to build something that’s closer to a real business application, such as:
Recruitment/HR management
Clinic management
Warehouse/inventory system
Internal business tools
API gateway or authentication service
I’m trying to optimize my time and build projects that will genuinely improve my chances of landing a junior backend role rather than just checking boxes.
For those of you who interview junior developers or work as backend engineers:
What projects actually impress you?
Is the project idea important, or is the quality of the implementation what matters most?
What features make you think, “This candidate knows backend development”?
I’d really appreciate hearing from people who have interviewed candidates or recently landed backend jobs themselves.
Thanks!

reddit.com
u/AnasKaithakoden — 10 days ago

Is it harder to get an entry-level DevOps job than a software development job?

Hi everyone,
I’m a college student currently trying to decide where to focus my learning.
I’ve been learning Linux, networking, virtualization (KVM), Docker, Kubernetes and some automation tools because DevOps interests me. However, I recently spoke with an employee at a company who told me that entry-level DevOps jobs are relatively rare. According to him, many people start as software developers, system administrators, or IT support engineers and then transition into DevOps after gaining experience.
I’m curious how accurate this is in today’s job market.

A few questions:
Are true junior/entry-level DevOps roles uncommon?
Did you start directly in DevOps, or did you transition from another role?
As a college student, would it be better to focus primarily on software development and keep learning DevOps on the side?
If you were starting from scratch today, what path would you take to maximize your chances of getting hired?

For context, I enjoy Linux, networking, cloud technologies, and automation more than building front-end applications, but I also want to be realistic about job opportunities.
I’d appreciate hearing about your experiences and advice.

reddit.com
u/AnasKaithakoden — 19 days ago

Is it harder to get an entry-level DevOps job than a software development job?

Hi everyone,
I’m a college student currently trying to decide where to focus my learning.
I’ve been learning Linux, networking, virtualization (KVM), Docker, Kubernetes and some automation tools because DevOps interests me. However, I recently spoke with an employee at a company who told me that entry-level DevOps jobs are relatively rare. According to him, many people start as software developers, system administrators, or IT support engineers and then transition into DevOps after gaining experience.
I’m curious how accurate this is in today’s job market.

A few questions:
Are true junior/entry-level DevOps roles uncommon?
Did you start directly in DevOps, or did you transition from another role?
As a college student, would it be better to focus primarily on software development and keep learning DevOps on the side?
If you were starting from scratch today, what path would you take to maximize your chances of getting hired?

For context, I enjoy Linux, networking, cloud technologies, and automation more than building front-end applications, but I also want to be realistic about job opportunities.
I’d appreciate hearing about your experiences and advice.

reddit.com
u/AnasKaithakoden — 19 days ago