Timeline Day 1: Applied to the position Day 9: Received an email saying they'd like to schedule interview 1 Day 15: First interview Day 16: Received an email saying they'd like to schedule interview 2 Day 24: Second interview Day 40+: They said they would tell me the results of my second interview a few days later, but I didn't hear anything back at all. Guess if you're not a top candidate they do not care. Interview 1 (1 hour) (with software developer): The first 5 minutes were just chatting as most interviews start off with, with 2 questions "tell me about yourself" and "have you tried our demo?" The following 5-10 minutes was the setup and explanation of the technical question you have to complete. The rest of the time is allocated to completing the question and spending the last few minutes to ask the interviewer any questions you have. The Technical question was about pagination/sublist with an array, roughly leetcode easy/medium in difficulty. You're allowed to complete the question with your language of choice, but it must be completed on a google doc. They say a couple of times that the interview is about your attention to detail, details of the logic, and overall code, not the syntax, so make sure to notice the edge cases (1-3) in the question and account for them. Interview 2 (2 hours) (With tech lead): The first hour was the technical question. It is the same symmetric/mirrored binary matrix question others in previous years have gotten, roughly leetcode medium/hard, more difficult than I expected. The second hour was all behavioral. The first few questions were about the company itself. The next set (the bulk of the questions) was based on past experiences based on your resume but nothing really technical, more along the lines of your likes/dislikes, easy situational stuff, and experiences. The last 2-3 questions were more standard interview questions like "how would you handle the situation if your coworker was xyz."

First Technical Assessment (1 hour) This round focused on a coding exercise requiring the implementation of a list manipulation algorithm. The problem was straightforward but did take some time to solve fully. My descriptive thought process was highly valued, although I wasn't able to complete the coding task within the time limit. Second Technical Assessment and Situational/Behavioral Assessment (2 hours with a break) Technical Part: The difficulty level jumped up significantly. I spent 40 minutes on the whiteboard solving the algorithm, but due to recent illness affecting my cognitive abilities, I wasn't able to complete the coding task. Situational/Behavioral Part: This part lasted around 50 minutes and focused on teamwork, problem-solving, and past experiences. This section was described as "situational" by the company and went quite well. Communication Communication with the recruiter was polite and professional. However, contrary to what was initially communicated, I had to follow up to get the final decision on my application. Overall The interview process was demanding, requiring both technical prowess and keen attention to detail. The interviewers were appreciative of candidates who thoroughly explained their thought processes and were willing to offer gentle guidance when needed. There was a delay in receiving the final feedback, which only came after my follow-up. Tips for Future Candidates Be Prepared for Google Docs: The technical interview is conducted on Google Docs, which can be challenging for visualizing your code, especially for neurodivergent individuals like myself who have ADHD. The lack of syntax highlighting and other code-friendly features can make it difficult to track your progress. Speak Your Thoughts: The interviewers value your thought process almost as much as the solution. Make sure to articulate your thinking clearly. Follow Up: Even if you are told you will be notified, it may be beneficial to take the initiative and follow up for feedback. Consider Your Health: Make sure you're at your best cognitive function before the interview, as the tasks can be very challenging. Note for the Company: The Google Docs platform can be a hindrance for neurodivergent individuals and may not truly reflect a candidate's coding abilities. A more accessible platform or adjustments for neurodivergent candidates would make the process fairer.