7 ms·
I wish everybody would follow this format. It's so easy to read, everything is in a predictable place. I've seen so many poorly formatted resumes with things li
by DavidPeiffer 4y ago
I wish everybody would follow this format. It's so easy to read, everything is in a predictable place. I've seen so many poorly formatted resumes with things like
* Soft skills listed above all work and education
* Multiple columns of information
* Inconsistent formatting. Past/present tense inconsistent within a job, extra spacing between sections, and typos.
* Files submitted as "Resume 1.pdf" and similar. Not a huge deal individually, but it's tedious to download 10 resumes like that from the hiring platform then rename as they're reviewed.
- Swizec 4y ago> Not a huge deal individually, but it's tedious to download 10 resumes like that from the hiring platform then rename as they're reviewed What kind of shit platform preserves uploaded filenames? At worst they should turn into opaque IDs. Ideally into an easily indexable, sortable, consistent, human readable filename format.
- dylan604 4y agoI've been on both sides of this argument. Return files as originally named vs return files based on a filenaming rule. I think both have merit, but there's an asterisk next to each with a list of caveats. GIGO is always fun.
- kjeetgill 4y ago> What kind of shit platform preserves uploaded filenames? You're coming in pretty strong for design space that has plenty of room for differences and isn't even that dramatic or extreme? And you're on the weird side of it? You don't want your email attachments to preserve filenames both in platform and when you download them? Dropbox? Flashdrives?!? If you're responding to the candidate eventually it'll be nice to be able to respond with "You send me Resume_ABC_V1.pdf" for whatever reason it comes up. If you're preserving file contents like this for later retrieval you want the filename too like, atleast 90% of the time.