How to Make a ULTIMATE Resume GUIDE That Actually Gets 5x Opportunities

and the number of ré getting filtered out in the first stage itself. Girls

typically have more aesthetic sense than us boys. We do accept that. Nothing

us boys. We do accept that. Nothing

wrong in that. But have a girl look at your resume and ask her is this ré pretty? It's not about your skills. It's

pretty? It's not about your skills. It's

not even about talking to you. Write

filtration off at the first point is painful. Today in this video I will talk

painful. Today in this video I will talk about 10 of the most brutal mistakes that I see repeating in the resume over

and over again.

Hello girls and boys how's it doing? Let

me give you something upstraight and frontal something that will hit you right in the guts. Over the course of years, I've seen thousands of DevOps,

cloud, S sur, software engineering ré and the number of réumé getting filtered out in the first stage itself. The ré

screening is ridiculously high. It's not

about your skills. It's not even about talking to you. Right filtration off at the first point is painful and you're left wondering why am I not even getting

the calls. Today in this video I will

the calls. Today in this video I will talk about 10 of the most brutal mistakes that I see repeating in the

resume over and over again. By the end of this video, you will know exactly what not to do in your resume and also what is the right way to fix all of

those mistakes as well. If you're new here, my name is Savindra Puri. I've

been in the build, release, DevOps, software engineering area for over two decades. You can check out my LinkedIn

decades. You can check out my LinkedIn profile to know more about my details.

Let's get started.

[music] [music] So the format of this video is very simple. I'll give you a sample line from

simple. I'll give you a sample line from a potential resume. Then I'll tell you the issues in that line and I'll also give you the solution for this. The way

to consume this video is also very simple. First see the video end to end.

simple. First see the video end to end.

See if you resonate with some of them.

Then once you're done watching the video, then actually take a print out of your resume or keep your resume side by

side if you're watching this on a laptop and then go line by line. Seek each of those 10 issues and if you find them in your resume, mark them. And as I'm

giving you the potential solution, create the fix in your resume right there. You would have watched this video

there. You would have watched this video twice and you would have fixed it. It is

the most important one hour that you can spend fixing your resume which will give you substantial bang for the buck. Let's

get started now with number one. So the

text in a resume worked in CI/CD pipelines for improving deployment. Now

what's the issue here? No numbers, no clarity. What the heck is improving?

clarity. What the heck is improving?

What's the lesson? Always convert

statements into measurable impact. For

example, you can word reward this into saying reduce deployment from 2 hours to 30 minutes via automated genkins or

GitHub actions pipeline serving about 50 microservices. What have you said here?

microservices. What have you said here?

You have said the tool. You have set the impact. You have set the technology

impact. You have set the technology stack. Without all of that, this

stack. Without all of that, this statement is fluff. And this is one of the most common mistakes I see in the resume. generic gan fluff no impact

resume. generic gan fluff no impact example number two the statement in the resume reads something like I'm part of an agile team migrating monolith to

micros service again what does part of mean what is exactly your contribution is that you typing documents is that you designing the architecture is that you

automating the CI/CD pipeline is that you resolving the rollbacks the value that you ad is completely invisible in

this. So potentially you can revert it

this. So potentially you can revert it saying let a threeperson team and set up automated uh uh infrastructure as code

and configuration management using terraform and anible uh reducing the deployment time from 3 hours to less

than 10 minutes. Now DevOps is almost always an individual sport played as a team. So your contribution in that team

team. So your contribution in that team matters. [clears throat] Example number

matters. [clears throat] Example number three, the statement in the resume.

Build web app using Java, Spring Boot, MySQL microservices on AWS services. What's the issue? It's

a classic list of technologies in the resume section. No link to GitHub, no

resume section. No link to GitHub, no code example, no talk of what you have actually done. Now, obviously, if you've

actually done. Now, obviously, if you've done this for an enterprise, you can't give the GitHub link, but figure out a way in which you can somehow showcase

some of your personal work also so that the hiring manager can look at some of the code that you've contributed. It

could be a personal project. It could be an open-source contribution. It could

generally be something that you made for yourself. But highlight that having a

yourself. But highlight that having a look at the GitHub repository makes sense always. But make sure there are

sense always. But make sure there are valid contributions and not three green dots in the last one year. That is more detrimental. So how do you fix this? Uh

