Just finished my PIMCO software engineer interview process and wanted to write this up while it's fresh. Applied to a senior SWE role on their technology division out of Newport Beach (role was listed as hybrid, three days in office).
Timeline was about five weeks total from recruiter screen to offer call.
Recruiter screen (30 min): Standard stuff. Why PIMCO, what I've been working on, salary expectations. The recruiter was pretty direct about PIMCO's culture being different from typical fintech startups. More structured, more emphasis on cross-team communication. She said the team was specifically looking for engineers who'd worked on high-throughput, latency-sensitive systems, which made sense given what they do.
Technical phone screen (1 hr): One coding problem, medium difficulty. Sliding window type problem. Standard LeetCode-style. Then about 20 minutes of system design, conversational level, not a deep whiteboard session. Interviewer was an engineer on the risk analytics platform.
Onsite / virtual loop (4 rounds, same day via Zoom): Coding: Two problems, both medium. One string manipulation, one graph traversal. About 45 minutes each with a bit of time at the end for questions. System design: Full 60 minute deep dive. I'll post separately on what they actually asked. Behavioral: 45 minutes with the hiring manager. Real structured questions, not casual chat. Domain knowledge / cross-functional: This one surprised me. An hour with a portfolio manager and a quant. They weren't testing coding but wanted to see if you understood what the business actually does. No fixed income exam but you'd better know what a bond duration is and why latency matters in their context.
Debrief call came about a week after onsite. They asked one clarifying follow-up question over email before extending the offer, which I hadn't seen before.
Overall: the loop is longer than big tech in some ways because of that cross-functional round. The engineers I talked to seemed sharp. One thing they said repeatedly was that the tech org is still relatively small compared to how much AUM they manage, so each engineer has broader ownership than you'd expect.