I had a structured interview process with Insulet, which included:
30-minute phone call with the Technical Recruiter
30-minute phone call with the Hiring Manager
Two 90-minute technical interviews with two Staff Android Engineers each
I was already familiar with the Hiring Manager, and we had a good conversation, but that didn’t seem to have much influence on the process. The role was listed as hybrid for a local office near me, but it became clear that Insulet no longer prioritizes location, as they appear to be hiring internationally and relying on contractors.
The technical interviews were challenging, with a fast-paced format where the interviewers alternated asking a large number of questions. Across both rounds, I was asked about 100 technical questions, including details on work I had done over a decade ago. The first interview was conducted by contractors from India, and the second by engineers in Mexico.
The recruiter had mentioned that 70% of the interview would be focused on a coding challenge, but that wasn’t the case. Instead, the majority of the time was spent going through my resume in extreme detail.
Throughout the process, I noticed some potential concerns that aligned with reviews I had seen on Glassdoor. It appears that shipping work is a challenge due to resistance from the Android team towards product and design requests. The pull request process is also lengthy, with PRs often remaining open for a week or more. A significant portion of the job seems to involve documentation, unit tests, and arguing on PRs.
After completing all the interviews, I received an automated rejection email with no follow-up from the recruiter. While in the past, an experience like this would have been a good networking opportunity, in this case, it felt like a poor use of time.