detrimental. So how do you fix this? Uh

add a link to your GitHub. Describe the

key module that you wrote. Talk about

the test coverage. talk about how you have uh put up the CI/CD pipeline for this. All of that will add credibility

this. All of that will add credibility to your work. Example number four. I

worked on a project where I designed the architecture, handled backend services, front-end UI, client integration, yada

yada yada. What's the issue? It's too

yada yada. What's the issue? It's too

freaking detailed. You don't need that.

Hiring managers want impact, not the full screen play. Nobody's using or reading your long paragraphs. People

will just skip over it. What's the

lesson? Be condensed. Use bullet points.

Use action verbs. Use matrices. And keep

your project definitions to maximum one or two lines. That's it. Now, if any of these points is hitting you hard, type hard relate in the comments so I know

that this is making sense. Example

number five. Under the skill sections, you've been something like DevOps, agile, team player, solid contributor,

problem solver. What the heck? Issue is

problem solver. What the heck? Issue is

these are all buzzwords without any context. [music] DevOps doesn't mean

context. [music] DevOps doesn't mean anything unless you specify some tools, some impact, the work that you have actually done. Team player doesn't mean

actually done. Team player doesn't mean anything unless you show how you have contributed your part in a bigger piece.

Otherwise, this is just bull crap thrown in in the resume. What's the lesson?

Replace team player, for example, with something like collaborated with crossf functional team of eight developers. QA

and S sur to deliver monthly releases with zero critical bugs in production for 6 months. Proof of work technology

shows what you did. Example number six.

Now in the famous objective section uh I read somewhere somebody writing looking for growth in big data and DevOps rule

or something like to learn and grow in a reputed organization. Now what's the

reputed organization. Now what's the issue? These lines are like you're

issue? These lines are like you're living in 2002.

Also, the objective is generic and serves you and not the organization. You

want to work in data. You want a DevOps role. That's awesome. What about the

role. That's awesome. What about the organization? What value do you bring?

organization? What value do you bring?

What contribution can you make? So,

what's the lesson? In my humble opinion, objective for people who are less than maybe 10 12 years experience doesn't matter [clears throat]

because you all tend to have the same objective, right? It it really doesn't

objective, right? It it really doesn't make sense. If you really have less than

make sense. If you really have less than 10 years experience and you if you still want to put an objective, use that space

wisely. Use one sentence and let it be a

wisely. Use one sentence and let it be a summary of your entire resume. Maybe

something like DevOps engineer, two-year experience in Azure DevOps, AKS, same family. Keep it simple but let that have

family. Keep it simple but let that have meaning. So I know the number of year

meaning. So I know the number of year experience, your key skill, that's all I need to know in the resume. Right? Good

key summary. Now if you have less more than 10, 12, 15 years experience, use the objective again to summarize your own experience. And if you're making a

own experience. And if you're making a pivot, announce that upright right up front. So for example, you can say

front. So for example, you can say something like project manager with 15 years experience having managed three

DevOps projects in the last 2 years pivoting into technical project manager.

That makes sense because that tells me where are you coming from and what are you looking to do. So use that space to convey this kind of an objective if

you're a senior person. Okay. Example

number seven. This is very very interesting. I see this quite a lot in

interesting. I see this quite a lot in the certification section. You mention

studying for AWS certification. Even

better. I've read AWS solution architect, Terraform Associate, Hashikop Certified, CKAD, a full laundry list of certifications

which is great. But the point is okay you know some stuff you've passed the certification have you used them in the project what's your practical experience

this is all theory generic gan great if you have one or two years experience 3 years I know you have passed ckd so you have the basic knowledge good not good

enough if you've above 3 4 5 years of experience because then I need to see how you have used this in the project otherwise it's theoretical technical gan

doesn't value also if you're a fresher then you can potentially say um AWS this certification target completion date

December 2025 for a fresher with somebody with 1 2 years experience this matters this makes sense I will buy it all right now this is my favorite one

example number eight [music] now you read in the resume and I'll quote this is from an actual resume it says spearheaded the design of a multi-reion

cloud solution deafly handling scalability ensuring high availability and instrumental in major cost savings.

This is a shashi level devops engineer entering guant. Tell me some impact. Tell me what

guant. Tell me some impact. Tell me what you have done. You've just added objectives before every technology word.

