Director of Software Engineering

We need to output HTML fragment with sections: About the role? The posting includes "A bit about us:" and "Why join us?" and "Job Details". We need headings:

for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use

• for any list of duties/requirements/benefits, and

  for prose. Do NOT repeat the job title as a heading. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. We need to decide which sections to include based on content. Content: - Salary: $150,000 - $170,000 per year => Pay section. - Hybrid Schedule: 2 days/week in the Denver-area office => Schedule section. - Benefits: listed under "Why join us?" includes 401(k) with Company Match, Comprehensive Benefits: Company-subsidized Medical, Dental & Vision (incl. $100/mo employer HSA contribution); company-paid Short-Term & Long-Term Disability and Life Insurance (1x salary up to $250K); Pet Insurance Flexible PTO & Paid Holidays Training & Tuition Assistance Program Modern Tech & AI-Forward Culture: Build on .NET, React, Azure, and Power Platform, with AI development tools used daily to accelerate engineering work Clear Growth Path: Defined runway to Senior Director and VP of Engineering as the function scales Thus Benefits section. - About the role: "A bit about us:" gives description of company. Could be "About the role" or "About the company". The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can have About the role (maybe summarizing the role). The posting includes "Job Details KEY RESPONSIBILITIES & DUTIES" which is responsibilities. Also "QUALIFICATIONS (Needed)" which is qualifications. Also "Nice-to-have:" which could be skills? But we can treat as Skills or Qualifications. We need to avoid duplication and boilerplate. Remove application instructions like "Easy Apply now by clicking the "Easy Apply" button". Also remove "Want to learn more about this role and Jobot? Click our Jobot logo and follow our LinkedIn page!" repeated at start and end. Remove EEO boilerplate etc. We need to preserve all substantive information: responsibilities list, qualifications list, benefits list, pay, schedule, about us description, maybe growth path, tech stack. We need to format using

  headings and

  • for lists,

    for prose. We should not create sections with filler. So include sections: About the role (maybe from "A bit about us:"), Responsibilities (from KEY RESPONSIBILITIES & DUTIES), Qualifications (from QUALIFICATIONS (Needed) plus maybe nice-to-have as Skills?), Benefits, Pay, Schedule. We could also include Skills section if we want to separate nice-to-have. But we can incorporate nice-to-have into Qualifications or Skills. The instruction says prefer a few substantive sections over many thin ones. So maybe combine Qualifications and Skills into one Qualifications section, listing both required and nice-to-have as bullet points. But we need to preserve all substantive information; we can list required qualifications and nice-to-have as separate bullet points under Qualifications. We need to avoid duplication: The posting repeats "Want to learn more about this role and Jobot? Click our Jobot logo and follow our LinkedIn page!" at start and end; we drop those. Also drop "Jobot is an Equal Opportunity Employer..." etc. Also drop "Interested in hearing more? Easy Apply now by clicking the "Easy Apply" button." etc. Also drop "Sometimes Jobot is required to perform background checks..." etc. Also drop legal notices about privacy, AI-generated calls etc. Now construct HTML. We'll start with

    About the role

    then

    containing the company description: "Founded over a decade ago and based in the Denver metro area, we are a privately held, technology-first storage and logistics platform serving multi-location and enterprise businesses nationwide. Backed by private equity and growing fast, we pair enterprise-grade, cloud-based software with a national network of storage and fulfillment partners to help our customers centralize, simplify, and scale how they manage assets across the country. We're a solutions-driven, accountability-focused team building modern software that turns a traditionally fragmented industry into a seamless, data-driven experience." Then maybe also include growth path and tech culture? Those are under "Why join us?" but could be part of About the role or Benefits? Actually "Why join us?" includes benefits and also growth path and tech culture. We could put growth path and tech culture under About the role as well, but maybe better to keep Benefits separate for benefits only, and put growth path and tech culture under About the role or maybe a separate section like "What we offer"? But instruction only allows certain headings; we could put growth path and tech culture under About the role as prose. Alternatively, we could create a section "About the role" for role description, and then "Why join us?" could be Benefits plus other perks. But we already have Benefits section for tangible benefits; growth path and tech culture could be part of About the role or maybe a separate "What we offer" but not allowed. So we incorporate them into About the role. Thus About the role paragraph could include company description, growth path, tech culture. But we need to avoid too long paragraph? It's okay. Next Responsibilities:

    Responsibilities

    then
    • each duty. List from "KEY RESPONSIBILITIES & DUTIES": - Own the vision, strategy, and execution for the software engineering function; align technical roadmaps with company objectives and OKRs - Partner with the CTO and Product leadership to shape the technology roadmap and sequence delivery priorities - Lead architecture decisions across modern cloud-based applications — .NET/C# backends, React/TypeScript frontends, RESTful and event-driven services, Power Platform, and Azure infrastructure - Establish and enforce engineering standards: code quality, security, automated testing, and documentation - Build, mentor, and scale a high-performing team of full-time engineers and contractors; manage performance and develop future technical leaders - Own end-to-end delivery across agile teams — sprint planning, backlog refinement, estimation, and capacity planning — for predictable, high-quality releases - Partner with DevOps on Azure environments, CI/CD pipelines, observability, and production readiness - Balance new feature delivery against reliability, performance, and technical-debt reduction - Own engineering operational metrics (reliability, performance, security) and drive continuous improvement - Partner cross-functionally with Product, Data, Operations, and Customer Success to translate priorities into execution - Use AI development tools daily to accelerate design, code review, planning, and documentation, while operating as the experienced human in the loop and setting responsible-use guardrails for the team - Deliver written weekly leadership updates and lead a monthly engineering KPI review We need to keep the exact phrasing? Preserve all substantive information; do not invent or summarize away detail. So we should keep the bullet points as they are, maybe trimmed of extra dashes? Keep as is. Next Qualifications:

      Qualifications

      then
      • for required qualifications and nice-to-have. Required qualifications from "QUALIFICATIONS (Needed)": - Bachelor's degree in Computer Science, Software Engineering, or related field, or equivalent experience - Minimum 10+ years of professional software development experience, including at least 3–5 years leading or managing engineering teams - Strong expertise in .NET / C#, including ASP.NET Core and Web APIs - Strong experience with modern frontend development using React and TypeScript - Solid understanding of RESTful API design, authentication, authorization, and security best practices - Experience architecting scalable systems with relational databases (SQL Server) and data modeling - Experience delivering software in cloud environments — Azure preferred - Familiarity with CI/CD pipelines and modern DevOps practices - Proven ability to build, mentor, and scale high-performing engineering teams - Hands-on experience using AI tools (e.g., Microsoft Copilot) to accelerate engineering work, with the judgment to use them responsibly - Comfort operating in a dynamic, high-growth, PE-backed environment Nice-to-have: - B2B SaaS / logistics / operations-tech background - Azure App Services, Functions, Service Bus - microservices & modular monolith architectures - Power Platform integration with custom code We'll list them as bullet points; maybe separate with a comment? But we can just list all; it's fine. Next Benefits:

        Benefits

        then
        • each benefit. From "Why join us?": - 401(k) with Company Match - Comprehensive Benefits: Company-subsidized Medical, Dental & Vision (incl. $100/mo employer HSA contribution) - company-paid Short-Term & Long-Term Disability and Life Insurance (1x salary up to $250K) - Pet Insurance - Flexible PTO & Paid Holidays - Training & Tuition Assistance Program - Modern Tech & AI-Forward Culture: Build on .NET, React, Azure, and Power Platform, with AI development tools used daily to accelerate engineering work - Clear Growth Path: Defined runway to Senior Director and VP of Engineering as the function scales But note that "Modern Tech & AI-Forward Culture" and "Clear Growth Path" are more like cultural perks; but they are under Why join us. We could include them in Benefits section as bullet points. However, the instruction says only create Benefits section if posting actually states them. It does state them, so okay. But we might want to avoid duplication with About the role if we already included growth path and tech culture there. To avoid duplication, we could keep About the role focused on company description only, and put growth path and tech culture in Benefits. That seems reasonable. Thus About the role paragraph only includes company description (the "A bit about us:"). Then Benefits includes the list of benefits plus growth path and tech culture. Now Pay:

          Pay

          then

          Salary: $150,000 - $170,000 per year

          Schedule:

          Schedule

          then

          Hybrid Schedule: 2 days/week in the Denver-area office

          We need to ensure we don't include any filler like "commensurate with experience". Not present. Now we need to output only HTML fragment, no /, no markdown fences. Let's craft. We'll need to escape any HTML special characters? The text includes ampersands (&) and maybe em dashes — we can keep as is; they are okay in HTML but better to use & for & and — maybe keep as — (em dash) which is okay. But to be safe, we can replace & with &. The text includes "C#" which is fine. ".NET/C#" includes slash. "ASP.NET Core". "React/TypeScript". "Power Platform". "Azure". "CI/CD". "PE-backed". We'll keep as is. But there are ampersands in "Company-subsidized Medical,