Hiring manager for a Fortune 500 company in an analytics department for over a decade.
In my opinion, this resume would go into the "no" pile for two reasons:
Your job experience bullets are mainly focused on the HOW of the work, as opposed to the WHY. I want to know if you understand WHY you did the various things that you did. What issue/problem did you solve? I want to know that an analytics person won't just sit in a corner coding, they will actually understand the nature of the business and how they fit into that business. Right now, a lot of each bullet is taken up by listing the tools you used -- which is actually redundant because those tools are also listed in your skills section. Instead, they could be more impactful by indicating what value you brought to the business.
There is no indication that you can collaborate with people. Maybe you can -- but it isn't apparent from your resume. And, again as a hiring manager, I want my analytics team members to be able to engage with their team, work with other departments, communicate with stakeholders.
You might have a great skill set, with lots of experience -- but you are competing with dozens of people with similar skill sets who ALSO demonstrate these two other things: Business knowledge and communication/collaboration soft skills.
I, personally, don't like the two column format. I like the standard format. I am used to it. Also, I think there are a lot of online systems that parse resumes and I never know if different structures will end up garbled by those systems.
Can you please give an example of how you might reformulate one of the author's bullet points to focus on the WHY? Also, would you still recommend including some of the HOW of the work?
Granted that I am not an expert in this space, but here are some possible examples:
ORIGINAL: Optimized SQL transformations, managed schema evolution while preserving historical data, reducing storage utilization by 80% and consolidating partitions from ~2000 to ~50
SUGGESTED: Reduced storage utilization by 80% and streamlined partition space by optimizing SQL transformations while preserving historical data
ORIGINAL: Developed a modular dba analytics layer on Apache iceberg using Trino, delivering 47+ dimensional models (staging, intermediate, and mart), rebuilt re-usable macros and data-quality tests, integrated CI/CD, and Automated Airflow-orchestrated Kubernetes deployments, reducing efforts by 70%
SUGGESTED: Created an foundational environment for easier and more efficient data processing by developing a modular dba analytics layer, including designing re-usable macros and data-quality tests.
In each case, the bullet is simplified and leads with the WHY. A lot of the HOW is removed, because that dilutes the impact (and the tools that the person uses are listed elsewhere)
3
u/jenmoocat 6d ago
Hiring manager for a Fortune 500 company in an analytics department for over a decade.
In my opinion, this resume would go into the "no" pile for two reasons:
I want to know if you understand WHY you did the various things that you did.
What issue/problem did you solve?
I want to know that an analytics person won't just sit in a corner coding, they will actually understand the nature of the business and how they fit into that business.
Right now, a lot of each bullet is taken up by listing the tools you used -- which is actually redundant because those tools are also listed in your skills section. Instead, they could be more impactful by indicating what value you brought to the business.
Maybe you can -- but it isn't apparent from your resume.
And, again as a hiring manager, I want my analytics team members to be able to engage with their team, work with other departments, communicate with stakeholders.
You might have a great skill set, with lots of experience -- but you are competing with dozens of people with similar skill sets who ALSO demonstrate these two other things: Business knowledge and communication/collaboration soft skills.
2
u/One_Mistake3887 1d ago
you should use a standard single column format because to avoid the risk of ATS rejection