A recruiter initially reached out through LinkedIn. Following a phone conversation, I was referred to another recruiter to continue the process.

The second recruiter, who became the main point of contact, had a call with me to discuss the process and then sent me the CodeSignal assessment information. Both recruiters were very kind, helpful, and respectful.

After passing the CodeSignal assessment (I believe a score of 700 out of 1200 is required), they scheduled a grueling session of back-to-back interviews, referred to as "Power Day." This involved a full day of interviews over Zoom, conducted one after the other. The last interviewer was switched at the last minute to someone currently in the position I was interviewing for.

The Power Day itself was a horrible experience. It was evident that none of the interviewers had read my resume. They lacked knowledge of my previous work and were unaware of the programming and scripting languages I was familiar with. Their primary focus seemed to be on Python and JavaScript frameworks like Angular and React. I believe they should reconsider the Power Day format.

• First Interviewer (Principal level - Technical): This individual was kind and respectful. The interview was generally good, except for the fact that it referenced programming languages and tools that I had previously stated I did not use.
• Second Interview (Behavioral - Sr. Manager and Manager): This was a typical behavioral interview, focusing on "what would you do" or "have you faced" questions. Overall, it was a good interview, and the people were very kind and respectful.
• Third Interview (Case - 1 Manager): This was the part where I actually had fun. It focused on assessing my problem-solving abilities, logic, and math skills. It was a good interview, and the interviewer was kind and respectful.
• Fourth Interview (Technical - person at position level): This interview was horrendous. The interviewer was very disrespectful, constantly interrupting, rolling their eyes, and raising their voice. I question how this person is in a leadership role. It was clear they were very familiar with their specific tasks but lacked patience when someone with a more diverse background needed to explain different approaches or the use of alternative tools. At one point, the interviewer literally put their hands up and asked, "Are you making stuff up? Why are you bringing up, X tool or Y programming language? That's not how things are done! That company is garbage." At this point, I knew I would not accept an offer, even if one were extended. The thought of dealing with this person daily would create a toxic environment.

By the end of the day, I was emotionally and physically drained, experiencing knee and back pain from prolonged sitting. I hope these detailed observations can help others navigate this absurd process.

Ultimately, the recruiter informed me that although the Hiring Manager liked me, they were proceeding with other candidates whose experience more closely matched their established processes.

Code Signal 2 easy 2 medium - 70 minutes

PowerDay: 1. First Interview: a. Find errors in Dockerfile, suggest changes. b. Write code to get data from logs file: 1. Amount of logs 2. Errors and what can be learned from them 3. All prices for a specific month

PowerDay: 2. Second Interview: a. Example when you challenged the way things are done. b. How you overcame an obstacle at work. c. What did you do when work tried to assign you more work than you can handle.

PowerDay: 3. Third Interview: a. Calculate if the budget for performing tests is enough based on some tables. b. What would you recommend as an improvement to their testing process, especially if you have more budget than needed for their current plan.

PowerDay: 4. Fourth Interview: A plethora of in-depth (very specific details) technical questions related to Software Development and DevOps Pipelines, like: a. How to use Git. b. How to create pipelines. c. How do you test software in the pipelines (how do you configure it). d. How do you set pipeline and repository permissions (how do you configure it). e. How do you create repositories (how do you configure it). f. How do you set up Jenkins jobs (how do you configure it). g. How do you do performance testing (how do you configure it). h. How do you solve conflicts between developers and their codes (how do you configure it). i. How do you process and consume logs (how do you configure it). Which tools have you used? j. Have you had a P1 (production emergency) and are you used to or okay with working late (past midnight)? k. How do you troubleshoot network issues or even switch to disaster recovery or another region? l. etc.