Role: ServiceNow Architect
Location: Plymouth, MN (Hybrid)
Direct client
Dear Partners,
Enclosed below please find detailed JD for ServiceNow Partner Solution Architect Requirement for one of our Direct Client in Plymouth, MN. Kindly share the most qualified candidates resume in word format, along with the contact information and their current location.
1 Objective Engage an experienced ServiceNow Architect from a credible ServiceNow implementation partner to guide and mentor internal technical resources through the initial stand-up of a ServiceNow instance, including foundational platform configuration, critical integrations, and initial ITOM Discovery. The engagement is hands-on and advisory, with a strong emphasis on knowledge transfer, architectural correctness, and adherence to ServiceNow best practices.
2 In-Scope Activities
2.1 Initial ServiceNow Instance Setup & Foundation The Architect will guide the internal team through the foundational setup of a new ServiceNow instance, including:
Initial instance configuration and validation
Core system properties and baseline settings
User, role, and group model design (initial)
Environment strategy (prod / non-prod assumptions)
Plugin activation strategy aligned to near-term scope
Validation of baseline configuration against ServiceNow best practices
Key expectation: The architect does not simply do the setup, but explains the why behind each decision, ensuring the internal team understands the platform foundations.
2.2 2. MID Server Architecture & Deployment
The Architect will design and guide the deployment of MID Servers within the organization, including:
MID Server architecture design (quantity, placement, redundancy)
Security and network considerations
Credential handling and secure communication model
Installation and configuration of MID Servers in customer-managed infrastructure
Validation of MID Server health and connectivity
Guidance on scaling MID Servers for Discovery and integrations
Key expectation: The architect demonstrates real-world MID Server experience, including common pitfalls, security concerns, and operational best practices.
2.3 3. Critical Initial Integrations
The Architect will guide the design and initial build of essential integrations, including but not limited to:
Single Sign-On (SSO) integration
o Identity provider alignment
o Authentication method selection
o Role and user mapping strategy
- Authoritative data sources
o User and organizational data o Foundational reference data
Integration pattern selection (inbound vs outbound, scheduled vs event-driven)
Secure credential and certificate management
Error handling, logging, and operational considerations
Key expectation: The architect prioritizes secure, maintainable integration patterns and avoids short term or brittle solutions.
2.4 4. Initial ITOM Discovery Kickoff
The Architect will lead and guide an initial ITOM Discovery effort to explore the organization s infrastructure, including:
Discovery scope definition (what to discover vs what not to discover)
Credential strategy and security considerations
MID Server usage for Discovery
Discovery scheduling and execution
Initial review and interpretation of Discovery results
High-level guidance on CMDB population, relationships, and data quality expectations
Identification of early Discovery risks, gaps, or prerequisites
Important note: This phase is exploratory and foundational, not a full CMDB implementation. The goal is to:
Validate Discovery feasibility
Establish correct patterns
Educate internal teams on Discovery behavior and outcomes
2.5 5. Knowledge Transfer & Enablement (Critical)
Throughout all activities, the Architect is expected to:
Actively mentor internal technical staff
Explain platform concepts, not just tasks
Provide guidance, diagrams, and rationale
Enable the internal team to independently continue configuration and expansion
This engagement should leave the organization more capable, not dependent.
3 Out of Scope (for clarity) Full ITSM or ITOM process implementation
Extensive CMDB modeling beyond Discovery fundamentals
Custom application development
End-user training
Ongoing operational support
4 Architect Qualifications
Vendors must propose a named ServiceNow Architect who meets the following qualifications.
4.1 Required Experience
Demonstrated experience standing up ServiceNow instances from scratch
Hands-on experience with:
o MID Server architecture and deployment
o Secure integrations (including SSO)
o ITOM Discovery in enterprise environments
Experience working with customers new to ServiceNow
Experience guiding and mentoring internal technical teams
4.2 ServiceNow Expertise
The proposed architect must demonstrate deep understanding of:
ServiceNow platform foundations
Instance health, maintainability, and upgrade readiness
Secure configuration practices
Integration design patterns
ITOM Discovery behavior and limitations
Certifications are expected but real-world implementation experience is more important than paper credentials.
4.3 Consulting & Communication Skills The Architect must:
Be able to explain complex concepts clearly
Provide structured guidance and rationale
Communicate risks and trade-offs effectively
Work collaboratively with internal technical staff
Demonstrate architectural judgment, not just tool knowledge
4.4 Delivery Expectations
The role is guide, mentor, and architect, not doer only
Decisions should be documented and explainable
Best practices should be enforced thoughtfully, not dogmatically
4.5 Ideal Profile (Non-Mandatory, but Strongly Preferred)
Has led multiple greenfield ServiceNow implementations
Has worked closely with ServiceNow product teams or official best-practice programs
Comfortable operating without a fully defined roadmap
Strong instinct for long-term platform health over short-term delivery
Never miss an opportunity! Create an alert based on the job you applied for.
