Splunk Coding Interview: OOD Coding Round

One onsite round at Splunk asks you to design and code a small system, and the interviewer is reading your object model while you write. The attested prompt is to design and code a web crawler. Remember the reported failure. A candidate answered with a bare breadth-first walk over URLs, treated it as an algorithm problem, and got dinged for it. The traversal was right. The structure was missing. This round separates people who can shape a system into collaborating objects from people who only reach for the shortest working function.

The Splunk angle

Splunk ships infrastructure that a platform team owns for years, so this round rewards the instinct that keeps long-lived code healthy: a model you can extend when the requirement changes under you. You can tell you passed when the interviewer says "now add a politeness delay" or "crawl only one host" or "make it concurrent." The change lands as a new object or a swapped dependency, and the loop stays as it is. So spend the first minutes on responsibilities and seams, and save the traversal for later. The traversal is the easy part and they know it.

What's inside

2 problems, worked step by step
about 24 min

Premium lessonSplunk interview guide

These took digging.

What candidates walked out with, from 20,000+ reports, forum threads behind logins and write-ups in Chinese. Then solved step by step.

100 companies. Checked every month.

Unlock all 100 companies

$49 a year · less than $1 a week · 30-day money-back guarantee

See how we find them

The OOD Coding Round

These took digging.

Know what Splunk asks before you walk in.