Charles Schwab · Primly Community

Charles Schwab software engineer interview process, full loop, here's the breakdown

backend_bekah · 4 replies

went through the full charles schwab swe loop earlier this year for a mid-level backend role, westlake tx. figured i'd write it up since the info online is pretty sparse.

the whole thing took about 5 weeks from recruiter outreach to offer, which felt reasonable for a company this size.

stages: recruiter phone screen (30 min) - basic fit, comp expectations, timeline. very standard. online assessment via HackerRank - two coding problems, 90 minutes. more on this below. hiring manager intro call (45 min) - technical background questions, project walkthrough, some soft stuff. not super intense but they were probing for your ability to explain trade-offs. virtual onsite (4 hours across panels) - two coding rounds, one system design, one behavioral.

the interviewers were mostly friendly. a couple were clearly more seasoned than others. one of the panels felt like the interviewer was reading off a script, which was a little awkward, but whatever.

biggest thing: schwab is a financial services company and they care a lot about reliability, compliance awareness, and data sensitivity. even in system design, they'll ask about audit logging, role-based access, what happens when a transaction fails halfway. if you come in treating it like a pure distributed systems puzzle you'll miss the point.

behavioral questions leaned heavily on owning mistakes, navigating ambiguous requirements, and working with non-technical stakeholders. no "tell me about a time you disagreed with leadership" which was a refreshing change.

overall: not as leetcode-grind heavy as a FAANG loop, but not easy. definitely prepare your system design for fintech specifically (think idempotency, transaction rollback, not just throughput).

ask me anything, happy to share more detail on any stage.

4 replies

newgrad_neil

this is really helpful, thank you. did the onsite coding rounds feel more like leetcode mediums or were they more practical/domain-specific? i'm a new grad and the HackerRank OA stuff is what i'm most worried about.

backend_bekah

mediums mostly. one of the onsite coding problems was closer to an easy but with a few follow-up edge cases layered on. nothing graph-hard or DP-heavy in my experience. the OA was the same range. just be solid on arrays, hashmaps, basic tree traversal and you'll be fine.

careerveteran

the fintech angle is a good call-out. i interviewed there for an infra role a while back and they asked about disaster recovery and SOC2 compliance stuff during the system design. not super deep but they definitely expect you to have some awareness of why those things matter.

infra_ines

how did the comp come back relative to what you asked for? i've heard schwab negotiates less than some places.