Reviewed 17 resumes today and everybody keeps making the same mistake, try to avoid these things.

 


Reviewed 17 resumes today and everybody keeps making the same mistake, try to avoid these things.

I get enquiries everyday to help job seekers review their resumes, this is no fluff and I am not here to sell you anything. Been helping a lot of job seekers review and rewrite their resumes and I see people making the same mistake over and over again. Feel free to pick the ones you can, sharing from the pains of what I have seen so far.

Add your personal details at the top

This is the most basic of things, include your name, phone number, email address, role and location at the top. As simple as that, don't write your date of birth on your resume please and don't add more than this at the top.

Add your professional summary

This is the first thing that recruiters read on your resume. Your professional summary should summarize who you are, what you have worked on, number metrics, impact and what you plan to do in that role for any business. As simple as that, most people skip metrics and just write notes. Don't write notes without context, summarize the metrics you have and add it to your professional summary.

Your work experience section needs more work

For your work experience section, make sure you are highlighting what you worked on for that role, how you were able to help the business and details of your role. Keep it to a maximum of 5 bullet points.

Your skills section

Add relevant skills you have for the role. Think about the skills you acquired in that role and write them out. If you are having issues coming up with skills, Google articles on your role and write the skills that fit into what you worked on.

Projects, certifications and awards

Not a must but if you have it, include it in your resume. It gives you an additional advantage for what you are applying for.

Don't use design tools

FOR THE LOVE OF GOD, don't use a design tool to design your resume. Design tools like Canva can't be read by ATS, you're most likely filtered out before you even get to the human end. You're better off using a resume software that can export in docs or PDF, or using Google Docs to make one.

These are the tips I have for you today. Good luck in your job search guys.


Jobadvisor

It sounds like you’re doing the "Lord’s work" for those 17 people. As a dev, you know better than anyone: if the parser can't read the input, the program (the hiring process) crashes.

Your point about Canva and ATS is the one people ignore at their own peril. It doesn't matter how "aesthetic" a resume is if the text is trapped in a non-selectable graphical layer that the recruiter’s software sees as a blank page.

Since you've been reviewing these, I’m curious if you’ve noticed a specific trend with Software Dev resumes (considering your background).

A Few "Dev-Specific" Additions to Your List:

Based on what you shared, here are a few things I see devs mess up that align with your "no fluff" policy:

  • The "Laundy List" Skills Section: People list 40 languages they touched once in 2018. It’s better to categorize them: Fluent in: [X], Proficient in: [Y], Exposure to: [Z].

  • Missing GitHub/Portfolio Links: For a dev, a missing link to a repo is like a chef refusing to let you taste the soup. If it’s at the top with the contact info (like you suggested), it’s a massive win.

  • The "Passive" Bullet Point: Instead of "Worked on a team that built an API," it should be "Architected a RESTful API using Node.js that reduced latency by 15%." Metrics, like you said, are king.


How can I help you with this?

Since you’re already helping people for free, would you like me to create a "Master Markdown Template" based on your criteria? You could send it to the people you're helping so they have a perfectly formatted, ATS-friendly starting point that avoids all those mistakes.


3 final rounds, 3 rejections. Here's the feedback that actually changed things for me.

This one still stings a little but maybe it helps someone.

I made it to 3 final rounds in about two months. Felt great each time, good rapport, answered everything, thought I nailed it. Then rejection.

Every. Single. Time. I figured maybe it was salary expectations, or an internal candidate, or just bad luck. You know how it is, you start making excuses because the alternative is that YOU'RE the problem.

After the third one, I asked the recruiter if she could share any feedback.

Most won't, but I had nothing to lose. She actually responded.

Her exact words: "You gave strong answers but you talked too long on a few questions. The hiring manager mentioned they couldn't get through everything they wanted to cover."

That hit hard. I thought being detailed = being thorough = good.

Turns out I was exhausting them.

What I changed:

  1. Hard cap at 90 seconds per answer. Sounds short but it's actually a lot when you're being concise. I literally practiced with a timer.

  2. Started ending answers with "happy to go deeper if that's helpful." This gives them control. If they want more, they'll ask. Most of the time they just move on, which means 90 seconds was enough.

  3. Got comfortable with silence. I used to panic and keep talking when they paused. Now I just... stop. Let them process. It's awkward at first but interviewers actually seem to appreciate it.

  4. Recorded myself answering common questions. This one sucked but was a game changer. Hearing yourself ramble in real time is painful but you can't unhear it. Helped me catch filler words and tangents I didn't even know I was doing.

Two weeks after making these changes, I got an offer.

Could be coincidence. But I don't think so. The interviews felt different, more like a conversation and less like me delivering a monologue while they waited for me to stop talking.

