ServiceNow Developer (SNOW SME TC2) (Government)
AT&T · Columbia, MD · 4 wk ago
On-siteOTHR$98k–$274k/yrFull-time
We need to output HTML fragment with sections: About the role? The posting includes description. We need to use for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include only sections with real content.
We need to parse the posting.
Key info:
- Company: AT&T Global Public Sector description. Could be "About the role" maybe includes overview.
- Responsibilities: list of duties.
- Required Qualifications: list.
- Desired Qualifications: maybe under Skills or Qualifications.
- Pay: salary range $98,100 - $273,900 yearly.
- Benefits: list of benefits.
- Schedule: Weekly Hours 40, Time Type Regular.
- Location: Columbia, Maryland (maybe not a heading; could be in a paragraph).
- Clearance: Required Clearance: Clearable. With ability to obtain/maintain TS/SCI with polygraph. This is a requirement; could be under Requirements or Qualifications.
We must not repeat job title as heading. The job title is "mid-level ServiceNow Software Developer" maybe also "ServiceNow Developer (SNOW SME TC2) (Government)". We should not put that as heading.
We must not include boilerplate like EEO, application instructions, etc.
We must not include duplicated lines.
We must preserve all substantive information.
We need to output only HTML fragment, no /, no markdown fences.
We need to decide sections.
Potential sections:
- About the role: overview paragraph.
- Responsibilities: list.
- Requirements: maybe includes clearance, required qualifications.
- Qualifications: maybe includes desired qualifications? But we have both required and desired. Could combine under Requirements and Qualifications? The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can have multiple.
We need to decide what goes where.
- About the role: description of AT&T Global Public Sector, mission, role purpose.
- Responsibilities: bullet list of duties.
- Requirements: maybe includes clearance, required qualifications (degree, years, etc.) and maybe required certifications.
- Qualifications: maybe desired qualifications? Or we could treat Qualifications as both required and desired? But we have separate headings. Could put required under Requirements, desired under Qualifications.
- Skills: maybe list of technical skills (JavaScript, HTML/CSS, etc.) but many are in qualifications. Could put under Skills.
- Benefits: list.
- Pay: salary range.
- Schedule: weekly hours, time type.
We must not create sections with placeholder text. Ensure each section has substantive content.
Let's extract content.
About the role: The first paragraph: "AT&T Global Public Sector is a trusted provider of secure, IP enabled, cloud-based, network solutions and professional services to the Federal Government. We are dedicated to recruiting, developing and empowering a diverse, high-performing workforce that is passionate about what they do, committed to our shared values and dedicated to our customers’ mission. RIS I is the delivery of regional IT services to the end user. We offer support of end user devices including desktop, workplace peripherals, and voice and video devices. We support local and campus area networks, including wireless and cable plant. Join our team as a mid-level ServiceNow Software Developer and help design, enhance, and support mission-critical ServiceNow solutions that enable efficient IT service delivery, workflow automation, and platform modernization. This role is ideal for a technically skilled, collaborative developer who is ready to contribute to a high-impact environment while working closely with business, technical, and leadership stakeholders."
That's substantive.
Responsibilities: The bullet list under "Key Responsibilities". Also earlier description of duties: "This position offers the opportunity to design, develop, test, and deploy custom ServiceNow solutions while partnering with framework managers, senior leaders, customers, vendors, and technical teams. The ideal candidate brings strong development fundamentals, a customer-focused mindset, and the ability to translate business needs into reliable, scalable platform solutions."
But we can combine.
List:
- Design, develop, test, and deploy custom applications and enhancements within the ServiceNow platform.
- Support and maintain IT Asset Management (ITAM), Configuration Management Database (CMDB), and IT Service Management (ITSM) processes and applications.
- Partner with business stakeholders, managers, customers, and technical teams to gather, refine, and implement software development requirements.
- Provide ServiceNow technical support, consultation, and troubleshooting for platform users and stakeholders.
- Troubleshoot and resolve system defects, performance issues, and configuration challenges.
- Create and maintain technical documentation, reports, and user-facing support materials.
- Participate in User Acceptance Testing, Technical Exchange Meetings, platform upgrades, and Agile development activities.
Also maybe include "This position requires office presence a minimum of 5 days per week and is only located in the location(s) posted. No relocation is offered." That's more about schedule/location; could go under Schedule or a separate note but we have Schedule heading.
Requirements: Required Clearance: Clearable. With the ability to obtain/maintain TS/SCI with polygraph. Also Required Qualifications list:
- Bachelor's degree in Computer Science, Information Systems, or related field (or equivalent experience).
- 2-5 years of ServiceNow development experience.
- Proficiency in JavaScript.
- Strong analytical, troubleshooting, and problem-solving skills.
- Security+.
- ServiceNow Certified System Administrator (CSA).
We could put these under Requirements.
Qualifications: Desired Qualifications list:
- Strong knowledge of HTML and CSS.
- Understanding of CMDB concepts and asset lifecycle management.
- Experience supporting ServiceNow IT Service Management (ITSM) and IT Asset Management (ITAM) applications.
- Experience with ServiceNow development, including: Catalog Page configuration, Client Scripts, UI Policies, Business Rules, Script Includes, UI Pages, UI Actions, Glide API, Flow Designer, ACLs.
- Knowledge of SQL and relational database concepts.
- Familiarity with Agile development methodologies.
- Familiarity with version control processes.
We could put under Qualifications.
Skills: maybe we could list technical skills like JavaScript, HTML/CSS, etc. But many already in qualifications. Could combine but we need to avoid duplication. Perhaps we can put Skills as a summary of technical skills: JavaScript, HTML/CSS, SQL, etc. But we risk duplication. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we must not omit details. If we put skills section, we must include all skills details, but they'd be duplicated if also in qualifications. Better to not have a Skills section if it would cause duplication. However we could still have Skills section with a subset not covered elsewhere, but we risk missing details. The instruction: "Prefer a few substantive sections over many thin ones." So we could omit Skills section and include skills within Qualifications or Requirements. That's acceptable.
Thus we will have sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay, Schedule.
We need to include location maybe in a paragraph under About the role or separate? Could add a short paragraph after About the role: "Location: Columbia, Maryland". But we must not create a heading for location. Could embed in About the role paragraph.
Also mention office presence 5 days per week, no relocation. That could go under Schedule? Actually schedule heading is for Weekly Hours 40, Time Type Regular. The office presence 5 days per week is more about work arrangement; could be included in Schedule section as note.
We'll include Schedule section with: Weekly Hours 40, Time Type Regular, Office presence required minimum 5 days per week, No relocation offered.
Now Benefits: list all benefits.
We need to ensure we don't include boilerplate like EEO, etc.
Let's extract benefits list:
- Medical/Dental/Vision coverage
- 401(k) plan
- Tuition reimbursement program
- Paid Time Off and Holidays (based on date of hire, at least 23 days of vacation each year and 9 company-designated holidays) *Pro-rated when working less than 40 hrs/wk.
- Paid Parental Leave
- Paid Caregiver Leave
- Additional sick leave beyond what state and local law require may be available but is unprotected
- Adoption Reimbursement
- Disability Benefits (short term and long term)
- Life and Accidental Death Insurance
- Supplemental benefit programs: critical illness/accident hospital indemnity/group legal
- Employee Assistance Programs (EAP)
- Extensive employee wellness programs
- Employee discounts up to 50% off on eligible AT&T mobility plans and accessories, AT&T internet (and fiber where available) and AT&T wireline phone
We need to preserve all.
Pay: "$98,100 - $273,900 yearly. Individual starting salary within this range may depend on geography, experience, expertise, and education/training."
We'll include that.
Now we need to output HTML fragment.
Structure:
for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include only sections with real content.
We need to parse the posting.
Key info:
- Company: AT&T Global Public Sector description. Could be "About the role" maybe includes overview.
- Responsibilities: list of duties.
- Required Qualifications: list.
- Desired Qualifications: maybe under Skills or Qualifications.
- Pay: salary range $98,100 - $273,900 yearly.
- Benefits: list of benefits.
- Schedule: Weekly Hours 40, Time Type Regular.
- Location: Columbia, Maryland (maybe not a heading; could be in a paragraph).
- Clearance: Required Clearance: Clearable. With ability to obtain/maintain TS/SCI with polygraph. This is a requirement; could be under Requirements or Qualifications.
We must not repeat job title as heading. The job title is "mid-level ServiceNow Software Developer" maybe also "ServiceNow Developer (SNOW SME TC2) (Government)". We should not put that as heading.
We must not include boilerplate like EEO, application instructions, etc.
We must not include duplicated lines.
We must preserve all substantive information.
We need to output only HTML fragment, no /, no markdown fences.
We need to decide sections.
Potential sections:
- About the role: overview paragraph.
- Responsibilities: list.
- Requirements: maybe includes clearance, required qualifications.
- Qualifications: maybe includes desired qualifications? But we have both required and desired. Could combine under Requirements and Qualifications? The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can have multiple.
We need to decide what goes where.
- About the role: description of AT&T Global Public Sector, mission, role purpose.
- Responsibilities: bullet list of duties.
- Requirements: maybe includes clearance, required qualifications (degree, years, etc.) and maybe required certifications.
- Qualifications: maybe desired qualifications? Or we could treat Qualifications as both required and desired? But we have separate headings. Could put required under Requirements, desired under Qualifications.
- Skills: maybe list of technical skills (JavaScript, HTML/CSS, etc.) but many are in qualifications. Could put under Skills.
- Benefits: list.
- Pay: salary range.
- Schedule: weekly hours, time type.
We must not create sections with placeholder text. Ensure each section has substantive content.
Let's extract content.
About the role: The first paragraph: "AT&T Global Public Sector is a trusted provider of secure, IP enabled, cloud-based, network solutions and professional services to the Federal Government. We are dedicated to recruiting, developing and empowering a diverse, high-performing workforce that is passionate about what they do, committed to our shared values and dedicated to our customers’ mission. RIS I is the delivery of regional IT services to the end user. We offer support of end user devices including desktop, workplace peripherals, and voice and video devices. We support local and campus area networks, including wireless and cable plant. Join our team as a mid-level ServiceNow Software Developer and help design, enhance, and support mission-critical ServiceNow solutions that enable efficient IT service delivery, workflow automation, and platform modernization. This role is ideal for a technically skilled, collaborative developer who is ready to contribute to a high-impact environment while working closely with business, technical, and leadership stakeholders."
That's substantive.
Responsibilities: The bullet list under "Key Responsibilities". Also earlier description of duties: "This position offers the opportunity to design, develop, test, and deploy custom ServiceNow solutions while partnering with framework managers, senior leaders, customers, vendors, and technical teams. The ideal candidate brings strong development fundamentals, a customer-focused mindset, and the ability to translate business needs into reliable, scalable platform solutions."
But we can combine.
List:
- Design, develop, test, and deploy custom applications and enhancements within the ServiceNow platform.
- Support and maintain IT Asset Management (ITAM), Configuration Management Database (CMDB), and IT Service Management (ITSM) processes and applications.
- Partner with business stakeholders, managers, customers, and technical teams to gather, refine, and implement software development requirements.
- Provide ServiceNow technical support, consultation, and troubleshooting for platform users and stakeholders.
- Troubleshoot and resolve system defects, performance issues, and configuration challenges.
- Create and maintain technical documentation, reports, and user-facing support materials.
- Participate in User Acceptance Testing, Technical Exchange Meetings, platform upgrades, and Agile development activities.
Also maybe include "This position requires office presence a minimum of 5 days per week and is only located in the location(s) posted. No relocation is offered." That's more about schedule/location; could go under Schedule or a separate note but we have Schedule heading.
Requirements: Required Clearance: Clearable. With the ability to obtain/maintain TS/SCI with polygraph. Also Required Qualifications list:
- Bachelor's degree in Computer Science, Information Systems, or related field (or equivalent experience).
- 2-5 years of ServiceNow development experience.
- Proficiency in JavaScript.
- Strong analytical, troubleshooting, and problem-solving skills.
- Security+.
- ServiceNow Certified System Administrator (CSA).
We could put these under Requirements.
Qualifications: Desired Qualifications list:
- Strong knowledge of HTML and CSS.
- Understanding of CMDB concepts and asset lifecycle management.
- Experience supporting ServiceNow IT Service Management (ITSM) and IT Asset Management (ITAM) applications.
- Experience with ServiceNow development, including: Catalog Page configuration, Client Scripts, UI Policies, Business Rules, Script Includes, UI Pages, UI Actions, Glide API, Flow Designer, ACLs.
- Knowledge of SQL and relational database concepts.
- Familiarity with Agile development methodologies.
- Familiarity with version control processes.
We could put under Qualifications.
Skills: maybe we could list technical skills like JavaScript, HTML/CSS, etc. But many already in qualifications. Could combine but we need to avoid duplication. Perhaps we can put Skills as a summary of technical skills: JavaScript, HTML/CSS, SQL, etc. But we risk duplication. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we must not omit details. If we put skills section, we must include all skills details, but they'd be duplicated if also in qualifications. Better to not have a Skills section if it would cause duplication. However we could still have Skills section with a subset not covered elsewhere, but we risk missing details. The instruction: "Prefer a few substantive sections over many thin ones." So we could omit Skills section and include skills within Qualifications or Requirements. That's acceptable.
Thus we will have sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay, Schedule.
We need to include location maybe in a paragraph under About the role or separate? Could add a short paragraph after About the role: "Location: Columbia, Maryland". But we must not create a heading for location. Could embed in About the role paragraph.
Also mention office presence 5 days per week, no relocation. That could go under Schedule? Actually schedule heading is for Weekly Hours 40, Time Type Regular. The office presence 5 days per week is more about work arrangement; could be included in Schedule section as note.
We'll include Schedule section with: Weekly Hours 40, Time Type Regular, Office presence required minimum 5 days per week, No relocation offered.
Now Benefits: list all benefits.
We need to ensure we don't include boilerplate like EEO, etc.
Let's extract benefits list:
- Medical/Dental/Vision coverage
- 401(k) plan
- Tuition reimbursement program
- Paid Time Off and Holidays (based on date of hire, at least 23 days of vacation each year and 9 company-designated holidays) *Pro-rated when working less than 40 hrs/wk.
- Paid Parental Leave
- Paid Caregiver Leave
- Additional sick leave beyond what state and local law require may be available but is unprotected
- Adoption Reimbursement
- Disability Benefits (short term and long term)
- Life and Accidental Death Insurance
- Supplemental benefit programs: critical illness/accident hospital indemnity/group legal
- Employee Assistance Programs (EAP)
- Extensive employee wellness programs
- Employee discounts up to 50% off on eligible AT&T mobility plans and accessories, AT&T internet (and fiber where available) and AT&T wireline phone
We need to preserve all.
Pay: "$98,100 - $273,900 yearly. Individual starting salary within this range may depend on geography, experience, expertise, and education/training."
We'll include that.
Now we need to output HTML fragment.
Structure:
About the role
...
Responsibilities
- ... ...
Requirements
- ... ...
Qualifications
- ... ...
Benefits
- ... ...
Pay
...
Schedule
...
Make sure no extra whitespace? It's fine. Now craft the About the role paragraph: combine the description. Let's write: AT&T Global Public Sector is a trusted provider of secure, IP‑enabled, cloud‑based network solutions and professional services to the Federal Government. The company is dedicated to recruiting, developing and empowering a diverse, high‑performing workforce that is passionate about its work, committed to shared values and focused on customers’ missions. RIS I delivers regional IT services to end users, supporting desktop and workplace peripherals, voice and video devices, and local and campus area networks (including wireless and cable plant). As a mid‑level ServiceNow Software Developer you will help design, enhance and support mission‑critical ServiceNow solutions that enable efficient IT service delivery, workflow automation and platform modernization. This role suits a technically skilled, collaborative developer ready to contribute to a high‑impact environment while working closely with business, technical and leadership stakeholders. The position is based in Columbia, Maryland and requires office presence a minimum of five days per week; no relocation is offered. That captures location and office presence. Now Responsibilities list as above. Now Requirements list: include clearance and required qualifications. We need to include clearance as a bullet maybe. List: - Clearable; ability to obtain and maintain TS/SCI clearance with polygraph. - Bachelor's degree in Computer Science, Information Systems, or related field (or equivalent experience). - 2‑5 years of ServiceNow development experience. - Proficiency in JavaScript. - Strong analytical, troubleshooting and problem‑solving skills. - Security+ certification. - ServiceNow Certified System Administrator (CSA). Now Qualifications list: desired qualifications. We need to capture the list exactly. Desired Qualifications: - Strong knowledge of HTML and CSS. - Understanding of CMDB concepts and asset lifecycle management. - Experience supporting ServiceNow IT Service Management (ITSM) and IT Asset Management (ITAM) applications. - Experience with ServiceNow development, including: - Catalog Page configuration - Client Scripts - UI Policies - Business Rules - Script Includes - UI Pages - UI Actions - Glide API - Flow Designer - ACLs - Knowledge of SQL and relational database concepts. - Familiarity with Agile development methodologies. - Familiarity with version control processes. We need to format as- ... maybe nested lists for the subitems. The instruction: Use
- for any list of duties/requirements/benefits. It didn't forbid nested lists. We can include nested
- inside
- for the subitems
- for any list of duties/requirements/benefits. It didn't forbid nested lists. We can include nested