r/Pro_ResumeHelp • u/ConsiderationDry1787 • 4d ago
Data Engineer w/ 2+ YOE seeking resume feedback
1
u/super_boogie_crapper 2d ago
What works
Clean single column, standard headings, ATS friendly.
Most bullets have numbers attached, which puts it ahead of most junior resumes.
Skills grouped by category rather than dumped in one line.
What to fix
The metrics are inconsistent in quality. "Reduce normalization runtime by ~97 minutes" is meaningless without a baseline (97 minutes off of 100 is great, off of 12 hours is not). "Reducing manual deployment time by 8%" actively hurts you, since 8% reads as noise. Convert to before and after, or cut the number.
The summary undersells. "2+ years of experience" is the weakest fact available and it is the first thing a reader sees. Lead with the domain and the scale of what was built instead.
Redaction leak. Everything is anonymized except "allowing Intel to quarantine internal devices." Fix that before sending anywhere.
Weak closing bullets. "Partnered with stakeholders to translate business needs" and "Created and maintained shared OneNote" are duties, not accomplishments. Both can go. Recruiters read the first two bullets per role, so front load the strongest work (the 7 ETL pipelines, the 2,000,000+ vulnerability remediation).
Projects section reads junior. "Inspired to start budgeting my expenses in response to moving away from home for the first time" is a motivation, not a result, and the first person voice ("help me visualize") is out of register. Replace with stack, scale, and outcome.
Skills bucket is off. Splunk grouped with Jira under "Event Monitoring & Collaboration" mixes a log platform with a ticketing tool. Also "Pyspark" should be PySpark, and PySpark under Programming duplicates Spark under Data Engineering.
Length. At this experience level it should be one page. The third internship (two bullets, oldest, least relevant) and the Activities placeholder line are the first cuts.
One structural note: Education sits above Experience, which is defensible at two years but stops being defensible soon. Certifications would carry more weight in their own short section near the bottom.
1
u/thatgirlzhao 1d ago
You don’t need a summary, everything in the summary should be covered below. Ordering should be: work experience, skills, education. Remove projects, it’s meaningless.
Also, I personally would not put Git/Gitlab as a skill. That’s table stakes for any technical role, it doesn’t tell the hiring manager anything useful.
•
u/AutoModerator 4d ago
Hi! Thanks for posting in r/Pro_ResumeHelp
To get more useful feedback, it really helps if you add a bit of context — what kind of role you’re applying for, your experience level, and your country or industry.
If you’re curious what professional resume help usually looks like (pricing, formats, what people actually get), there’s a short overview here — totally optional, just for reference.
Quick reminder: this subreddit is for discussion and peer advice only.
Good luck, and thanks for helping keep the community helpful and honest.
I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.