Principal Software Engineer

for prose. We need to decide which sections to include: - About the role: The paragraph starting "The job You will join a team..." etc. That's description of role. Could be About the role. - Responsibilities: The list under "Key responsibilities:" bullet points. - Requirements: The "Essential requirements:" list. - Qualifications: maybe combine essential requirements? But we have both essential requirements and desired skills. Could treat essential as Requirements, desired as Skills? Or Qualifications could be education etc. The posting says "Bachelor’s in computer science or related degree" under essential requirements. That's qualification. Could put that in Qualifications. But we must not duplicate. Let's map: Essential requirements list includes: Bachelor’s in computer science or related degree; Strong background in AI/ML concepts...; Proficiency with Angular; Proficiency with multiple software dev languages including TypeScript, JavaScript, HTML5, CSS3; Proficiency with application development using C#; Experience creating self-contained, reusable, testable modules; Experience working in agile; Experience with debugging, diagnostics, unit testing, leveraging AI tools; Excellent analytical skills; Professional and precise communication skills. Desired skills and competencies list includes: Demonstrated experience driving AI adoption; Hands-on experience applying HVE concepts; Industrial automation domain knowledge; Expert-level proficiency in Angular; Strong knowledge of C# and advanced topics in .NET Framework and .NET Core; Experience with Microsoft Azure, including AI services, deployment, provisioning, high availability; Knowledge of UI automation using Playwright, Cypress, Storybook; Knowledge of RESTful services and Web APIs. We could have sections: Requirements (essential), Skills (desired). Qualifications maybe education only? But we could put education in Requirements as well. However instructions: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have multiple sections. We need to decide what goes where. We have Pay: Salary Range given: $142,100.00 - $271,300.00 with explanation. That's specific, so include Pay section. Schedule: Not explicitly given. There's hybrid working description: "Most roles are based at a local AVEVA office, with an expectation of being on-site 50% of your working hours". That's schedule info (hybrid). Could be Schedule section. It says "The working arrangement for this position will be confirmed during the hiring process." That's somewhat vague but we have some detail. Should we include Schedule? The rule: never create Pay/Schedule/Benefits sections unless the posting actually states them. The posting does state hybrid working expectation, so we can include Schedule. Benefits: The posting includes "USA Benefits include: Flex work hours, 20 days PTO rising to 25 with service, three paid volunteering days, primary and secondary parental leave, well-being support, medical, dental, vision, and 401K." Also note about multiple countries. That's specific benefits. So include Benefits. Now About the role: The paragraph after "The job". Could be About the role. Responsibilities: list under Key responsibilities. Requirements: essential requirements list. Qualifications: maybe we could put education (Bachelor's) here, but it's already in essential requirements. To avoid duplication, maybe we treat essential requirements as Requirements, and desired skills as Skills. Qualifications could be left out if no distinct content besides what's already covered. But we need to include a section only when posting has real specific content for it. If we don't have distinct qualifications beyond essential requirements, we could omit Qualifications. However the heading list includes Qualifications as an example; we are not required to include all. So we can omit Qualifications if no distinct content. Skills: desired skills list. Now we need to ensure we preserve all substantive information. Let's extract each piece. First, About the role paragraph: "You will join a team of Architects responsible for designing innovative, AI-enabled solutions to solve customer problems, with a strong emphasis on encouraging AI adoption across teams, particularly in support of Hypervelocity Engineering (HVE) initiatives. In this role, you will collaborate with tech leads and cross-functional partners to embed AI-driven approaches into solution design, development, and delivery. You will also play a crucial part in troubleshooting complex issues, mentoring junior team members, and championing modern engineering practices that leverage AI to improve quality, velocity, and customer outcomes." We need to keep that as prose in

. Responsibilities list: each bullet after "Key responsibilities:": - Responsible for design, development, and hands-on implementation of Microsoft Azure cloud solutions using Angular, C#, and AI-enabled services - Act as a technical leader and advocate for AI adoption across teams, identifying opportunities to apply AI/ML to accelerate delivery, improve engineering throughput, and drive measurable impact in alignment with Hypervelocity Engineering (HVE) principles - Serve as a Microsoft Azure and AI technical resource in the team’s efforts to determine and address the needs of our customers - Participate in planning and implementation of intelligent solutions for our cloud platform, incorporating AI-assisted development, automation, and observability where appropriate - Work closely with architects and engineers to recommend and design infrastructure, database, data storage, and AI solutions that reflect our clients’ business needs, security, and service level requirements - Collaborate with application and infrastructure teams to conduct proof of concepts (POCs) and deliver production-ready, AI-enhanced designs in Microsoft Azure - Align solutions with standards and best practices while promoting responsible, scalable, and repeatable AI usage across engineering teams - Establish strong and lasting relationships with key stakeholders and influence adoption of AI-driven and HVE-aligned engineering practices - Contribute to the development of internal best practices, including AI-enabled development patterns and Hypervelocity Engineering guidance We need to preserve each as

• for any list of duties/requirements/benefits. Benefits is a list; we could turn into
  • . However the sentence includes prose. Could split: we could keep as

    with list? But rule: Use

    • for any list of duties/requirements/benefits. So we should make a list. Let's extract items: - Flex work hours - 20 days PTO rising to 25 with service - three paid volunteering days - primary and secondary parental leave - well-being support - medical - dental - vision - 401K Also note the sentence about multiple countries etc. That's extra prose; we could keep as

      after list. Pay: Salary Range: $142,100.00 - $271,300.00 with explanation: "This pay range represents the minimum and maximum compensation that the position offers, and final compensation can vary within the range depending on work location, job experience, skills, and relevant educational attainment and/or training." We should keep as

      . Schedule: Hybrid working description: "We work in a hybrid way at AVEVA. Most roles are based at a local AVEVA office, with an expectation of being on-site 50% of your working hours to support collaboration and connection. Some positions are fully office-based depending on the nature of the work, and certain roles that support specific customers or markets may be remote. The working arrangement for this position will be confirmed during the hiring process." We should keep as

      . Now we must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. So we need to cut out sections like "Hiring process", "About AVEVA", background check, EEO, etc. Also remove "Find out more:" links? Those are likely boilerplate/application instructions. We should remove them. Also remove "Interested? Great! Get started by submitting your cover letter and CV through our application portal." etc. Also remove "AVEVA requires all successful applicants to undergo and pass a drug screening..." etc. Also remove "AVEVA is an Equal Opportunity Employer..." etc. Also remove "About AVEVA" paragraph. Also remove "R&D at AVEVA" paragraph? That is substantive about company but maybe not required sections; but it's not about role specifics. The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. However the "R&D at AVEVA" paragraph is about the company, not the role. Is that substantive information about the job? It's general company info. Might be considered boilerplate? Not exactly. But the instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. It doesn't say to remove company overview. However the sections we are to output are limited to those headings. If we include company overview, where would it go? Not in any of the allowed headings. So we likely should omit it because it doesn't fit into those sections. The instruction: "Output ONLY the HTML fragment — no /, no markdown code fences." It didn't say we must include all info; we