The job role was focused on documenting their digital products, such as the Member App, Trainer App, Business Suite, and more. I love that they pitched this new role to me, even though I applied for the role to document their machine software. The HR and Technical interview went well. I spoke about what I do in my current role, such as the following: - Docs-as-code - Information architecture and documentation frameworks like Diataxis and custom frameworks - How I prioritize tasks to work on - Integrating LLMs for pull request reviews The only thing I disliked about the interview was the following: - There was no learning experience for me. When I got rejected, there was no feedback. - There was also some confusion during the technical interview where my country of origin was repeatedly misstated, despite being clearly indicated in my CV. The rejection was surprising because I spoke a lot about my experiences and took the opportunity to read their docs and try to understand "the why" behind the issues I am seeing in their docs. Issues such as the following: - No URL pointing to the API docs - No current documentation about the Member app and Trainer app. Which isn't great because the Sales team pitching to their MMS clients would have to be showing the clients how the apps work with no reference to any docs. Also, new users in a gym will struggle to onboard due to missing docs. There were other issues I didn't point out too because they said work is ongoing to make their docs platform better, issues such as: - Blurry images (I wasn't sure if their docs platform caused this issue) - Inability to browse through the docs on mobile. When you click on the sidebar to browse other page titles, you can't go back to the current page you were initially reading unless you refresh the page. - Typos - Unambiguous API paths that can cause problems later for users Most of these issues have been solved in my current role at a Startup where I lead the documentation effort. I assumed they had seen my recent work before inviting me for an interview. It made me feel safe knowing that with these issues in their docs in place, plus the main role I will be assigned to do, there is room for growth, and that when changes can't be made, there is usually a reason behind it. Knowing all these, I thought it made no sense to ask further questions about issues in the docs when “the why” had already been explained. Even when I mentioned an issue in their API docs, like missing API descriptions, and asked them to tell me about their contribution process for working on them, they said there is an opportunity for growth there. They also said this is because they don't manage that part of the docs yet, and they are hoping that their writers will manage those in the future. I saw a great opportunity to apply my skills there and grow my career in the industry. The rejection came as a shock, regardless of how great the technical interview was. Why tell the interviewee about issues you are currently experiencing in your team and get them excited about the challenges they will work on if hired, only to reject them? Now I can't even get feedback about my rejection; it’s just surprising. These are my suggestions: - It’ll be great to give feedback to people after taking them through several interviews for months. - Actually look at people’s CVs and their most recent documentation work before inviting them for a technical interview. Looking back now, given how the team couldn't even tell my country of origin, it is obvious they never had time to look at my work. They probably just assumed people are applying for a job only for a paycheck, another random applicant, without realizing that some people want to actually build. Income is normal. The lesson I have learnt is the following: - Assume interviewers haven’t prepared fully - Complete a thought after highlighting an issue, regardless of when the interviewer keeps saying “work is ongoing”.