T E K D E X

Loading

TekDex is a technology-driven consulting and engineering company. We build agentic AI, cloud-native platforms and ServiceNow solutions for enterprises worldwide.

Hiring

Hiring ServiceNow: five questions that separate a developer from an architect

Certifications tell you someone passed an exam. These five tell you whether they have run a platform in anger.

TekDex28 Jul 20265 min read

Certifications tell you someone passed an exam. These five tell you whether they have run a platform in anger.

ServiceNow CVs look remarkably alike. Everyone lists ITSM, ITOM, Flow Designer and a stack of certifications. The gap between a competent developer and someone who can own your platform is real, but it does not show up on paper. These five questions surface it in twenty minutes.

1. "Talk me through a customisation you argued against."

Anyone senior has been asked for something that would have made the platform harder to upgrade, and has pushed back. What you are listening for is whether they understood the cost — upgrade debt, testing surface, who inherits it — and whether they proposed a configuration alternative. A developer builds what is asked. An architect negotiates.

2. "How do you know your CMDB is accurate?"

Weak answer: "we run Discovery." Strong answer talks about identification and reconciliation rules, which CI classes are authoritative from which source, how duplicates get caught, and what the actual completeness numbers look like. This one question separates people who have owned a CMDB from people who have queried one.

3. "What broke the last time you upgraded?"

Everyone has an upgrade story. The useful part is what they did afterwards — whether they remediated the customisation that broke, or just patched it and moved on. Listen for ATF coverage, update set discipline, and whether they treated the upgrade as a recurring event or a one-off crisis.

4. "Where would you not use Flow Designer?"

A good sign is a candidate with opinions about the limits of the tools they like. Performance at volume, debuggability, error handling, where scripted logic is genuinely the right answer. Someone who says Flow Designer is always the answer has not hit its edges.

5. "How would you approach Now Assist here?"

  • Do they lead with knowledge quality and CMDB accuracy, or with features?
  • Do they sequence the rollout, or turn everything on?
  • Do they mention measuring a baseline before and after?
  • Do they raise what should stay human?

This is the question that most cleanly separates current practitioners from people whose platform knowledge stopped a few releases ago.

Five questions, twenty minutes, and you will know. Certifications get someone to the interview; these decide it.

More insights

All insights