Want me like that?

I'm an ex Google Tech leap and it is my coffee time now.

Recently, I have been reviewing a number of resumes as part of my course tech interview pro dot com Check it out if you're interested in interview training, but I have been looking at all of your resumes, and most of them are pure garbage.

And I just wanted to make this video to set you guys straight.

When you apply for a top tier tech company like a faint company, you really want to make sure that your resume is in tip top shape and they just give you the best possible chance possible.

I would definitely not underestimate how difficult it can be to get into some of these companies.

You're going to want everything you can going for yourself.

And if you make a silly mistake and you get yourself rejected at that resume stage that you've just blown your whole chances, I'm here to give you some of my top tips on how you can get your resume in shape.

Today I have some brownies here.

They're pretty good.

I'll have a link for these in the description below, if you're interested.

This video, by the way, is brought to you by brilliant outwork.

Slash Tack lied every day.

Brilliant publishes daily challenges that provide a quick and fascinating view into math, science, logic, engineering or computer science.

As an example.

In the past month, tens of thousands of people have calculated the chance of rain just by looking at the clouds.

If you like the concept and want to learn more, there's a four interact, of course, on each of these daily challenges, and if you want to learn on the go or if you're on the flight or in an area with spot the Internet connection Brilliance I was and Andrew adapts provide full offline access so you can continue learning.

So to support, tack lied and get unlimited access to brilliance.

Daily challenges and interactive courses head on over to brilliant outward slash tech lead get 20% off for the 1st 200 subscribers.

All right, so the first tip I have for you is what I call the 12th rule.

Think about 10 seconds, maybe 20 seconds or so, and just glance over your resume really quickly.

pretending that you know nothing about the technology's order words that you're using and take a look at that and think about what picture doesn't paint about this person.

You know, I've seen somewhere is a maze where I take a quick look and just says the words cofounder everywhere.

And when I look at that, I just think to myself, Is this prison really qualified to be a software engineer?

If it seems like they're trying to be a co founder?

So I would recommend that you think about the road that you're trying to go for, and then you target your resume to apply for that specific road.

The other thing is, I see some people, their descriptions, the verbs that they're using aren't targeted for suffer engineering, if that's where you're going for.

For example, I saw resume where someone said that they managed something.

Then they developed a terra form, which I don't know what that is, and then they reviewed and rewrote something.

So when I see something like that, it's like, OK, you managed, you develop the one thing and then you reviewed and rewrote something.

Those are not really key words for software development.

So, for example, for a software engineering resume, I would expect to see words like Develop something.

Something in Python, Java C++ created something, something built, something, something implemented something.

That's the key words that I'm looking for here.

But if it's just like Managed managed, the CEO reviewed something, wrote some documentation, tested something, led something, maybe even supervised something guided something None of those verbs are really came in on that trade that I'm looking for for this specific role, which is, say, development not the second tip I have for you is to really focus in your resume and target it to the role at hand that you're trying to apply for.

Like most people, all of us have many different skills.

I've seen some resumes where people say that they're good at painting.

They may list side skills like photo shop.

They'll be premier video editing, maybe some three D modeling.

If you're a cook, maybe you can say you're a chef, but none of that is really relevant.

Red.

Just because a company happens to have chef and cook for the employees doesn't mean that if you happen to have that skill that it would be somehow useful for the company.

That's not where you expect to do that right.

That's not the role you're going for.

And if you have a bunch of other random even say software development skips, let's assume you're a plane for suffer engineering.

You may have a bunch of skills and say, Lynn Nix, html CSS.

But if you're applying for, say, an android Java engineer, you want to key in on the words of Java, Coughlin, Android Mobile.

Those are what you want to focus in on.

And then I'll see some people, though those still continue to be highlighting their HTML CSS scale C plus plus maybe a little bit of machine learning here.

And they're like, That's not really what the row is looking for at that point.

Similarly, in this case, you really wanna highlight yourself for engineering skills, you won't be focusing in on explaining which languages you're using.

That may be relevant, right?

Like if you're playing for, say, a python role, then you want.

Make sure that you're mentioning python in every single description that you can, and it is within the first few descriptions that you're listing.

You won't be talking about how you're setting up arrest a p.

I took a client front and then back in if you're playing for something else, like Save Machine Learning Engineer, that you would focus in on that portion and they would avoid words that are all about like, say, html CSS JavaScript, because that's not really going to be necessary for the road that you're looking for.

There I see a lot of resumes where people don't actually mention which languages they're using.

Their just say implemented Ex developed the why.

It's really hard to understand to what degree of involvement this prison got into it.

And if it was really such a great, awesome project, which it sounds like it was, why is there only a single short sentence about it?

Shouldn't there be more about it?

Which is another thing instead of going for a quantity of bullet points about what you're doing, have a few really good key ones and then explain the technical challenge of each of those and make each other's really stand out and memorable?

It's I'm just saying you did a B, C D E f g, and when I looked, that is like what any of these could be impressive.

But how come there's just no technical details about any of these?

And you're not really mentioning which languages you're using?

A lot?

People come in and they think that, you know, coding is too low level for them.

They're above that.

Their senior now and they want to be involved in strategizing, managing and, you know, mentioning which language they're using.

Ah, that's just too low level details for you, right?

And they don't want to mention that on the resume.

But I would say that the issue with that is that it makes your resume really opaque.

And then when Rita is just like, What are you applying for here?

Are you trying to be the team lead?

