I applied through a recruiter. The process took 2 weeks. I interviewed at 1Password (Toronto, ON) in Mar 2023
Interview
After taking to recruiter, I was interviewed by two developers in the team. Interview was strange, the female interviewed seemed to be in a really bad mood, but the guy was engaging and asking a lot of questions . I was wondering if it was a “good cop, bad cop” kind of interview, but left feeling hopeful. I later received a rejection that I didn’t have enough Go experience, even though the job posting clearly stated go as a plus. I have many years of experience in the same domain as the team, but not a lot of experience with specific technologies.
Interview questions [1]
Question 1
Behavioral questions, domain questions and general programming questions.
I went through a recruiter screen and then a call with the hiring manager. I wasn't progressed after the hiring manager call.
I requested feedback after the interview and the recruiter was quite helpful and willing to have a brief call to share feedback.
Interview questions [2]
Question 1
Q: Walk me through a design decision and the process you followed
I applied online. The process took 3 weeks. I interviewed at 1Password (Vancouver, BC) in Jul 2024
Interview
Everyone from beginning to end was extremely pleasant and nice. The interview process took about 3 weeks. The recruiter began by explaining what to expect and details of the job. The first interview was a manager screening which went pretty well and questions were asked about my overall experience level and collaboration/problem solving skills. The second interview was a technical interview with a take home assignment. You basically go over the assignment and discuss tradeoffs, improvements etc. the third interview was behavioral. The fourth interview was a system design interview where you are supposed to discuss a prior project that you have experience with. You get to draw the diagram in advance, and then bring it to the interview to discuss. They ask questions about why you chose specific tools over others, tradeoffs in the system, potential improvements, etc. This part I found a bit challenging because, if you're an engineer that works primarily in large enterprises your entire career (like I am), it's really difficult to discuss extremely large systems in the span of an hour, and know precise answers to every question. Like, why would I know why they chose SQL instead of PostGres, I wasn't there! Lol
This was ultimately my downfall of the process as I couldn't speak effectively about the tradeoffs and choices made. If this is you, I'd highyl recommend practicing in this particular interview. About a week later I got a rejection email and was able to talk to the recruiter about reasons why I wasn't picked. Overall, great people and nice atmosphere, typical standard interview process.
Interview questions [2]
Question 1
Build an events API for POST and GET 1Password account events
Recruiter call then hiring manager interview then take home assessment, then code review style interview, then system design interview. After that there was an offer. Overall very positive experience but I found it was fairly easy.
Interview questions [1]
Question 1
Describe some of the technical tradeoffs you made in the assessment