Invoice2go Interview Questions
& Process

My staffing agency reached out about this job. I had an in-person interview because my recruiting background is a bit different. Everyone was really nice. The interview went well, but I felt like the process took too long and my time was wasted. The interviewer really liked me but was hesitant because I don't have formal recruiting experience. I had to prepare for some hypothetical situations for another part of the process. If they weren't going to hire me, they should have just been upfront. They didn't follow up like they said they would, which was disappointing. You shouldn't promise things you can't deliver. Still, Invoice2go seems like a great company, people should check them out!

It started with an initial email and then a quick technical screening. Then there was a take-home test followed by a technical pair programming session, and finally a system design interview. Everything was done online. The process was really fast. The people were friendly, and I think they have a good culture and a strong engineering team. However, their interview skills weren't great. For the initial screening, there was no warning that technical questions would be included, so it felt like a surprise JavaScript quiz. The initial impression given about the technical test was also misleading. They said we'd code on things used in our current roles, but it was entirely different. The interviewers were nice, but it felt like the test was set up for failure. The system design test was just another technical coding round, not really system design, which also didn't meet expectations. I think their main issue was setting the right expectations about what would be asked. They weren't clear, which wastes everyone's time. Otherwise, everyone from the recruiter to the interviewers was nice.

A recruiter reached out, and we discussed my background and past work. It was a really nice chat. Then, I met one-on-one with a Senior Designer to go deeper into my experience and projects, which took about an hour. They suggested having mobile design examples ready. After that, I got a design task to work on for a few days, focusing on improving an existing feature. They give you plenty of time for it. I sent it in on Friday, and by Monday, I was invited for a design review with the Senior Designer and two other team members. It lasted around an hour, and while I was a bit nervous, they made me feel at ease. Expect a lot of questions and be ready to defend your design choices. Lastly, I spoke with the Business Operations Manager for about 30 minutes; it felt like a check on whether I'd fit the team culture. The whole thing took about a week and a half, and I really enjoyed it.

After applying for the Customer Operations Associate position, I was contacted by a recruiter within a few days to schedule a call. Following our conversation, I was given a three-question assessment to gauge my understanding of support, problem-solving skills, and writing abilities. The next day, the recruiter emailed again to arrange a phone interview with the Customer Operations Manager. After that, I was invited to the office for an in-person interview. The onsite portion lasted about an hour and a half, split into three 30-minute sessions, where I met with four individuals and the recruiter. Each session focused on different areas, including my experience and responses to situational questions. The following day, the recruiter called to offer me the job.