#2 YOE, Low callback rate

1 messages · Page 1 of 1 (latest)

unique citrus
#

yoo I see

#

waht is your name? is that your resume? theres some fundamental things I would change

woven cloak
#

I would be less descriptive with bullet points

#

And since ur at 2 YOE you can have a opening statement just explaining your experience maybe in more detail.

#

U can also get rid of ur projects

#

I don’t think u need that anymore

#

Also the project b is cool, u can probably just have that under awards section

#

U don’t need to say what the project was fully

#

Like the first bullet point of project b is fine. U can put that under education

#

Have a bullet point specifically for technologies used

#

I see u have technologies used in bold

#

Maybe have that as bullet point instead to group everything

#

Everything before mentioning snowflake is fine

#

U should leave out the finer details

#

That’s something u can say in an interview I think

#

Just saying Optimizing database schema seems kinda vague

#

Basically just keep everything that measures impact. Everything else cut out

#

And also add an opening statement if you want to give more insight into what you have done over the past 2 years

#

That’s another way to filter down the bullet points

#

Lastly, maybe add a separate bullet point for technologies used for each experience u have had

past hawk
woven cloak
past hawk
woven cloak
past hawk
#

@fresh forge I’d suggest highlighting the tech used in the bullet points. The way I do it is by making those keywords bold

woven cloak
#

Also at 2 YOE u don’t need projects

past hawk
#

It’s fine to include projects

woven cloak
#

Yea it’s fine to

past hawk
#

Since you don’t have enough work exp to fill up the resume

woven cloak
#

He has 2 YOE though

past hawk
#

An opening statement isn’t needed tho

past hawk
woven cloak
past hawk
#

Unless you’ve switched companies within those 2 years

woven cloak
#

If u stay long term at a company u get put on more serious projects

past hawk
#

Well, I mainly advocate bolding it within the bullet points since it saves space, but you could go either way imo

woven cloak
#

Switch companies and ur onboarding for 6mths before making any serious contribution

past hawk
woven cloak
past hawk
#

You can’t just be like “changed button color from blue to red”

#

So 2 yoe def isn’t enough to fill a resume

woven cloak
past hawk
#

And an opening statement is rarely read by recruiters in big tech at least so that’s just wasting space

past hawk
woven cloak
#

At the end of the day u want someone to quickly assess what uve done in 15seconds

past hawk
woven cloak
#

Each quarter is 3mths to work on a project

#

Some are big/small

past hawk
woven cloak
#

Ull be doing multiple projects at once

#

Yea like u will have multiple expectations given each quarter

#

Ur not just working on one thing for 9 straight mths

#

Just not how that works

past hawk
#

Unless it’s a small one

woven cloak
woven cloak
#

Over 1.5 years

#

Easily

past hawk
woven cloak
#

Also it depends on a lot of things, manager, company, etc

past hawk
#

We had 2 projects in 1 year

woven cloak
#

It’s too general to say 2 YOE won’t give u 10 bullet points

past hawk
#

It definitely won’t

woven cloak
#

I’ve had like 4 over the past 9mths

#

And have been given 2 more this quarter

past hawk
#

What do u define as projects

woven cloak
#

Some are small, 1 medium to large one

woven cloak
past hawk
#

And also, you generally don’t go over 4 bullet points per role unless you’ve done some mega contributions

woven cloak
#

Again that’s too general I think

#

Some projects take a month to complete

#

Some 2mths

#

Some 6mths

past hawk
woven cloak
past hawk
#

Otherwise you’d have like 4 projects after 6 months

past hawk
woven cloak
#

Ur not making endless services

#

Ur always modifying existing code

past hawk
#

Projects consist of multiple features/improvements which are split over 2 or 3 quarters

woven cloak
#

Unless ur a new team

past hawk
#

. Edited for more clarity

woven cloak
past hawk
#

Regardless

woven cloak
#

Also it doesn’t even have to be projects. I said expectations

past hawk
woven cloak
#

Given by manager

past hawk
#

Regardless

woven cloak
#

Maybe u are changing your teams deployment process

past hawk
#

Agree to disagree

woven cloak
#

That’s definitely noteworthy

past hawk
#

Since this is about the resume

woven cloak
#

Maybe moving ur team to Kubernetes

past hawk
#

And I gave my 2 cents

woven cloak
#

Maybe improving ur alerting infrastructure

#

Etc

#

Operations work

#

So many bullets to put in resume

past hawk
#

Like I said dude

woven cloak
#

It’s about expectations given by manager and what u gained from that

past hawk
#

U can pad your resume with 50 points

#

And talk about color changes or whatever

#

But that’s just not something I agree with

woven cloak
#

I didn’t even mention color changes

past hawk
#

And I’ll just leave it at that

woven cloak
#

U don’t think deployment process, alerting infra is important?

#

Also not all projects have multiple features. Some can just have a few that can be completed within a few mths. Just depends

past hawk
#

Gl man

woven cloak
#

I think it looks way better @fresh forge

#

Your top experience is much more clear to read now

past hawk
#

@fresh forge looks good. just move the skills to the top is what I would suggest and move education to the bottom