Skip to main content
You’re hiring ServiceNow engineers, but no two openings are the same: one team needs ITOM, another needs HRSD, a third needs both. This recipe shows the clean way to handle that — without rebuilding your interview every time. The trick: build a few reusable module Interviewers once, then create a Role per opening flavor that simply picks which module Rounds to include.

​
Step 1 — Build the Interviewers (once)

Under Interviewers, create these four. You’ll reuse them for every ServiceNow opening forever.
InterviewerPersona (how it introduces itself)Scores on
Friendly Screener”Hi, I’m Riya — I’ll ask a few quick questions about your background.”Motivation, communication, basic ServiceNow exposure
Platform Fundamentals”I’m Dev, I’ll dig into core ServiceNow platform skills.”Tables, ACLs, flows, scripting, integrations
ITOM Specialist”I’m Arun, I focus on IT Operations Management.”Event mgmt, Discovery, Service Mapping, CMDB health
HRSD Specialist”I’m Meera, I focus on HR Service Delivery.”Case management, Employee Center, knowledge mgmt, lifecycle events
Keep each Interviewer narrow. A focused “ITOM Specialist” gives sharper, fairer scores than one giant “ServiceNow expert” trying to cover everything.

​
Step 2 — Create a Role per opening flavor

Create one Role for each kind of opening. They all share the same Interviewers — only the Rounds differ.
Role: ServiceNow Engineer — ITOM
#RoundInterviewerPass mark
1ScreeningFriendly Screener60
2Platform FundamentalsPlatform Fundamentals70
3ITOM Deep-diveITOM Specialist75
See it? The “both” opening just adds a Round. You never touch the Interviewers — they’re shared across all three Roles.
Why a Role per flavor (not one Role)? Rounds belong to a Role, so the cleanest way to give different openings different interview loops is a separate Role each. Use Duplicate Role to spin up a new variant in seconds, then add or drop the module Round.

​
Step 3 — Put the module knowledge where it belongs

  • Attach general ServiceNow context (your platform version, conventions) to the Role’s knowledge base.
  • Attach module-specific reference docs (your ITOM runbooks, HRSD catalog) to that Round’s knowledge base, so the deep-dive stays scoped.

​
Step 4 — Add candidates and go

Add candidates to the right Role (or share the Role’s apply link), then schedule. Each candidate walks the Rounds in order; passing advances them, and you get a scorecard per Round plus an overall recommendation.
On the Role’s applications page, candidates are ranked by interview score (CV match breaks ties), so your strongest ITOM or HRSD engineers rise to the top automatically.

​
Doing it over the API

The dashboard is enough for most teams. If you automate, the shape mirrors the steps above — create the Interviewers once, then a Role + its Rounds per flavor: 
# 1. Create a reusable Interviewer — once
curl -X POST https://api.intervyo.ai/api/v1/interviewers \
  -H "Authorization: Bearer $API_KEY" -H "Content-Type: application/json" \
  -d '{
    "name": "ITOM Specialist",
    "persona": "Arun, a ServiceNow ITOM specialist.",
    "useCase": "hiring",
    "evaluationDimensions": [
      { "name": "Event Management", "description": "Alert rules, correlation", "weight": 35 },
      { "name": "Discovery & CMDB",  "description": "Discovery, Service Mapping, CI health", "weight": 40 },
      { "name": "Communication",     "description": "Explains trade-offs", "weight": 25 }
    ]
  }'

# 2. Create the Role, then add its Rounds,
#    pointing each Round's interviewer_id at the right Interviewer.
See the full field reference in Interviewers, Roles, and Rounds.
Last modified on June 30, 2026