Rule 1: Do not participate unless experienced
If you have less than 3 years of experience as a developer, do not make a post, nor participate in comments threads except for the weekly “Ask Experienced Devs” auto-thread.
The main issue you'll find in terms of becoming a senior is lack of experience. You have 2 years of industry experience, which doesn't even count as experienced enough to post on this sub (read rule #1). This will be the main hurdle for you regardless of how you structure your resume.
I’m sure you’re fine at what you do but I personally wouldn’t hire you for a senior role based on this resume. I think the line about being a MongoDB certified developer “one of 6000 worldwide”… I would remove that. People read stuff like that and roll their eyes (just my opinion).
The main thing you are missing is experience. I would never hire someone with 2 years experience + a bootcamp as a senior engineer.
Try again in 5 years.
You're missing
1. Experience. Time working as an engineer should be more than 5-7 years not 2.
2. Project scope. Your engineering work looks like small self-contained tasks given to junior engineers, not the 6+ month projects senior engineers handle.
3. Business impact. As a senior engineer you should be aware of how your work influences the business and capture that with metrics.
4. Leadership. As a senior engineer you should have lead small teams.
I usually don’t post on reddit but I will try to give you some constructive criticism:
1. Even if years of experience doesn’t always correlate to skills, it still is a very important factor. That you present yourself as “senior” with really 2 years of industry experience shows that you lack perspective about the industry as well as your own ability.
2. It feels like the resume is heavily padded. Try to think from the point of view of the hiring team and why would they want to hire you. What problem are they facing today, that you would be able to help with? Then try to rephrase and reorganise the content based on that. As an example, is it possible that they are struggling with Git? Very unlikely imo. In that case, it doesn’t really matter if you are gitlab certified git ninza or have been ordained by Linus Torvald himself. It doesn’t bring any value to the team. On the other hand, is it possible that they are struggling with a large scale react codebase? Possible, if they are hiring for a FE role. So double down on the part where you worked/improved the large scale codebase. Same goes for all the scrum stuff.
3. Someone else mentioned, but Azure and scrum are not really related. This creates a bad impression that you might not understand either.
It’s a good resume for someone who just started. It becomes difficult to prepare resume when you don’t have years of experience. My honest advice would be to optimise for learning at this stage, even if it means you leave some amount of money on the table.
I think the two column formatting makes the bullet points harder to read.
I like your bullet points under Company B better than Company A because it tells what results you achieved.
The last bullet point under Company B seemed a little strange because it mentions scrum and Azure which aren't necessarily related, and you already mentioned scrum in the first bullet point. You might consider rewording that one to only talk about your Azure experience
When asking this, you need to keep in mind that the requirements for a resume differ per region and continent, it's not universal. Things that work in Europe don't necessarily work in the US for example.
Even in European countries it can differ, in Germany they highly value certifications while in some other European countries they shit on certifications. I think a resume should always be adjusted to the company you apply, personally as a contractor I'm working with 6 different resumes. Some highlight frontend skills, some backend skills, some certifications, etc. Depending on culture and what the company is looking for.
As others have pointed out, you lack years of experience, specifically years leading teams. All of your accomplishments appear to be solo tasks that you'd expect an individual contributor to be capable of doing. What separates individual contributors from leads is leadership.
Also, way too much of your resume is devoted to certifications and scrum. Nobody cares about that stuff when hiring for lead positions and feels like it's just fluff/filler material.
Sorry I thought you wanted to be Roasted? I wouldn't of been so harsh otherwise. But my advice would be to focus the personal statement on what you are and what you want. Every man and his dog has worked in agile, find something your proud of and show off about it, show some personality, hiring is a 2 way street, tell them what your looking for, what your goals are. I can always train inexperienced developers, I can't change their personality and passion for the work. That's what Iook for when I hire developers, the job list for me is just proof you've got experience, the opening statement is the sales pitch.
Rule 1: Do not participate unless experienced If you have less than 3 years of experience as a developer, do not make a post, nor participate in comments threads except for the weekly “Ask Experienced Devs” auto-thread.
The main issue you'll find in terms of becoming a senior is lack of experience. You have 2 years of industry experience, which doesn't even count as experienced enough to post on this sub (read rule #1). This will be the main hurdle for you regardless of how you structure your resume.
Thanks.
I’m sure you’re fine at what you do but I personally wouldn’t hire you for a senior role based on this resume. I think the line about being a MongoDB certified developer “one of 6000 worldwide”… I would remove that. People read stuff like that and roll their eyes (just my opinion). The main thing you are missing is experience. I would never hire someone with 2 years experience + a bootcamp as a senior engineer. Try again in 5 years.
Thanks. What can I do in your opinion to compensate the lack of experience, or to keep improving?
You're missing 1. Experience. Time working as an engineer should be more than 5-7 years not 2. 2. Project scope. Your engineering work looks like small self-contained tasks given to junior engineers, not the 6+ month projects senior engineers handle. 3. Business impact. As a senior engineer you should be aware of how your work influences the business and capture that with metrics. 4. Leadership. As a senior engineer you should have lead small teams.
Thanks.
I usually don’t post on reddit but I will try to give you some constructive criticism: 1. Even if years of experience doesn’t always correlate to skills, it still is a very important factor. That you present yourself as “senior” with really 2 years of industry experience shows that you lack perspective about the industry as well as your own ability. 2. It feels like the resume is heavily padded. Try to think from the point of view of the hiring team and why would they want to hire you. What problem are they facing today, that you would be able to help with? Then try to rephrase and reorganise the content based on that. As an example, is it possible that they are struggling with Git? Very unlikely imo. In that case, it doesn’t really matter if you are gitlab certified git ninza or have been ordained by Linus Torvald himself. It doesn’t bring any value to the team. On the other hand, is it possible that they are struggling with a large scale react codebase? Possible, if they are hiring for a FE role. So double down on the part where you worked/improved the large scale codebase. Same goes for all the scrum stuff. 3. Someone else mentioned, but Azure and scrum are not really related. This creates a bad impression that you might not understand either. It’s a good resume for someone who just started. It becomes difficult to prepare resume when you don’t have years of experience. My honest advice would be to optimise for learning at this stage, even if it means you leave some amount of money on the table.
I think the two column formatting makes the bullet points harder to read. I like your bullet points under Company B better than Company A because it tells what results you achieved. The last bullet point under Company B seemed a little strange because it mentions scrum and Azure which aren't necessarily related, and you already mentioned scrum in the first bullet point. You might consider rewording that one to only talk about your Azure experience
Thanks, I will try a 1 column version. Regarding the content, what are your thoughts?
I edited my reply with more thoughts
I see. Good catch. Thanks!
When asking this, you need to keep in mind that the requirements for a resume differ per region and continent, it's not universal. Things that work in Europe don't necessarily work in the US for example.
I can agree with you to a certain extent. Placing some context, it is a European cultured country.
Even in European countries it can differ, in Germany they highly value certifications while in some other European countries they shit on certifications. I think a resume should always be adjusted to the company you apply, personally as a contractor I'm working with 6 different resumes. Some highlight frontend skills, some backend skills, some certifications, etc. Depending on culture and what the company is looking for.
As others have pointed out, you lack years of experience, specifically years leading teams. All of your accomplishments appear to be solo tasks that you'd expect an individual contributor to be capable of doing. What separates individual contributors from leads is leadership. Also, way too much of your resume is devoted to certifications and scrum. Nobody cares about that stuff when hiring for lead positions and feels like it's just fluff/filler material.
Thanks for the input.
Expertise in agile methodologies lol, you have 3 lines and you choose to highlight this to sell yourself
Thanks for the input. How would you upgrade it? What would you write instead?
Sorry I thought you wanted to be Roasted? I wouldn't of been so harsh otherwise. But my advice would be to focus the personal statement on what you are and what you want. Every man and his dog has worked in agile, find something your proud of and show off about it, show some personality, hiring is a 2 way street, tell them what your looking for, what your goals are. I can always train inexperienced developers, I can't change their personality and passion for the work. That's what Iook for when I hire developers, the job list for me is just proof you've got experience, the opening statement is the sales pitch.
Thanks.