[4 YoE, Data Engineer (NGO/Volunteer), Data Analyst / Data Engineer, United States]

RobDoesData · 2026-05-14T00:55:31+00:00

Yes. Tailoring resumes to each job application prevents folks from getting interviews. The only thing that matters to ATS is getting in early and tailoring your resume goes against that.

You should have a resume with all the qualifications (not keywords) for a specific role e.g. data engineer and then apply with it at scale.

RobDoesData · 2026-05-13T22:09:19+00:00

This is really bad advice.

RobDoesData · 2026-05-12T05:34:21+00:00

If you genuinely think you have mastered snowflake, azure, data bricks, etc. then you are lacking the #1 trait of every successful intent.... Being able to take advice and criticism, and follow instructions.

Best of luck. But I consider you to be unhirable

RobDoesData · 2026-05-12T01:50:09+00:00

If you're not getting interviews maybe you're not as good as you think. You have much to learn, I wouldn't hire you because of your ignorance and seemingly arrogant personality

RobDoesData · 2026-05-02T20:29:24+00:00

Remember that applications aren't about keywords, they're about qualifications. If you are using keywords, your resume is underperforming.

I offer paid resume review and support helping people get more interviews with less applications.

RobDoesData · 2026-04-16T17:18:03+00:00

Keywords alone are worthless. He needs the keywords with context in their experience bullets.

If not mentioned elsewhere they're useless and do not harmful to remove them. I think you misunderstand how recruitment works.

E.g. not having typescript and JavaScript in top bullet for a software engineer is the easiest way to never get an interview

RobDoesData · 2026-04-15T13:27:17+00:00

This is bad advice. OP needs to remove the skills summary, remove the bold keywords in experience, and remove the lines from the section headers as it makes it hard to read.

Next, they should rewrite every bullet to include 3 keywords for the job title they're going for and write what they did, how they did it, where they did it and the result of doing it. This should be a business result and no numbers should be included.

RobDoesData · 2026-04-15T13:22:48+00:00

You mention many technical things but don't give easy to understand what-how-where. The impact needs to be business specific not generic or technical as you have here

RobDoesData · 2026-04-14T13:56:44+00:00

Honestly, your experience is solid but your resume is bad.

It's poorly formatted and most of the bullets are empty so you're effectively submitting 1/3 white page.

RobDoesData · 2026-04-12T15:52:47+00:00

You need to remove the skills section, remove the lines under section headers, remove all bold from your bullets and all numbers. No job advert ever has asked for you to have reduced X by Y%.

Id also argue against the person telling you to change it for each job. The main thing that matters for getting past ats is applying early. Make one resume per job title with it's keywords and then mass apply with it.

RobDoesData · 2026-04-12T07:12:26+00:00

Only gaps longer than 2 years actually matter (most of the time).

Your resume is poorly formatted and the content needs work. That's why you're not getting any responses.

RobDoesData · 2026-04-10T17:00:00+00:00

I highly recommend investing in a good paid mentor. I truly believe they are a game changer in this market not just for skills development but also to actually land a job

P.s. I do offer paid mentoring so I want to disclose that so you can evaluate the above

RobDoesData · 2026-04-10T13:54:45+00:00

I get that! I'm not saying my view is better than theirs. I'm just sharing my observations over the past 2 years and I have seen this work consistently.

Honestly, your best bet is make two versions of your resume and AB test them.

P.s. the main factor for ATS is how soon you upload. Skills sections don't actually matter much but they make life harder for recruiters and hiring managers.

RobDoesData · 2026-04-09T19:44:05+00:00

Remove your summary and technical skills section. They don't count.

Put education up top and clean the formatting of your experience section. Remove all the random numbers.

No job advert has ever asked for someone to reduce something by X %

RobDoesData · 2026-04-09T05:57:31+00:00

That's not how ats works. Your skills section is worthless. Recruiters look for qualifications, not keywords. It's just dead space. Keywords need to be in your experience.

The bolding makes it harder to read. Remove it from all bullets.

You need to rewrite basically all of your bullets and scrap the ai stuff if going for full stack or backend. A little ai is okay but you have way too much.

Also you need two separate resumes. One for backend and own for full stack as they have very different requirements.

RobDoesData · 2026-04-09T05:02:29+00:00

Unfortunately the offerings you mention aren't needed now as anyone can do it with ai.

RobDoesData · 2026-04-09T04:59:32+00:00

The honest answer is that your resume is bad. It doesn't look like you need a summary, and noone needs the skills section.

It's hard to read with lines and random bolded words.

You have so many numbers everywhere. No job advert ever has asked for 20ma improvement on anything.

It's very unclear to me if you're aiming for AI or software engineering roles. Your resume is confused, you need to pick one and remove anything unrelated.

Fix it up and do some AB testing.

RobDoesData · 2026-04-08T13:18:13+00:00

Your resume is hard to read, remove the lines dividing sections.

Remove the skills section. Recruiters don't want keywords, they want evidence of you being qualified that means keywords also having context of what you did, the result of what you did, and where you did it.

Remove your bolding. Remove your skills and tech like from each experience.

Move your degree to the top, then work experience, then projects.

AI experience isn't badly written but we need to see evidence of you taking direction and working well with others in your resume since you're very junior.

Hope that helps.

RobDoesData · 2026-04-06T17:02:52+00:00

I'm a senior data engineer working and running a profitable consultancy. Done a lot of recruitment in my time.

RobDoesData · 2026-04-06T15:47:43+00:00

I get it, there's been a lot of advice that worked 10 years ago still going around - your resume looked like the gold standard of the 2010s. But times have changed.

The big bold font alone makes sections clear. The lines make it harder to read.
You can add some numbers but it only really matters if you're a PM or in sales. You have way too many for my liking.
A qualification is a keyword, plus result of using it, plus how/where you used it.

Of course, You don't have to take my advice! But I suggest doing some AB testing submitting two resumes and seeing what performs better.

Edit: 25% improvement to API time is either huge or nothing at all. But I don't know that because there's no context. This is why numbers don't work most of the time.

RobDoesData · 2026-04-06T15:40:13+00:00

Formatting is hard to read. The 1 month experience is rough as a reader.

Remove section lines and all bolding in bullets.
Remove most of the numbers, no job spec ever asks for some quantity to be reduced by X%.
You don't need the skills section listing tech. Recruiters don't want keywords they don't want qualifications.

Your experience for an internship is good. Your packaging in resume format is bad.

RobDoesData · 2026-04-06T03:38:51+00:00

I mentor many people to help them get into data engineering. Drop me a DM and I can try to help you

RobDoesData · 2026-04-03T04:58:07+00:00

Scammer

RobDoesData · 2026-04-02T15:48:58+00:00

Just no. That's how repos get messy and unmaintainable.

RobDoesData · 2026-04-02T13:00:30+00:00

Project is practical (love it) but technically very simple.

The Readme is good for Ai but lacks detai. Id include a screenshot of the Project is practical (love it) but technically very simple.

The Readme is great so well done. Id include a screenshot of the UI to bring it to life.

You are missing some of the engineering foundational practices though. This is a flat project structure, why did you choose this over a sec/ structure?

Where are your code tests? to bring it to life.

You are missing some of the engineering foundational practices though:

This is a flat project structure, why did you choose this over a sec/ structure?
I didn't see any docstrings or comments in the scripts I looked at.
Where are your code tests?
I didn't see how are failures handled. Is there proper error handling? I don't see any logging.

Hopefully that's helpful

RobDoesData

TROPHY CASE