There may be edge cases where some obscure software can't parse a weird resume format, but in general if you put anything remotely resembling a common resume format (Company name, dates worked there, optional description and/or bullet points) it will be parsed properly.
I'm in a big Slack where people ask and give career help. Several hiring managers have offered to test people's resumes on their company's ATS over the years. Nobody has ever found a combination that actually failed the ATS except when it was an obvious problem (like someone who made their resume in Illustrator) or an obvious user error (exporting a resume as an image).
A few job sites, like WorkDay, have mangled my PDF resume every time I upload it. Like the OP, I've had to massage the layout and formatting to make it more compatible.
Almost all recruiters are "most recent resume in" type of folks or "curated long term list" type of folks - they'll either circle you for years trying to get you hired for something or they'll forget your name in 25 minutes.
It's possible that there is some selection bias here, where mediocre parsing systems give you the option to manually correct everything because they know they are mediocre. I remain skeptical.
“Oh no it’s 2 pages with only education on p2.”
Quickly comment out a bullet and print off a fresh 1 page pdf. I don’t use dumb words or phrases now to fit layout, at least far fewer. And git makes me less worried about deleting when it isn’t working.
One pattern i use, that i think makes things simpler, is to have a layout/contact template with definitions, then different context specific main latex files inputting from a sub directory of section blocks: experience, skills, education, etc.
I’d thought I was slick with word table layouts for sections, until a counselor told me the table structures persist in the supposedly flat pdf.
I wish there were an standard optional JSON attachment with a ridiculous small kb size limit to upload along with a human readable resume to help out the user data AST parser.
AFAIK one can embed arbitrary RDF into PDFs, and then one wouldn't need an extra field https://pdfa.org/wp-content/until2016_uploads/2011/08/pdfa_m...
Here's an example of a simple resumé [0].
You can see in the "Quick Start" section how the resumé template is used, which is very similar to how you described yours.
LaTex is a dark art and I just repeat basic incantations learned from the elder boards.
But, I cannot bring myself to write docs in a web browser and use web app storage. I have a personality disorder that requires me to use a local text editor for personal use cases.
Also I will buy a perpetual license for software. Like sublime text i just renewed a 3 year license to text+merge.
I get that subscription licensing is better for the dev business but I can’t do it.
The UX has been simply amazing, there is a VSCode extension that allows you to have the raw text content open in one tab on the left and the pdf on the right, with it updating everytime you save.
I also think it has translated to better grades, given some of the marks come from structure and presentation! For example, in my last essay I was using Binary Search Trees, wouldn't you know, there's a package that allows you to draw them easily!
Seriously, I can't sing it's praises enough. I'm sure if I was doing some more complex writing Latex may be the more appropriate choice but Typst's plug-n-play approach has been so smooth
https://www.reddit.com/r/EngineeringResumes/wiki/index/#wiki...
(In short, they might not be as important as you think they are)
I don't think people realize how many of the ATS myths have been promulgated by people trying to sell services to job seekers. The ATS myth resonates with people for some reason, so desperate job seekers will often pay (unnecessarily) for various "ATS friendly" templates or ATS reviews.
That's it. That's all you need to do.
The reason? My resume lists my name as follows, where I means the initial for my middle name:
Firstname I. (Nickname) Lastname
And yes, even professionally I do use my nickname and my last name, except for things which must match my government ID, such as offer letters and payroll/tax records, where of course I omit Nickname and use the legal Firstname as well as sometimes the middle initial or full middle name.
With this format, how does Personio parse my name? It thinks I’m called Firstname Nickname. No human would make this mistake, nor would a copy-paste into Notepad cause a human to do that.
And if it has any LLM intelligence at all, it should know that this is unlikely, because Nickname is actually a very common nickname for Firstname, so it should suspect a disperse and have a human double-check its conclusion. Alas.
I’ve also had other issues with these systems misparsing my employment history, since they don’t always properly parse jobs that span corporate acquisitions (changing title and employer at that point but being the same job) and are accurately reflected as such on the resume.
sounds like they did something like:
first_name, last_name = name.split(" ")
which is an issue, but unrelated to what everyone else is talking about, which seems to be how text data is being parsed/encoded inside pdfs. Pasting into notepad would check for that issue, but obviously wouldn't do anything for bad first name/last name extraction logic.I call this easily avoidable because name is usually a separate field in the application or referral forms, so this is the bad auto-parsing overriding accurate manual input.
Some examples that come to mind from my experience are applicants with Chinese names that also use a western name professionally ("Yu-Chen Liew, but I go by Janet"), Spanish names that include patronymics ("Penelope Cruz Sanchez") and cultures that place the family name first ("Park Lee"). Maybe (f,l) = split(name, " ") works in some very homogeneous country like Iceland, but it sure doesnt work in the US.
By contrast, Spanish last names simply use two last names, with a child taking one last name from each parent. Traditionally this is the father's first last name followed by the mother's first last name, though efforts toward gender equality have made the law more flexible nowadays in both Spain and many other countries.
It doesn't violate Spanish naming conventions for given names to be reused in the next generation, and some families do that, but that isn't patronymic since it's not a "son/daughter of X" name, just a reused given name.
In my case, I had a simple layout with sections clearly delineated and very simple formatting (bulleted lists). Dates were spelled out eg September 2024 rather than 9/24. UTF-8 throughout. No difficult latex packages, just classic ones like enumitem and fancyhdr.
I've spoken with two technical recruiters who say they prefer reading templates instead of hand-crafted Resumes on top of them also parsing better in the ATS system ):
Frankly, plain text rendered to PDF is probably going to be the most easily parsed by their systems. If they let you add attachments separate from your resume, then stick your "beautified" resume there.
[0] For the curious: https://www.hropenstandards.org/
Especially for remote positions, there are hundreds of people applying for every open req and it’s hard to stand out
The year before last when I did do targeted outreach, it was because I both had relevant experience in a niche AWS service and I was a major contributor to an open source official “AWS Solution” while I was at AWS that was popular in that niche.
But that trick had a very small window.
So I guess the answer is do something that allows you to stand out from the crowd and then you can do prior outreach and tell them why they should hire you over someone else.
My biggest piece of advice is don’t be a “ticket taker”. Volunteer to lead larger initiatives.
Sure. But who’s going to do all those boring tickets? I know people need to work for themselves, but this just feels so wrong.
I have done two different types of resumes; long and sort. When I was learning about resumes in high school and college, they said to just list your jobs and maybe some key skills. I have been told this is useless to recruiters. So I rewrote things to have a couple paragraphs about major projects at this jobs. I have been told this is too long and nobody has time to read it. So now I have both and you can pick the one you want.
I got laid off recently so this is fresh in my mind, but I got a job through my network instead which did not involve a resume or interviews. That's really how it should be. (I'm kind of just waiting for the founders from my last startup to start something new... they didn't survive the reorg either, which was a "sort by salary descending and only keep the last 3". The joys of having your software startup bought by an indecisive large company that doesn't do software ;)
Not sure about the 'should', but I think it is. Over the years I had the pleasure to work with quite a few good people, but there were also some buffoons (not counting those in marketing). I can only imagine, that the resume of the latter will look more appealing.
The design always struck me as a clumsy attempt to take up space.
Please see the job history array.
I remember seeing a list of companies you could "apply" to with your resume that would then show the ATS-parsed version back to you. Every single person who used it got a reasonable result back, which is usually enough to put an end to all of the ATS myths out there.
they offer the option to parse your cv and see what "comes out on the other side"
I am not sure whether the idea of the parser is to be a starting point to then use the editor, or a test.
https://www.overleaf.com/latex/templates/jakes-resume/syzfjb...
I've never found good leads with cold approaches. Even when getting contacted and receiving an offer, it was always low salaries on that method. What worked best was going to related events, talking to people hosting the booths, talk to presenters of topics where I'm an expert and this way get warm introductions.
It turned out the ATS didn’t properly parse ligatures like “ffi”, “fi”, etc. It rendered them as a blank space, so “artificial” became “arti cial”. I turned over ligature rendering in my resume and started to get more callbacks.
Upon further inspection, I discovered that a lot of LLMs also have problems with ligatures and just ignore them when fed a pdf.
So, maybe those annoying job apps where you upload a resume and still have to fill everything in an HTML form aren’t the worst thing.
The problem seems to be that ATSes struggle with the "modern" style of resume, much beloved of Word template authors, where you might have a left column with your contact details, github, and maybe some skills and then a borderless table on the right side with your positioning statement and job history.
I went from zero callbacks to 80% after I junked Word and rewrote my resume in a much more old fashioned, linear format. I used Overleaf (LaTeX) like it was 1999 and exported to PDF.