msb-public
/
tech-interview-handbook
mirror of https://github.com/yangshun/tech-interview-handbook
2
1
Code Issues Projects Releases Wiki Activity

Reverting formatting of markdown table.

Browse Source
pull/612/head
figo-rabo 2 years ago
parent c2178703fc
commit 70502550fe
1 changed files with 9 additions and 13 deletions
Show Stats Download Patch File Download Diff File

22
apps/website/contents/resume.md
Unescape View File

@ -77,22 +77,18 @@ ATS readers need to identify and parse standard types of information from your r
This is the order which has worked well for me and recommended by recruiters:
| Section | Heading Name |
| ----------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------- |
| Professional summary | (Use resume headline as section title, for e.g. "Senior Software Engineer at Google with over 5 years of experience leading teams") |
| Contact information | "Contact Information" |
| Skills - programming languages, frameworks, etc. | "Skills" |
| Experience | "Work Experience" |
| Education (Note: if you are still in school or have less than 3 years of experience, you may put Education first) | "Education" |
| Projects | "Projects" |
| Other optional sections - e.g. Certifications, Awards, etc | "Awards and Accolades" / "Certifications" / "Awards, Accolades and Certifications" |
| Section | Heading Name |
| --- | --- |
| Professional summary | (Use resume headline as section title, for e.g. "Senior Software Engineer at Google with over 5 years of experience leading teams") |
| Contact information | "Contact Information" |
| Skills - programming languages, frameworks, etc. | "Skills" |
| Experience | "Work Experience" |
| Education (Note: if you are still in school or have less than 3 years of experience, you may put Education first) | "Education" |
| Projects | "Projects" |
| Other optional sections - e.g. Certifications, Awards, etc | "Awards and Accolades" / "Certifications" / "Awards, Accolades and Certifications" |
:::caution
Never add symbols to your headers to avoid ATS readability issues.
:::
<InDocAd />
## How to write good Software Engineer resume content

Write Preview
Loading…
Cancel
Save