Thanx Software Engineer Interview Questions
& Process

The interview process was good, with nice communication throughout. It started with an interview with the Director/Lead, followed by a take-home assignment to build a Reward Redemption app. Then there was a technical coding round, and finally a System Design round.

Seriously, don't even bother with this company. My experience was exactly the same as what other recent interviewers have posted. It started with an intro call with their engineering director, which lasted about 30 minutes. Then, I was given a take-home challenge where I had to build an app with both backend and frontend components. Finally, I just got a generic rejection message. If you're putting serious effort into the take-home, expect to spend 3-5 hours on it, maybe more if you want to make it really polished. Getting rejected with no feedback after putting in that much time feels really disrespectful, and it makes me wonder what it's like to actually work there.

The interview process was disorganized and unprofessional, wasting my time with tasks that didn't seem to matter. Feedback was unhelpful and clearly AI-generated. It included an initial screening, a take-home assignment, a behavioral interview, a coding interview, and a system design interview. The initial screening and behavioral interview were standard. I spent hours on the take-home assignment (Ruby on Rails backend, React frontend), submitting clean, documented, and tested code, but received no feedback on it. The coding interview was a bait-and-switch; they said it would be about the take-home but it was live coding, citing worries about AI code. The task was basic, meant to 'see how I worked,' and I finished early. However, their feedback claimed I couldn't write production code in the time limit, which wasn't the goal and seemed unrealistic for the 30-minute coding time. The system design interview was also poorly managed. It blended system design with more behavioral questions. The 45-minute slot started late, cutting into meaningful discussion. The conversation jumped between unrelated topics, repeating earlier questions or business context. There wasn't enough time for system design and too much for repeated behavioral questions, leading to a lack of structure and technical depth, which ironically was part of their feedback.