Principal, IT Software Engineer 1

We need to output HTML fragment with headings

for 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 etc. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Also remove Fair Chance Ordinance notice etc. Also remove "Apply today!" etc. We need to preserve all substantive information. Let's parse the posting. First paragraph: description of role: "The Principal, IT Software Engineer 1 is a senior technical authority ...". That's about the role. So we can put under

About the role

a

with that description. Then "Here’s what you’ll do:" followed by bullet list of responsibilities. Those are responsibilities. So

Responsibilities

with

• each bullet. Then "What you’ll need to be successful:" followed by list of requirements/qualifications/skills. We need to split into sections: Requirements, Qualifications, Skills. The posting lumps them. We need to decide how to categorize. The instruction: use headings for those sections if there is real specific content. We can split: Requirements (education, experience), Qualifications (maybe certifications? none), Skills (technical skills). But we must not invent sections with filler. We need to see if we can meaningfully separate. The list after "What you’ll need to be successful:" includes: - Bachelor's degree in Computer Science, Engineering, or related field, or equivalent practical experience; advanced degree a plus. - 3 – 5 years of progressive software engineering experience, including significant experience in senior/lead technical roles with at least 2 years focused on high-scale Contact Center as a Service (CCaaS), CX enterprise software or Field Services enterprise software. - Extensive experience designing and building reliable workflows and integrations in major CRMs, specifically Salesforce. - Experience in AWS services (e.g., Lambda, EC2, SQS, Kinesis) and proven production experience using Terraform for infrastructure provisioning. - Experience working with REST and SOAP based web-services preferred. - Recognized subject matter expert with deep, broad technical expertise across software engineering, system design, and architecture. - Demonstrated track record of designing and delivering large-scale, distributed, and highly available systems. - Proven ability to influence technical direction and decision-making at an organizational (not just team) level. - Strong expertise in agile methodologies, SAFe/PI planning, and scaled agile delivery models. - Exceptional communication and executive presence; able to translate complex technical concepts for both technical and non-technical audiences, including senior leadership. - Demonstrated success mentoring and developing engineering talent, including senior engineers and tech leads. - Experience driving enterprise architecture standards, technology governance, or engineering best-practice initiatives. - Strong business acumen with the ability to connect technical strategy to organizational and business outcomes. - May require a background check due to job duties requiring routine access to DIRECTV and DIRECTV customer’s proprietary data. - Qualified applicants with arrest and conviction will be considered for employment in accordance with local ordinances and state law. - This is a remote position that can be located anywhere in the United States, with the exception of Alaska. Then after that: "A career with us comes with big rewards: DIRECTV's compensation structure ..." includes pay range info. So we need Pay section. Also there is mention of benefits? Not explicitly. It says "when you consider all of these together, it represents a pretty impressive total compensation package." No explicit benefits list. So we should not create Benefits section unless there is specific content. There's no explicit benefits like health, 401k, etc. So omit Benefits. Schedule? Not mentioned. So omit Schedule. Qualifications? Could treat education and experience as Requirements. Skills could be technical skills like AWS, Terraform, Salesforce, REST/SOAP, agile, etc. But many items are overlapping. We need to avoid duplication and ensure we preserve all substantive info. We could put all items under Requirements (or Qualifications) and not create Skills if it's just splitting same list. But instruction: Prefer a few substantive sections over many thin ones. So maybe we combine Requirements and Qualifications into one section? But we have headings for each; we can choose to include only those with real content. Could we put all under "Requirements" and skip Qualifications and Skills? That would lose distinction but still preserve all info. However the instruction says use headings for those sections if posting has real specific content for it. It doesn't require us to use all headings; we can omit sections if no specific content. So we can have only About the role, Responsibilities, Requirements, Pay. That seems reasonable. But we need to ensure we don't miss any important details like "Recognized subject matter expert" etc. Those are qualifications/skills but we can include them under Requirements. Let's extract the responsibilities list exactly: - Architects and delivers highly complex, cross-system solutions, proactively identifying and resolving dependencies, risks, and technical debt across multiple teams and platforms. - Sets technical direction and establishes architectural standards, patterns, and best practices adopted across the engineering organization. - Lead development of data pathways between internal and external systems, especially with integration to CRM, AI Platforms, and APIs. - Leads and facilitates architectural review boards, design reviews, and technical governance forums, ensuring solutions align with enterprise architecture and long-term technology strategy. - Drives multi-PI (Program Increment) and multi-quarter technical roadmaps, translating business strategy into actionable engineering initiatives and sequencing work across teams. - Serves as the primary technical escalation point for the most complex, ambiguous, or high-risk problems, often those without established precedent or playbook. - Mentors and coaches senior engineers, tech leads, and managers, building organizational depth in technical decision-making, system design, and engineering craftsmanship. - Champions engineering excellence by defining and promoting best practices, coding standards, tooling strategy, and quality processes across the development community. - Proactively identifies systemic risks (technical, operational, and organizational) and partners with leadership to shape mitigation strategies and influence prioritization. - Represents engineering in cross-functional strategic discussions, influencing product, platform, and infrastructure decisions at an organizational level. - Evaluates emerging technologies and industry trends, making recommendations on adoption that materially affect the technology roadmap. - Leads technical due diligence for major initiatives, including build-vs-buy decisions, platform migrations, and large-scale re-architecture efforts. - Drives resolution of critical production issues requiring deep system knowledge and cross-team coordination. Now the requirements list (we need to keep each bullet). Let's list them as bullets under Requirements. - Bachelor's degree in Computer Science, Engineering, or related field, or equivalent practical experience; advanced degree a plus. - 3 – 5 years of progressive software engineering experience, including significant experience in senior/lead technical roles with at least 2 years focused on high-scale Contact Center as a Service (CCaaS), CX enterprise software or Field Services enterprise software. - Extensive experience designing and building reliable workflows and integrations in major CRMs, specifically Salesforce. - Experience in AWS services (e.g., Lambda, EC2, SQS, Kinesis) and proven production experience using Terraform for infrastructure provisioning. - Experience working with REST and SOAP based web-services preferred. - Recognized subject matter expert with deep, broad technical expertise across software engineering, system design, and architecture. - Demonstrated track record of designing and delivering large-scale, distributed, and highly available systems. - Proven ability to influence technical direction and decision-making at an organizational (not just team) level. - Strong expertise in agile methodologies, SAFe/PI planning, and scaled agile delivery models. - Exceptional communication and executive presence; able to translate complex technical concepts for both technical and non-technical audiences, including senior leadership. - Demonstrated success mentoring and developing engineering talent, including senior engineers and tech leads. - Experience driving enterprise architecture standards, technology governance, or engineering best-practice initiatives. - Strong business acumen with the ability to connect technical strategy to organizational and business outcomes. - May require a background check due to job duties requiring routine access to DIRECTV and DIRECTV customer’s proprietary data. - Qualified applicants with arrest and conviction will be considered for employment in accordance with local ordinances and state law. - This is a remote position that can be located anywhere in the United States, with the exception of Alaska. Now Pay section: we need to include the salary range info. The posting includes: "A career with us comes with big rewards: DIRECTV's compensation structure is designed to be market-competitive and fully supports efforts to attract and retain employees. It is the company's policy to offer pay that is competitive with other employers in the local market. Our salary ranges are determined by role, level, and location. The Base Salary range displayed below reflects the minimum and maximum target salary for each of DIRECTV's 4 (four) US Labor Market Zones. Within the range, individual pay is determined by work location and additional factors, including job-related skills, experience, and relevant education or training. DIRECTV WAGE ZONES: $134,363 - $244,036 Low (N1): $134,363 - $201,595 Mid (N2): $141,435 - $212,205 High (N3): $155,579 - $233,426 Top (N4): $162,650 - $244,036 Click HERE to review information on some of the largest Designated Market Areas (DMAs). Your recruiter can share more about the specific salary range for your preferred location during the hiring process. Please note that the salary ranges reflect base salary only and do not include bonus or benefits - when you consider all of these together, it represents a pretty impressive total compensation package." We need to preserve all substantive information. So we should include that paragraph(s) under Pay section. Possibly also include the note about base salary only etc. We should not include the "Click HERE" link as it's likely a navigation/link; but it's part of the content. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "Click HERE" is a link; could be considered navigation. Might be safe to omit? But it's part of the salary info. However it's a link to DMAs; could be considered navigation. The instruction says remove navigation boilerplate. So we can omit the "Click HERE..." sentence. Also "Your recruiter can share more about the specific salary range for your preferred location during the hiring process." That's substantive? It's about process; maybe we can keep as it's about salary range. It's not boilerplate. Keep. We also need to omit "Apply today!" and Fair Chance Ordinance notice etc. Thus final HTML:

  About the role

  ... (the description)

  Responsibilities

  • ... each bullet

  Requirements

  • ... each bullet

  Pay

  ... (the compensation paragraph(s) without the Click HERE line)

  We need to ensure we don't include any duplicated lines. Also ensure we don't include any EEO etc. The posting had "Qualified applicants with arrest and conviction will be considered for employment in accordance with local ordinances and state law." That's actually an EEO-like statement but it's about fair chance. Might be considered EEO/equal-opportunity boilerplate. The instruction says remove EEO/equal-opportunity/scam-warning boilerplate. So we should remove that line. Also "May require a background check due to job duties requiring routine access to DIRECTV and DIRECTV customer’s proprietary data." That's not EEO; it's a requirement. Keep.