4 ms·

If you are applying to work at this company, this is probably good advice. If you're applying to work at most companies, ignore this advice. Everything he write

If you are applying to work at this company, this is probably good advice. If you're applying to work at most companies, ignore this advice. Everything he writes here makes sense, which is why you know that in our nonsensical industry, it is a waste of your time to put it into practice.

deleted 4y ago
[deleted]
kube-system 4y ago
It’s how things work at small companies or early stage startups that don’t have non-technical layers of bureaucracy reading your resume.
pyb 4y ago
I think "he"'s actually a "she".
ThaDood 4y ago
Any advice you would give for brushing up a resume? I'm not a dev but work in IT and do a lot of admin work, networking and a lot of security work. I am having a super hard time fitting all of the skills and tools I use on a one page resume. I had considered using like a GitHub Pages resume but haven't had a solid reason to do so.
looping8 4y ago
It's remarkable that, for an industry that prides itself on having individualist approaches and everyone doing things their own way, everyone somehow also keeps trying to give universally true advice. That said, the title is, explicitly, "What WE Look for in a Resume". The intro makes it clear this is about them and them only and is more of a transparency report, an encouragement for others to be more open too. So I wouldn't blame this particular post of trying to be too general.
gwbas1c 4y ago
Honestly, having spent half of my career at small companies and occasionally screening resumes... I'd say this is great advice for joining a small company. More importantly, if you're directly applying to a role, or you're applying through a recruiter, it's useful advice. I generally follow these practices, too, and I'm quite happy where I've landed.
- quickthrower2 4y ago
  I worked at 7 small companies total. All CVs are read. There may be some screening if recruitment agencies are used. Which is sad. Aside: if using an agency you might need a CV for them and then when you talk about the job switch to the role-facing CV. I got burned by this in the past presenting a microsoft heavy story to a non microsoft using company they didn’t want to talk.
lucb1e 4y ago
I don't agree with a lot of the things¹, but by and large, it's good advice to apply for us as well. Not sure what exactly the "nonsensical" things are that you say we need to waste time on to put into practice instead. ¹ like those "good metrics" examples such as having picked a store location using <magic> and the location worked out doesn't mean as much as the "bad metric" example of how many code reviews you've done (tells me you've seen a lot of code and collaborated, even if "you could have done it in just one year" as the post argues)

deleted 4y ago

[deleted]

kube-system 4y ago

It’s how things work at small companies or early stage startups that don’t have non-technical layers of bureaucracy reading your resume.

pyb 4y ago

I think "he"'s actually a "she".

ThaDood 4y ago

Any advice you would give for brushing up a resume? I'm not a dev but work in IT and do a lot of admin work, networking and a lot of security work. I am having a super hard time fitting all of the skills and tools I use on a one page resume. I had considered using like a GitHub Pages resume but haven't had a solid reason to do so.

looping8 4y ago

It's remarkable that, for an industry that prides itself on having individualist approaches and everyone doing things their own way, everyone somehow also keeps trying to give universally true advice. That said, the title is, explicitly, "What WE Look for in a Resume". The intro makes it clear this is about them and them only and is more of a transparency report, an encouragement for others to be more open too. So I wouldn't blame this particular post of trying to be too general.

gwbas1c 4y ago

Honestly, having spent half of my career at small companies and occasionally screening resumes... I'd say this is great advice for joining a small company. More importantly, if you're directly applying to a role, or you're applying through a recruiter, it's useful advice. I generally follow these practices, too, and I'm quite happy where I've landed.

quickthrower2 4y ago
I worked at 7 small companies total. All CVs are read. There may be some screening if recruitment agencies are used. Which is sad. Aside: if using an agency you might need a CV for them and then when you talk about the job switch to the role-facing CV. I got burned by this in the past presenting a microsoft heavy story to a non microsoft using company they didn’t want to talk.

lucb1e 4y ago

I don't agree with a lot of the things¹, but by and large, it's good advice to apply for us as well. Not sure what exactly the "nonsensical" things are that you say we need to waste time on to put into practice instead. ¹ like those "good metrics" examples such as having picked a store location using <magic> and the location worked out doesn't mean as much as the "bad metric" example of how many code reviews you've done (tells me you've seen a lot of code and collaborated, even if "you could have done it in just one year" as the post argues)