You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@@ -10,158 +10,180 @@ This repository contains materials for the Google Technical Resume Workshop, whi
10
10
11
11
## Mission
12
12
- Organize the world's information and make it universally accessible and useful.
13
-
-Building a Google for all of us to build helpful products for everyone
14
-
-To build products that help billions of people reach their goals, we're bringing together talented people from everywhere, and empowering them to do their best work.
15
-
16
-
> What is the purpose of a resume?
17
-
-Beyond the basics: Your narrative
18
-
-Making the first impression
19
-
-Highlighting relevant qualifications
20
-
- Your goal: The interview
21
-
-An opportunity to open a door and get that interview
22
-
- Give the employer a chance to say "hey this resume really sticks outlet's talk about this person"
23
-
- The Ultimate Outcome: Getting the job
13
+
-Build a Google for all of us to create helpful products for everyone.
14
+
-Bring together talented people from everywhere and empower them to do their best work, helping billions reach their goals.
15
+
16
+
> **What is the purpose of a resume?**
17
+
-Go beyond the basics: Tell your narrative.
18
+
-Make a strong first impression.
19
+
-Highlight relevant qualifications.
20
+
- Your goal: Get the interview.
21
+
-Open the door to an interview opportunity.
22
+
- Give the employer a reason to say, "This resume stands out—let's talk to this person."
23
+
- The ultimate outcome: Get the job.
24
24
25
25
# Important Notes for First Resumes
26
-
- High School Highlights: Know when to let go
27
-
- Coding competition, hackathon organize, start a club
28
-
- Don't let high school information overshadow other skills
29
-
- Beyond the Classroom: Build your Story now
30
-
-Want to see engagement outside of school
31
-
- Tech hobbies?, Coding projects, Open source contributions
32
-
- Skills that shine: Focus on what you can do
33
-
- Instead of just saying "I am efficient in problem solving", demonstrate it with examples
34
-
- Even without extensive experience, make sure that the skills that you have garnered are highlighted
35
-
- Resume essentials: Clarity, structure, and impactful language
36
-
-Every second word highlighted, different fonts, commas
37
-
- Keep it simple, clear, and structured
38
-
-Make sure you have the basic clarity, basic fonts, basic sentence structure that doesn't offput anyone
26
+
-**High School Highlights:** Know when to let go.
27
+
- Coding competitions, hackathon organization, starting a club.
28
+
- Don't let high school information overshadow other skills.
29
+
-**Beyond the Classroom:** Build your story now.
30
+
-Show engagement outside of school.
31
+
- Tech hobbies, coding projects, open source contributions.
32
+
-**Skills That Shine:** Focus on what you can do.
33
+
- Instead of just saying "I am efficient in problem solving," demonstrate it with examples.
34
+
- Even without extensive experience, highlight the skills you have developed.
35
+
-**Resume Essentials:** Clarity, structure, and impactful language.
36
+
-Avoid excessive highlighting, fonts, and punctuation.
37
+
- Keep it simple, clear, and structured.
38
+
-Use basic clarity, fonts, and sentence structure that don't distract the reader.
39
39
40
40
# General Resume Tips
41
41
42
-
## Know your audience
43
-
- Adapt and iterate, resume is never done
44
-
- Quantify wins, show don't tell
45
-
- Communicate your value, what makes you the right fit
46
-
- Authenticity matters let your unique contributions shine
42
+
## Know Your Audience
43
+
- Adapt and iterate—your resume is never done.
44
+
- Quantify wins; show, don't tell.
45
+
- Communicate your value—what makes you the right fit?
46
+
- Authenticity matters; let your unique contributions shine.
47
47
48
48
## Formatting
49
-
- Save as PDF
50
-
- Bullet points and consistent formatting
51
-
- Action + metric = results
52
-
- Github & contact information
53
-
- Attach a link to the portfolio (especially for US)
54
-
55
-
## IMportant notes
56
-
-**Review qualifications:** review minimum and preferred qualifications
57
-
-**Coursework:** include relevant coursework pertinent to the role
58
-
- Think DSA, OS, etc.
59
-
- Showcase your foundational knowledge
60
-
-**References and objectives:** do not include references or lengthy objectives
61
-
- Better to skip especially early on in your career
62
-
- Objectives are outdated
63
-
- Only include when explicitly asked
64
-
-**One page:** Please keep your resume to only one page
65
-
- Aim for a single page, very selective, and most relevant information
66
-
- Quality over quantity
67
-
68
-
## What should I include?
69
-
70
-
### Must have
71
-
- Contact information
72
-
- Name, email, phone
73
-
- Location not really necessary
74
-
- Education
75
-
- Lead with this, major anticipated graduation montha nd year
76
-
- Technical skills
77
-
- Programming experience, not just about internships, personal projects, tehcnical skills
78
-
- UX designs, hackathon wins, etc, whereever you have applied skills
79
-
- Portfolio
80
-
- Portfolio can showcase, well documented piece of work that can showcase skill
81
-
82
-
### Good to have
83
-
- Awards and Honors
84
-
- Academic awards
85
-
-*Interests*
86
-
- Super selective
87
-
- What can spark conversation with the interviewer
88
-
- Tools
89
-
- Figma, Adobe, Sketch, etc
90
-
- Qualifications and Projects
91
-
- 1 Page
49
+
- Save as PDF.
50
+
- Use bullet points and consistent formatting.
51
+
- Action + metric = results.
52
+
- Include GitHub and contact information.
53
+
- Attach a link to your portfolio (especially for US applications).
54
+
55
+
## Important Notes
56
+
-**Review Qualifications:** Review minimum and preferred qualifications.
57
+
-**Coursework:** Include relevant coursework pertinent to the role.
58
+
- Think DSA, OS, etc.
59
+
- Showcase your foundational knowledge.
60
+
-**References and Objectives:** Do not include references or lengthy objectives.
61
+
- Better to skip, especially early in your career.
62
+
- Objectives are outdated; only include when explicitly asked.
63
+
-**One Page:** Keep your resume to one page.
64
+
- Be selective and include only the most relevant information.
65
+
- Quality over quantity.
66
+
67
+
## What Should I Include?
68
+
69
+
### Must Have
70
+
-**Contact Information:**
71
+
- Name, email, phone.
72
+
- Location is not necessary.
73
+
-**Education:**
74
+
- Lead with this; include major and anticipated graduation month and year.
75
+
-**Technical Skills:**
76
+
- Programming experience, not just internships; personal projects and technical skills count.
77
+
- UX design, hackathon wins, etc.—wherever you have applied skills.
78
+
-**Portfolio:**
79
+
- Showcase a well-documented piece of work that demonstrates your skill.
80
+
81
+
### Good to Have
82
+
-**Awards and Honors:**
83
+
- Academic awards.
84
+
-**Interests:**
85
+
- Be super selective.
86
+
- Include what can spark conversation with the interviewer.
87
+
-**Tools:**
88
+
- Figma, Adobe, Sketch, etc.
89
+
-**Qualifications and Projects**
90
+
-**One Page**
92
91
93
92
### Small Stuff
94
93
- Consistency
95
94
- Proofread
96
-
- Actionbased language
95
+
- Action-based language
97
96
- PDF format
98
97
99
-
## Resume Flow: Our recommended structure
98
+
## Resume Flow: Our Recommended Structure
100
99
- Education (technical skills)
101
100
- Work experiences
102
101
- Projects (classroom & personal)
103
-
- Leadership Updates
102
+
- Leadership updates
104
103
105
-
# Resume deep dive
104
+
# Resume Deep Dive
106
105
107
106
## Header
108
-
- Name listed at the very top
109
-
- Contact information
110
-
- Email, phone number, LinkedIn, GitHub, portfolio link
0 commit comments