← All videosTHE SHORT VERSION
Watch the course ↗

software engineering / tech careers / job search

Stop Getting Ignored: Build a Resume That Stands Out

Build a résumé that makes your software engineering work easy to understand. Follow the template, organize education, experience, projects and skills, explain the impact of your work, and revise with two independent AI reviews. Apply the same process to LinkedIn and GitHub.

Transcript

0:00You're a junior level software

0:01engineer and you finally have a

0:03little bit of real world work

0:06experience

0:07It isn't something monumentally

0:09substantial

0:10Maybe it's just you're working

0:11at a research lab at your

0:13institution

0:14Maybe you won second place at

0:16a hackathon

0:17Maybe you had an unpaid internship

0:20which was really just your friend

0:21Greg and building up his website

0:23But you put it on your

0:25resume as a software engineering

0:26intern at Greg LLC Technologies

0:29You have a little bit of

0:31real world work experience I'm

0:35going to teach you how to

0:36turn that experience into a resume

0:37that attracts the attention of

0:40these big tech recruiters So if

0:43you want to be a software

0:45engineer commanding 100,000

0:48150,000

0:50200,000 per year then save

0:53this video and send it to

0:55your friend that always talks about

0:56how AI is going to take

0:58your job AI is going to

0:59take his job but it's not

1:01going to take yours because you

1:02did these steps to prepare yourself

1:05for the industry So step one

1:08you need to find a good

1:10resume template that you like You

1:12can Google things like Stanford

1:15Resume Template or Harvard Resume

1:17Template or just Google Resume

1:19Template and fill it out yourself

1:22or hell give it to Codex

1:24and it can fill it out

1:26for you And actually let's do

1:28a little bit of an aside

1:29because the rest of these steps

1:30will require you to use an

1:33agentic coding tool So this can

1:35be Codex This can be Claude

1:38Code You can be the weirdo

1:40that uses Hermes

1:41I wouldn't really use Hermes but

1:43if you want to use Hermes

1:44and it has access to a

1:47browser in your docs you can

1:48And if you did that that

1:49can even be a project on

1:51your resume Let's be real An

1:52Hermes agent can be a project

1:54on your resume but you need

1:55to have an agentic coding tool

1:58You're going to give the agentic

2:00coding tool your resume

2:01I'm going to fill in all

2:03of your experience

2:04It should likely be just one

2:06page and it should look like

2:08this as follows the top of

2:10your resume will have your education

2:12Unless you just didn't go to

2:14college then you might want to

2:16skip it out but preferably you

2:17have an education on the top

2:20Below that is your experience It's

2:22not your skills It's not your

2:26projects unless you have no relevant

2:28work experience

2:30The next part is your experience

2:33and then below your experience

2:35is your projects

2:38After that you want to have

2:39your skills and your skills should

2:41include any technology that you

2:43can talk intelligently about This

2:45could include Python CSS

2:48HTML and JavaScript

2:49It might include React You might

2:51have taken a course in Java

2:53It can be all these things

2:55but it should also include the

2:57technologies that these big tech

2:58recruiters are actively looking

3:00for Things like Postgres MongoDB

3:02and yes even agentic coding tools

3:05like Cursor

3:06Codex and Claude Code After you've

3:09done all of this you want

3:11to give your finished resume to

3:13a fresh session in an AI

3:16chat tool like ChatGPT

3:18Google Gemini

3:20or Claude

3:21And then you're just going to

3:22say this simple thing

3:24grade this resume

3:26It's going to give you an

3:28unbiased account of your resume

3:30and it's going to give you

3:31a grade for it

3:33And with that grade it's going

3:35to give you specific feedback that

3:38you can improve on Some of

3:40the things that are really important

3:42are making sure your experience

3:43doesn't just explain what you did

3:46but it explains what your impact

3:49was Did you reduce the latency

3:50of this service by 50

3:54How? Did you optimize a query

3:56and made it more performant Did

3:58you add a caching layer to

4:00the system What did you do

4:03and what was the impact

4:05That should absolutely be on the

4:07experience for your resume You

4:10want to have selective bolding

4:11so if a recruiter reads your

4:12resume and they look it over

4:14in three seconds they have an

4:16idea of what you actually did

4:18You don't want just large blocks

4:20of text You want to have

4:23direct links to your GitHub profile

4:26You want to have the experience

4:27organized in a way that makes

4:29sense likely in chronological order

4:32unless you have an extremely special

4:35circumstance which you probably

4:37don't so put it in chronological

4:39order The top of your resume

4:40should have your name

4:42It should have a U S

4:44citizen if you're a U S

4:46citizen It should include an email

4:48address you want recruiters to

4:49contact you You might even want

4:50to include your phone number and

4:52yes your LinkedIn profile and GitHub

4:54profile are also strong candidates

4:57and yes spend a little bit

4:59of time polishing these profiles

5:02You're going to keep grading the

5:05resume over and over and over

5:07again until at least two different

5:09independent language models grade

5:12your resume to be an A

5:13or better

5:15Once you have a resume that's

5:16A or better you're ready to

5:18start finding the software engineering

5:20jobs of your dreams Good luck

Join the conversation

Loading conversation…