Lead Application Developer

We need to output HTML fragment with sections: Use

for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. We need to parse posting. The posting includes: - Intro: "This role requires the ability to work lawfully in the U.S. without employment-based immigration sponsorship, now or in the future." That's a requirement (legal work authorization). Could be part of Requirements. - Job title: "Lead Applications Developer" (should not repeat as heading). - Paragraph: "Imagine leading the creation of innovative enterprise web applications that drive the digital transformation at Spectrum Reach. As a Lead Applications Developer, you will leverage your expertise to deliver top-quality solutions, mentor team members and shape impactful projects. Your work will directly enhance user experiences for both internal and external stakeholders, ensuring Spectrum remains at the forefront of technology." That's about the role. - Then "How You’ll Make An Impact" followed by bullet-like sentences (list). Those are responsibilities. - Then "Required Qualifications" with subheadings: Education, Experience, Skills (list). Then "Preferred Qualifications" with Education, Experience, Skills. - Then some filler: "ISW390 2026-82116 ISW390 2026" maybe job ID etc - drop. - Then "Here, our employees don’t just have jobs, they're building careers. That’s why we offer a comprehensive pay and benefits package that rewards employees for their contributions to our success, supporting all aspects of their well-being at every stage of life." This mentions benefits but not specific details. It says "comprehensive pay and benefits package". No specifics. According to rule: never create Pay/Schedule/Benefits sections unless posting actually states them. It mentions pay and benefits package but not specifics; we should not create those sections because no concrete details. So we omit Benefits, Pay, Schedule. - Then "A qualified applicant’s criminal history, if any, will be considered in a manner consistent with applicable laws, including local ordinances." That's legal boilerplate; remove. - Then "Get to Know Us Charter Communications provides superior communication..." That's company description; could be part of About the role? Might be considered "About the company". Not a required heading but we could include as part of About the role or maybe a separate section? The instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can include About the role (maybe includes company description). We'll keep About the role as a section with prose. - Then "Grow Your Career Here We’re committed to growing a workforce that reflects the customers and communities we serve – providing opportunities for employment and advancement to all team members. Spectrum is an Equal Opportunity Employer, including job seekers with disabilities and veterans. Learn about Life at Spectrum." That's EEO boilerplate; remove. Thus we need sections: About the role, Responsibilities, Requirements (maybe combine Education, Experience, Skills?), Qualifications (maybe Required Qualifications?), Skills (maybe separate). The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have sections: About the role, Responsibilities, Requirements, Qualifications, Skills. However we have both Required and Preferred qualifications. Could combine into Requirements (maybe includes education, experience) and Skills (list of skills). Or we could have Requirements (education+experience) and Skills (skill list). The posting includes both Required Qualifications (Education, Experience, Skills) and Preferred Qualifications (Education, Experience, Skills). We need to preserve all substantive info. We could have a section "Requirements" containing Required Qualifications (Education, Experience, Skills) and maybe a subsection for Preferred? But we cannot create subheadings besides h3? We could use

for prose and

