4 ms·

> Your resume should talk about results. meh. I think that's bad advice in 2023 (even in 2018), as a moderate volume resume reviewer with lots of hiring experi

> Your resume should talk about results. meh. I think that's bad advice in 2023 (even in 2018), as a moderate volume resume reviewer with lots of hiring experience -- resulting in 25% fewer remorseful hires. Well, not quantifiable results as you describe anyway. If you are a VP level with a budget, then ok. Or a very low level IT person with metrics to meet, then ok. But as an average SWE, no one is believing these numbers. Even when true, it feels like a force fit to fit a misguided expectation. Unless you specifically went into the project to improve efficiency, and YOU were the one that identified the problem and INITIATED the project SPECIFICALLY to grind out more widgets, then I'd find some other aspect to crow about. In the CMS case, then sure if you identified the CMS as a real issue, worth fixing, and led the project, and can describe the size of the team (could be just yourself) to tackle it, and are taking responsibility including if it failed, then ok. If you're just assigned the task and it happens to be more efficient, blah. Maybe the starting point was exceptionally bad, n^2 vs log(n) due to the first version being a hack. This 70% "result" tells me nothing useful, honestly, except that you are a slave to bad, one-size-fits-all, resume guidance.

jedberg 4y ago
It tells you that the candidate at least understood the business impact of what they were doing, and it gives you something to talk about in the interview. "How was that issue identified? Did you find it or were you assigned the task?" "How did you achieve those results? What technical decisions did you make to get there?". "Were you the team lead or did you work under another team lead?". So many good questions to spawn from that one line.
- jiveturkey 4y ago
  Those lines of questioning are open always, regardless of what’s written in the resume. You have precious few inches in the resume, they should be reserved to highlight your own accomplishments, the aspects of any project that you actually drove. When I see these kind of metrics on every other bullet (for L5 and below) it tells me a lot about the candidate and not that they have an appreciation for the business impact of their technical skills.

jedberg 4y ago

It tells you that the candidate at least understood the business impact of what they were doing, and it gives you something to talk about in the interview. "How was that issue identified? Did you find it or were you assigned the task?" "How did you achieve those results? What technical decisions did you make to get there?". "Were you the team lead or did you work under another team lead?". So many good questions to spawn from that one line.

jiveturkey 4y ago
Those lines of questioning are open always, regardless of what’s written in the resume. You have precious few inches in the resume, they should be reserved to highlight your own accomplishments, the aspects of any project that you actually drove. When I see these kind of metrics on every other bullet (for L5 and below) it tells me a lot about the candidate and not that they have an appreciation for the business impact of their technical skills.