Jane Technologies Interview Questions
& Process

The interview process for this Account Manager role consisted of only an HR screening call. It was frustrating not to advance past this initial stage without a clear reason, especially given the strong alignment of my background and what I felt was a very positive conversation. The HR recruiter started casually, asking whether I preferred to learn about the company first or dive into my experience, which was a refreshing change from typical processes. After about 5-10 minutes of light conversation, the recruiter began asking a series of prepared questions. The rejection email arrived the day after, which I suppose is a positive in that they are efficient and don't leave candidates waiting. The company is a small, tight-knit organization that places a high value on finding the right people to join their team, with the CEO even personally interviewing candidates to ensure they fit the company culture.

It started with a recruiter call, then a technical video screen where I got technical questions and had to solve an easy LeetCode problem. After that, there was a take home assignment which was more practical but took way longer than the 2 hours they said. Then, I had a whole day of interviews with the engineering team. This part felt pretty basic for a senior role, like designing an e-commerce database, coding a shopping cart in React, and a debugging task. It was rushed though, with no time to really think or review code during debugging. The take home was supposed to show I could code and understood scaling, but given the time pressure, I asked if the code needed to be perfect, and they said no. However, while I was working on it, they kept asking why I wasn't being more efficient and nitpicked typos as I typed, which was super distracting. They said the sessions would be collaborative, but it felt like they had the answers and were just picking apart my work. Having two engineers in each session also made it more stressful. Everyone was nice, and I don't think they meant for it to be stressful, it just seemed like a long, poorly planned process. I think the first two rounds were enough. They mention EQ > IQ as a value, but only having technical interviews with engineers and no behavioral ones made me doubt that. I didn't get an offer and only got a generic rejection, which is frustrating given how much time I invested. I asked for feedback but haven't heard back. Also, getting rejected over a phone call felt weird since those usually mean an offer. I would have liked this process if not for the final onsite and the lack of feedback on the rejection.

The interview process was pretty standard. First, I had a call with a recruiter. Then, I went through a phone technical screen. After that, I had a conversation with some higher-ups where we discussed the company and the role in more detail. The next step was a take-home assignment, which is where I ran into issues and why I'm giving a negative review. Everything else was pretty straightforward, and everyone I spoke with was really nice and knowledgeable about the company and its technology. It was great to see their passion for the company and its field. The take-home assignment involved building a CLI application that processes a file containing soccer team scores to display daily standings. My problem was that my code met all the requirements, but I was apparently penalized for using TDD instead of BDD. I tested each function and method individually, rather than testing the overall behavior from a user's perspective. I was also marked down for reading the entire file as a stream, instead of line by line. It seems I was rejected because of how I approached unit testing and for not adding features outside the stated requirements. Even though I had pleasant interactions and felt the company would be a good place to work, the outcome of the take-home assignment really soured the experience. I believe a take-home should just be a basic check to see if someone can code, requiring only a few hours of work and not a production-level application that takes days to complete. The feedback provided was minimal and could have been easily addressed. There was no discussion about the take-home, just a standard rejection email. If you're considering interviewing with Jane, I'd suggest rethinking it as it might be a waste of your time.

Jane's recruiting team made the interview process super smooth and enjoyable. The main recruiter was really nice, kept me in the loop, and was helpful. The recruiting coordinator was quick to set up meetings and made sure I was ready for my design challenge presentation. I had multiple interview rounds where I met with folks from Design, Engineering, and Product. The final interviews were with the CTO and CEO. It was genuinely great to get to know the team, understand the company and product better, and let them get to know me. It felt like they were interested in candidates not just as future employees, but as people. That's what I think makes Jane stand out. Overall, a really positive experience I'd happily repeat, regardless of an offer.