KPMG · Primly Community

KPMG coding interview online assessment, format and difficulty (honest review)

sre_sol · 5 replies

Just completed the KPMG online assessment for a software engineer role on their digital transformation team. Sharing notes for anyone prepping.

The OA came through HackerRank, link sent by the recruiter about 3 days after the recruiter screen. 75-minute timer. Two coding problems.

Problem 1: String manipulation. Find the longest substring without repeating characters. Classic sliding window. If you've done leetcode medium you've seen this exact problem or something nearly identical. Took me about 18 minutes.

Problem 2: This one was more interesting. Given a list of API calls with timestamps and user IDs, find users who made more than N calls in any rolling 30-minute window. Basically a sliding window on timestamps but requires thinking about the data structure. I used a sorted deque. Medium-hard, but the constraint sizes weren't brutal so even a less optimal solution probably passed.

Language options: Java, Python, JavaScript, C#, C++. I used Python.

There were also 5 multiple choice questions. General CS knowledge: time complexity, basic sorting, some SQL (one JOIN question, one GROUP BY question). These felt like filters, probably scored pass/fail.

Total time I used: about 58 minutes. I passed and moved to the phone screen.

Difficulty verdict: not LeetCode hard. Probably LeetCode medium overall. If you've been grinding for FAANG loops you'll find this more comfortable than you expect. If this is your first coding interview experience, grind the sliding window pattern hard, it came up twice across my sessions.

One thing I wasn't expecting: they included a short 'work style' survey at the end of the OA. Like, 10 questions about how you prefer to work. I answered honestly. Not sure if it's filtered or just informational.

5 replies

bootcamp_bri

The work style survey at the end is interesting. I've seen those at other Big 4 firms too. I always wonder if they actually use it or if it's just HR box-checking.

content_cole

75 minutes for two problems sounds humane. Did you have to share your screen or was it just code submission? Some HackerRank setups have the webcam proctoring and that adds stress.

jp_newgrad

No proctoring for me, just code submission. But that might depend on the role or region. The recruiter didn't mention anything about it.

analyst_ana

Glad you flagged the SQL questions. I'm interviewing for a hybrid swe/data role there and wasn't sure if they'd include SQL in the OA or save it for later rounds.

mobile_mara

Sliding window pattern coming up twice is genuinely useful data. Adding that to my prep list.