Because that's not what we're offering here, right?

We're offering for our software engineer in role where you're going to be spending hours at night slugging through the code, hunting down smaller, the strange bugs That's the test, right?

That's the role that people are hiring for.

People are looking for a coder.

They're not looking for necessarily somebody who's just going to be watching around in a suit in the office trying to look good sipping their coffee.

That's what I do.

One more point here is to be concise and prune out on relevant information from your resume.

If you are listing like you know how to do Microsoft XO, you know howto type of marks southward.

You've got communication skills.

Everybody's got that stuff and then ends up losing your resume.

There are some 1,000,000 resumes.

I see where people say that they are a hard worker, that they have great communication ability, that they're passionate, that they're enthusiastic, that they have a good work ethic.

And then I see the experience and it's like two bullet points and that's it.

And I haven't actually built any pet projects or anything on their own, and it's just like if you're such a hard worker, where's all the projects?

If you're such a good communicator, how come you didn't put on any presentations?

How come you did that?

Mentor Anybody at your last company, if you can show instead of telling, is going to be far more impactful and powerful.

You need to remember that trained resume reviewers people who read tons of resumes every day they have their B s filter on.

So any time you just say something, people are going to read that with a grain of salt, because what reason do they have to actually believe you?

You need to really be convincing and show them that which kind of goes back to my earlier point where instead of having a ton of different bullet points about all the stuff you did and none of them are convincing, you have just a few really high quality bullet points that just sells you on these things, right?

If you have, say, for really good bullet points and these are great stories that really demonstrate your skill, that's really all you need to convince somebody that you're good for the job.

You don't need 20 different bullet points if you're good on the just a few.

So here's what I recommend, and this is how they taught us over at Google to explain our achievements.

By the way, such that we could really explain why our accomplishments RMP convincing about that.

You structure your resume in terms of the challenge, your accomplishments and the results.

So too many people there just say implemented X.

That really doesn't tell me anything was this hard, right?

And if you implement that, what was the result of that?

Did this project succeed, or did you just implement that?

And that worked out throwing away And that was pretty easy.

So if you could say something like in two months you taught yourself this language and then you met some deadline and you implemented X, and then it launched to some results.

You generated some revenue for the company or it just got used by a lot of different people.

Maybe it made some news on the press.

Any of that stuff can be good validation for your work.

Maybe it just got open source and you got a few number of people using your open source project.

That's right, too.

But without that result without the validation of your work is really hard for any outsider who does not know about the work to evaluate.

Was this really useful work?

Was this impactful?

Now, for the fourth tip, let me just take a moment and talk about formatting.

I strongly believe that your resume should be a single page.

A lot of people like to stretch out other bullet points and descriptions and then the resume.

It becomes 223 or four pages even.

And that's just way too long.

And I'm just not used to reading that much stuff is too much of her beaus garbage, and you're just stretching thin your stories.

So trim your resume down to one page, such that I can print it.

And when I go to the interview, I can just have this one page of that.

I can take a look at which some raises your skills.

I would also recommend keeping the formatting simple.

Once you start having tons of colors, double column layouts, your photos there it's just, I think you look like amateur hour.

You want portray yourself as a professional expert and that somebody who is just really interested in playing around with fonts and colors and all of that other stuff, which is good.

It's nice also, but you're not applying to be a U Ie designer here, right, unless you are one more point here is that as I've been reviewing these resumes, I have no this love spelling typos and grammar issues.

Make sure that you proof read your resume.

You should be using active verbs I saw some resumes where people would say development of ex implementation of Wye maintenance of Z.

But that does not strongly explain what you did personally while you were there.

So instead you just say develop ex implemented way maintained.

See, one more point here is that as I've been reviewing these resumes for that program, by the way, you should check it out.

Interview Training Tech interview pro dot com Me and Joma We review your resumes, and we give you all of the best interview tips on how you can land a job at the top tier tech company you want.

Also make sure that your spelling out the full company names and university names like If you work that uber I would put uber ink just such that it looks more official and then for the universities and degrees.

I think it really helps to just spell those out fully such that they look more official on paper.

Major campsite that just doesn't look official doesn't instill confidence in me.

Not the fifth tip I have for you is that a lot of software engineering resumes.

They're overloaded with technical jargon.

It's like implemented terra form using terror creator Migrated car blows you away to carbonite implemented Js So using the abstract pattern oxides, it's like I don't even know what any of that is.

And when I read it, it's meaningless, completely meaningless.

You've just filled up your rest may with garbage words, as far as I'm concerned.

In order to make this much more usable for other people, Number one I would avoid use of too much jargon unless you know that the person reading this is going to understand what you're talking about.

And usually the person redeemed, by the way, is a non technical recruiter.

I might mention the other thing you might do if you're using love.

Proprietary technologies is explain how your skill in this can be expanded and broadened to be useful for other people.

So, for example, if you implement the terra form using the language terabyte, then you might just say that Hey, you were able to learn this language in two months and then you worked with a team of four to implement terra form, and as a result, it got used by 200 people, and you did this using test driven development.

All of these other skills, like Bambi, to learn quickly working collaboratively with a team and launching it, supporting it and using tester of in development.

All of that could be good skills.

But if all you said is you implement the Terra form using terabytes, that's just very meaningless for other people when they take a look at the resume.

So I would be very careful about Dragon.

Many attempts.

I'll read a resume and 50% of it.

I just don't even understand what they're going on about.