I've Reviewed Enough Developer CVs. Here's What Made Me Immediately Close Them

Let me be honest with you.Most developer CVs I receive don't get rejected because the candidate isn't good enough.They get rejected because the CV tells me, before we've even spoken, exactly what kind of developer this person is going to be to work with.And most of the time? That's not a good sign.I've reviewed a lot of CVs — juniors, seniors, full-stackers, specialists. I've hired some, skipped most, and regretted a few on both sides. Here's every single thing that made me close a CV within 30 seconds, ranked roughly from most to least common.1. "Proficient in: HTML, CSS, JavaScript, React, Node.js, Python, Django, Flask, Java, Spring Boot, Kubernetes, Docker, AWS, GCP, Azure, Figma, Photoshop, SEO, and Excel."This isn't a skill section. This is a confession.Either you copy-pasted every buzzword you've ever heard in a YouTube tutorial, or you genuinely believe that watching a 4-hour crash course makes you "proficient."Neither is a good look.Real developers know what they don't know. When I see a CV with 30 technologies listed at the same skill level — with no context, no depth, no project to back them up — I assume you know approximately nothing about all of them.Pick your stack. Own it. Drop the rest.2. The "Experience" section that's actually just a job description."Responsible for developing web applications using React and Node.js."Okay. And? What did you actually do? What did you build? What broke and how did you fix it? What decision did you make that mattered?Nobody cares that you were responsible for something. Responsibility is the minimum threshold for employment. I want to know what you delivered."Reduced API response time by 60% by migrating from REST polling to WebSockets" tells me more about you in one sentence than three bullet points of job-description language ever could.3. Lying about seniority.I've interviewed "Senior Developers" who couldn't explain the difference between a LEFT JOIN and an INNER JOIN without Googling it.I've interviewed "Mid-level" candidates who'd independently built and deployed full production systems, handled traffic spikes, debugged memory leaks in prod at 2am, and taught junior devs the next morning.The title you give yourself on your CV is a promise. When your interview doesn't match that promise, you haven't just wasted my time — you've burned any shot at a second conversation.4. No Date of Birth. Because Apparently That's "Modern" Now.Let me tell you where this trend came from — because most people just follow it without knowing.The push to remove date of birth from CVs started in the UK with the Equality Act of 2010, then spread across the US, Australia, Canada, and eventually Western Europe. The argument was simple: employers might discriminate based on age, so let's remove the data point. HR consultants picked it up, career coaches turned it into gospel, and now it's treated as a universal law of professionalism.I disagree. And here's why.Your date of birth is context. When I see that a developer built their first production system at 22, that tells me something. When I see that someone is 40 years old with 6 years of experience, that tells me a completely different story than a 28-year-old with the same 6 years — and both stories matter. Not because I'm going to discriminate. Because I'm trying to understand who you are.The "remove your DOB to avoid discrimination" argument is well-intentioned but it solves the wrong problem. If a company would reject you because of your age, removing the date of birth doesn't protect you — it just delays the discovery by one interview round. You haven't avoided the discrimination, you've just made yourself invisible slightly longer.And practically speaking: hiding your age doesn't make you ageless. I can calculate it from your graduation year. Anyone can. So the protection is largely theatrical.Include your date of birth. Own your timeline. If a company has a problem with it, that's information you want to know early — not after you've invested three rounds of interviews.5. "Team player. Hard worker. Fast learner. Detail-oriented."This section is useless. Completely, entirely useless.Every single candidate writes this. Every single one. Including the ones who showed up late to their interview, submitted broken test tasks, and then asked me where they can "learn what they need on the job."These phrases say nothing because everyone claims them and nobody proves them in a CV. Use that space for something that actually differentiates you.Or just delete it. Seriously. Delete it.6. Formatting that belongs in 2008.Times New Roman. Walls of text. No hierarchy. No whitespace. Three different font sizes for no reason. Tables that don't align. A photo in the corner that looks like it was taken on a Nokia 3310.You're applying for a job in technology. Your CV is a product you're shipping. It is, literally, the first piece of work I see from you.If you can't design a clean, readable, professional one-page document — or at least Google a template that does — I start to wonder what your pull requests look like.7. Gaps with no explanation.I don't care that you took six months off. I genuinely don't. Life happens. Burnout is real. Family situations are real. Personal projects are real.What I do care about is when that gap sits there on your CV, unexplained, like a black hole. Because then I start filling it in with my own assumptions. And my assumptions are not charitable.One line. That's all it takes. "Career break — personal project / freelance work / family care / learning sabbatical." Done.8. Applying for a role that's nothing like what you've done.This one stings because I actually feel bad closing these CVs.You've spent three years doing WordPress theme development and you're applying for a senior backend engineering role building distributed systems in Go. That's not a career pivot — that's a different career.I respect ambition. I respect people who want to grow. But your CV needs to show me the bridge — the side projects, the courses completed, the open source contributions, the personal systems you've built — that connects where you are to where you want to be.Without that bridge, I can't take the leap with you.What Actually Makes Me Stop and Read?Since I've been harsh, let me be useful.The CVs that genuinely made me pause — and that led to hires I'm still grateful for — had a few things in common:They told a story. Junior → mid → senior wasn't just a timeline, it was a progression you could feel through the work described.They showed judgment. "We chose PostgreSQL over MongoDB because our data relationships were complex and consistency mattered more than flexibility" — that one line told me more than five years of job titles.They were honest about gaps and weaknesses. Nothing builds trust faster than a candidate who says "I haven't worked with Kubernetes in production, but here's how I've been learning it."They had something real. A GitHub that's actually alive. A blog. A side project with real users. A talk they gave at a meetup. Something that showed me this person cares about what they do beyond their 9-to-5.The Uncomfortable TruthThe best developers I've ever worked with had mediocre CVs.Because they were too busy building things to polish their personal marketing.So if you're one of those people — please, for the love of all that is holy, spend two hours this weekend on your CV. You're competing against people who are much better at looking good than being good. Don't let that beat you.And if you're one of the people who has a beautiful CV but a shallow GitHub — maybe spend that same two hours writing some actual code instead.ITI-X is a software engineering and consultancy company based in Skopje. We build products, lead teams, and occasionally tell uncomfortable truths on the internet.If you want to work with us, we'd love to hear from you.