The conversation

Lessons learnedExperience excerpt · English

Like I'm able to say a speech application I made was used in over a million calls, because I looked …

… Like I'm able to say a speech application I made was used in over a million calls, because I looked at the database and saw that many call records in there. But I can't say it "saved the company X million dollars" or whatever because I wasn't in management and didn't have those figures shared with me. At least not honestly. I could make some bullshit up (I don't, but I could), like you said, and how are you going to verify it? Do you think a past employer will confirm or deny those figures if you call? They're lucky to give much more than confirmation that you worked for them and what dates at this point, thanks to all the liability around it. Also there's no guarantee that they know (or remember offhand) themselves, maybe they weren't on that project.

Original discussionWhat We Look for in a Resume311 source comments · at import
3

What was this responding to?

Parent context · original excerpt

JW

At first you say: “No one reads resumes” Then follow up with the age-old advice: Your resume should talk about results. Don't say "Created a new CMS for the company". Say "Created a new CMS for the company in Python that resulted in an ~70% reduction in website update times, from 1 hour to 18 minutes." My take: I’m actually not convinced anyone cares too much about those numbers in a resume. Great topics to probe in an interview, but not much of a signal on a resume. Reason being: they’re easy to fluff and are almost always inflated bs. I do agree with all of your other points

Full original

Community replies 0

No community replies yet. Add your perspective.

Replies from the source 3

Direct replies available in this import. Original-language excerpts.

LI

You can come up with decent figures. And i think it is worth it not just for a resume but monthly lookbacks So multiple engineers on hand for 8 hours - let's say 5 engineers. That's 5 person days. A deployment a month (cos anything that painful gets done less often ) gives 60 person days, at something like 2x daily salary of engineer (assume 500pd for easy maths) and you saved company 60,000 usd a year whilst increasing reliablity and speed. Nice one

Full original
JE

Not all of them have to be money related. > Like I'm able to say a speech application I made was used in over a million calls, because I looked at the database and saw that many call records in there. And I'm able to say that I set up an one-click 30 minute devops process for deployment that was previously done over the span of 4-8 hours manually with multiple engineers onhand in case things went wrong (and they often did due to user error), because I was physically present during those manual processes and could directly compare and contrast the time difference. These are both perfect for a resume. They are quantified and measurable and would be interesting to talk about in an interview. For example, I'd probably ask you what tools you used to set up your 30 minute deployment process and what they were using before and how you managed such a huge gain. I would ask you how you built your…

Full original
KE

Getting the numbers in the first place is one challenge, but if you do metrics and measurement, you get hundreds of numbers and improvements, different each week. It's not like you're working on a single goal and target, and then wave goodbye when you're done. Who remembers all those numbers and improvements? What did they come down to cumulatively over the years? No one can know. But crucially, one also works in teams. There's no way one person can claim credit on one measured improvement unless it's something very trivial and isolated, a single-person project. There are many people saying that they read negative things between the lines about people who don't put quantifiable metrics to their CV items. I don't mind missing metrics, it's much better than having some fudged up bullshit metrics in there. The CV is there to establish trust between two people who don't know each other. Don'…

Full original
Continue on Hacker News

Respect different perspectives. Share concrete experiences.

Sign in to post, reply, repost, and quote.