I really appreciated the way the recruiter kept me informed and asked about my thoughts after every step of the process. It speaks volumes about the hiring process and culture. However, the decision to pivot on the job requirements after 2 rounds of interviews seems puzzling. The role was advertised for someone who would come in, own and shape the documentation experience, so the pivot on the decision to hire someone with API development experience seems contradictory to the posting. It defeats the purpose of the role, because it would inevitably set in a bias of a development background which would hamper a long term strategy of a good documentation experience. Technical writing is as much a vital skill as development, if not more. If the hiring was always going to be biased towards a developer perspective, inviting technical writers with experience in content strategy, information architecture and documentation seems to be the wrong way to go about it. It shows a lack of understanding of the value technical writers bring to the organisation. Sadly, it also explains why there have been no technical writers in any of the teams before.