4 ms·
Maybe. How intelligent are the resume scanners? Just a few years ago, I shotgunned my resume to a bunch of big companies and experienced something like: Resume
by huehehue 8y ago
Maybe. How intelligent are the resume scanners? Just a few years ago, I shotgunned my resume to a bunch of big companies and experienced something like:
Resume: "Ported XYZ from Angular to React, built a Rails app"
Response: "Sorry, we need someone with JavaScript and Ruby experience"
I think it's best to have two resumes, one that's more or less a big list of keywords, and another that you can show actual humans.
- WrtCdEvrydy 8y agoI have a resume that contains a block on the left 33% of the page with the following: \subsection{Technology Fluencies} Java \textbullet{} Python \textbullet{} PHP \textbullet{} Ruby on Rails \\ Javascript \textbullet{} NodeJS \textbullet{} ReactJS / Native \\ SQL \textbullet{} SQLite \textbullet{} MySQL \textbullet{} DB2 \textbullet{} Redis \\ Postgres \textbullet{} Bitcoin / Blockchain \textbullet{} REST \\ ActionCable / WebSocket \textbullet{} JSON \textbullet{} XML \\ ElasticSearch \textbullet{} JWT \textbullet{} JUnit \textbullet{} Jest \\ TestNG \textbullet{} Selenium \textbullet{} Robot \textbullet{} Maven \textbullet{} Ant \\ ESXi \textbullet{} Docker \textbullet{} Flynn \textbullet{} Dokku \textbullet{} Heroku \\ Analytics 360 \textbullet{} Google Tag Manager \\ Salesforce DMP \textbullet{} Github \textbullet{} Git \textbullet{} SVN \\ JIRA \textbullet{} Vagrant \textbullet{} Ansible \textbullet{} Perforce \\ \subsection{Additional Fluencies} Amazon Web Services \textbullet{} Agile Dev. \\ TDD \textbullet{ }SDLC \textbullet{} SaaS \textbullet{} IaaS \textbullet{} PaaS \\
- _pmf_ 8y ago> I think it's best to have two resumes, one that's more or less a big list of keywords, and another that you can show actual humans. You can probably integrate both by having a keyword-only layer in white on white below the real text.