4 ms·
Workaround for #4. List all relevant tech at/near the top of your resume under a section called something like "Skills" or likely a better name than that. Try t
by handbanana 8y ago
Workaround for #4. List all relevant tech at/near the top of your resume under a section called something like "Skills" or likely a better name than that. Try to be as concise as possible and avoid going too granular (listing just SQL vs TSQL, MYSQL, XYZSQL). I do something similar and avoid listing the tech used for jobs. If I was versed in many stacks/frameworks, I might have a bullet point/mention under each position what stack each company used (Rails, .NET, Django). As a side note to all of this, I believe resumes/CVs should be a single page
- cimmanom 8y agoSingle page resumes made sense when it was typical to stay in the same job for decades. They're not much use for explaining 20 years of experience and growth with 2-4 years at each stop.
- handbanana 8y agoI guess this goes back to being concise. I comfortably fit 5 jobs and volunteer work on mine. I have no issue getting interviews or offers. I know others who stick to 1 page that have decades of experience, and similarly don't have issues finding work.
- zimpenfish 8y ago> Try to be as concise as possible and avoid going too granular (listing just SQL vs TSQL, MYSQL, XYZSQL). Tried that. Got endless calls from recruiters who assumed I knew Oracle, Sybase, MSSQL, etc.
- handbanana 8y agoWhat did you do, upload your resume somewhere lots of recruiters have access to?
- zimpenfish 8y agoWell, yeah, that's kinda how it goes.
- handbanana 8y agoIf you're in tech you shouldn't need to do it that way. Indeed/linkedin/stackoverflow/craigslist etc all have tons of tech jobs which you can selectively (or not) target. Many require not much more than a resume to apply