
Jane Technologies Software Engineer Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 7 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at Jane Technologies.
Software Engineer Intern
It was a really great interview experience, the people interviewing me were super nice! The interview process was a bit different, involving simple system design questions and a focus on technical and behavioral interviews. It was a pleasant experience, and all the engineers were easy to work with. I'm bummed I didn't get an offer, but I guess it's for the best!
- Can you tell me about a project you've worked on?
Senior Software Engineer
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.
- What is the first letter that repeats in a given string?
- Can you solve a simple string or array problem similar to LeetCode?
- Complete a practical take-home task that might take a significant amount of time.
Software Engineer
This company does top grading, so it's a very long process. I first had an introductory talk with the hiring manager who was 15 mins late. Then came a short technical exercise with a one of their engineers simply meant to see if you know how to code or not. I can't remember exactly what it entailed. I did ok on it as I moved onto the next step which was the take home I poured a ton into the take home and spent more time on it than requested just to polish it and because I was enjoying. I got very positive feedback on it and was asked to continue. This is where the "onsite" (which was done online) came in. I was told I would be doing 4 different interviews back-to-back with a "meet the team" in the middle. Each interview had at least two people involved. I have taken part in hiring before so I know how it is, but EVERY person but one were acting like they would rather be anywhere. No one was very engaging, just asking me questions like robots. At one point two people were clearly talking to each other over IM and were clear-as-day laughing while on mute. No idea if they were laughing at me or not but it's certainly really disconcerting. And when it came time to meet the team? Well NO ONE SHOWED UP. I sat around waiting for the hour before someone came on and apologized. To me in a 5-straight hour interview that I've already put a bunch of time into, this would be the most important part for me. I really got the impression they had already made up their mind about me but didn't want to end the interview early. Once rejected I was offered another hour meeting to get feedback. Even though it would have been somewhat interesting to hear what they had to say, at that point I'd put so much time into this process that I just wasn't up for listening to what was probably a very good chance of just a bunch standard platitudes. Jane is highly rated as a good place to work and I'm sure it is, but there are other great places to work out there that don't ask that much time of you.
- Could you debug some intentionally bad JavaScript code?
- Can you build a basic autocomplete dropdown?
Jane Technologies Software Engineer Interview Questions
Quoted word for word from Jane Technologies interview reports.
“What is the first letter that repeats in a given string?”
Read reports →“Create a functional shopping cart using React.”
Read reports →“Design a basic database for an online store.”
Read reports →“Design a database given specific constraints.”
Read reports →“Can you build a basic autocomplete dropdown?”
Read report →“Could you debug some intentionally bad JavaScript code?”
Read report →“Can you solve a simple string or array problem similar to LeetCode?”
Read report →“Can you explain the CAP theorem and relate it to your past work?”
Read report →“Are you knowledgeable about compliance?”
Read report →Formats, difficulty and experience
Across all 7 Jane Technologies interview reports.