Solution Engineer Sr

We need to produce HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title as heading. No Job ID. Remove boilerplate like EEO, etc. Must preserve all substantive info. Let's parse the posting. Job Title: Solution Engineer Sr Location: Columbus, OH Work Model: Onsite / Hybrid / Remote Position Overview: ServiceNow experience and deep expertise in designing, developing, and supporting enterprise ServiceNow solutions. The ideal candidate will have a strong understanding of the ServiceNow platform, including CMDB, integrations, workflows, and platform best practices. Experience leading or participating in annual ServiceNow platform upgrades is required. Experience working with both on-premises and cloud-based ServiceNow environments is highly preferred. What You Will Be Doing: list of bullet points (actually a paragraph with many sentences). We need to extract duties/responsibilities. WHAT’S NEEDED: Basic Qualifications: Education: Bachelor's degree in computer science, engineering, or related technical field is required. Experience: Minimum of 5 years of relevant work experience is required. An equivalent combination of education and related experience may be considered. Compensation & Benefits: Medical, dental, and vision insurance 401(k) Other standard benefits as applicable Distribution List: IT/Technical (metadata, maybe drop) About Unicon: description of company, maybe not needed? It's boilerplate but maybe we can keep as "About the company"? Not required sections. The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "About Unicon" is not exactly boilerplate but could be considered company description; not required to keep? It says preserve ALL substantive information; do NOT invent or summarize away detail. The "About Unicon" is substantive about the employer. Should we include? There's no specific section for company overview; we could put under "About the role" maybe? But "About the role" is for role description. Could create a section "About the company" but not in allowed headings list. The allowed headings are only those listed; we should not create other headings. So we likely omit the About Unicon paragraph, as it's not required to be in any of the allowed sections. However, we must preserve ALL substantive information; but if we omit it, we lose info. The instruction says "Prefer a few substantive sections over many thin ones." It doesn't forbid adding other sections, but says "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It gives examples but not exclusive list? It says "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That suggests those are the expected headings. It also says "include a section ONLY when the posting has real, specific content for it". So we should only use those headings if we have content. If we have content that doesn't fit those, maybe we could still use one of them? For company description, maybe we could put under "About the role"? Not ideal. But maybe we can omit as it's not required for the job posting core. The instruction to preserve ALL substantive information may be overridden by the instruction to remove boilerplate. The "About Unicon" might be considered boilerplate (company description). It's not EEO/legal but still generic. I'd lean to omit it. Now we need to extract content for each possible section. About the role: Could be the Position Overview paragraph. That's a good fit. Responsibilities: The "What You Will Be Doing" list. Requirements: Could be the "WHAT’S NEEDED" basic qualifications? But we also have Qualifications separate. Usually Requirements = basic qualifications, Qualifications = preferred qualifications. However the posting only has basic qualifications under WHAT’S NEEDED. There's no separate preferred qualifications list. So we could put Requirements as the basic qualifications (education, experience). Qualifications could be left out if no content. But we have also "Experience leading or participating in annual ServiceNow platform upgrades is required." etc. That's more like responsibilities? Actually those are under Position Overview. Might be considered requirements. Let's parse: Position Overview: ServiceNow experience and deep expertise in designing, developing, and supporting enterprise ServiceNow solutions. The ideal candidate will have a strong understanding of the ServiceNow platform, including CMDB, integrations, workflows, and platform best practices. Experience leading or participating in annual ServiceNow platform upgrades is required. Experience working with both on-premises and cloud-based ServiceNow environments is highly preferred. That's a mix of responsibilities and qualifications. Could treat as part of "About the role" or "Requirements". Since we have a separate "What You Will Be Doing" for duties, we can put the Position Overview under "About the role". Then the "WHAT’S NEEDED" under "Requirements". Then maybe "Skills" for technical skills list (Java, JavaScript, etc). "Benefits" for compensation & benefits. Pay and Schedule not present, so omit. We also have "Work Model: Onsite / Hybrid / Remote" - that's schedule? Could be considered Schedule. But schedule usually refers to hours, shift. Work model could be considered Schedule? The instruction: include Pay/Schedule/Benefits sections only if posting actually states them. Work Model is stated; we could put under Schedule? Might be acceptable. However the allowed heading list includes Schedule. We could put work model there. But is that "schedule"? Might be a stretch but we have no other schedule info. I'd include Schedule section with the work model. Now Benefits: Medical, dental, and vision insurance 401(k) Other standard benefits as applicable. Now Skills: list of technical skills: Java programming language and related software development technologies. Experience developing integrations using REST, SOAP, and Integration Hub. Proficiency in JavaScript, Flow Designer, Business Rules, Client Scripts, Script Includes, and UI customization. Additional code languages such as powershell, python, bash, C++ are a plus. Also maybe "Serve as technical expert on development projects." etc. But those are more responsibilities. We'll extract skills. Now Responsibilities: the "What You Will Be Doing" bullet list (the long paragraph). We'll break into bullet items. Let's extract each sentence as a bullet. What You Will Be Doing list: - Proven experience planning, testing, and executing ServiceNow annual upgrades. - Strong knowledge of the ServiceNow platform architecture, development framework, and best practices. - Extensive experience with CMDB, Discovery, Service Mapping, and data governance. - Experience supporting or migrating between on-premises and cloud ServiceNow environments are a plus. - Ability to collaborate with business stakeholders, architects, and technical teams to deliver scalable solutions. - Strong troubleshooting, problem-solving, and documentation skills. - Use Java programming language and related software development technologies. - Experience developing integrations using REST, SOAP, and Integration Hub. - Proficiency in JavaScript, Flow Designer, Business Rules, Client Scripts, Script Includes, and UI customization. - Additional code languages such as powershell, python, bash, C++ are a plus. - Serve as technical expert on development projects. - Participate in full development life cycle including requirements analysis and design. - Write technical specifications based on conceptual design and stated business requirements. - Support, maintain, and document software functionality. - Identify and evaluate new technologies for implementation. - Analyze code to find causes of errors and revise programs as needed. - Participate in software design meetings and analyze user needs to determine technical requirements. - Consult with end-user to prototype, refine, test, and debug programs to meet needs. - Considered highly skilled and proficient in discipline. - Conducts complex work important to the organization. - Works under minimal supervision with wide latitude for independent judgment. Some of these are more like skills or qualifications. But we can keep them under Responsibilities. Now Requirements: Education and Experience. - Bachelor's degree in computer science, engineering, or related technical field is required. - Minimum of 5 years of relevant work experience is required. - An equivalent combination of education and related experience may be considered. Also maybe "Experience leading or participating in annual ServiceNow platform upgrades is required." and "Experience working with both on-premises and cloud-based ServiceNow environments is highly preferred." Those could be under Requirements as well. But they are in Position Overview. However we already used Position Overview for About the role. Might duplicate. Better to keep them under Requirements as they are qualifications. But we risk duplication. The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. So we need to include that info somewhere. If we put Position Overview under About the role, we still need to include the upgrade experience and on-prem/cloud experience. We could incorporate them into About the role as well. That's okay; we can keep them there. Then Requirements only education/experience. Now Skills: we can list technical skills. Let's craft HTML. We'll have:

