Hi everyone,

I haven't been working for a while and now want to get back into hands-on ServiceNow development on my PDI: Business Rules, Script Includes, client scripts, Flow Designer, REST integrations, ATF and CI/CD with GitHub.

Instead of small separate exercises, I'd like to build one realistic app that covers most of these. What app ideas or real-world scenarios would you recommend? Bonus points for requirements that look simple but are tricky to build properly.

Thanks!

Biggest pain: IRE tells you a merge/split looks wrong, not why you dig through ID rules, correlation IDs, source precedence yourself to find the actual root cause.

Thinking of building a local LLM (Ollama, via MID Server, no cloud) that sits after IRE and explains suspicious reconciliation events legit update vs false merge vs false split, with confidence scores, and "insufficient evidence" when it can't tell.

Scoping to Server/Network Device/AWS EC2, Discovery + CSV Import sources.

Before I build it is this a real gap, or does tuning ID rule precedence already solve it? #cmdb #servicenow #automation

Prepping for senior consultant/developer roles (CMDB + ITOM focus Service Mapping, Discovery, IRE, CSDM). Would love to hear from people who've been through these interviews recently in the US.

• What scenario-based questions came up? (e.g. "customer's CIs are duplicating, diagnose it")
• How deep did they go on CSDM/identification & reconciliation rules?
• Any system design or architecture-style questions?
• What separated "senior" answers from mid-level ones in your experience?

Trying to study smart, not just wide appreciate any real war stories or question patterns you can share.