Insulet Corporation Software Engineer Interview Questions
& Process

I applied through their website. First, there was a recruiter call, and then I had an interview with the hiring manager. Unfortunately, I didn't make it to the next round because they decided to go with other candidates they found to be a better fit.

I started with a recruiter screening call, then had a follow-up with the manager. After that, there were 5 separate panel interviews, each lasting 45 minutes, with one interviewer per session. These interviews were pretty conversational, and didn't really have dedicated coding or system design parts. Some questions felt quite junior, like asking about different types of database joins. They also threw in some small coding tasks and questions specific to certain languages or frameworks, for example, about how rate limiting is implemented in Spring Boot. My overall feeling was that some interviewers weren't fully prepped, as they asked questions only relevant to their specific projects.

So Insulet had this structured interview process for the Senior Software Engineer - Android role. It started with a 30-minute call with the Technical Recruiter, then another 30-minute call with the Hiring Manager. After that, there were two 90-minute technical interviews, each with two Staff Android Engineers. I knew the Hiring Manager already, and we chatted nicely, but it didn't really sway the interview. The job was advertised as hybrid, but it seemed like location isn't a big deal for them anymore, as they're hiring internationally and using contractors. The technical interviews were tough and moved really fast, with a ton of questions coming at me. They asked about 100 technical questions across both rounds, even asking about stuff I did over ten years ago. The first set of interviewers were contractors from India, and the second group were from Mexico. The recruiter said it would be 70% coding challenge, but that wasn't the case at all; most of the time was spent digging deep into my resume. I did notice some red flags that matched what I'd seen on Glassdoor, like potential issues with getting work shipped because the Android team apparently resists product and design changes. The pull request process also takes ages, sometimes over a week for a PR to get approved. It looks like a lot of the job involves documentation, unit tests, and arguing on PRs. I got an automated rejection email with no follow-up after finishing everything, which felt like a waste of time.