Senior ServiceNow Developer - Public Trust Clearance

We need to output HTML fragment with sections: About the role? The posting includes description at start: "LightFeather is seeking a highly skilled Senior ServiceNow Developer to play a critical role..." That's about the role. Then Responsibilities, Required Qualifications and Skills (maybe combine as Requirements/Qualifications/Skills). Also Pay (Salary). Schedule? Not given. Benefits? Not given. So we include sections: About the role (maybe not required but we can include). The instruction: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Include a section ONLY when posting has real, specific content for it. So we need About the role (the introductory paragraph). Responsibilities (list). Requirements/Qualifications/Skills: we could combine into one section "Requirements" or separate Qualifications and Skills. The instruction says prefer a few substantive sections over many thin ones. So we could have "Requirements" covering qualifications and skills. Pay section: salary given. Schedule: not given (only Full Time, Remote Position, EST hours). That's schedule info? It says Full Time, Remote Position. Location: Fully Remote (EST hours). That could be considered schedule? It's more about location and hours. The instruction says include Schedule section only if posting actually states them. It does state Full Time, Remote Position, EST hours. That's schedule info. So we could include Schedule section with that info. Benefits: not given, so omit. Also need to include metadata like Job ID etc? Not present. So we output:

About the role

...

Then Responsibilities with

