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

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

@ -78,7 +78,7 @@ 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: This is the order which has worked well for me and recommended by recruiters:
| Section | Heading Name | | 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") | | 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" | | Contact information | "Contact Information" |
| Skills - programming languages, frameworks, etc. | "Skills" | | Skills - programming languages, frameworks, etc. | "Skills" |
@ -89,10 +89,6 @@ This is the order which has worked well for me and recommended by recruiters:
:::caution :::caution
Never add symbols to your headers to avoid ATS readability issues.
:::
<InDocAd /> <InDocAd />
## How to write good Software Engineer resume content ## How to write good Software Engineer resume content

Write Preview
Loading…
Cancel
Save