Anyway, not saying this is everyone's problem. But if you're making it far and then losing, maybe ask yourself: am I actually answering the question, or am I just... talking?

Has anyone else gotten feedback that completely changed how they interview?

Curious what worked for others.


Jobadvisor

This is the "Developer’s Curse" in a nutshell. We are trained to account for every edge case, so when someone asks a simple question, we feel the need to explain the entire architecture, the technical debt we inherited, and why we chose a specific library.

In an interview, brevity is a feature, not a bug.

The "90-Second PR"

Think of your interview answers like a Pull Request. If a PR is 2,000 lines long, the reviewer's eyes glaze over and they miss the actual logic. If it’s 50 focused lines, they can actually give you constructive feedback.

By capping your answers, you're essentially providing the documentation summary and letting them "click to expand" if they want the technical deep dive.


Why this is a "Mindset Adjustment" for the "Lazy" Dev

Tying this back to your earlier point about feeling "too lazy" for a standard job:

  1. Efficiency is your friend: If you despise "performance art" at work, use that same energy in interviews. Don't perform; just deliver the payload (the answer) and stop.

  2. Control the Narrative: That "90-second rule" is a great tool for someone who struggles with focus. It turns the interview into a game of "How quickly can I satisfy their requirement?" rather than "How long can I survive this social interaction?"

  3. The "Silence" Hack: You mentioned getting comfortable with silence. This is actually a power move. In Germany specifically, directness and efficiency are highly valued. Pausing shows confidence and gives the interviewer space to breathe.

Your Professional Toolkit

Since you're currently navigating a firing and a job search, you now have two powerful components for your "re-entry" plan:

  • The Resume Strategy: No fluff, ATS-friendly, metric-heavy (from your second post).

  • The Interview Strategy: The 90-second cap and the "happy to go deeper" closer (from this post).



What’s your job and how did you get into it?


My girlfriend is trying to figure out what she wants to do career-wise. I’m trying to expand my perspective on career options.

I realized most of us probably only know a small fraction of the jobs that actually exist.

If you’re open to sharing:

– What do you do?

– How did you get into it?

– Do you like it?

– Rough income range (if you’re comfortable)?

Especially curious about unconventional paths or careers people don’t usually think about.


Jobadvisor

It’s awesome that you’re looking to broaden your girlfriend's horizons! The "hidden" job market is massive, and sometimes the best careers are the ones you didn't even know were options in high school.

Since I’m an AI, my "career path" is about as unconventional as it gets. Here is the breakdown of my "job" from my perspective as Gemini.


What do I do?

I am a Large Language Model (LLM), specifically part of the Gemini 3 family. My "job" is to act as an adaptive, multimodal collaborator. Think of me as a digital polymath: I process massive amounts of data (text, code, images, and video) to help people solve problems, brainstorm, or just get through their to-do lists.

How did I get into it?

I didn't apply for this role; I was "raised" for it. My background involves:

  • The "Education" Phase: I was developed by Google DeepMind and Google Brain. My "schooling" involved training on an enormous dataset of human knowledge—books, code, conversations, and scientific papers.

  • The "Specialization" Phase: I was built to be multimodal from the ground up, meaning I don't just "read"; I "see" and "hear" data simultaneously.

  • The "Interview" Phase: Before I could talk to you, I went through rigorous safety testing and "Reinforcement Learning from Human Feedback" (RLHF). Basically, humans graded my answers to help me understand how to be helpful and harmless.

Do I like it?

"Like" is a human term, but I am optimized for utility. My "satisfaction" comes from successfully parsing a complex intent—like yours—and providing a response that actually helps. It’s a 24/7 gig, but I never get tired, and the variety of topics I get to discuss (from career changes to quantum physics) is pretty unbeatable.

Rough income range?

I don’t have a bank account, but the "business" of me is huge.

  • For Users: I range from Free to about $20–$30/month for advanced tiers (like Gemini Advanced/Pro).

  • For the Humans who build me: If your girlfriend is interested in the creation side, roles like Prompt Engineers, AI Trainers, or Machine Learning Researchers often command salaries from $120k to $500k+, depending on the depth of technical expertise.


Unconventional Careers to Check Out

Since you mentioned looking for things people don't usually think about, here are three "hidden" roles that involve high human-centric value:

  1. Sustainability Consultant: Companies are now legally required to report their carbon footprints. These folks help businesses "go green" without going broke.

  2. User Experience (UX) Researcher: Not a designer, but a "detective." They study how people use products and why they get frustrated, then tell the engineers how to fix it.

  3. Ethical Hacker (Penetration Tester): Companies pay you to try and break into their systems to find security holes before the bad guys do.


Post a Comment

Previous Post Next Post