Design the Multi-Instance Platform
Start with the boundary around one customer, because on this platform that boundary is the architecture. Ask what a "customer" physically is here and two answers are on the table. It could be a slice of a shared database, thousands of companies packed into one schema and told apart by an id column. Or it could be a wall: its own application server, its own database, its own copy of everything, sharing nothing with the customer next door. That single choice decides the shape of every other problem in the design. It sets how you add a column, how a bad query hurts your neighbors, how you fail over, and how you patch the fleet. Pick the shared slice and you optimize for density. Pick the wall and you optimize for isolation. ServiceNow picked the wall, and the platform is the consequences of that.
- 1 diagram
- 5 sections
- about 47 min
Premium lessonServiceNow 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 · Cancel anytime
ServiceNow interview guideKnow what ServiceNow asks before you walk in.
21 coding · 5 system design · 30 behavioral questions
Get their questions first.
InterviewLegend is independent and not affiliated with or endorsed by any company it covers.