• ... each bullet. Then Requirements with
  • ... each bullet. Then Pay with

    $90,000–$115,000 annually, based on experience

    Then Schedule with

    Full‑time, remote position; work hours aligned to EST.

    We must preserve all substantive information. Need to include clearance requirement: U.S. citizenship required for Public Trust clearance. That's part of requirements. Also need to include "Clearance Requirement: U.S. citizenship is required for this position due to federal contract requirements and the need to obtain and maintain a Public Trust level security clearance". So include that in requirements. Also need to include "Active DHS Public Trust clearance or higher." as required qualification. Also need to include "9+ years of hands-on experience with ServiceNow platform development and administration." Also need to include certifications etc. Also need to include "Preferred:" items; we can include them as part of requirements but maybe note as preferred. We'll include them as bullet points with note "(Preferred)" maybe. We must not invent or summarize away detail. Keep all specifics. Let's extract responsibilities list: - Lead the design, configuration, development, and deployment of ServiceNow applications, ensuring alignment with business requirements and industry best practices. - Develop, customize, and enhance ServiceNow modules, including but not limited to ITSM, ITOM, HRSD, App Engine, and Service Portal. - Create and manage complex workflows, business rules, UI policies, ACLs, and automation scripts using JavaScript, GlideScript, and Flow Designer. - Develop custom widgets and UI components for the Service Portal using AngularJS, HTML, CSS, and JavaScript. - Lead integration efforts with external systems using REST APIs, SOAP APIs, MID Server, Integration Hub, and third-party connectors. - Ensure platform security, compliance, and best practices, including role-based access controls (RBAC) and data governance policies. - Mentor and lead a team of ServiceNow developers, providing guidance, technical oversight, and best practices for efficient solution delivery. - Collaborate with stakeholders and business analysts to translate requirements into scalable, maintainable ServiceNow solutions. - Troubleshoot and resolve platform issues, optimize system performance, and conduct root cause analysis. - Work within an Agile framework (Scrum/Kanban), participating in sprint planning, backlog grooming, and daily stand-ups. - Document technical solutions, workflows, and architecture designs for internal knowledge sharing and client handover. Now qualifications/skills list: Required Qualifications and Skills: - Active DHS Public Trust clearance or higher. - 9+ years of hands-on experience with ServiceNow platform development and administration. - ServiceNow Certified System Administrator (CSA). - Strong expertise in ServiceNow App Engine and custom application development. - Advanced knowledge of ServiceNow Service Portal Development, including widget customization and UI scripting. - Experience integrating ServiceNow with external systems using REST, SOAP, and third-party APIs. - Proven ability to lead development teams and ensure efficient, high-quality solution delivery. - Experience working in Agile environments with tools like Jira or Azure DevOps. - Experience with CI/CD pipelines and DevOps practices for ServiceNow application deployment. - Experience working with Amazon Web Services (AWS). - Strong scripting skills in JavaScript, GlideScript, and Flow Designer. - Excellent communication skills with the ability to present technical concepts to both technical and non-technical audiences. - Strong leadership and mentoring skills, with experience managing development teams. - Exceptional problem-solving, analytical thinking, and troubleshooting abilities. - Excellent stakeholder management, communication, and presentation skills. - Conflict resolution expertise to mitigate risks and ensure project success. - U.S. citizenship is required for this position due to federal contract requirements and the need to obtain and maintain a Public Trust level security clearance. Preferred: - Experience with HR Service Delivery (HRSD) solutions within ServiceNow. - Deep expertise in ServiceNow platform architecture and solution design. - Experience with scripting languages such as JavaScript, GlideScript, and UI policies/business rules. - Proficiency in designing and implementing complex integrations using Integration Hub and external APIs. We need to include all. We'll combine required and preferred into one Requirements section, maybe separate subheadings? But we cannot add extra headings beyond allowed list? We can still use
    • and maybe add a note like "(Preferred)" inside li. That's okay. Now About the role paragraph: The first sentences: "LightFeather is seeking a highly skilled Senior ServiceNow Developer to play a critical role in designing, developing, and deploying ServiceNow solutions for federal government projects. This role requires deep technical expertise, strong leadership, and the ability to drive the successful implementation of ServiceNow applications while ensuring optimal performance, security, and scalability. The ideal candidate will have extensive experience in ServiceNow platform architecture, development, integrations, and workflow automation, along with the ability to lead teams in an Agile environment. This is a Full Time, Remote Position. Location: Fully Remote (EST hours)Job Type: Full-timeSalary: $90,000–$115,000 annually, based on experienceClearance Requirement: U.S. citizenship is required for this position due to federal contract requirements and the need to obtain and maintain a Public Trust level security clearance" We need to avoid repeating job title as heading. Already not. We need to remove duplicated lines and boilerplate like EEO etc. At end there is EEO statement; we should remove. Also remove "Why Join LightFeather?" section? That's promotional but maybe considered boilerplate? It's not EEO but it's a marketing section. The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. "Why Join LightFeather?" is not explicitly listed but could be considered promotional; but it's substantive? It describes culture. Might be considered not required but could be kept? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. The "Why Join LightFeather?" is substantive about company culture. However, they didn't list it as a section heading to include; but we could include it as a paragraph under About the role? Might be okay to keep as part of About the role. But we already have About the role paragraph; we could append that paragraph. But we must not create sections with filler. The "Why Join LightFeather?" includes: "At LightFeather, you're not just taking a job—you're joining a purpose-driven team that delivers innovative, mission-critical solutions to make a real difference. You'll work on diverse, meaningful projects that challenge and inspire you, alongside some of the best minds in the industry. LightFeather is an Equal Opportunity Employer. We consider all qualified applicants for employment without regard to race, color, religion, sex, pregnancy, sexual orientation, gender identity, national origin, age, disability, veteran status, genetic information, or any other status protected by applicable federal, state, or local law." The EEO part we need to remove (the second sentence). The first two sentences are substantive; we can keep them. So we can add them to About the role paragraph. Thus About the role paragraph will combine the initial description plus the Why Join LightFeather sentences (excluding EEO). Let's craft: "LightFeather is seeking a highly skilled Senior ServiceNow Developer to play a critical role in designing, developing, and deploying ServiceNow solutions for federal government projects. This role requires deep technical expertise, strong leadership, and the ability to drive the successful implementation of ServiceNow applications while ensuring optimal performance, security, and scalability. The ideal candidate will have extensive experience in ServiceNow platform architecture, development, integrations, and workflow automation, along with the ability to lead teams in an Agile environment. This is a Full Time, Remote Position. Location: Fully Remote (EST hours). At LightFeather, you're not just taking a job—you're joining a purpose-driven team that delivers innovative, mission-critical solutions to make a real difference. You'll work on diverse, meaningful projects that challenge and inspire you, alongside some of the best minds in the industry." We should not include the EEO sentence. Now Pay section: we have salary. Schedule section: we have Full Time, Remote Position; EST hours. Could phrase: "Full‑time, remote position; work hours aligned to EST." Now output HTML fragment. We must not include or . Just the fragment. Let's construct:

      About the role

      LightFeather is seeking a highly skilled Senior ServiceNow Developer to play a critical role in designing, developing, and deploying ServiceNow solutions for federal government projects. This role requires deep technical expertise, strong leadership, and the ability to drive the successful implementation of ServiceNow applications while ensuring optimal performance, security, and scalability. The ideal candidate will have extensive experience in ServiceNow platform architecture, development, integrations, and workflow automation, along with the ability to lead teams in an Agile environment. This is a Full Time, Remote Position. Location: Fully Remote (EST hours). At LightFeather, you're not just taking a job—you're joining a purpose-driven team that delivers innovative, mission-critical solutions to make a real difference. You'll work on diverse, meaningful projects that challenge and inspire you, alongside some of the best minds in the industry.

      Responsibilities

      • Lead the design, configuration, development, and deployment of ServiceNow applications, ensuring alignment with business requirements and industry best practices.
      • Develop, customize, and enhance ServiceNow modules, including but not limited to ITSM, ITOM, HRSD, App Engine, and Service Portal.
      • Create and manage complex workflows, business rules, UI policies, ACLs, and automation scripts using JavaScript, GlideScript, and Flow Designer.
      • Develop custom widgets and UI components for the Service Portal using AngularJS, HTML, CSS, and JavaScript.
      • Lead integration efforts with external systems using REST APIs, SOAP APIs, MID Server, Integration Hub, and third-party connectors.
      • Ensure platform security, compliance, and best practices, including role-based access controls (RBAC) and data governance policies.
      • Mentor and lead a team of ServiceNow developers, providing guidance, technical oversight, and best practices for efficient solution delivery.
      • Collaborate with stakeholders and business analysts to translate requirements into scalable, maintainable ServiceNow solutions.
      • Troubleshoot and resolve platform issues, optimize system performance,