First Republic Software Engineer Interview Questions
& Process

The interview process was really nice, and the people on the team were super helpful and great to work with overall. I'd definitely recommend it. People seem to like the company because it's collaborative, offers flexible work, and really focuses on learning and growing. The leaders are easy to talk to, and there are lots of chances to move up. On the flip side, some folks mentioned that project deadlines can get pretty intense, and the fast pace might be a bit much sometimes. It could be even better if they improved how they allocate resources and managed workloads.

A recruiter reached out on LinkedIn asking for my resume, which I sent. About 10 days later, they called to discuss the role. They liked my enthusiasm and said we'd move forward, sending a link to apply online and asking me to submit a background check because it's a financial company, which I found a bit unusual before any interviews. Two days later, I got an onsite interview schedule, with no input on the date/time. There was no online coding test, just straight to onsite. The onsite had 5 rounds plus lunch, and everything was running very late. Round 1 was with a Director, focusing on past internships and projects, and a high-level discussion of a graph algorithm. Round 2 was with an engineer for only 10 minutes due to delays, asking what I wanted in a role. Round 3 with a Manager/Director involved common behavioral questions like solving a technical challenge and resolving conflict, followed by two coding questions (one easy string, one more complex). Round 4 was with someone in a more HR-like role, asking about problem-solving approaches and how work was split in past projects. Round 5 was a rushed lunch with the recruiter. Round 6 was with an engineer who asked about internships/projects, implementation, and a coding question. The interviews were more of a resume deep dive than coding focused, with little attention to Big O. After the onsite, there was no follow-up, even after I emailed the recruiter. It was an unpleasant experience due to unprofessionalism, being significantly behind schedule, and interviewers deflecting questions.

The interview process started with a 30-minute phone screen with a recruiter. After that, there was a take-home coding test that was timed to about one day and needed to be completed using Java. Finally, there was a 20-30 minute behavioral interview with someone from the engineering team.