2 ms·
Was going to come here to post the same thing, so glad to see this at the top. From the article: > I led a project to refactor the core code base and make
by hn_throwaway_99 2y ago
Was going to come here to post the same thing, so glad to see this at the top. From the article:
> I led a project to refactor the core code base and make performance improvements which accelerated development speed by 30% and decreased app size by 50%, leading to 10% in app installs.
>
> (please note all numbers are illustrative)
In my experience, it's more like "please note all numbers are bullshit". I agree with you, in that whenever I see numbers like this I would say 5 out of 10 people are totally making them up, 4 out of 10 are taking credit for a large team effort, and maybe 1 in 10 has a real right to say he was responsible for that metric change. So the problem is that even if you're that 1 out of 10 person, the interviewer may be coming at this with the attitude of "90% of people are bullshitting".
I feel like the article is "half right". Yes, I want to know how you drove business outcomes, but I really really care what you actually did. I've been in too many interviews where people could talk a good game but then when I tried to drill down into specific actions the interviewee took, I felt like that consultant from Office Space: "What would you say ya did there??"
- RaftPeople 2y agoSame here, I was going to post the same thing. I want to know lots of specifics about how you approached the work because that is the only way I can read between the lines and gain a lot of information about your experience and general style. I have no interested in the stats because they don't help me understand how your capabilities+style will actually translate to the role.