About the role

ServiceNow experience and deep expertise in designing, developing, and supporting enterprise ServiceNow solutions. The ideal candidate will have a strong understanding of the ServiceNow platform, including CMDB, integrations, workflows, and platform best practices. Experience leading or participating in annual ServiceNow platform upgrades is required. Experience working with both on-premises and cloud-based ServiceNow environments is highly preferred.

Responsibilities

• Proven experience planning, testing, and executing ServiceNow annual upgrades.
• Strong knowledge of the ServiceNow platform architecture, development framework, and best practices.
• Extensive experience with CMDB, Discovery, Service Mapping, and data governance.
• Experience supporting or migrating between on-premises and cloud ServiceNow environments are a plus.
• Ability to collaborate with business stakeholders, architects, and technical teams to deliver scalable solutions.
• Strong troubleshooting, problem-solving, and documentation skills.
• Use Java programming language and related software development technologies.
• Experience developing integrations using REST, SOAP, and Integration Hub.
• Proficiency in JavaScript, Flow Designer, Business Rules, Client Scripts, Script Includes, and UI customization.
• Additional code languages such as powershell, python, bash, C++ are a plus.
• Serve as technical expert on development projects.
• Participate in full development life cycle including requirements analysis and design.
• Write technical specifications based on conceptual design and stated business requirements.
• Support, maintain, and document software functionality.
• Identify and evaluate new technologies for implementation.
• Analyze code to find causes of errors and revise programs as needed.
• Participate in software design meetings and analyze user needs to determine technical requirements.
• Consult with end-user to prototype, refine, test, and debug programs to meet needs.
• Considered highly skilled and proficient in discipline.
• Conducts complex work important to the organization.
• Works under minimal supervision with wide latitude for independent judgment.

Requirements

• Bachelor's degree in computer science, engineering, or related technical field is required.
• Minimum of 5 years of relevant work experience is required.
• An equivalent combination of education and related experience may be considered.

Skills

• Java programming language and related software development technologies.
• Experience developing integrations using REST, SOAP, and Integration Hub.
• Proficiency in JavaScript, Flow Designer, Business Rules, Client Scripts, Script Includes, and UI customization.
• Additional code languages such as powershell, python, bash, C++ are a plus.

Benefits