Technical Delivery Manager, Installation & Maintenance

We need to output HTML fragment with sections: About the role (but note "About The Role" heading), Responsibilities (maybe "What You'll Do"), Requirements (maybe "Required Qualifications"), Qualifications (maybe "Preferred Qualifications"), Skills (maybe not separate), Benefits, Pay, Schedule (if present). The posting includes "Base salary: $155,000-$180,000 per year." That's Pay. Benefits Overview present. Schedule not mentioned (no schedule). So we should not include Schedule section. We need to use

for section headings. Use

• for any list of duties/requirements/benefits. Use

  for prose. We must preserve all substantive info, not invent or summarize away detail. Remove boilerplate: About Legence paragraph, location, employment type maybe? Actually location and employment type are metadata; we can fold minor metadata into short

  or drop it. The instruction: "Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it." So we can include a short paragraph with location and employment type maybe. We need sections only when posting has real specific content. So we will have sections: About the Role (maybe heading "About the Role"), Responsibilities (maybe "What You'll Do"), Requirements (maybe "Required Qualifications"), Qualifications (maybe "Preferred Qualifications"), Benefits, Pay. Possibly also Skills? Not needed. We need to convert lists: Under Responsibilities, there are bullet-like paragraphs with headings: Build and Ship, Lead the Technical Team, Engage Stakeholders, Drive Delivery (Lightweight). Each has sub-bullets. We can treat each main heading as maybe a

  ? But instruction only says use

  for section headings. For subheadings we can just use

  with bold? But we should preserve content; we can use

  • for each duty. Could flatten: each bullet point as
  • . Might lose grouping but okay. However we need to preserve all substantive info; grouping not required. We'll just list each duty as
  • . For sub-bullets we can also nest
    . Simplify: For each major duty, we can have
    • containing the heading as and then a nested
      for subpoints. Similarly for Required Qualifications: list items. Preferred Qualifications: list. Benefits: list. Pay: just a paragraph. We need to avoid boilerplate like EEO, etc. Let's extract content. About Legence paragraph: we can drop as boilerplate? It's company description; maybe not required but it's substantive? The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." About Legence is not boilerplate but maybe considered company overview; could keep? It's not a section heading; we could include as a short

      before sections. It's not prohibited. We'll keep a brief paragraph. Location and employment type: "Location: Any Legence location, with remote option Employment Type: Full-Time". We'll fold into a short

      . Now sections. About The Role: we have a paragraph after that heading: "Legence is seeking a Technical Delivery Manager who leads by building. This is a player- coach role in the fullest sense: you'll spend real time in the codebase — designing solutions, writing code, reviewing pull requests, and shipping — while leading a team of engineers and serving as the trusted technical voice for business stakeholders. You keep delivery on track not by administering process, but by understanding the work deeply enough to make the right calls, grow your team, and jump in yourself when it matters. The ideal candidate can present a solution approach to executives in the morning and implement a tricky integration in the afternoon. Deep, practical experience with AI-driven software development and enterprise systems is a must." We'll put that as

      under

      About the Role

      . Responsibilities: Use "What You'll Do" heading. We'll treat as section heading

      What You'll Do

      (or Responsibilities). The instruction says use

      for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should use "Responsibilities" as heading. We'll put

      Responsibilities

      and then list. We need to capture all bullet points. Let's extract bullet points from "What You'll Do": - Build and Ship - Design and implement solutions hands-on: services, integrations, automation, and prototypes — you write production code, not just review it - Own technical decisions on your initiatives: architecture, build-vs-buy, tooling, and integration approach - Set the technical bar through code reviews, pairing, and example — engineers should learn from working alongside you - Lead AI-driven development in practice: build with AI coding assistants and agentic workflows (e.g., Claude Code, GitHub Copilot), integrate LLM APIs into products and internal tools, and show the team how to get real leverage from these tools safely - Ensure solutions integrate cleanly with enterprise systems — ERP/CRM, identity, data platforms, cloud infrastructure — and hold up on security, scalability, and maintainability - Lead the Technical Team - Lead a team of engineers day to day: set direction, assign ownership, and keep the team focused on the highest-value work - Grow engineers through hands-on mentorship — pairing, design discussions, and honest, specific feedback rather than annual-review platitudes - Build a strong engineering culture: high standards for code quality and testing, healthy debate on design, and shared ownership of outcomes - Shape the team itself— participate in hiring, onboard new engineers, and develop senior engineers into technical leaders - Shield the team from noise and churn; absorb ambiguity from stakeholders and hand engineers clear, well-framed problems - Foster effective adoption of AI development tools across the team, establishing shared practices for where they accelerate work and where human judgment stays in the loop - Engage Stakeholders - Act as the primary technical counterpart for business stakeholders and product owners - Translate business goals directly into working solutions — shorten the distance between "what we need" and "here it is" with prototypes and demos rather than documents - Communicate progress, risks, and trade-offs in plain language; earn trust by showing working software early and often - Push back constructively when a request doesn't make technical or business sense, and bring better options - Drive Delivery (Lightweight) - Keep initiatives moving end to end — scope, sequence, ship — with just enough structure to stay predictable - Remove blockers fast, usually by solving the underlying technical problem rather than escalating it - Coordinate dependencies across teams and vendors pragmatically; favor working agreements over heavyweight process - Use metrics that matter (cycle time, quality, outcomes delivered) instead of ceremony for its own sake We'll represent each top bullet as
      • with heading and nested
        . Now Required Qualifications: heading "Required Qualifications". Then paragraph "What You Bring" then list items: - 7+ years building software, including recent, sustained hands-on coding — this is a technical role first - Strong command of at least one modern language (e.g., Python, C#, TypeScript/JavaScript, Java) and comfort picking up others; able to design, build, debug, and ship production systems - Demonstrated experience with AI-driven software development: daily use of AI coding assistants, building with LLM APIs, prompt/context engineering, or shipping Al-augmented features and workflows - Solid experience with enterprise systems and integration patterns: ERP/CRM platforms, REST/event-driven APIs and middleware, identity and access management, cloud platforms (Azure, AWS, or GCP), and data pipelines - Track record of leading delivery of enterprise software initiatives while remaining a hands-on contributor - Experience leading and growing an engineering team (or acting as tech lead for one — mentoring, technical direction-setting, and building team culture, without stepping away from the code - Excellent communication skills — able to explain technical decisions to executives, negotiate scope with stakeholders, and mentor engineers - Working fluency with modern engineering practices: CI/CD, DevOps, testing, and iterative delivery Note there is a line break missing closing parenthesis but we keep as is. Preferred Qualifications: heading "Preferred Qualifications". Then list: - Experience in the built environment, energy, engineering services, or a related industry - Familiarity with MCP, agentic AI systems, or deploying LLM-based features to production - Hands-on integration work with platforms such as Microsoft 365, Salesforce, ServiceNow, or similar enterprise ecosystems - Bachelor's degree in Computer Science, Engineering, or related field (or equivalent experience) Who You Are: This is more traits; could be considered part of Qualifications? But we could treat as a separate section maybe "Who You Are". However instruction only lists certain headings; but we can include if substantive. It's a list of traits. We could include as
        under a heading "Who You Are". But not in the list of allowed headings; but we can still use

        for any section heading; they gave examples but not exclusive. Safer to include as a section maybe "Who You Are". We'll include. Benefits: heading "Benefits". Then list: - 401(k) Plan with Company Match: Currently match contributions dollar-for-dollar up to 4% of eligible pay; immediate vesting. - Health & Welfare Benefits: Employer provided medical, dental, vision, prescription drug, Employee Assistance Program and accident & illness coverage. - Life and Disability Insurance: Employer provided basic life insurance and AD&D valued at 50K coverage amount with the option for voluntary buy up for additional coverage. - Time Off: Flexible non-accrual vacation; company holidays per policy. (For California employees, this is separate from California paid sick leave, if applicable.) - Expenses: Business travel and related expenses reimbursed per company policy. - Reasonable Accommodations: If you need assistance or accommodations during the application or interview process, please contact us at ta@wearelegence.com or your dedicated recruiter with the job title and requisition number. But note "Reasonable Accommodations" maybe considered application instructions? It's contact for accommodations; maybe we should keep as it's substantive. However instruction says remove application instructions. This is about accommodations, not how to apply. Might be okay to keep. We'll keep. Pay: heading "Pay". Then paragraph: Base salary: $155,000-$180,000 per year. This role may be eligible for participation in discretionary bonus plan based on company and individual performance. Notes: Actual compensation will be based on skills, experience, and work location, and may vary from the posted range. Hiring bonuses (and any guaranteed year-end bonuses) are administered under Company policy and are not earned until all stated conditions are met (e.g., active employment on the payment date). This posting reflects compensation at the time of posting and may be updated. We should keep all that. Schedule: not present, so omit. Now we need to output only HTML fragment, no /, no markdown. We'll start with a

        for company description? Maybe we include About Legence paragraph as

        . Then location paragraph. Let's craft. We'll need to escape any HTML special characters like &, <, >. The text includes em dashes — which is okay as is. We'll keep. We'll produce:

        About Legence Legence (Nasdaq: LGN) is a leading provider of engineering, consulting, installation, and maintenance services for mission-critical systems in buildings. The company specializes in designing, fabricating, and installing complex HVAC, process piping, and other mechanical, electrical, and plumbing