That's all you've done. Too much jargon, too much gan without any clarity.

Specifically, what multi-reion? How many

regions? What was the output? What is

the cost or performance metrics? What

scale up scale down patterns? What

architectural trade-offs did you make?

You're just claiming architectural leadership without showing any context any result. How the heck does it add

any result. How the heck does it add value? How do you fix this? You could

value? How do you fix this? You could

say something like architected across two AWS regions US East one US west one solution for 50 plus

microservices achieving 99.9% uptime reducing cost region dis disaster

recovery RTO from 4 hours to 10 minutes cutting the annual infrastructure cost by 13%. that tells you a story. That

by 13%. that tells you a story. That

gives me at least three solid questions to ask you, the answers to which you already know. Now, if some of these tips

already know. Now, if some of these tips are hitting you, you can type in the resumeumé. What did I say? Hard relate,

resumeumé. What did I say? Hard relate,

hard hit, something like that. Type in

the comments so I know this is making sense to you. Okay. Example number nine.

The in the achievement section you write participated in hackathon attending a 3-day AWS boot camp. It's great you are

a proactive person but what is in it for me as a recruiter for a hiring manager [music] doesn't give me anything.

Convert these into outcomes. Recruiters

often see this as filler content.

So how do you revert this? You say

ranked in the top three at XYZ hackathon. Uh developed a containerized

hackathon. Uh developed a containerized app using AWS Lambda to do this or you say completed a 3-day AWS boot camp

built and deployed an AWS hosted static website as part of this. So you're no longer a participant. You are a doer.

You have spoken about what you've done.

And if it's a hackathon, if it's a boot camp, you better have the code linked on GitHub because this is public code.

Number 10, and this is completely my personal opinion, but this is something that really, really puts me off in a rum. Two things. Number one, typo

rum. Two things. Number one, typo errors. Nothing is more terrible in a ré

errors. Nothing is more terrible in a ré than typo errors. Here is what it tells me when I see a spelling mistake in a resume. Number one, you do not care

resume. Number one, you do not care about your work. Number two, I cannot depend on you when I give you a work.

Hence, number three, why should I even bother interviewing you? That's one goes in my head in less than 1 second whenever I spot a spelling mistake in

the resume. What's the lesson? run the

the resume. What's the lesson? run the

damn spelling checks. As simple as that.

Invest that time. Number two in this people off is lack of formatting in a resume. You look at your resume for 1

resume. You look at your resume for 1 second and you don't even feel like reading the damn thing. It looks like a blob of text thrown on paper. How

[snorts] do you fix this? First, let me give you a quick test to figure out if you formatted your resume well or not.

put it in a PDF and zoom out so that you can see the whole page. Now, when you see the whole page, you might not be able to read the text. That's fine. But

just visually look at it. Does it look pretty to you? Now, if your answer is obviously yes, then you've already failed the test. Get a girl to look at

the resume. Girls typically have more

the resume. Girls typically have more aesthetic sense than us boys. We have to accept that. Nothing wrong in that. But

accept that. Nothing wrong in that. But

have a girl look at your resume and ask her, "Is this ré pretty?" And she will tell you honestly. Make the changes. Use

AI formatterers. Don't go fancy over the top. Keep it simple, but keep it

top. Keep it simple, but keep it elegant. But invest time in formatting

elegant. But invest time in formatting your resume completely. It should

visually look interesting for me to read it. and pick out one thing that will

it. and pick out one thing that will stand out in your resume which you have not seen any of your peers do it. It

could be anything. I'll give you an idea on the skills. Some people put a number graph, some people put a scale, right?

So, terraform is eight, then anible is nine. So, they put a scale on top of it.

nine. So, they put a scale on top of it.

Something little different. In one

resume I have seen for a senior guy that guy put a pie chart on how I spend my time. So 30 40% of my time goes in

time. So 30 40% of my time goes in meetings, 10% in one-on- ones, 2% 15 20% talking to customers, designing solution. It's a beautiful way in which

solution. It's a beautiful way in which I can get in 30 seconds what are the five things that you do in a day. Do

something different. One piece, one section of your resume should visually stand out. Think about it. Search for

stand out. Think about it. Search for

different kinds of résumé. It's worth

putting in the time and the effort. Hope

this video made sense. I'll see you in the next one.