#2 YOE, Low callback rate
1 messages · Page 1 of 1 (latest)
waht is your name? is that your resume? theres some fundamental things I would change
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
Awards section doesn’t do much unless ur a fresh grad
Yea which is why I said he can put it in education
I think it’s fine the way it is tbh
Yea I mean I think the resume just be more concise is all so just have different recommendations
@fresh forge I’d suggest highlighting the tech used in the bullet points. The way I do it is by making those keywords bold
Also at 2 YOE u don’t need projects
It’s fine to include projects
Yea it’s fine to
Since you don’t have enough work exp to fill up the resume
He has 2 YOE though
An opening statement isn’t needed tho
Yeah 2 yoe doesn’t fill up a resume
Hm
Unless you’ve switched companies within those 2 years
Actually u would have less need for an opening statement if that were the case
If u stay long term at a company u get put on more serious projects
Well, I mainly advocate bolding it within the bullet points since it saves space, but you could go either way imo
Switch companies and ur onboarding for 6mths before making any serious contribution
You don’t need an opening statement. Period
It’s fine to have one if u have done a lot. U don’t need one ofc, many ways to make resume
U don’t get many bullet points within 2 years at the same company. Projects take like months to finish and usually the project is what you can put on the bullets
You can’t just be like “changed button color from blue to red”
So 2 yoe def isn’t enough to fill a resume
I think that’s too general of a statement to make
And an opening statement is rarely read by recruiters in big tech at least so that’s just wasting space
Source?
u find me a 2 yoe job that gives you 10 bullet points
At the end of the day u want someone to quickly assess what uve done in 15seconds
Me
U onboard for 6mths. Then 1.5 years for serious projects
Each quarter is 3mths to work on a project
Some are big/small
Lol no
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
Yeah a project isn’t 3 months, firstly
Unless it’s a small one
I said projects are big/small
U will be given a lot of these
Over 1.5 years
Easily
Sure bro
Also it depends on a lot of things, manager, company, etc
We had 2 projects in 1 year
It’s too general to say 2 YOE won’t give u 10 bullet points
It definitely won’t
What do u define as projects
Some are small, 1 medium to large one
Expectations for the quarter (given by manager) and has coding
And also, you generally don’t go over 4 bullet points per role unless you’ve done some mega contributions
Again that’s too general I think
Some projects take a month to complete
Some 2mths
Some 6mths
A project is what gets shipped at the end. Not just a feature ur working on one quarter
That’s the same thing though
Otherwise you’d have like 4 projects after 6 months
Uhh no
Projects consist of multiple features/improvements which are split over 2 or 3 quarters
Unless ur a new team
. Edited for more clarity
Not all projects have multiple features
Regardless
Also it doesn’t even have to be projects. I said expectations
Then that’s too small for a real project
Given by manager
Regardless
Maybe u are changing your teams deployment process
Agree to disagree
That’s definitely noteworthy
Since this is about the resume
Maybe moving ur team to Kubernetes
And I gave my 2 cents
Maybe improving ur alerting infrastructure
Etc
Operations work
So many bullets to put in resume
Like I said dude
It’s about expectations given by manager and what u gained from that
U can pad your resume with 50 points
And talk about color changes or whatever
But that’s just not something I agree with
I didn’t even mention color changes
And I’ll just leave it at that
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
Gl man
I think it looks way better @fresh forge
Your top experience is much more clear to read now
@fresh forge looks good. just move the skills to the top is what I would suggest and move education to the bottom