#Mid/Senior AI/ML Engineer

68 messages ยท Page 1 of 1 (latest)

proud ocean
#

I put "mid-level" too but i'm mostly getting reached out for Senior level

#

and yes I am going for traditional 1in margins instead of less, looks better for a 2-pager (not like margin matters in the long run ik)

slim ruin
#

2 pager with only a few years of experience means most of your content will be ignored, focus on presenting all the high value info in a single page

#

Any bullet that is more than 2 lines = too long, hard stop

proud ocean
#

almost 5 years now, I am not actively applying it's mostly to be sent to recruiters that reach out

slim ruin
#

Almost no metrics

proud ocean
#

like numbers?

slim ruin
#

april 2022 -> present = 3.5 years, not 5

proud ocean
#
  • intern
#

i guess that doesn't matter

slim ruin
#

internships don't count towards yoe

proud ocean
#

fair

slim ruin
#

focus on adding impactful metrics with more concise language, your bullets are all way too long and don't come off very impactful

proud ocean
#

Personally I heard really conflicting stuff about metrics, I lean more to agree that adding numerical metrics don't make sense

#

they care more about understanding what you do too

slim ruin
#

you should be able to find something for basically every bullet

proud ocean
#

hmm

#

I'll review

slim ruin
#

example, your "produced graphs..." essentially useless, you're not a data analyst, focus on what the impact of those presentations was

proud ocean
#

That's the latter part but yeah it's way too long

#

I'll focus on the impact before saying what i do for that one

slim ruin
#

No, what I'm saying is, no one cares you produced some graphs for leadership, what will make them care is the outcome of presenting to leadership

proud ocean
#

makes sense

#

I specificially added this due to the job postings that i was targeting were mentioning stuff like this for AI/ML eng

#

it's a datasci/data analyist point but it was mentioned within the postings

slim ruin
proud ocean
#

I'll rephrase it and comment it out if not mentioned within a position

slim ruin
#

I'm saying reframe around the actual leadership presentations

proud ocean
#

Yeah my bad, rephrase wasn't the right term

#

rework*

slim ruin
#

Another example, your first bullet, what was the impact of that work? What did you drive by using ML and AI on those datasets? Is there a metric you can pull out here?

#

"Pioneered internal..." can you provide a metric on volume of data you enabled to be processed?

proud ocean
#

Good points

#

I'll think of metric/impact

slim ruin
#

seems like you got a lot of good experience buried behind too generic phrasing

proud ocean
#

Maybe i went too generic

#

My previous resume was more impact and metrics but after hearing conflicting takes from recruiters I decided to go for this way

#

like I had a lot of metrics that don't matter basically

#

I think I'll add where i can find something actually impactful

#

mix of both

#

Thanks for your feedback still

slim ruin
#

my rule of thumb is:
If it's implementation work I need to have a good metric, sometimes using a business outcome instead of a technical one
If it's architectural work I prefer to have a metric but often it can stand on it's own

proud ocean
#

fair

slim ruin
#

As someone who does team match interviews and reviews resumes that side, I'd rather see 4-5 bullets where I can get a clear idea of their impact than a laundry list of ambiguous tasks

proud ocean
#

Yeah me too personally

#

Issue is idk what a recruiter might want

#

Ik what the hiring manager wants to see

#

but when it comes to recruiter, idk ๐Ÿ’€

#

guess I need to keep both in mind, balancing act

#

at the same time I saw applicant resumes that were just metrics and 90% of them did not matter and were just filler for metrics sake and i hate those ๐Ÿ’€

slim ruin
#

recruiters like metrics too, even if they don't fully understand them

proud ocean
#

it's really a balancing act after all

#

I didn't use this resume at all btw it's still in preproduction

slim ruin
#

yeah, bad metrics aren't helpful, might need to lean into business context rather than technical

proud ocean
#

Good feedback fam, thanks i'll reply when i update

slim ruin
#

awesome, good luck

manic wren
#

I agree, too long bullets

proud ocean
#

appreciate y'all i did some edits

#

but idk if i should start a new thread

#

for the bullet points.. I can't get them much shorter

#

i updated margins back to 0.5inches

#

back to 1 page

#

omitted "skills" section as I already mentioned all the relevant skills/stack/etc in bullet points

#

afaik that section is:
ignored best case
hurts you worst case

#

issue with some points where i mention libraries

#

had to repost a few times cuz of wrong version soz

proud ocean
proud ocean
#

@upbeat jetty