• for lists. We could combine Required and Preferred into one Requirements section with two sublists? But we need to preserve distinction. Could do:

  Required Qualifications

  and

  Preferred Qualifications

  but those are not in the allowed list? The list includes Qualifications as a heading. It says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". Likely they expect those headings only. However we could still use Qualifications heading and inside include both required and preferred as paragraphs/lists. But we need to preserve the distinction. Could do:

  Qualifications

  then

  Required: ...

  etc. That's acceptable. Similarly Skills could be a separate section. Thus final HTML:

  About the role

  This role requires the ability to work lawfully in the U.S. without employment-based immigration sponsorship, now or in the future. Imagine leading the creation of innovative enterprise web applications that drive the digital transformation at Spectrum Reach. As a Lead Applications Developer, you will leverage your expertise to deliver top-quality solutions, mentor team members and shape impactful projects. Your work will directly enhance user experiences for both internal and external stakeholders, ensuring Spectrum remains at the forefront of technology.

  Responsibilities

  • Organize and assign project tasks for Application Development team members, guiding successful execution
  • Design and implement robust web applications for a seamless user experience
  • Build engaging user interfaces and integrate rich data for optimal application performance
  • Mentor and coach less experienced staff to develop technical and professional skills
  • Collaborate with technical staff to analyze and resolve software issues, ensuring timely solutions
  • Lead application reviews through unit testing and code reviews to maintain high standards
  • Contribute to process improvements and best practices using your extensive experience
  • Work with cross-functional teams comprising internal and external resources, both onshore and offshore
  • Actively pursue knowledge of new development technologies in the areas of enterprise web applications, operational tools and other niches as necessary
  • Works with the team to write new features and UI enhancements for existing web applications
  • Executes automated tests during functional and regression test cycles
  • Isolates, replicates, and reports defects and verifies defect fixes
  • Provides general system users and management with system analysis and feedback
  • Focus on meeting deadlines and deliverables while adapting to shifting priorities
  • Mentors and coaches less experienced staff
  • Analyzes and resolves automation related problems by coordinating with team to diagnose and fix issues

  Qualifications

  Required:

  • Education: Bachelor’s degree in Information Technology, Computer Science or a related field or equivalent work experience
  • Experience: 7+ years of relevant .NET web application development experience
  • Skills: Effective written and verbal communication skills; In-depth ability to analyze and resolve defects; Strong attention to detail; Ability to work well with shifting priorities; Ability to work with cross-functional team of internal and external resources located onshore and offshore; Thorough understanding of quality assurance processes, tools and methodologies; Proficient in Visual Studio and Microsoft Office applications; Expert knowledge of the AGILE software development life cycle; Deep understanding of database schemas and querying tools; Negotiation Skills And Ability To Influence Others; Ability to assist others in learning new technical and professional capabilities; Ability to accurately analyze automation opportunities for technical requirements; Expert knowledge of C#, AJAX, JSON, HTML, XML and SQL technologies; Expert knowledge of AWS Lambda, DynamoDB, API Gateway, Cloudfront, Typescript CDK and IAM; Knowledge of Gitlab CICD pipelines; Knowledge of developing and consuming APIs and Web Services; Knowledge of AI driven development patterns; Professional, positive, and approachable demeanor

  Preferred:

  • Education: Bachelor’s degree in Computer Science, Engineering or related field
  • Experience: 5+ years developing .NET (C#, MVC) web applications; 5+ years working with JSON, REST and SOAP web services; 5+ years of professional software development experience
  • Skills: Ability to assist others in learning new technical and professional capabilities; Experience with AWS MediaConvert; Experience with Python

  Skills

  • Effective written and verbal communication skills
  • In-depth ability to analyze and resolve defects
  • Strong attention to detail
  • Ability to work well with shifting priorities
  • Ability to work with cross-functional team of internal and external resources located onshore and offshore
  • Thorough understanding of quality assurance processes, tools and methodologies
  • Proficient in Visual Studio and Microsoft Office applications
  • Expert knowledge of the AGILE software development life cycle
  • Deep understanding of database schemas and querying tools
  • Negotiation Skills And Ability To Influence Others
  • Ability to assist others in learning new technical and professional capabilities
  • Ability to accurately analyze automation opportunities for technical requirements
  • Expert knowledge of C#, AJAX, JSON, HTML, XML and SQL technologies
  • Expert knowledge of AWS Lambda, DynamoDB, API Gateway, Cloudfront, Typescript CDK and IAM
  • Knowledge of Gitlab CICD pipelines
  • Knowledge of developing and consuming APIs and Web Services
  • Knowledge of AI driven development patterns
  • Professional, positive, and approachable demeanor
  • Experience with AWS MediaConvert (preferred)
  • Experience with Python (preferred)
  But we have duplicated skills list; maybe better to not duplicate. The instruction: Prefer a few substantive sections over many thin ones. Could combine Qualifications and Skills into one section? But they ask to use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we could have Qualifications (including education/experience) and Skills separate. However we already listed skills inside Qualifications; duplication may be okay but could be considered redundant. Better to keep Qualifications for education/experience only, and Skills for skill list. Let's restructure:

  Qualifications

  Required:

  • Education: Bachelor’s degree in Information Technology, Computer Science or a related field or equivalent work experience
  • Experience: 7+ years of relevant .NET web application development experience

  Preferred:

  • Education: Bachelor’s degree in Computer Science, Engineering or related field
  • Experience: 5+ years developing .NET (C#, MVC) web applications; 5+ years working with JSON, REST and SOAP web services; 5+ years of professional software development experience

  Skills

  • Effective written and verbal communication skills
  • In-depth ability to analyze and resolve defects
  • Strong attention to detail
  • Ability to work well with shifting priorities
  • Ability to work with cross-functional team of internal and external resources located onshore and offshore
  • Thorough understanding of quality assurance processes, tools and methodologies
  • Proficient in Visual Studio and Microsoft Office applications
  • Expert knowledge of the AGILE software development life cycle