There's definitely a lot of ghosting in hiring. My resume is finally at a point where it ticks all the boxes, and of about 10 of those recruiter chats recently I progressed to speak with the hiring company on 2 or 3 of them.
There are lots of good reasons for a company to be really choosy in who they hire, primarily because a bad hire can be hugely damaging to a company. Rightly or wrongly, this means that a single perceived negative on your resume can mean you're immediately discarded.
If you're not having much luck, it might be worth getting your resume read by someone who hires, to understand if there any inadvertent red flags, or missing key info. I did this recently with a friendly recruiter and they made some useful suggestions. I also made changes in response to concerns people raised about my background that they said during interviews, so I could counter potentially negative reactions to things in my work history.
> There are lots of good reasons for a company to be really choosy in who they hire, primarily because a bad hire can be hugely damaging to a company.
I think this is overstated. The only engineering positions that can really do any reasonable amount of damage to a company are people who set policy for the whole company (CTO, CEO, VPs). Everybody else is designed to be replaced. Any changes they make can be reversed. The worst you've lost is a little time and money.
> If you're not having much luck
I utilized /r/EngineeringResumes/ and rewrote my resume last month in an X, Y, Z format. I haven't had any problem getting interviews since then. But, I apply directly through the company website. I haven't had a single response on hired or linkedin, but I've had about 20 interviews in the past two weeks at companies I applied to directly. ¯\_(ツ)_/¯
Yes, we have this in my city too, and it works really well - I’d say 98% of scooters get parked in these places. The council leans on the hire company to incentivise good parking - seems like a solved problem.
I really value working with a good technical writer, but you can't always have that. I worked with one of the authors of this book briefly many years ago. This book encapsulates a lot of their experience, for writing developer docs, such as API docs.
Developer docs have a lot of conventions and it's useful to have them written down.
I've been applying the book's advice this week on my hosting platform's docs. For example, there's good advice for an information architecture, and the different content types to have it in it. The book's an easy and relatively quick read.
When the org pays for Google Analytics, Google does not share the tracking data with the rest of its business, so users' privacy is not harmed. GDS and many other UK government orgs do pay, for this reason.
There are lots of good reasons for a company to be really choosy in who they hire, primarily because a bad hire can be hugely damaging to a company. Rightly or wrongly, this means that a single perceived negative on your resume can mean you're immediately discarded.
If you're not having much luck, it might be worth getting your resume read by someone who hires, to understand if there any inadvertent red flags, or missing key info. I did this recently with a friendly recruiter and they made some useful suggestions. I also made changes in response to concerns people raised about my background that they said during interviews, so I could counter potentially negative reactions to things in my work history.