YT YouTube2Text

YouTube2Text → Transcripts → Want a Software Engineer Job? You NEED This

Want a Software Engineer Job? You NEED This — Transcript

by Headless Headhunter · 12,174 words · 1,742 segments · language en · Watch on YouTube

Open in transcriber Summarize with AI Download SRT/VTT

Full transcript

0:00I'm a recruiter and I'm going to teach
0:01you how to get a job by telling you the
0:04secrets of what human resources actually
0:06want and the hiring manager so that you
0:09can get a job. We've got some résumés
0:11coming up. The first one is a full stack
0:13software engineer, but I am going to
0:15review this and the other résumés uh and
0:18tell you what's good and garbage about
0:19them. And I do more than tech. I do
0:22everything from accountants to zebra
0:23farmers, but most of the résumés sent to
0:26me are tech. So, most of the résumés
0:28that I review are tech, but I do do
0:30other non- tech résumés. And if you want
0:32your résé to be reviewed, hop on down to
0:35the live stream every Monday, Wednesday,
0:37Friday at 11:00 a.m. where I review
0:38résumés live and type exclamation point
0:41raffle to get a chance to get your
0:43resume reviewed. But with that said, we
0:45have a full stack software engineer
0:47coming up and I'm going to see if this
0:49is good or bad. Uh, you can actually
0:51tell if a resume is good or bad by their
0:53ratio. Um the ratio is how many
0:55applications it takes to get an
0:57interview. And this one person has a bad
0:59ratio. It takes them over a 100red
1:01applications to get an interview. Uh and
1:03when people follow my method, they get
1:05one interview per seven applications.
1:08That is the average rate of people that
1:09follow my advice. Now there's an
1:11asterisk for that. No advice is a
1:13magical panacea. If you are looking for
1:15purely remote roles, I can get you a one
1:17in 20, which is one interview per 20
1:19applications. And if you were looking
1:20for an international role, I can get you
1:22one in 100, which is sadly extremely
1:25good for internationals. Most
1:27internationals, it takes them close to
1:28400 applications to get a single
1:30interview. So, we have a full stack
1:32software engineer. Uh, and let's see
1:35what do we need. We need this. Uh, these
1:39are the keywords. So, what are keywords
1:42and what am I going to be looking for?
1:43Well, if you already know this, you can
1:45skip to the timestamp below. Uh, but the
1:47keywords are basically what the hiring
1:50team needs. So, a hiring manager will go
1:52to a recruiter, that's me, and say,
1:55"Hey, recruiter," hopefully they'll use
1:56my name. I need you to find somebody
1:58that knows Python or Typescript or
2:01Docker or any type of skill that is in a
2:04job posting under qualifications, not
2:06responsibilities. Responsibilities don't
2:09matter. Qualifications do. So, they will
2:11go to me and say, "I need somebody with
2:12Docker and Kubernetes and building
2:14products from 0ero to one." And that is
2:15a keyword. But recruiters are not
2:18keyword hunting. We are qualification
2:21hunting. Uh and qualifications are
2:23different than keywords. So uh there are
2:27two things that make a qualification.
2:29One is the keyword itself. Keywords are
2:3150% of them. The other is why you did
2:34what you did in a way that Bob would
2:36understand the impact. So who is Bob and
2:39why is there what is their impact? I
2:41want you to imagine that there is a guy
2:43or gal at a company that's been there
2:45for 20 years. They are the manager. They
2:47are going to be your boss. They are
2:48going to be the recruiter looking at
2:49your resume. They cannot send an email
2:52without asking their assistant for help.
2:54They cannot turn on their monitor
2:56without calling tech support. This is
2:58the person that is reviewing your
2:59resume, both the manager and recruiter.
3:01And you need to show that person, Bob,
3:05why you did what you did in a way that
3:07they understood the impact. So, you need
3:09to show the impact for Bob, which is a
3:12very boiled down version of what you did
3:15because if they don't get the impact,
3:17you're going to get rejected. The other
3:19thing is I want to make sure you don't
3:20have hot dogs. So, what is a hot dog?
3:24Imagine that you're hungry and the only
3:26thing you want is a hamburger. So,
3:28you're like, hm, I want to go to
3:30Headless Head Hunters Hamburger HUD.
3:32I've heard they have good hamburgers.
3:34So, you go there and the menu only has
3:36one thing on it, a single cheeseburger.
3:38So, you're like, "All right, it must be
3:39a good cheeseburger. I'm going to order
3:40the cheeseburger." So, you order the
3:42cheeseburger and the waiter comes back
3:44and the waiter says, "Here is your
3:45cheeseburger." But guess what? It's not
3:47a cheeseburger. It's a hot dog. And you
3:49may be thinking, "Wait, wait. Why did
3:51you give me a hot dog in one of the
3:52cheeseburger?" And the waiter, who is
3:54weirdly southern, says, "Well, honey, if
3:56you think about it, a a hot dog is like
3:59a hamburger, cuz a hot dog has buns like
4:01a hamburger. A hot dog has meat like a
4:04hamburger. And a hot dog can't have
4:05ketchup, mustard, tomato, and all the
4:07other stuff that a hamburger can have.
4:08So, if you think about it, a hot dog is
4:10just a hamburger. And you would look at
4:12them like they were crazy and you would
4:14walk away without paying. And that is
4:16the same problem that a lot of people
4:17have in their resume is they fill it
4:19with stuff that is adjacent to what we
4:20want, but is not actually what we want.
4:23So, with that said, let's actually start
4:25the review and end the time stamp. So,
4:28what do we need for a full stack
4:30software engineer? We need TypeScript,
4:32React, JavaScript, HTML, CSS. Yes, you
4:35do. Yes, you do. Don't you dare tune
4:36out. Yes, you do. I understand you think
4:39this is ridiculous. I understand you
4:40think that one implies the other. But
4:41guess what? Rule number three, four, or
4:44five, whatever. I haven't made the rules
4:45yet for ré creation is that if it is
4:48implied, it does not count in your
4:51resume. So, you need to put TypeScript,
4:54JavaScript, HTML, CSS. But what about
4:57the technical? No, no, no, no, no, no.
4:59the technical person wants it. You need
5:01to have that. The the people that I've
5:03gotten one in seven for full stack
5:05engineers at fang by the way have
5:08Typescript, JavaScript, HTML, CSS in
5:11their first bullet point that shows why
5:13you did it. So it may seem ridiculous to
5:16you and guess what? It is ridiculous,
5:18but it's how you get a job. So degree
5:20TypeScript, React, JavaScript, HTML,
5:22CSS, Python and or Java, Angular, Node,
5:26RESTful API or REST API, SQL any uh AI
5:29coding tools or agents that you have
5:32made even better for the AI
5:34infrastructure uh cloud AWS, Azure or
5:37GCP uh Docker, Kubernetes, CI/CD, Git
5:41and if you are applying to a startup
5:43then you want building products from 0
5:44to one otherwise most other companies
5:46don't really care about it and then nice
5:48to have is the best of that. So, with
5:50that said, let us put 20 seconds on the
5:53clock, which is the only amount of time
5:54recruiters have. If we see what we like,
5:57then we keep going. But 20 seconds is
5:59all you get off the cuff. So, and start.
6:03Okay, this doesn't count. This doesn't
6:05count. Where's your education? Where's
6:07your education? Okay, all the way at the
6:08bottom. Good. You graduated. We go back
6:10up. So, then we go down to here. And
6:12that took 10 seconds. Developed a
6:14responsive end payment application for
6:16writers. What's that? including a
6:18ReactJS. Nope. Front end with Spring
6:21Boot. Okay. Microservices and a Juice
6:24Pay. J pay just pay. No. For digital
6:28wallet collection. Actually like your Y
6:30time. So I understand why this person is
6:34struggling. First things first, you want
6:36to use this format. This is the format
6:38that will get you a job. The only time
6:40you don't want to use this is if you are
6:42a manager who is applying to like a VP
6:44role and you have 20 plus years
6:45experience or you're a job hopper.
6:47Everybody else from accountants to
6:49software engineers to whatever uh stuff
6:51stouts with a Z, zebra farmers wants
6:54this format. This is how you do it. It
6:56looks boring and basic but that is what
6:58gets you an interview. So uh the things
7:01that are problems with this resume, one,
7:04too many hot dogs, not enough wise for
7:06Bob. Um, and quite frankly, not enough
7:10hamburgers. So, none of this matters.
7:12Summaries don't count. There's only
7:14three reasons you would ever want a
7:15summary, and that is if you are
7:16relocating, explaining a nonH1B OPT visa
7:20without a approved I140, or you are
7:22switching industries, and I mean going
7:24from a software engineer to a baker.
7:26That level of difference. Uh, that is
7:28the only reason to do it. Then you have
7:30a skill section. Guess what? Skills
7:31don't matter because remember what we
7:34said, skills are keywords, but keywords
7:36are not qualifications and
7:38qualifications get you hired. This does
7:40not tell me why you did what you did in
7:43a way that Bob would understand. So
7:45guess what? Doesn't count. And remember,
7:47the education needs to go up here
7:49because otherwise I'm going to have to
7:50scroll all the way down to the bottom,
7:51which you cannot even see, and then
7:54determine it, which guess what? Lost you
7:5610 out of 20 seconds. That took half the
7:59time away from your resume because you
8:02did not put your education up at the
8:03top. That is why you put your education
8:06up at the top. Then down here, uh, we
8:10have the bullet points. And you know
8:11what? I'm going to give it to you. I
8:13like your wife or Bob here.
8:16Uh, this is this is understandable. Um,
8:20I don't know if UPI is understandable,
8:22but Bob would understand at least cards
8:24and wallets. enabling digital payment is
8:27a good why. So, I'm giving you credit
8:28here in a resume that is bad. This is a
8:31good why for Bob. The problem I have
8:34here is guess what? Where's the
8:35TypeScript? I don't know. I can't find
8:37it. Where's the re uh JavaScript?
8:39Where's the React? But Lee, you have
8:41ReactJS? No. If Java is different than
8:44JavaScript, then ReactJS could be
8:47different than React. I don't make the
8:49rules. That's just how software
8:50engineering works from a technical
8:52standpoint. So this may be the same
8:54thing as React, but companies aren't all
8:56looking for ReactJS. They are looking
8:58for React. And you have to write what
8:59they want, not what you think they want.
9:02So this doesn't actually count as React.
9:05Uh Spring Boot does. And then remember
9:07there should be a comma here. Spring
9:09Boot, microervices. So the only thing I
9:13have here is a good Y, but a good Y with
9:17no what doesn't count. And a good what
9:19with no why doesn't count. You need both
9:22to make a good bullet point. So I only
9:24see two things that I'm looking for
9:26here, which is Spring Boot and
9:27microservices. In fact, am I even
9:29looking for Spring Boot? I'm not. I'm
9:31actually not looking for Well,
9:35microservices is extra credit. And if
9:39you are a Java dev, I will say Spring
9:41Boot is probably okay to put here. So
9:44this actually only has one and a half
9:46keywords I want. And each bullet point
9:49you have needs a minimum of three, a
9:54maximum of six bullet points. And you
9:57know what I don't see? I don't see
9:59TypeScript. I don't see React cuz it
10:01doesn't count. I don't see JavaScript. I
10:03don't see HTML, CSS. And I do not see
10:05Python or Java. Where is it? I don't see
10:08it anywhere here, which is going to get
10:10you rejected. And your first sentence is
10:13the most impactful thing in your resume.
10:16So you may have built and automated a
10:18CSD pipeline keyword by using Jenkins
10:21hot dog to test build AWS keyword which
10:24is only two but guess what this is uh
10:27two keywords I want but what do you mean
10:28reducing deployment time and improving
10:30release reliability why is that
10:32important to the company guess what Bob
10:34doesn't understand too technical this
10:36doesn't count also no numbers
10:40the only numbers that you want in your
10:41resume are your phone number if you
10:44graduated recently
10:46and your date of employment. Those are
10:48the only numbers that you want in your
10:49resume. Otherwise, this makes your
10:52resume worse. So, designed to deliver to
10:54real-time logistics trackboard, all hot
10:56dogs. And what is supply chain
10:59visibility? I don't. You didn't tell me.
11:02Why is it important the supply chain is
11:03visible? Did it get a new clothes? Did
11:05it get a new outfit and it wants to look
11:07cute cuz it's going on a date? I don't
11:09know. You didn't tell me. What is it?
11:11Why does it want to be visible? Why does
11:12it want to be unvisible? I don't know.
11:14You didn't tell me. And you may be
11:15asking, well, no, this is ridiculous.
11:17No, no, no, no. Remember, Bob exists in
11:21every company. Bob is both your manager
11:24and recruiter. And if you do not build
11:26it for Bob, you are going to get
11:28declined. So, the problem with this
11:30resume is a formatting, b too many hot
11:33dogs, c not enough hamburgers, d not
11:36enough good y for bobs, although your
11:38first sentence had a good wife for Bob
11:39and I will give that to you. And is
11:42there anything else? That is the
11:43problem. And just not enough. It's just
11:45not enough. I need Python or Java. I
11:48need TypeScript, React, JavaScript.
11:49Nothing that is implied counts. So, your
11:52first sentence should have said,
11:55uh, by the way, AWS should always go in
11:57your first sentence for a a software
11:58engineer or GCP or Azure. You really do
12:02want cloud in your first one. It should
12:04have said developed a payment
12:06application using
12:09Python. Uh, no, this person is probably
12:11Java. using Java, TypeScript,
12:13JavaScript, HTML, CSS in an AWS
12:17environment. And then your second bullet
12:19point should be blahy blahy blah with
12:21React, SQL, and then Spring Boot and
12:25whatever else you want to put in there.
12:27But this is why you're getting rejected.
12:29This is why you're not getting a one and
12:31seven. And it is ridiculous. I I am
12:33aware of that. But unfortunately, a lot
12:36of things in life are ridiculous. you
12:38kind of have to just do it cuz I can't
12:40tell you how to beat I can't tell you
12:41how to overturn the game we play. I can
12:44only tell you how to beat it. Uh and
12:46this person all wanted to know before
12:47the human that so many jobs do AI
12:50screening that you need a skill. You do
12:52not need a skill section. Um I made a
12:54video on it which if I can figure out
12:56how to link videos will be right here.
12:57If not, I'm sorry. I am a recruiter
13:00first. I don't know how to link that
13:01video uh about how ATS's actually sort
13:04your resume but it is humans and if you
13:08are not within the first 100 applicants
13:11you are going to get declined. Uh that
13:13is the case. I made a guide that is free
13:15down below. You can look at it. It tells
13:17you how to find jobs to be within the
13:19first 100. Uh but you need to be within
13:21the first 100. So you need all of the
13:23advice I said and within the first 100,
13:25which is actually really easy to do. The
13:28guide can show you how to do it. It's
13:29just kind of hard to say verbally to get
13:31an interview to get a one in seven.
13:34Everything combined makes it. There is
13:36no one if you do this one thing. There
13:38is not that. It is you need to do
13:40multiple things. So with that said,
13:42before we go to the next resume, um
13:45thank you very much for watching and if
13:46you want to support this channel to keep
13:48it alive, you can become a member in the
13:50link below. You get access to videos
13:52early, uh a lot of videos early and you
13:54get access to the past live streams. But
13:56most importantly is your membership lets
13:58me keep doing this. And I could not keep
14:01making this content for everybody
14:02without members. So if you want to
14:04become a member and support this
14:06channel, join the link below. With that
14:08said, let's go to the next resume. This
14:10is a backend Java engineer. So uh what
14:14do we need? We need Java, Spring Boot,
14:16SDLC, SQL, RESTful API or REST APIs,
14:19microservices, CI/CD, SDLC,
14:22objectoriented programming, oop, uh, Git
14:24or GitHub actions, Linux, Unix, Agile,
14:26Scrum, Cloud, you do need to be
14:28specific. So, AWS, GCP or Azure, uh,
14:33architecting or systems,
14:35containerization,
14:36hibernate, Kafka, AI, and rare but nice
14:38to have is DevOps, Revit, MQ, and Maven.
14:41So this person, it takes them over 150
14:44applications to get an interview. So
14:46this is a bad resume and they want to
14:48get into Fang. Well, my advice does work
14:50for Fang. So I've gotten plenty of
14:52people jobs at Fang before. Uh really
14:55like there's not the interview process
14:57at Fang is different. Um but the actual
15:01resume that gets you that interview is
15:03not different from Fang and the Bob's
15:06shoe store down the corner. They're all
15:08looking for the same things. Uh,
15:10startups want a little bit different
15:12stuff, but beyond that, it's it's all
15:13the same resume. So, 20 seconds is on
15:16the clock. Uh, and I am Let's see. Boop.
15:21And
15:23let's begin. I'm getting my stuff set
15:26up. Uh, let's begin and go. Okay. Uh,
15:30Java, no. Anna, where's your education?
15:34Uh, okay. You did graduate or you're
15:38about to graduate.
15:39uh ship to customer java supporting 10k
15:42teams this doesn't matter architect
15:44loading following right mode for for
15:47where's uh integrating circuit breakers
15:49reach out this means nothing uh garbage
15:52optimiz
15:54requirements uh garbage time so a couple
15:58of notes um your education needs to be
16:01up at the top um
16:05you I believe this person will need
16:07immigration services. So, the best I can
16:10get them is a one in 100, which is
16:12shockingly good for internationals. That
16:14is how hard it is to get an
16:15international job. But your education
16:18still needs to be up at the top. And
16:19once you graduate with the masters, you
16:21don't need to put your bachelors. Uh
16:24they are graduating in December, but it
16:26definitely needs to be at the top. Then
16:28my problem with this is a there's just
16:31not enough keywords. There's too many
16:33hot dogs. And Bob has no idea what you
16:36do. And again, I have gotten people
16:38interviews and jobs at Fang. This is how
16:42you write your resume doesn't change. Uh
16:44the interview process does. So, if you
16:46want to know what the interview process
16:47is is, well, I haven't directly
16:49recruited for Fang. I have like talked
16:51around them and it's it's really
16:53interesting is that Fang um Fang and
16:56startups interview processes, everybody
16:59else copies. So what Fang is doing for
17:03interviews now, the rest of the world
17:06will probably do in about a year or two.
17:09Um, so they're usually like separate
17:12interview processes uh from the rest of
17:14the world, but the resumes are the same.
17:17So ship the customerf facing backend
17:19features in JavaScript. No, none of
17:22this. There should be a comma. All
17:24right, make it a comma. Do not do
17:26slashes. All right. I do slashes up here
17:30because I have space issues. You do not
17:32do that. Java Spring Boot supporting
17:34teams. Does the 10K matter? I don't
17:37think so. Across multiple products.
17:39Cool. What products were they? What else
17:42did you use? Because the only thing I
17:44see is two keywords here. Uh, and Bob
17:46doesn't know what you shipped. Was it
17:48SAS products? Uh, was it a sales thing?
17:51I don't know. You didn't tell me.
17:54Architected. That is one. a low latency
17:57fault tolerant that means nothing rest
17:59api microservices rest api
18:03comma
18:04microservices if java is different than
18:07javascript then rest api microservices
18:10are different than rest api and
18:12microservices for industrial data what
18:15is industrial data I have no idea
18:17integrating circuit breakers retry
18:19policies and blah blah blah ttl tender
18:23something loving cing layers resulting
18:26in Bob doesn't understand this. Your
18:28grandmother doesn't understand this.
18:30This is a bad bullet point. And again,
18:32you have three here, which is actually
18:33the correct amount. Uh optimized, who
18:37cares? Frequency used API. You already
18:39mentioned API with Postgre SQL to
18:41execution plan analyze blahy blahy blahy
18:45blahy blahy blahy blah. This doesn't
18:47matter. Uh and by the way, I'm being
18:49extra harsh because internationals
18:52suffer harder job searches than almost
18:54anything else. So they need to learn
18:56this. Uh that is only one keyword. Then
18:59remember you've been here for three
19:00years. Guess what? You get
19:04three bullet points. This is all that
19:07I'm going to read in this job. So you
19:09better make it count. And I have six
19:11keywords across three bullet points.
19:14Also, the rest of this basically has
19:17like one keyword per sentence.
19:21Uh
19:23I actually like this one. I actually
19:25like this one, but again, it needs to be
19:26more. Yeah. So, this has one keyword.
19:29This has one. This has extra credit, so
19:32that doesn't count. This has
19:34nothing.
19:36This has nothing. This has nothing
19:40because you did not put a comma. It's
19:41Azure, DevOps. But if you did put it,
19:44it' have two. So, you have a problem
19:46with most of these sentences being
19:48worthless. And again, what is enforcing
19:50consistent permissions to safety
19:52whatever configurations? Why is that
19:55important? And remember, your
19:57grandmother needs to know the why. So,
20:00if your grandmother cannot understand
20:02the why, you are not going to get an
20:04interview. And that works for Fang. So,
20:07you need to redo all of this resume. You
20:09need to make it in this format. Um, you
20:12would not put this, you did do this,
20:14right, of relocating to San Francisco in
20:16December. That's fine. But if you really
20:19want to get into Fang, you need to make
20:20it understandable to your grandmother.
20:22Uh because your grandmother is not going
20:24to understand
20:26uh enforcing consistent permissions for
20:28safety system configurations or maintain
20:31system integrity. I they would
20:33understand minimize downtime. That one
20:35actually is okay. Or reducing build
20:37times by parallel execution incremental
20:39builds. I know as an international your
20:42tendency is to overdo it on the tech.
20:45That is actually going to hurt you. The
20:47internationals that I have saved and
20:49been able to work in the US, they make
20:52it boring and basic. I it it you cannot
20:55overdo it. I know you're afraid. I know
20:57you want to prove you're better than
20:58anybody else because you're in for the
20:59hardest job search. You can't do that.
21:01You have to make it basic and boring.
21:04Next resume. This is a intern
21:09resume. Uh they said this is a new
21:11resume. After applying the feedback,
21:13only apply to about 30 rs with this
21:15resume. Well, make sure you're applying
21:17within the first 100, otherwise it
21:19doesn't count. That is another core
21:20tenant of my rule and my guide is you
21:23need to be within the first 100, but uh
21:2530 is not enough of a sample size. So,
21:28let's see if this resume works or not.
21:30And what do we need? We need degree, one
21:33of the following languages, uh SQL, API,
21:37any cloud, AI, and the ability to work
21:39well with others and take direction and
21:41criticism. So, let's find out if they've
21:44got it. We got 20 seconds on the clock.
21:47Boop and go. Okay, good. Good. Built
21:51trading software using Go React
21:53JavaScript HTML CSS
21:55to produce live updates. Okay, good.
21:57Develop Python REST APIs scripts through
21:59the Git and Kubernetes. K9 to support
22:01CSD releases. I'm only doing updates.
22:03Proceed weekly agile to present progress
22:05while applying senior engineer feedback.
22:06We need one more. Uh, it's not bad.
22:09Engineered a pipeline using Python, SQL,
22:11and AWS. Managing clients immigration
22:15documents. All right. Time. Um, I like
22:18most of it. So, the problem I have with
22:20this is 1 2 3 4 5 6
22:257. There are too many keywords here. You
22:28want a maximum of six, a minimum of
22:32three. So, minimum of three, maximum of
22:35six. Uh, and then let's see, what am I
22:38missing? So I I don't think these are
22:41bad. I think your order is off. Um so
22:46what I would like you to do is built tra
22:51a trading software using Python
22:57REST APIs,
23:00JavaScript, HTML, CSS
23:04and no SQL.
23:08Right? So that would be six. Then down
23:11here you can put React, Go, Git, and
23:16Kubernetes.
23:17Uh, which is what I would like to do.
23:19Um,
23:22see is there anything else? I don't
23:24think it's bad though. Uh, and then here
23:26particip I have with this is there's
23:28only two. Uh, agile is nice to have and
23:31agile is sort of implying that you can
23:33work with others. So I would like you to
23:35add at least a little bit of tech here
23:37which you know maybe you could add one
23:39of the other from here like uh
23:41Kubernetes would probably be nice or
23:44maybe CI/CD. Uh but I would like a
23:47little bit more here. Um participated in
23:50weekly agile scrum to present progress
23:54while applying senior engineer feedback
23:56uh to ensure the projects released on
23:58schedule. Otherwise it's fine. So minor
24:01issues this should work. Just remember,
24:03apply within the first 100 and your
24:06ratio doesn't count in well, I don't
24:08know if your ratio doesn't count in
24:09November for Canada. It doesn't in the
24:11US, but it won't count in December. Uh,
24:14engineer to pipeline from may migrate
24:17client templates to a modern platform.
24:19Smoother document loading. Yeah, that's
24:20okay. I just I think I would like I kind
24:23of want to know a little bit more about
24:25maybe the product. Uh like this is this
24:28is good and you've trimmed out all the
24:30fat and it's very lean and now we got to
24:33add just a little bit of extra to it. Uh
24:35so I want a teeny bit more. But it's it
24:38it is good. I do think this is good.
24:40Just make sure you're applying within
24:42the first 100. Uh is there anything else
24:45that I'm missing?
24:48No, I don't think so. Otherwise, I think
24:50this is a good job. Um, I just want
24:54maybe a little bit more detail about the
24:57product itself. So like live price
25:00updates for stocks, keeping the system
25:01online during updates and then maybe so
25:05it would not crash for customers, right?
25:08Just a little bit more. But otherwise, I
25:10think it's a good job. The biggest issue
25:11I have is you need to switch this around
25:13and you have seven in the first when you
25:16want a maximum of six. Next resume. This
25:18is a full stack software engineer. Uh
25:22this is their second try. They said they
25:25removed uh a 3-month old job as it was
25:28not worth showing. That is correct. If
25:30you've been at any place for less than 3
25:32months, not counting internships, do you
25:35do not want to include it on your
25:37resume? Um remove the open to
25:39relocation. Good. That is a giant yellow
25:42flag. And rewrote their bullet points.
25:44appreciate
25:46uh having a look and giving any
25:47feedback. So let's see what we have.
25:51Let's get the keywords for full stack.
25:53So degree TypeScript, React, JavaScript,
25:56HTML, CSS, Python and Java, sorry,
25:59Python or Java, uh Angular, Node.js, JS,
26:02restful API or REST API, SQL, any AI
26:05coding and or agents, cloud, Docker,
26:08Kubernetes, CI/CD, Git, building
26:10products from 0ero to one. If you are
26:12applying to a startup only, uh startups
26:15really do value 0ero to one. Other
26:17companies [clears throat] e not so much.
26:21Uh nice to have is all that other stuff.
26:24But again, nice to haves are nice to
26:25haves. So 20 seconds is on the clock. Uh
26:29I don't we do not know this person's
26:31ratio or their previous ratio but let's
26:34go and start. Formatting is way off. Uh
26:37okay.
26:39Uh architected a bilingual educating
26:41platform using React Nex.js Node and
26:44GraphQL.
26:46Hot dog mostly on AWS to help kid
26:49biology interactive lesson game. Okay.
26:51Good though. Built an AI tutor in Python
26:53using fast API in Google Gemini. True V
26:56on. Okay. Good wise. I love your wise.
26:58uh developed in analytics using React,
27:00TypeScript, JavaScript, GLCS. Pretend
27:01this is okay. Uh your So, first off,
27:04this does not look like this. Uh your
27:08font is wrong. I I don't know what you
27:11did with your font, but this is wrong.
27:14Cuz if you notice, this is not this.
27:18You can ignore that. This is not this.
27:22Remember 1.15 spacing for this. Then 1.5
27:27spacing for this. And the entire font
27:31below your contact information.
27:33Everything here should be
27:3710.5 aerial. This
27:41I don't know what this is but it's not
27:43it. And don't cheat on the margins. Stop
27:47cheating on the margins. There is a
27:50reason I have this space here. It is
27:52because it is easier to read. This is
27:55very difficult to read. So, um, is this
27:58the worst resume in existence? No, not
28:00at all. I I don't think this is
28:01terrible. But there's a lot of fixes
28:04that we can do besides just the
28:06formatting. So, first things first, um,
28:10what we're doing here is next is a hot
28:12dog. I know that's weird. Node.js is a
28:17hamburger. Next is a hot dog. React is a
28:21hamburger. Postgres SQL and AWS are uh
28:26hamburgers. Uh also my problem with this
28:29is a don't double up on React. Remember
28:32do not double up on the same keyword in
28:34the same one. Uh my problem is you need
28:38this up here. Normally I'm not the
28:40biggest uh stickler for order, but for a
28:44full stack developer I need to see
28:46TypeScript, JavaScript, HTML, CSS in the
28:48first bullet point. That should be one
28:50of the f sorry it should be typescript
28:52react javascript html css and then AWS
28:56that is your first line typescript
28:59javascript html css
29:03uh your primary language is Python. So
29:05sorry let me re redo this cuz you you've
29:07thrown me for a loop now. So the most
29:10important thing is your backend. So,
29:12Python should be first then it will be
29:15so it's Python, TypeScript, JavaScript,
29:18HTML, CSS and then it is AWS then in
29:23your second line I want you to lead with
29:25React. So, and then you can put Node.js
29:29and Postgres SQL. I will give you props
29:32because
29:33I love these wise. I don't think
29:39uh I don't think there's any real
29:41problem with it.
29:45Yeah, I don't I don't think there's any
29:47problem with the wise. A minor minor
29:49minor quibble is
29:52Oh, no. No, that would still make sense.
29:54Built an antuno to improve access to
29:56automate. Yeah. No. Uh I love your wise.
29:58I don't really have any problem with
30:00them. Um automate workflows. Streamline
30:03business operations. Again, this is a
30:06little vague, but your first ones are
30:08the most important ones. So, this is a
30:09little vague. Uh, this is a little
30:13vague. But my problem here is the order
30:15primarily. And remember, as an
30:17international, you have less of a chance
30:20than anybody else. You need to lead the
30:22you need to lead right off the gate with
30:24your stack. And the stack is going to be
30:26Python, [gasps]
30:29Python, TypeScript, JavaScript, HTML,
30:30CSS, and then AWS. And then the second
30:33sentence can be react. Uh there is some
30:36potential thing of trying to put react
30:40in the first one, but I would make sure
30:43you keep Python first. So is this an
30:46awful resume? No. But there are some
30:48flaws mainly with formatting and mainly
30:51with the order of your bullet points. Um
30:55and
30:59I think that's it.
31:02Uh otherwise I think that's fine because
31:04remember you're going to get a close to
31:06100 to one with a perfect resume and I
31:09want to make sure you can actually get
31:10that next resume. This is a resume of a
31:15sales development representative. Uh
31:17this person has a 1 in 25 ratio which
31:20you're about to say wow this is a
31:22fantastic resume. No. Um I needed to
31:26look up the keywords for this cuz I did
31:28not have them on hand. This is a blazing
31:30hot res. This is a blazing hot industry.
31:33Uh if you have the required skills or
31:36even if you semi have it, you should be
31:38getting a 1 in 10. Uh a 1 in 10 would be
31:41the equivalent of a 1 in 60 to 75 for
31:45others. There were jobs with easy apply
31:48that were remote that only had nine
31:50applicants apply. So this market is very
31:53very very very very
31:56good, which means a 1 in 25 is not good.
31:59they should be getting much much better
32:01than that. So, what do we need for a
32:04sales development rep? Uh industry, they
32:07they really care about what industry
32:08you're in. Uh sales experience, sourcing
32:11prospect and closing sales
32:13independently. Communicate in English or
32:15any other languages that you have uh
32:18both written and verbal. And then sold
32:20or built trust through phone, email, and
32:22in person. Uh and then basic computer
32:25skills. So CRM, MS Office, B2B, close
32:28deals in successive sales, multitask and
32:31meet deadlines, and that you can grind
32:34it out even through adversity. Uh, a big
32:38thing of sales is you will get a,000 nos
32:40before you get one yes. But that one yes
32:42is worth it. And I need to see that
32:45through the resume. So 20 seconds on the
32:49clock.
32:50It looks awful, but maybe the bullet
32:52points are good. I'm going to give them
32:53the benefit of the doubt. I will be
32:55honest. You get more than 20 seconds for
32:57this because the industry is so hot. You
32:59get probably 40. So, I'm going to run
33:01out of time and then do it again. So,
33:04let's go. Okay.
33:07Okay. Education. Okay. This doesn't
33:09matter. Okay. Uh I'm highly driven. This
33:13doesn't matter. Oh, SAS. SAS actually
33:16matters. Okay. Uh graduated of swords.
33:19What is that? Comparatively linked to
33:20world with freedom seate to receive
33:22coaching.
33:23Uh, I'm not against it. Time again. The
33:27industry is hot, so they get another 20
33:29seconds. Never make your resume two
33:32columns, please. Uh, responsible cold
33:34outreach through a omni channel approach
33:36of cold calling, cold emailing. I love
33:39this one. This is a good sentence.
33:40Participated in regular coaching and
33:42outbound strategies, campaign
33:43management, improving cold outreach.
33:45That's fine. Research understanding of
33:48IPOs. Uh, it's like mid handled customer
33:51conversations across email and chat. I
33:53definitely think that one's solid time.
33:56You actually have some good bullet
33:57points here. So,
34:03people get upset at me when I say Jake's
34:05resume template is bad. Jake's resume
34:07template is a C minus. I say it is a C
34:11minus because you can do a lot better,
34:15such as my formatting, but you can also
34:16do a lot worse. like this formatting.
34:19This is worse than Jake's resume
34:21template. Anything with two columns or
34:24more is a terrible format. And the worst
34:28part is you actually had some solid
34:31bullet points in here that I really
34:33liked. Like this right here, responsible
34:36for strategic outbound co outbound
34:40through an omni channel approach of cold
34:42calling. Good cold emailing, video
34:45prospecting, and LinkedIn outreach. That
34:47is something that they want. That
34:49handles computer. That shows computer
34:52skills. That shows that you can cold
34:54call. That shows that you can cold
34:55email. You can I actually don't know
34:58what video processing is, but they might
35:00want that. Uh then participate. So like
35:03this is a good sentence and it actually
35:05covers a lot of what I need. Then
35:08proficient at prospect research and
35:10understanding values. That doesn't mean
35:12anything. So, one of the bigger mistakes
35:15I see in this resume is that you showed
35:18how you learned and you didn't show how
35:21you did. You never want to show that you
35:24learned something. You want to show that
35:26you did something. And the first bullet
35:29point shows what you learned, which is
35:31why it's bad. The second bullet point
35:33shows what you did. So, graduate of
35:36Swords SDR into program with 3%
35:38acceptance rates to receive coaching
35:40from leaders on how to be an elite SDR.
35:43That shows that you learned. I don't
35:45really You know what? Actually, I'm
35:46going to take that back. Learning is
35:48actually something that I saw in a
35:49couple of job descriptions. So, learning
35:52is not terrible in this one, but it
35:54shouldn't be your entire bullet point,
35:56but this shows that you done something.
35:59This was you were responsible for rather
36:02than learned. So, I do actually like the
36:06received onetoone coaching. I actually
36:09think that part in particular should be
36:12in your resume, but I do not think it
36:14should be the entire bullet point
36:16itself. Uh,
36:19and then don't say participate, say you
36:21did. And then down here, I like this.
36:24This is a number that is good. So, sales
36:26people need numbers. And this is a
36:29number that gives you context. handled
36:3230 to 50 daily conversations across
36:34phone, email, and chat. Again, shows you
36:36what you're doing. It identifying needs
36:38and guiding customers to the right
36:40solution. That's a phenomenal bullet
36:42point. But then this one you basically
36:45already repeated repeated above. This
36:47one is fine with Salesforce, but this
36:50doesn't matter. And this one I like
36:52because it shows you hit your KPIs,
36:54which they want for sales. So, your
36:57formatting is atrocious, but your bullet
37:00points, the ones that exist are solid,
37:02and I'd like you to make the rest of
37:04your bullet points like that. Um, mainly
37:07because it's just that's what they're
37:10looking for. Uh, and then again here,
37:12what do you mean? So, there's also a
37:14critical error that you had is
37:18never just say the year. You need to say
37:21the date. So, because your sales, you
37:23can get away with doing two things at
37:25once. That's fine. Sales people do that.
37:28They like the grind. So, you can get
37:30away with that. But 2026 is a no-go.
37:33This needs to say the number 2025.
37:36So, 2025 could be January of 2025 or it
37:40could be January to December of 2025.
37:43So, you always always always always
37:45always
37:49need the month in addition to the date
37:51there. If you've already graduated, you
37:54don't need to say your month
37:55necessarily, but for the company, you
37:58do. So, is this the worst resume I've
38:01ever seen? No. It's bad. But you
38:04actually have some really solid bullet
38:07points. I just have to dig through to
38:09find them. And digging through to find
38:11bullet points is a luxury that you don't
38:13necessarily have. So, next resume.
38:18This is a product manager. Uh this
38:21person is about a 100 to1 ratio. So it
38:23is not a good resume but it is not the
38:25worst ever. Uh and see I do more than
38:28tech. I do more than tech. See uh even
38:32though this is kind of in tech cuz we're
38:34doing AI agents. So uh what do we need
38:37for a product manager? Uh which is
38:40different than a project and program
38:42manager. We need degree industry. I want
38:45to see what industry you're in. This is
38:46going to change some of the keywords. I
38:48cannot be in every single industry. Then
38:50I want to see that you can do
38:51presentations and communications that
38:53you can handle multiple projects and
38:55deadlines. That you can do basic
38:56computer skills such as MS Office,
38:58Excel, Word and PowerPoint. You can work
39:00cross functionally with product shipping
39:02product 0ero to one. Remember in the
39:04very beginning uh full stack had a 0ero
39:06to one product for startups. This is for
39:09everybody as a product manager. They
39:11want to see 0ero to one. Um there's also
39:13from inception to end. Those are all
39:16basically the same things. Then
39:19communicate clearly on product goals and
39:22translate it into a product crossf
39:24functional or matrixed and stakeholder
39:26management. So let's see what's getting
39:28this person a one in a 100.
39:3120 seconds is the clock. Uh sorry
39:34there's a heat wave in California at the
39:35time we're doing this and it [laughter]
39:38this room does not get good AC. Uh so I
39:41am broiling alive. All right.
39:4420 seconds on the clock and go. Okay,
39:48this doesn't matter. Where's your
39:50education? Okay, you did graduate. All
39:52right. Built agent zero to one. Okay. An
39:55AI care agent voice agent as a PM and an
39:57AI engineer and one pilot contracts
39:59behind a multi-million series A. Is that
40:01really necessary? What did the agent do
40:03though? Scaled the agent to patient
40:06calls after two. Like that's not really
40:07relevant. Replace a onetime client with
40:09a multi client platform. Why is that
40:10relevant? expanded big payer from what
40:14is that uh
40:17see this one at least did something
40:18founded evaluation team by convincing
40:20our SVP that time I'm going to read the
40:23rest of this sentence but founded the
40:24evaluation team by convincing our SVP of
40:26technology and CPO that call volume had
40:28outgrown manual review I like okay so
40:33you you of all people you have no excuse
40:37for this I I want to ask you something
40:40if you presented this resume
40:45to uh the stakeholders that you are
40:47talking about, would they understand
40:50what you did? Because you have succeeded
40:53in convincing these people such as this
40:55SVP and CPO. Uh do do you think they
40:59would understand what a multi-client
41:01platform across company or a pilot
41:03contract would they understand all of
41:05this? they might understand one or two
41:07bits of it, but if you told them you
41:09built an agent01 and AI care manager as
41:12a PM and AI engineer, would they get
41:14that? And the answer is probably not.
41:17Um, which is part of the problem that
41:20you are having is
41:23that's you wrote it for an audience that
41:25doesn't exist. They are your audience.
41:28You know how to write it for them. You
41:30didn't do it for this one. So remember,
41:32formatting is off. Your format should
41:34look like that. Um, second off, your
41:36first sentence is very almost
41:38incomprehensible. I would get rid of it
41:40and remake it. Uh, second off, you've
41:42been at this job for less than three
41:45years. You get three bullet points max.
41:48So, this should be crunched down into
41:49three. Um, and then where do I see that
41:52you can work crossf functionally? Um, I
41:55do see that you can do product goals and
41:57translate into product. I think the
41:58founded the evaluation team is good. uh
42:02which does also count as stakeholder
42:05management. So product goals and
42:07translate into a product. Um I don't So
42:10you did say 0ero to one but it's
42:12actually buried here. So even though you
42:14did it they may miss it cuz it may sound
42:16like you built an AI that's called 01
42:20which could be an issue. You didn't say
42:22built an AI agent from 0 to one. You
42:26said built agent 01 and AI care. So that
42:30might have been the name. So technically
42:33you don't have that. Um again I don't
42:35see you can work crossf functionally. Um
42:38I don't see that you can use MS office,
42:40Excel, Word or PowerPoint which again
42:42it's not just basic computer skills is
42:43they want to see that you can use those
42:45to convince people. Um and I don't see
42:47that you can do multiple projects and
42:48deadlines. I do see presentation. So,
42:51this bullet point right here, while not
42:55perfect, is a very good bullet point
42:59that is kind of carrying the rest of the
43:01resume that if they got to that, they
43:04would understand more. The problem I do
43:07have with it is a lot of these numbers
43:08are not relevant. Why do I need to know
43:11that this had 500 calls a week that was
43:15scored by LL judges that review time to
43:1810 minutes? Like why not just say
43:21founded an evaluation team by convincing
43:24our blahy blah that call volume had
43:26outgrown manual review and created an AI
43:29agent that solved the issue. Like you
43:33don't even need to go into crazy thing.
43:35You can just say created an AI agent
43:37that solved the issue by reducing call
43:39time and then you do not have any of
43:41these numbers cuz they're filled with
43:43numbers man. And none of these numbers
43:45are the correct ones. Like I don't care
43:47if three days to two hours. I care about
43:50the budget which actually for a product
43:52manager I really don't. I really don't
43:54care about any numbers for a product
43:56manager. Um
43:58program and project I do care about
44:02numbers but like none of these matter.
44:04Like you focused on how good the product
44:07is, but guess what? I don't really care
44:09how good the product is. I care how good
44:12you are in making the product exist. and
44:15you kind of failed at that except for
44:17your third sentence that is carrying the
44:18rest of it. So that is the problem I
44:20have with this. It is filled with so
44:22many hot dogs and you focus so much
44:24about the individual product that you're
44:26not selling the product. This reads like
44:29someone trying to sell the product they
44:31made rather than them selling themselves
44:34of how they made the product. And I hope
44:36that made sense to you, but remember
44:39you're talking to stakeholders, so you
44:40need to lower this for Bob. Next resume.
44:43This is a Java developer. Uh, this
44:47person said, "I've got one in a 100
44:48applying for two months now. 20 a day
44:51and 15 interviews. Uh, this resume is 3
44:54weeks old and no interviews yet in
44:56Canada." Okay, so
44:58100 applying for two months now. 20 a
45:01day. Okay, so you're getting about a one
45:03in 100.
45:05All right, so what do we need for a Java
45:07developer?
45:09We need Java, Spring Boot, SDLC, SQL,
45:12RESTful API or REST API, microservices,
45:15CI/CD, SDLC, object-oriented
45:17programming, OOP, Git, GitHub actions,
45:20Linux units, Agile, Scrum, cloud
45:22architecting or systems work,
45:24containerization, Docker, Kubernetes,
45:26Hibernate, Kafka, AI, and nice to have
45:28is some of that other stuff. So, 20
45:30seconds is on the clock. Boop. Let's see
45:32if this is good or bad. Uh, and go.
45:36Okay, diploma is maybe an issue here.
45:39Uh, architected a restful API using Java
45:43Spring Boot object programming
45:45multi-threading hot dog to get data and
45:46deliver reporting to incentives trades.
45:48Good. Y store data in the cloud using
45:50Python and AWS. Uh, so the files were
45:53available to reporting to Sume. Um,
45:55there's two here. Placid using SDLC get
45:58Maven Jing containeration to automate
45:59deployments so users can begin testing
46:01immediately. Uh, I'm not sure I like
46:03that. All right. and time.
46:06So, you've got four years of experience.
46:08Uh the diploma is fine. You're good.
46:10You're fine. Uh that that's okay. Uh if
46:13you have four years of experience, it
46:14counteracts a lack of degree. Um or
46:18diploma. So, you're you're more than
46:19fine with that. Second off, this should
46:21not be here. Uh if you look, it's
46:24there's a slight gap. Is it? Or am I
46:26lying? Yeah, there's a slight gap here
46:28that should not be there. So, there's a
46:31teeny gap right here. Um, second thing
46:34is
46:37you have too many bullet points here.
46:41Look, I know this is your only job. Uh,
46:46and maybe you want to put projects under
46:47it. That's fine. But a big thing I have
46:49here is you don't actually have
46:54you don't need this much. Like four,
46:57five, six, seven, eight for a job you've
46:59been at four years a little bit. four
47:02and 1/2. I'd say you can have four and a
47:04half to five bullet points. That would
47:06be fine. But no one's going to read
47:08eight or seven, however many you had.
47:10Uh, and if it's a little blank, that's
47:12okay. If you want to put a projects
47:13below it, that's fine, too. But my big
47:15my big issue is just there's quite a lot
47:17here. And the first sentence is you want
47:21to start with Java. If you are a Java or
47:24Python or full stack, you always want to
47:27start with the primary language. And in
47:28this case, it should be Java. So, um
47:33I also don't want to see that you just
47:35architected a restful API. Um I'd rather
47:39you say architected data right using
47:43Java Spring Boot RESTful APIs or however
47:47you want to describe it. Uh which would
47:49be three object-oriented programming is
47:51good and multi-threading is
47:54when I last checked it wasn't hot.
47:56Sometimes multi-threading is hot. I
47:58would double check cuz multi-threading
48:00might be a hot dog. Sometimes it's a
48:03hamburger. I think right now it might be
48:06a hot dog. So double check. Uh and then
48:08I'd rather again if you have cloud, put
48:11it up here. And you don't need to tell
48:13me S3. You're not a data engineer,
48:16right? And you don't have to say cloud
48:19here. I just need to see AWS. So I would
48:22like you to remake this a little bit to
48:25say architected
48:27using Java Spring Boot uh restful APIs
48:31in that uh to get data and delivered to
48:34AWS so that the reporting team can
48:36analyze business trades and that alone
48:38would condense these and you could throw
48:40Python down somewhere else which
48:42truthfully Python is again more of an
48:44extra credit here so you don't want to
48:46put it up here which is a problem. um
48:49like it's nice to have but it should be
48:51towards the bottom like why is it that I
48:53only have one real thing I look at here
48:55and then we go here implemented a CSCD
48:57pipeline using SDLC good
49:00Maven extra credit but it's fine Jenkins
49:03hot dog and containerization docker is
49:05good uh to automate code deployment for
49:08data pipelines but then what why was it
49:10important that users could test
49:11immediately what was the impact the
49:14answer is I don't know
49:16and you could even say to automate code
49:19instead of deployment pipeline so that
49:21our users could blank, right? And then
49:23you have to tell me why. Then down here,
49:25hot dog. You already mentioned SQL right
49:27here. Why do you need to do it twice? Uh
49:30Linux is mostly a hot dog. Uh did I am I
49:35crazy? Did I not put that? No. I'm a
49:38fool. Linux is fine. Uh Hibernate is
49:40good, but then you also have Bash, which
49:44is a hot dog. Uh,
49:47and then I don't know if I need
49:49correcting state data. Why don't you
49:50just say that to ensure the reporting
49:53team had accurate reports to analyze
49:56company trades? Like that that would be
49:58more that I would want to want to hear.
50:01So,
50:03uh, and then again, you're way down
50:04here. Microservices
50:07should be way up top. I don't know why
50:08you put it here. Did you say it anywhere
50:10else? And then Kafka, which should be
50:13there. Apache is a hot dog. You already
50:15said GitHub, so GitHub copilot is not
50:18quite what we're looking for. Even
50:19though I would like AI, I would just
50:21rather you say co copilot and gradal,
50:24which again people don't know what that
50:26is. So they could improve and why why
50:28was it important that they improved
50:30trading decisions? Uh like here's my
50:33problem is you really elongated this.
50:36And if you notice, there's a lot of
50:38stuff here that is fluff. And I'd rather
50:40a short and sweet resume rather than one
50:43long big fluffy resume. So, is this the
50:46worst resume in the world? No, not at
50:49all. But [snorts] it's very elongated
50:51and I feel like you really have four
50:53bullet points since you stretched out
50:54into eight. And that's never a good
50:57thing. And remember, the order is a
50:58little off. Java should always be before
51:01that in a Java thing. And AWS or cloud
51:04should be in the first one.
51:06Um,
51:08other than that, you just need to trim
51:10it and make it a little bit more
51:11understandable to Bob. Uh, because they
51:14can understand this part, right? So,
51:16they can analyze business trades. I like
51:18that. That is understandable. But the
51:20improved trading decisions is so broad
51:22and testing immediately. Why is that
51:25relevant? So, uh, not the worst, but
51:27could definitely use improvement. Next
51:29resume. This is a
51:32Java developer. My brain stopped
51:34working. Uh they have been searching for
51:37close to a year now within Hungary. The
51:40best I could get into is a Java
51:41specialization campus program. I have
51:43rewrote my resume many times. This time
51:45with your format. Would appreciate your
51:46review. Okay. So the first thing I would
51:50say and this this matters more than
51:52anything is I would like to check if
51:54this is a resume issue. Um, are you
51:58legally authorized
52:00to do you sorry, do you have a visa to
52:04work in the places that you're applying
52:05to? Because relocation doesn't matter.
52:08You never want to say relocating. You
52:10need to say moving to X by Y date can
52:14move earlier if needed. Uh, but if you
52:17do not have a visa, then that is not a
52:20resume issue. um
52:23which is a big big issue. So I don't
52:27know if that is the case or not, but I
52:29do know there's a lot of people that
52:31think that you could just apply anywhere
52:33and that's not the case. You need a visa
52:35to apply. Now maybe in the EU you have
52:37the right visa for it. I don't know. But
52:40that is going to be my first thing is do
52:44do you have the actual visa for it? Uh
52:48so we already know what we need right
52:50here.
52:51Uh, did I take anything out from the
52:53previous one? I don't think so. So, 20
52:56seconds is on the clock. Boop.
52:59And go. Okay, this should be one line.
53:02Uh, you don't need a date. Built a
53:04multimodal rest API with Java involving
53:07for me to full. What does this mean?
53:09This means nothing. Uh, this means
53:11nothing. This means nothing. This means
53:14nothing. Okay. Transit training program
53:16in advanced Java and object Java memory
53:18management. Again, this means nothing.
53:20Uh this means nothing time. Okay, so you
53:23have no wise and that is the end of this
53:26application. Uh you may have all of the
53:28keywords, but remember a qualification
53:31is a keyword plus why you did what you
53:33did. And the answer to why you did what
53:35you did is I have no idea. What is
53:37hibernate persistence? What is brute
53:38force login? Why is that related to a
53:41company that is looking to hire you? And
53:44I would say also why are your projects
53:46ahead of your work experience? Uh
53:49because this doesn't count that you
53:51don't need the dates and the projects.
53:53And
53:55would you even need these? Are these
53:57relevant?
53:59Cuz you've only been here for 4 months.
54:03Uh is this an internship? I you need to
54:06write this as if this is an internship
54:08because this could be a training
54:11program. I would write Java training
54:13program because this is very confusing.
54:16But again, you don't say what you did.
54:19Uh, and that is going to be the end of
54:21it. And I don't want to see that even in
54:22the training program, which this looks
54:24to be. I don't ever want to see learned.
54:27If you say learned, you are going to get
54:29rejected. You need to say what you did.
54:33So, I don't want to hear that you
54:34learned via Docker and Docker Compose. I
54:37want to know how you used that even if
54:40it was in a training program and the
54:42purpose of using that. So, this resume
54:45does not work. Um,
54:48formatting wise, it's almost okay.
54:50Again, there's less whites space than I
54:52would like. Uh, and this is right here
54:55should be one line because you can just
54:57put BSC in CS from University of
55:01Peninoa. Uh, and then you don't need to
55:03tell me when you started, only that you
55:06graduated,
55:08which you can also just say status
55:09graduated. This is the part that's
55:11really confusing. It's just there's no
55:13wise for Bob. And I one of the reasons
55:14my advice works outside the US except in
55:17the Netherlands because the Netherlands
55:20uh everywhere else in the world it works
55:22except the Netherlands is because there
55:25is a Bob in Hungary. There is a Bob in
55:27India. There is a Bob in Japan. There is
55:29a Bob in
55:32Canada. There's a Bob in Mexico. And I'm
55:34not going to tell you what those names
55:36would be there because I don't know what
55:38that would be. But there's always going
55:40to be something somebody who is not good
55:43technically who ha who gets to decide
55:45your future. And if you do not write it
55:47for them so that they understand it,
55:49you're not going to move forward. Uh
55:51except apparently in the Netherlands,
55:52which whatever they're doing is insane.
55:55Uh I don't know what they're doing cuz
55:56like I've recruited for people in the
55:58Netherlands before and they actually
55:59struggle to get US talent. It was
56:02actually kind of a big learning gap that
56:04they had was teaching people in the
56:06Netherlands how to recruit in the US
56:08because their methodologies were not
56:09working. So anyway, that was a complaint
56:11I'm going to keep complaining about in
56:12the Netherlands. Uh but yeah, the reason
56:14is there's no wise and again I do not
56:16want to see that you learned and if this
56:17was an internship or an equivalent say
56:20Java training program so that we know
56:22what it is. Uh and then this doesn't
56:25have almost anything I need. Remember if
56:27it's not in the bullet points and you
56:28don't show me why you're going to get
56:30rejected. Next resume. This is a
56:33software engineer, Python developer. Uh,
56:36wow. We've gotten like everything in
56:37this one besides front end and AI. So,
56:40uh, what do we need for Python software
56:41engineer? We need Python, SQL, any,
56:44cloud, any, restful API or REST APIs.
56:46Git, CI/CD, Django, Flask, and Docker.
56:49This is where you want Flask. Uh, Agile,
56:51fast API. This is where you want fast
56:54API. Then, Python developers are broken
56:57into two. Um you don't need all of these
56:59but you need one or the other which is
57:01AI so AI agents lang graph basically
57:04creating the infrastructure or creating
57:07multi- aent systems or full stack which
57:09is JavaScript HTML CSS react and
57:12TypeScript that is where it is broken
57:14down into and there is a difference from
57:17a Python developer that is a full stack
57:20to a full stack developer that knows
57:22Python and you can kind of see it in the
57:24qualifications. So this person is
57:26getting zero interviews. It takes them
57:28over 150 applications. Um, and they are
57:32an international, so the best we can get
57:33them is a one in 100. So, let's see what
57:36we can find. And I feel like something's
57:39off with your formatting. Not really
57:41sure what it is. Is it like I think it's
57:45the font. Something's off. Oh, it's too
57:47crunched. Right. So, before I start, I
57:49know this is kind of cheating. Uh, but I
57:51believe your font Yeah, you should have
57:55Here we go. It should be 10.5 aerial and
57:591.5 spacing. I think your spacing is
58:021.15 and not 1.5. That's probably what's
58:05happening. So
58:08let us begin
58:10and go. Okay. Built Python backend
58:12services. You can just say back end uh
58:15and REST APIs for communication platform
58:17integrated with the next.js client of
58:19Postgre reminders business workflows.
58:22built a developed Reddus hot dog and
58:26bowl MQ hot dog. Yeah, it doesn't matter
58:28cuz you don't have any whats develop
58:30Python good SQL contractors and that's
58:33two development business rule of logic
58:35uh time. So as an international you need
58:40normally you need 75% of these. I don't
58:43see that. I we're not going to count the
58:45AI cuz you know that's not what we're
58:47going for with this one. But
58:50like why don't you just say built
58:53a communication platform like built the
58:57backend using of a communication
59:00platform using python
59:03rest apis and then typescript and
59:05postgrql but what about HTML and CSS and
59:08JavaScript I don't see in fact I'm even
59:10going to control F here no I'm not f in
59:12the wrong one Lee where is the
59:15JavaScript uh I don't see it that is
59:18probably going to be a decline. Where is
59:20the HTML? I don't see it. Where is the
59:21CSS? I don't see it. Where is the React?
59:24I don't see it. Uh, and that is me just
59:26fing, which again, the problem you have
59:29here is you don't have any. So, there's
59:32just not enough here. And remember,
59:34you're in a harder to find thing than
59:36anything else. As an international, you
59:38need basically all of this. I don't see
59:41cloud. Um, I don't see
59:44Git. I don't see CI/CD. I don't see
59:47Django. I don't see Flask. I don't see
59:48Docker. And your W's still do matter,
59:52but your W's don't matter if you don't
59:53have that. Like where is a fast API?
59:57Where is the actual full stack? I don't
59:59see that. This implies you just did back
1:00:02end develop Python and that. And this is
1:00:07that's a fine match roadside. This is a
1:00:11fine for Y for Bob. The problem is you
1:00:13only have two things which is Python and
1:00:15SQL. And then you don't have anything
1:00:17here. So there's zero here. There's
1:00:22three. There's four here.
1:00:24There's zero here,
1:00:28which is getting kind of cut off because
1:00:29your margins are so small. There is one
1:00:33here. And this is a bad Y for Bob.
1:00:37There's too many numbers. There's zero.
1:00:39Why do you even have this? This is not
1:00:41relevant at all. If it's not relevant,
1:00:44it shouldn't be here. I don't know why
1:00:45you have this. Then we have the projects
1:00:47and it's p Python a fast API
1:00:50and then I still don't see it lomit. You
1:00:52fill this with like again I understand
1:00:54why you're afraid. You're trying to
1:00:56prove how good you are but that's not
1:00:58what a resume is for. I would reject
1:01:00this even if you were a US citizen
1:01:02because you just don't have what I'm
1:01:03looking for. Where is the Git, the
1:01:05CI/CD, the Django, the Flash, the
1:01:07Docker? Where's the agile? Where's the
1:01:09fast API? It's all the way down here. No
1:01:11one's going to go down that far. Where
1:01:14is the full stack? I don't see it. I
1:01:16don't see any full stack on here. I only
1:01:18see a back end. And you need to make
1:01:21sure this is razor focused. So, I'm not
1:01:24afraid of you making this more than one
1:01:27page. Who cares? The biggest issue is
1:01:30this just doesn't have what I need. And
1:01:32again, if you were a US citizen either,
1:01:33there's the same thing. You would get
1:01:35rejected. You don't have what we need.
1:01:38Why is anything besides Python here even
1:01:40relevant for what I'm looking for? It's
1:01:43not. Why do I have to Why is this
1:01:45sentence here? There's nothing I need.
1:01:48This only has two stuff, which is very
1:01:51hard to see. This has three. This has
1:01:53zero besides Python, which you already
1:01:55mentioned. So, why do I even need it?
1:01:58Why is it I have 1 2 3 4 5 6
1:02:02bullet points and seven keywords to go
1:02:05between all of those?
1:02:08and your formatting is bad as you the
1:02:11the font size or the the the thing
1:02:13between them. You need to have a good
1:02:14hard look about what skills they
1:02:16actually want, which is this, and how to
1:02:18include them because there's no way
1:02:20they're going to move you forward.
1:02:22Now, if you're going just AI, that's
1:02:24fine, but I don't see it till down here.
1:02:29And even then that's integrating open AI
1:02:31services but I want to see agentic work
1:02:35which I don't see which is lang graph or
1:02:38lang chain mainly lang graph so the
1:02:41problem here is it's you don't have the
1:02:43qualifications you are showing that you
1:02:45do not have the qualifications and no
1:02:47one is going to move you forward without
1:02:48them next resume this is our second
1:02:52product manager which uh wow actually I
1:02:55don't usually get a ton of product
1:02:56managers so the twice in one stream is
1:02:59pretty interesting. So again we need
1:03:01degree industry presentation and
1:03:02communication multiple projects and
1:03:04deadlines MS office work crossf
1:03:07functionally with product shipping
1:03:09product shipping product from 0ero to
1:03:11one communicate clearly on product goals
1:03:13and translate it to the product and
1:03:15cross functional matrix and stakeholder
1:03:17management. So this person has stated
1:03:20nothing. They only get one in 100. So
1:03:22I'm expecting to find one or two things
1:03:24that I like but a lot of it is going to
1:03:26be bad. So 20 seconds is on the clock
1:03:29and
1:03:32boop and go. Okay, this doesn't matter.
1:03:36This is a problem. Uh drove 15 in
1:03:40procurement request from intake
1:03:41approvals buyer. This means nothing. Uh
1:03:44built three product road maps in
1:03:45advanced to three python. What does this
1:03:47mean to pilot driving writing stories?
1:03:50This is okay writing stories but it's
1:03:52bad for Bob. reduced repeat client
1:03:53escalation by 25% across by this means
1:03:57nothing bad authored. Okay. Type. So the
1:04:00one thing I'm I'm kind of confused at
1:04:02here is um
1:04:08how did you Oh, you're an in Okay. See,
1:04:11this is why the formatting matters. Uh I
1:04:14missed the in because you formatted this
1:04:16so poorly. I missed the fact that this
1:04:19showed an internship. Um, the other
1:04:22thing I want to note is again remember
1:04:24this this is this this is this this
1:04:26you're not going to get a job job
1:04:29[clears throat]
1:04:30until 3 months prior to you graduating.
1:04:34Um,
1:04:36now I think maybe is this person looking
1:04:38for a internship? Cuz they didn't
1:04:41mention an internship. Maybe they're
1:04:43looking for an internship. Uh, but it
1:04:46doesn't look like it. So I could switch
1:04:48this to an intern. Um, but like the big
1:04:51issue here is everything. Like why does
1:04:53it matter that you drove 15 million to
1:04:55procurement
1:04:57that's not the product again? You are
1:04:59making the same mistake as the previous
1:05:01person is that you're not selling the
1:05:04product.
1:05:06you're selling yourself and drove 15
1:05:09million in product requests from intake
1:05:10to approvals to SAP Aribba an internal
1:05:12sourcing system according to buyers and
1:05:14internal tracking of request injur
1:05:16that's not selling yourself which again
1:05:17I don't even like the word selling
1:05:19yourself but um okay they just messaged
1:05:22me on YouTube that they are looking for
1:05:24an internship so they are looking for an
1:05:26internship you got to tell me that
1:05:28because these keywords are slightly
1:05:30wrong I I have the internship for a
1:05:33product manager but I'm going to tell
1:05:34you they're a little outdated. They're
1:05:36about 2 months outdated. So, we're
1:05:38because they did not tell us, we're
1:05:40going to go for the outdated product
1:05:42manager internships because I have to
1:05:45tell I have to do this every 3 months.
1:05:48The product manager internship the last
1:05:50I did it. No, no, no. Never mind. I I
1:05:52lied to you all. I did it in last month.
1:05:55Never mind. This is fresh. I lied to
1:05:56you. This is it. So, I lied. These are
1:06:00fresh. These were last done on the 18th
1:06:04of uh brain stop of September.
1:06:09No, August, September, whatever last
1:06:11month is. I am a This is close to 4
1:06:14hours of streaming. All right. So, what
1:06:16do we need for an intern? We need
1:06:17degree, MS Office, Excel, PowerPoint,
1:06:19Word, Outlook, communicate to technical
1:06:21and non-technical people, influence
1:06:23people with data to solve problems, take
1:06:25direction and criticism, and work
1:06:26together with others. Uh, I don't think
1:06:29I see any of that, do I? Um, let's see.
1:06:33So, with new eyes, remember this doesn't
1:06:35count. Drove procurement request from
1:06:37intake to recording with buyers to
1:06:39internal. So, I like I like Where did it
1:06:43go? Where did it go? Where did it go? I
1:06:44like
1:06:46this. Nope. Nope. Nope. Nope. Nope. I
1:06:48like
1:06:51this. So the problem is I don't actually
1:06:55know what you did besides procurement
1:06:57requests. This is too technical. Bob
1:06:59doesn't understand it. I do like the
1:07:01coordinated buyers with internal uh with
1:07:03internal requesters because that does at
1:07:05least show that you can communicate to
1:07:07some people. The problem I have here is
1:07:10your bullet points are so technically
1:07:12deep that you have failed to prove that
1:07:15you can communicate to nontechnical
1:07:16people cuz you are not going to be with
1:07:18another product manager who's going to
1:07:20be like a
1:07:22blah blah you're going to be with
1:07:23someone like Bob and Bob is not going to
1:07:25understand this
1:07:27is Bob going to understand built three
1:07:29prioritize product roadmaps advance two
1:07:30to three Python minimum projects to
1:07:32pilot by defining uh adoption key
1:07:34performance indicators writing user
1:07:35stories with end users and executive
1:07:37requests
1:07:38probably not. Or could you just say
1:07:40instead
1:07:42uh created
1:07:45documentation using Excel, PowerPoint,
1:07:47Word, and Outlook uh which allowed us to
1:07:54define product specifications
1:07:57uh for our X and Y like that would be
1:07:59better. And you know what I don't see? I
1:08:02don't see that you can influence people
1:08:04because that is actually a requirement.
1:08:05I don't see that you can work well
1:08:07together with people. Um
1:08:09this like again you you're lucky in that
1:08:12you've already gotten four internships
1:08:13so you don't need to worry as much about
1:08:15direction and criticism cuz you've
1:08:16already had about four other
1:08:18internships. It's usually like okay you
1:08:20can kind of take direction and criticism
1:08:22so that would go towards more extra
1:08:24credit but like I don't know what you
1:08:26have here. Um
1:08:29like what is a one impactful solution
1:08:33hackathon by architecting an agentic
1:08:36sales assistant to neuroqueries tools on
1:08:38enterprise AI? How is that useful? Like
1:08:42you you need you are getting 100 to one
1:08:46because
1:08:48you're not showing the basics. And
1:08:51remember the basics across every resume
1:08:53is what gets you a job. If you want to
1:08:55see somebody who let their ego get in
1:08:57the way of actually writing a good
1:09:00resume, you can check out episode 500 I
1:09:02made because I reviewed my own resume
1:09:04and guess what? I let my ego get in the
1:09:05way of making a good resume. This is
1:09:08letting your ego get in the way of
1:09:10making a good resume. This doesn't show
1:09:12you can influence people. This doesn't
1:09:13show you can take direction and
1:09:14criticism and work together with others
1:09:16which again that would be extra credit.
1:09:18It doesn't show that you can communicate
1:09:19to technical and non-technical people.
1:09:21It does show your degree and it doesn't
1:09:23show that you can do MS Office and that
1:09:25is why you're failing is because you
1:09:27wrote this for an audience that doesn't
1:09:28exist. Also, your formatting is terrible
1:09:30and you need to use this one. So, uh,
1:09:33with that said, that is the last of the
1:09:35résumés for this episode. Thank you very
1:09:37much for watching. If you ever want your
1:09:39resume reviewed, feel free to drop by
1:09:40the live stream every Monday, Wednesday,
1:09:42Friday. And again, thank you so much for
1:09:45sharing this content with your friends.
1:09:46And if you are a member or want to be a
1:09:48member, you get access to videos early
1:09:50and you get access to the past live
1:09:52streams and it keeps this channel alive.
1:09:54I could not keep making this content
1:09:56without your support and your
1:09:57membership. So, thank you for allowing
1:09:59me to make this content. And with that
1:10:01said, I will see you in the next uh
1:10:04I will see you in the next video to help
1:10:06you get ahead of your job search

About this transcript

This page contains the full transcript of Want a Software Engineer Job? You NEED This by Headless Headhunter, generated from the public captions YouTube serves with the video. The transcript has 12,174 words across 1,742 segments, with the original timestamps preserved so you can click any line to jump to that moment in the embedded player.

What you can do with it

Use the transcript to take notes, quote the speaker, build a study guide, generate a summary with ChatGPT or Claude via the YouTube Summary tool, or export it as a timed subtitle file with YouTube to SRT. You can also re-open it in the transcriber to choose a caption track available on the video.

Free YouTube transcript tool

YouTube2Text is a free YouTube transcript generator — no signup, no daily limit. Paste any YouTube link and get the full transcript instantly, with timestamps, click-to-jump, caption language selection, AI prompts for ChatGPT, Claude, and Gemini, and exports to TXT, SRT, VTT, or Markdown.