The document provides guidance on writing effective resumes, emphasizing the importance of concise, clear presentations of skills and experiences. Key suggestions include tailoring resumes for each job application, focusing on relevant skills, and utilizing the 1-2 page format. It also highlights common pitfalls in resumes and the critical role of networking in the job search process.

2. How to write
a better
resume
John Clegg - Summer of Tech
Ruth McDavitt - Summer of Tech

3. 1) Why do you need a resume?
2) What are companies looking for?
3) What does a good resume look like ?
4) How to write a resume
Today

4. When I was in India,
An ad for a Java programmer got
>1500 responses in the first day

5. Disclaimer

6. Why am I doing this ?

7. The process of getting a job sucks

8. Your CV is the first contact
with a company

9. I’m here to help you get to
the top of the pile

10. Quick thoughts...
1.What are you good at?
2.Participate and create a track record
3.Take opportunities to learn
4.Your career has already started!
5.Find a mentor

11. Background

12. How long do does a
recruiter read a
resume ?

13. You’ve got 20 seconds to
impressYou have 20 seconds to impress
(Study 2005)

14. You’ve got 20 seconds to
impress
X

15. (Research 2012)

16. Eye Tracking shows CV Format matters

17. Why do you need a good resume?

18. Recruiters: Friend or foe?

19. Bots - Resume terminated

20. HR Dept - The gatekeepers

21. Networking....

22. Who do you know ?

24. What is the purpose
of a resume ?

25. To get you an
interview !

26. What does a
typical resume
tell me about
you ?

27. Example: Bad CV :-(

28. Example: Bad CV :-(

29. Example: Bad CV :-(

30. Example: Bad CV :-(
Tex
t

31. 1. What your role was
2. Where you have worked
3. What you have done in that
role ...
A normal resume tells
me...

32. ...
Job –> Role -> Results
A typical resume tells me...

33. Houston, we have a problem!

34. This type of resume
doesn’t show
what you’re
good at !?!?

35. Analogy...

36. What if you looked for a date
the same way you wrote
your resume ?

37. So what do
companies really
want to know
about you ?

38. What you are going to do for me?

39. Why do you want to work for us?

40. What are you good at ?

41. What are your core skills?

42. So what does a good
resume look like ?

43. Example: Good CV :-)

44. The resume told me ...
1) Who he is
2) What core skills he has
3) Where / How he has
performed those skills
repeatedly
Why was it good?

50. OK
Now what ?

51. What’s in a good
resume ?

52. 1. 1-2 page resume
2. Technical summary
3. Qualifications summary
4. References
Your “resume” should have...

53. 1. Your personal promise
2. 4-5 core competences / skills
with proof
3. Career History
Your 1 page resume should
have...

54. For each project / work look at
Objectives - What were the goals?
Analysis - What did analysis did you make?
Actions - What action did you take ?
Results - What were the results?
OAAR approach

55. behaviours
which lead to
core competencies
OAAR approach highlights

56. Example - Summer of Tech Project

57. Determined, Problem Solver,
Challenges convention,
Consistent, Lateral Thinker,
Passionate, Results driven, Finds
Patterns, Fast learner, Analytical
Examples of behaviours

58. For each skill:
ie:
What did you learn (SKILL)
By what actions (PROOF)
to achieve what result (RESULT)

59. Example 1:
Learning
Gained competency in Java, Python and C++ by
completing several course projects in OO design and
concurrency over the last 6 months. Implemented
Disrupter and Reactor patterns in Java.

60. Example 2:
Leadership
Led a 5 person project team to build an Android app
- the Bubble game. The team developed a multi-
level game which required cross function
specialisation across graphics, level development
within a 2 month time frame. The game was
submitted to Google Play store and has been
downloaded 3000 times.

61. Takeaways for Resume
4-5 Skills
2-3 Technical skills
1-2 Soft / Communication /
Team skills
Skill order is important

62. Provide one page about your technical skills:
–Skill
–Examples
–Level of Experience
–Is experience current
Drop anything that isn’t relevant
- “Should I include word and excel ???”
Technical Skills Resume

63. Technical Skills Example

64. Example Good CV

69. 5 resume tips

70. Tip #1
Resume must
be
one - two
pages

71. Tip #2 Adapt your resume to EVERY job

72. Tip #3
Tip #3 Put non-important
stuff in the back

73. Tip #3
Tip #4 Write it with
an employer in mind

74. Tip #5 Only use PDF

75. • Put the important stuff first
• Resume only 1-2 pages and PDF
• Resume contains
○ Your Goals / Aspirations
○ 5 core skills / attributes
○ Education Summary
• 1 page technical skills summary
• 1 page qualifications
Summary...

76. What should the employer
see in your Resume ?
- Who you are
- What you want to do
- What you can do for them
- Why you are interested in them
Summary...

77. Bonus tips

78. How do I beat the myths ?

79. Recruiters:
Call them
Always ask where you’re

80. Bots
Keyword match specific roles

81. HR Dept
Call them, talk to the Team Lead

82. Networking....
Meetups

83. Questions?

84. See you next time for part 2

85. Resume workshop part 2

86. RESUME SMACK DOWN

87. • Put the important stuff first
• Resume only 1-2 pages and PDF
• Resume contains
○ Your Goals / Aspirations
○ 5 core skills / attributes
○ Education Summary
• 1 page technical skills summary
•1 page qualifications
Summary...

88. What should the employer
see in your Resume ?
- Who you are
- What you want to do
- What you can do for them
- Why are you interested in them
Summary...

89. WARNING

90. •Resume Smackdown - a look over 100
resumes
- the Good, the Bad and the Ugly
•OAAR technique in practice
- Guest Fictional Character
Coming up

91. Findings from 100 student resumes
•Overall not bad. Better than I thought.
- Grammar / Spelling are OK. (BUT I’m not a grammar nazi)
•Lack of Depth
- What are you good at with APPLIED examples ?
•Relevance
•Not answering
- Who are you?
- Why are you good at what you do?
- What you can do for me?

92. Results - 100 student resumes
Excellent OK BAD
Resume
Structure
36% 32% 32%
Grammar
Spelling
82% 16% 2%

93. Results - 100 student resumes
Excellent OK BAD
Who are you 21% 39% 40%
What are you
good at
13% 38% 49%
What can you
do for me
11% 28% 61%
Depth 8% 51% 41%

94. Results - 100 student resumes
Excellent OK MISSING
Career
History
16% 68% 16%
Technical 13% 11% 76%
Referees 22% 39% 39%

95. Results - 100 student resumes
YES NO
Follow instructions 95% 5%
BONUS 21% 79%

96. OAAR Practice - #1

97. Fictional Character

98. Let’s break it down...
1. What did s/he do ?
2. What behaviours did s/he show
3. “Career” History
4. “Education”

99. 1. What did they do ?
Objectives aka
What were they trying to achieve ?
Analysis aka
What thinking / planning did they do ?
Actions aka
What actions did they take to achieve the goals ?
Results aka
What results did they achieve?

100. 2. List the behaviours
Find commonalities
Write the skill in this form…
What did they learn (SKILL)
By what actions (PROOF)
to achieve a result (RESULT)

101. Achiever Activator Adaptability Analytical Arranger Belief
Command Communication Competition Connectedness
Consistency Context Deliberative Developer Discipline
Fairness / Empathy Focus Futuristic Harmony Ideation
Inclusiveness / Includer Individualization Input Intellection
Learner Maximizer Positivity Relator Responsibility
Restorative Self-Assurance Significance Strategic
Some personal strengths

102. Questions?