Client: State of Utah
Posting title: IT Analyst II - KSSOW 26007 - BOPAP - IT Analyst - DTS - Department of Government Operations - IT
Posting ID: 153172
Job Title: IT Analyst II
Department/Agency: DTS
Division: Department of Government Operations
Projected Start Date: 02/02/2026
Projected End Date/Duration: 1 Years from projected start date
Address: 448 East Winchester, Suite 300, Murray, Utah - 84107
Tentative interview dates: January 27th and 28th
Remote or onsite: 80% onsite, 20% offsite
Local or non-local: Utah Residents Only
The following are required for bid submission:
- Resume
- R2R
- Cover Letter
- Meets Work Location
- MMR
Preferred/required skills:
- 3+ years of hands-on, extensive developer-level experience and knowledge of Salesforce designing and developing Salesforce solutions and experience using Java and Java Script
- Direct experience as a software developer on production systems
- Demonstrated expertise in designing, developing, securing, and maintaining APIs (REST and/or SOAP) and integrating with enterprise systems
- Extensive experience developing and customizing ServiceNow, including workflows, business rules, integrations, and platform configuration in an enterprise environment.
- Software Development Security knowledge Demonstrated experience developing systems that comply with CJIS security, privacy, and data protection requirements
Scoring:
- 20% - Cost
- 30% - Salesforce Architecture & Strategic Communication
- 15% - API Integration, Security Compliance & ServiceNow Development
- 30% - Domain Expertise
- 5% - Agile Execution & Technical Documentation
MMR
- Minimum Mandatory Requirement #1
- 3+ years of hands-on, extensive developer-level experience and knowledge of Salesforce designing and developing Salesforce solutions and experience using Java and Java Script in enterprise environments
- Demonstrated ability to produce clear technical documentation, including system designs, integration specifications, and deployment instructions.
- Experience working within an Agile or hybrid SDLC, collaborating with business analysts, architects, and stakeholders in large enterprise or government environments.
- The ideal candidate must possess exceptional cross-functional communication skills, acting as a strategic bridge between high-level business objectives and complex technical execution. You will be responsible for collaborating with corporate back-end engineering teams to ensure architectural alignment while regularly engaging with senior business leadership. You must be adept at facilitating sprint demonstrations, distilling executive feedback into actionable technical requirements, and translating abstract business needs into scalable, high-performance solutions
- Minimum Mandatory Requirement #2
- Direct experience as a software developer on production systems supporting criminal justice domains (e.g. Courts, Public Safety, Local Law Enforcement, Corrections, Parole Boards, Criminal Justice Commissions, etc.) as well as systems handling criminal justice data or justice information exchanges.
- Minimum Mandatory Requirement #3
- Demonstrated expertise in designing, developing, securing, and maintaining APIs (REST and/or SOAP) and integrating with enterprise systems, including identity management, case management, or data exchange platforms.
- Demonstrated ability to produce clear technical documentation, including system designs, integration specifications, and deployment instructions.
- Minimum Mandatory Requirement #4
- Extensive experience developing and customizing ServiceNow, including workflows, business rules, integrations, and platform configuration in an enterprise environment.
- Minimum Mandatory Requirement #5
- Software Development Security knowledge
- Demonstrated experience developing systems that comply with CJIS security, privacy, and data protection requirements, including role-based access control, audit logging, and secure API design
Summary - Scoring criteria
- 1. Salesforce Architecture & Strategic Communication
- Can you discuss your experience designing and developing Salesforce solutions in an enterprise environment? Specifically, how have you utilized Java or JavaScript alongside Apex/Visualforce to solve complex architectural challenges?
- Describe a time when senior management requested a feature that might be technically unfeasible or would break back-end integration. How did you handle that conversation at the moment?
- How do you explain complex technical hurdles-such as API latency or integration bottlenecks-to non-technical stakeholders?
- 2. API Integration, Security Compliance & ServiceNow Development
-
- Describe a specific project where you designed and maintained APIs (REST and/or SOAP) to integrate Salesforce with enterprise systems (e.g., identity or case management). How did you ensure the integration was scalable?
- How do you ensure the security and compliance of your systems, particularly regarding CJIS requirements, role-based access control, and audit logging?
- Describe your experience utilizing ServiceNow in an enterprise environment. Have you customized workflows, business rules, or platform configurations to support cross-system functionality?
- 3. Domain Expertise
-
- Can you describe your specific experience developing or supporting systems for a criminal justice system? Specifically, have you managed the unique privacy sensitivities associated with victim notification, parole hearings, or offender case management?
- 4. Agile Execution & Technical Documentation
- Discuss your experience working within an Agile or hybrid SDLC in a government or large enterprise environment. How do you ensure your technical documentation (system designs, integration specs) keeps pace with rapid sprint cycles?
Scoring Sheet
1. Salesforce Architecture & Strategic Communication Weight: (30%)
- Question 1 (Technical): Can you discuss your experience designing and developing Salesforce solutions in an enterprise environment? Specifically, how have you utilized Java or JavaScript alongside Apex/Visualforce to solve complex architectural challenges?
- Question 2 (Stress Test/Communication): Describe a time when senior management requested a feature that you knew might be technically unfeasible or would break back-end integration. How did you handle that conversation at the moment?
- Question 3 (Translation): How do you explain complex technical hurdles-such as API latency or integration bottlenecks-to non-technical stakeholders? (Look for analogies, e.g., comparing a bottleneck to a highway merger).,
Rating Scale:
- Foundational: Communication is strictly task-oriented; unable to articulate business value; minimal Java/JS experience in Salesforce contexts.
- Developing (Technical-Only): Strong communication with developers but struggles to explain trade-offs to non-technical audiences; sprint demos focus solely on code.
- Proficient (Collaborative): Communicates clearly with peers; can explain technical concepts if prompted but may struggle with high-level strategy or complex custom development.
- Advanced (Translator): Highly proficient at translating business needs into technical tasks; confidently leads demos; strong hands-on experience with Salesforce and Java/JS.,
- Expert (Strategic): Effortlessly switches between deep technical jargon and executive summaries; effectively pushes back on management by explaining risks; extensive architectural expertise.
2. API Integration, Security Compliance & ServiceNow Development Weight: (15%)
- Question 1 (API Strategy): Describe a specific project where you designed and maintained APIs (REST and/or SOAP) to integrate Salesforce with enterprise systems (e.g., identity or case management). How did you ensure the integration was scalable?
- Question 2 (Security): How do you ensure the security and compliance of your systems, particularly regarding CJIS requirements, role-based access control, and audit logging?
- Question 3 (ServiceNow): Describe your experience utilizing ServiceNow in an enterprise environment. Have you customized workflows, business rules, or platform configurations to support cross-system functionality?
Rating Scale:
- No Awareness: No clear understanding of API strategies, security compliance standards or experience with ServiceNow.
- Minimal Understanding: Basic knowledge; Awareness of integration but lacks depth in security concepts or CJIS requirements or ServiceNow knowledge.
- Adequate: Describes standard integration practices; basic knowledge of data protection and access control.
- Strong Experience: Demonstrates strong API design strategies; clear understanding of compliance standards and secure design and demonstrates competency with ServiceNow
- Expert: Expert in API optimization and security; describes implementing rigorous governance, audit logging, and CJIS-compliant architectures., as well as direct on-hands involvement with ServiceNow
3. Domain Expertise Weight: (30%)
- Question 1 Can you describe your specific experience developing or supporting systems supporting criminal justice domains (e.g. Courts, Public Safety, Local Law Enforcement, Corrections, Parole Boards, Criminal Justice Commissions)? Specifically, how have you managed the unique privacy sensitivities and workflows associated with victim notification, parole hearings, or offender case management?
Rating Scale:
- No Experience: No experience with related criminal justice systems.
- Minimal Familiarity: Has general IT experience in government but lacks specific exposure to sensitivities of criminal justice..
- Adequate (General Justice): Has worked with general criminal justice data (e.g., courts or police) but lacks specific depth in Victim Services or BOPP workflows; understands basic data privacy concepts.
- Strong Experience: Direct experience working with criminal justice systems; demonstrates a clear understanding of the distinct needs between offender management and victim protection.
- Expert (Domain Specialist): Extensive experience architecting solutions for Parole Boards or Victim Services; articulates deep knowledge of specific statutes, victim confidentiality requirements, and the lifecycle of parole hearings and notifications
4. Agile Execution & Technical Documentation Weight: Low (5%)
Question 1: Discuss your experience working within an Agile or hybrid SDLC in a government or large enterprise environment. How do you ensure your technical documentation (system designs, integration specs) keeps pace with rapid sprint cycles?
Rating Scale:
- Limited: Limited experience with Agile; documentation is sparse or nonexistent.
- Basic: Understands Agile concepts but struggles to produce clear technical specifications.
- Adequate: Experienced with Agile; provides examples of standard documentation that meets basic business needs.
- Strong: Strong experience collaborating with analysts/architects in Agile; produces clear, detailed system designs.,
- Extensive: collaborative leader in Agile environments; produces high-quality, comprehensive integration specifications and deployment instructions that enhance team efficiency.
Cleo Consulting is an equal opportunity employer (Minorities/Women/Veterans/Disabled)