3 ms·

I'm not sure I'd even interview this person; I'd at least have to find reasons to. It definitely doesn't give me anything to ask about. Quotes like "Save a lot

I'm not sure I'd even interview this person; I'd at least have to find reasons to. It definitely doesn't give me anything to ask about. Quotes like "Save a lot of time by automating an email process" are so vague and ambiguous that the bullet point may as well be omitted. Education on the top is a waste of most anybody's time, let it be on the top only if you have no work experience (and if that's the case, yikes). I don't care about language/skillset checklists, because that's not what I hire for. Especially with no indication of relative strength or accomplishments with them - if I need a specific skill I'll happily scroll to see if it's there or not, but I want to see an actual story about this person's career and interests, not a set of "fill in the blank" stuff that every graduate has: * woo high school and a college degree great, that's not something we're going to talk about * version control, editors, etc are table stakes Why is all of the experience effectively unscanable (by eye)? Prose-first, no easy way to separate by date, by project, or position held? A resume doesn't have to be a thesis in print design, but I think you'd do well to consider the feedback you're receiving in this thread and that you alluded to receiving before - this resume isn't advertising anything to me and it's work for me to construct a coherent story about why this candidate is a strong fit for hiring.

jimmaswell 4y ago
> It definitely doesn't give me anything to ask about. Quotes like "Save a lot of time by automating an email process" are so vague ... are you kidding with these two sentences side by side? you just answered your own question, ask about the email process! and how is that outline of what I did even that vague? and everyone says to list accomplishments that benefitted the company instead of responsibilities, which this is a perfect example of. I'll hopefully never have to write a resume again but if I have to I'll just pay an expert. The way I instinctively read and understand a document by actually reading it and caring about the content first is just too mismatched from the average neurotypical's way of looking at the world for me to empathize.
- blandflakes 4y ago
  Don't beg the question in your resume. I don't want coy points to ask about, I want details so I can make sure that I can actually have an engaging conversation about something, especially so that I can figure out how it might relate to work I'm doing here. It's astonishing to me that you can't grasp that a resume is a form of communication, and that therefore you might want to, I dunno, communicate in it. > and everyone says to list accomplishments that benefitted the company instead of responsibilities, which this is a perfect example of. It's not perfect, it's nearly worthless. A perfect example would have at the very least some hint of the business value and the nature of the problem at hand. > The way I instinctively read and understand a document by actually reading it and caring about the content first is just too mismatched from the average neurotypical's way of looking at the world for me to empathize. This is pretty patronizing. I'm actually suggesting that the content of the resume you provided is itself lacking. The issue is not that "oh no the neurotypicals don't want to read my resume", the issue is that this resume's content has room to improve, but you think that can't possibly be the case. Yeah, you're lacking empathy (or at the very least pretty defensive), but it's because we WANT content, not because we're looking for surface-level stuff. In fact most of the feedback has actually been that this resume is TOO surface-level (list of skills? don't care, vague bullet points? don't care), and you're defending the superficiality of content, which is incoherent alongside the claim that people don't care about the substance.
  - jimmaswell 4y ago
    "Saved over 30 hours of manual work, where the worker had to find a PDF, Excel sheet row contents, and information from one other data source, combine them into a formatted email with this information following certain conditions, and look up the right email to send it to. This was done with Python and the gmail api, <whatever the pdf library was, I forget>, and manual string parsing, building hashmaps of the information and sending the emails out once every 10 seconds to honor the rate limiting. Parsing failures or any other exception was logged for manual review." All that extra detail seems trivial to me and covered well enough by the gist provided. Is this version really that much better for these details? Is it even enough detail for you yet? It feels like too much detail to me. It was something about tax ID's and temporary merchant licenses for the state of Maryland.

jimmaswell 4y ago

> It definitely doesn't give me anything to ask about. Quotes like "Save a lot of time by automating an email process" are so vague ... are you kidding with these two sentences side by side? you just answered your own question, ask about the email process! and how is that outline of what I did even that vague? and everyone says to list accomplishments that benefitted the company instead of responsibilities, which this is a perfect example of. I'll hopefully never have to write a resume again but if I have to I'll just pay an expert. The way I instinctively read and understand a document by actually reading it and caring about the content first is just too mismatched from the average neurotypical's way of looking at the world for me to empathize.

blandflakes 4y ago
Don't beg the question in your resume. I don't want coy points to ask about, I want details so I can make sure that I can actually have an engaging conversation about something, especially so that I can figure out how it might relate to work I'm doing here. It's astonishing to me that you can't grasp that a resume is a form of communication, and that therefore you might want to, I dunno, communicate in it. > and everyone says to list accomplishments that benefitted the company instead of responsibilities, which this is a perfect example of. It's not perfect, it's nearly worthless. A perfect example would have at the very least some hint of the business value and the nature of the problem at hand. > The way I instinctively read and understand a document by actually reading it and caring about the content first is just too mismatched from the average neurotypical's way of looking at the world for me to empathize. This is pretty patronizing. I'm actually suggesting that the content of the resume you provided is itself lacking. The issue is not that "oh no the neurotypicals don't want to read my resume", the issue is that this resume's content has room to improve, but you think that can't possibly be the case. Yeah, you're lacking empathy (or at the very least pretty defensive), but it's because we WANT content, not because we're looking for surface-level stuff. In fact most of the feedback has actually been that this resume is TOO surface-level (list of skills? don't care, vague bullet points? don't care), and you're defending the superficiality of content, which is incoherent alongside the claim that people don't care about the substance.
- jimmaswell 4y ago
  "Saved over 30 hours of manual work, where the worker had to find a PDF, Excel sheet row contents, and information from one other data source, combine them into a formatted email with this information following certain conditions, and look up the right email to send it to. This was done with Python and the gmail api, <whatever the pdf library was, I forget>, and manual string parsing, building hashmaps of the information and sending the emails out once every 10 seconds to honor the rate limiting. Parsing failures or any other exception was logged for manual review." All that extra detail seems trivial to me and covered well enough by the gist provided. Is this version really that much better for these details? Is it even enough detail for you yet? It feels like too much detail to me. It was something about tax ID's and temporary merchant licenses for the state of Maryland.