Howdy Software Engineer Interview Questions
& Process

First, a recruiter call. Then, a HackerRank technical test. After that, a technical interview where the interviewer seemed to lack technical depth, sticking to a script with no follow-up questions and discouraging detailed explanations. There was also a very basic system design question. This was followed by an interview with a Howdy Engineering Manager, then an interview with the team's Engineering Manager. Subsequently, there were interviews with the client's Engineering Managers, a client team panel interview, and finally, an interview with the client's VP of Engineering.

First there is an HR interview, they show you a function and you have to say the result. Then they send you a HackerRank with 2 tests. And the third is a 1:1 technical interview, but you can tell the interviewer is not from systems. The questions are simple with no follow-ups or problem-solving. What I didn't like was the live HackerRank, they already send you one to do for 2 hours, then you have to do another one live where they mute themselves, there are no questions and they don't ask you to explain anything, you just have to make it pass.

It was long and arduous, starting in Dec 2024 when a recruiter approached me. After being screened, I went into a technical interview and then a live coding challenge. After that, I met with a manager to clarify Howdy's operations. Then I was put into a talent pool to be matched with partners. This first month was tedious but made sense. From Jan 2025 to Oct 2025, I took more technical interviews or screenings with different startup CEOs and CTOs, trying to find a match. I went through three partners who closed their postings, but I landed a contract with a fourth. Howdy was communicative and reassuring throughout, checking in and updating their understanding of my market standing. Despite being the longest process ever, it felt endearing and respectful, just had bad luck with partners backing out.