3 ms·
Pro: - What tech you actually work with. Don't list equivalents. If the people knew the area they would already know if they have equivalent skills. - Salary
by cbanek 10y ago
Pro:
- What tech you actually work with. Don't list equivalents. If the people knew the area they would already know if they have equivalent skills.
- Salary range and years of experience.
- What kind of actual real world user problems are you solving?
Cons:
- Anything about culture (it's always bullshit), team player, or being emotionally mature
- Useless fluff about "loving to work in a fast company", or how you were #1 2012's disposable ezine of the week's company to work for.
- Not saying what the job is, but just saying what tech you will be using, as if that is enough.
- You can't tell the description is any different between Intern/Junior/Senior/Architect level roles other than "years of experience"
- TurboHaskal 10y agoCulture is always bullshit until you get rejected with a line such as "unfortunately we don't see a good culture fit here"
- wott 10y agoNote that it is still bullshit at that point.
- jackgolding 10y agoI got through to the final offer stage of a job, and sent through a few questions to ensure I was making the correct decision. One of those was "are you okay with me being involved with the local X community by doing things like giving talks". The company actually didn't like this at all and revoked their offer (offer was verbal not on paper at this stage.) I consider that to be "not being a good culture fit" At one of my last roles, we actively tried to expand the team with people who weren't caucasian males so that our inter-team communication may get better (amongst other pros.) Mind you that company in question also had rules about having to interview females for every role.