Sure Software Engineer Interview Questions
& Process

The first call with the recruiter did not go well. After I talked about my recent experience, the recruiter asked, 'so how does that help me?' Instead of asking more, they just rejected my experience. This was for a junior role with 6 interviews, including a take-home assignment and multiple follow-up chats with the team. I don't get why anyone would want to work for a company that treats people like this, especially for a low salary and with no real team.

So basically, the interview process here is what you make of it, and don't take my word for it. I was kinda nervous after reading other people's experiences, but honestly, I'm glad I went through it. What others missed is that right after you talk to the recruiter, they send you this super detailed interview guide. It lists all the jobs, not just for SWEs, but for other roles too. It also explains company values, gives interview tips, and links to their social media and career pages. For the SWE role specifically, the guide goes deep into the whole process. If people actually read it, they'd see there are no surprises because it lays everything out. It even tells you how long each part takes, so I think people just didn't read it and then complained about unexpected stuff. My process went like this: First, a 30-minute recruiter call, who might be your main contact. Then, a 45-minute Engineer Manager Peer Screen. After that, you can either do a take-home assessment (you get 3 days) or a 90-minute live pairing session. If you did the take-home and did well, you'd have a 1-hour review session. Finally, a 45-minute VP of Engineering Behavioral Interview. The order might shift a bit due to scheduling, but the guide was really clear and they followed it closely. They always got back to me quickly when I had questions. The take-home involves building a web app, dealing with quotes and data persistence. Seriously, read the requirements carefully and don't just do the bare minimum. Get creative, document your code, and make it presentable, not perfect but functional. Your README needs clear instructions on setup and running. Using Django is a big plus since it's in the job description, along with Python 3. Showing you know Django will definitely help. But that's just my take. It's cool that it gives you a taste of the actual work. The take-home review felt more like a chat, giving you a preview of daily work and collaboration. Be ready to talk about how you'd improve the code or use different approaches. This is your chance to show what you know. They really focus on soft skills, which makes sense since it's remote. Good communication and teamwork are key. I got an offer and accepted it because the pay is great, benefits are solid, and I'm excited about the new team. The interview process was the most positive I've had, with recruiters and the team being responsive and accommodating. I recommend Sure if you're willing to put in the effort.

Started with a recruiter screen, then a hiring manager screen. After that, it was a choice between a 90-minute coding interview or a take-home assignment. Heads up, the take-home seems to be a trap. They say it should take 2-3 hours, but they expect you to build a full runnable app with data persistence. The instructions aren't super clear, so you have to make some assumptions about how to implement things. I put in extra time and noted what I'd do with more time, but like others, I was rejected without feedback even though I met all the requirements they listed. The people I interacted with seemed really nice and welcoming, so it's a shame they filter people out this way.