The following is a video of me giving this presentation: https://youtu.be/xJlS_2zIkUw
Structure, Content, and not lying.
The following is a walkthrough of my methodology for assembling a resume as a software developer.
5. General Advice
● Don’t lie
● Be prepared to answer questions
● Don’t hide keywords in the margins
● Don’t do more than 2-pages
● Don’t copy someone else’s resume
11. Opening Statement
● What you care about
● How you think
● Elevator pitch
● Maybe the only thing read
12. Kell Skills/Accomplishments
● Focus on a Keyword
● Relevant to Position
● Action Focus
● Current Work
Cybersecurity
● A deep understanding of all things cybersecurity having served as a Cryptologic
Warfare Officer for Company C.
● At Company A, implemented, managed, and secured the AWS EKS-based delivery
environment requiring hundreds of simultaneous containers for hosting both
persistent infrastructure and dynamic containers.
● At Company B, used Traefik to enable both HTTPS mutual auth and SNI to secure
vendor REST interactions with internal Cloud Native systems.
Operating at Scale
● At Company A, revolutionized monitoring and alerting to meet the needs of
running web-scale systems at 99.9% availability via Prometheus, Grafana, Kafka,
Elastic Search, and Zipkin (distributed tracing).
● At Company B, built the monitoring infrastructuring around a combination of
New Relic, Zabbix, and Grafana for dealing with AWS EC2 and EKS infra and apps,
capable of predicting certain types of issues prior to occurrence.
14. Avoid Red Flags
● Length
● Typos
● Bad Capitalization
● No longer relevant technologies
● No relevant experience
Editor's Notes
Length (Minor)
A resume should be 1-2 pages, and this becomes a big deal when a company mandates that the people involved in the hiring process read the entire resume. Anything longer than 2 pages is a CV, which is a matter of attention to detail. However, if the resume is over 10 pages that is significant enough to just be thrown out.
Typos (Minor)
Typos are a matter of attention to detail. If the resume is littered with typos, meaning more than 5 of them, I tend to throw it out. Attention to detail is critical in all aspects of software development.
Bad Capitalization (Minor)
Like a typo, bad capitalization refers to the use of a common acronym, by not using the capitalization or punctuation. For example, referring to JavaScript as JAVASCRIPT or JavaSCRIPT. This is a strong indication that an individual is not as familiar with a technology as they claim to be.
No Longer Relevant Tech (Major)
Unless a job is about maintaining some old legacy system, focusing on no longer used tech is an indication that the individual is no longer proficient in the relevant technology stack. For example, if someone has Salesforce Development experience, and specifies Aura but not LWC, or Classic but not Lightning.
No Relevant Experience (Major)
Unless this is a person band new to the field and we are accepting a hire with zero experience, the resume should indicate relevant work experience. If they don’t have existing job tiles involved software development, specifically in Dev and Ops roles, they will not be able to successfully fill a DevOps position.