KPMG · Primly Community

KPMG frontend engineer interview, what the technical round actually looks like

qa_quinn · 5 replies

Interviewed for a frontend engineer role at KPMG last month. Sharing because the process is different from product company frontend interviews and I didn't find good prep resources specific to this track.

Context: this was for a mid-level position in their tax and technology practice. They build internal tools and client-facing portals, a lot of React, some Angular on older projects.

Technical round (60 min):

This was a live coding session. Not a full leetcode-style assessment. The interviewer gave me a requirements doc for a dashboard component, basically a table with filtering, sorting, and pagination, and asked me to build it. They were evaluating: Component structure and prop design State management decisions (they didn't care which library, just wanted to see the reasoning) Accessibility, which surprised me. They explicitly mentioned WCAG and asked why I was adding certain aria attributes. Performance considerations when the dataset is large

We didn't finish the whole thing. That seemed intentional. The debrief questions after were things like: what would you do differently if this needed to support 50k rows, how would you test this component, what's your approach to cross-browser compatibility.

No system design round at this level, which makes sense. That usually shows up at senior and above.

Behavioral round (45 min):

Pure STAR, consulting-flavored. The framing was almost always: you're working with a client who needs X. How do you handle it? One question was specifically about a time you had to push back on a client or stakeholder request that you thought was technically wrong. Have a real story for that. Don't try to BS it.

Comp offer I received (NYC, mid-level, 2026): Base around $110k. Performance bonus eligible. They framed it as competitive for professional services which, yes, it's lower than product companies but not dramatically at the mid-level. Also remote flexibility was decent for a consulting org.

Overall, the process felt fair. They were clear about what they were assessing. I accepted the offer.

5 replies

mobile_mara

The accessibility question catching people off guard is so real. I've interviewed at a few enterprise consulting firms and it comes up more than at product companies. Honestly they often care more about WCAG compliance than startups do because their clients have stricter requirements.

brand_ben

Good to know the dashboard build scenario is common. I'd probably start with the filtering logic before building out the render layer, then add pagination. Did they care about the order you tackled it in or just the end result?

frontend_fran

They cared about reasoning more than order. I explained upfront what I was going to tackle first and why. The interviewer asked a few questions during my explanation. Thinking out loud clearly seemed to matter more than having perfect code.

sre_sol

Did they ask anything about deployment or build tooling or was it purely component-level? I always wonder how much KPMG frontend engineers own of the stack.

intl_isla

Was remote flexibility full-remote or is there an expectation to be in-office some days? I'm trying to figure out if KPMG roles could work for someone not in NYC.