3 ms·
There's a few levels to this. I'd say it's important even if you are personally handing the CV to the decision maker. "Architected a solution and led a team of
by selllikesybok 10y ago
There's a few levels to this. I'd say it's important even if you are personally handing the CV to the decision maker.
"Architected a solution and led a team of developers to implement a custom solution for a large merger & acquisition company" doesn't tell the HM whether you know her stack. Depending on other strengths or weaknesses of your application, this may cost you the call. Yes, a great engineer/dev can learn your stack, yadda yadda, but maybe you're hiring because you're the only one who knows it, you're already training the rest of the team, and need someone to hit the ground running, you know?
Good to have all the checkboxes from the job spec covered. Avoid uncertainty on their part.
- adrianratnapala 10y agoYou are right. But that reinforces the practical part of my advice: don't worry if the skills list doesn't make sense to you, as long as it conforms to whatever the job decription is asking for.
- selllikesybok 10y agoAgreed, and I meant to include that in my comment. Your practical advice is absolutely fine. Just wanted to clarify that it applies to all cases, not just passing recruiter/software review filters.