VP of Engineering

We need to output HTML fragment with sections: About the role? The posting includes "THE ROLE" and "COMPENSATION", "BENEFITS", "WHY ALBERT?" maybe not needed but could be a section? The instructions: use

for section headings (e.g. 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: The posting includes "THE ROLE" (responsibilities), "COMPENSATION", "BENEFITS", "WHY ALBERT?" maybe not needed but could be "About the role"? Actually "THE ROLE" is responsibilities. Could map to "Responsibilities". Also there is a description of team structure etc before "THE ROLE". That could be "About the role" or maybe "About the team". The instructions list example headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can choose appropriate. We have content: Team structure, Technologies, Product team, location, etc. That could go under "About the role" (or maybe "About the team"). Then responsibilities bullet list under "THE ROLE". That could be under "Responsibilities". Then compensation: "$180-225k + equity". That's Pay. Then benefits list: many bullet points. Then "WHY ALBERT?" could be maybe "About the company" but not in list; we could omit if not needed. The instruction says prefer a few substantive sections over many thin ones. Could combine "WHY ALBERT?" into "About the role" or maybe omit. But we must preserve ALL substantive information; we cannot omit substantive info. So we need to include that content somewhere. Could create a section "About Albert" but not in allowed headings? The instruction says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says e.g., not exclusive list. So we can add other headings like "About Albert" if needed. But better to keep within given examples. Could put "WHY ALBERT?" under "About the role" as prose. Also "INCLUSION AT ALBERT" is EEO boilerplate; we should remove that as per instruction: remove EEO/equal-opportunity boilerplate. So we can drop that. Also "REQUIREMENTS" section: we need to include that. Could map to "Requirements". Possibly also "Qualifications". The list of requirements is substantive. We'll put under "Requirements". We also have "Skills"? Not explicitly separate; but requirements include skills. Could combine. We need to output only HTML fragment, no /, no markdown fences. We need to use

  for each section heading. Use

  • for lists. Use

    for prose. We must not repeat the job title as a heading. The job title is "VP of Engineering". Not to be used as heading. We must not put Job ID/requisition numbers as headings; none present. We need to preserve all substantive information: team structure, technologies, product team, location, responsibilities bullet list, compensation, benefits bullet list, why Albert? (culture, mission), requirements bullet list. We need to remove duplicated lines, boilerplate, navigation, etc. Already removed EEO. We need to ensure no filler placeholder text. Let's craft sections: - About the role (or About the team): include team structure, technologies, product team, location (U.S., full-time, no contractors). Could be a

    with maybe a

    for team structure? The instruction: Use
    • for any list of duties/requirements/benefits. Team structure is a list; we could use
      . Technologies also list. Product team maybe list. Location maybe prose. We'll do:

      About the role

      Albert's engineering team consists of 10 engineers: 7 frontend, 6 backend, 1 infrastructure, 1 QA, and 1 SDET. A Director manages frontend technical and people management; the VP of Engineering will directly manage all backend engineers, the SDET, and infrastructure engineers.

      • Technologies: React frontend; Elixir, Phoenix, PostgreSQL backend; AWS and Clickhouse infrastructure.
      • Product team: 3 product managers and 2 full-time product designers.
      • Work arrangement: Fully full‑time, U.S.–based; no contractors, agencies, or outsourcing.
      But note we used a
      with one item containing multiple sentences; maybe better to split: each bullet separate. Let's do:

      About the role

      Albert's engineering team consists of 10 engineers: 7 frontend, 6 backend, 1 infrastructure, 1 QA, and 1 SDET. A Director manages frontend technical and people management; the VP of Engineering will directly manage all backend engineers, the SDET, and infrastructure engineers.

      • Frontend: React
      • Backend: Elixir, Phoenix, PostgreSQL
      • Infrastructure: AWS, Clickhouse (among other technologies)
      • Product team: 3 product managers, 2 full‑time product designers
      • Work arrangement: Fully full‑time, U.S.–based; no contractors, agencies, or outsourcing
      That preserves info. Next section: Responsibilities (THE ROLE). We'll list bullet points.

      Responsibilities

      • Partner with engineering and product teams to develop and maintain technical and product roadmaps grounded in customer value.
      • Manage engineering bandwidth to ensure delivery of product and technical roadmaps.
      • Continuously improve developer experience via internal tooling improvements and tech‑stack upgrades that free the team from lower‑level work.
      • Design and implement processes and communication structures that drive velocity, quality, and accountability.
      • Manage and optimize the engineering team’s budget as it relates to hiring, infrastructure costs, and tooling; advocate for necessary resources.
      • Represent the engineering team in discussions with senior management and build strategic alignment across the organization.
      • Occasionally contribute to implementation: conducting code reviews, fixing bugs, improving developer tools, or creating proof of concepts.
      • Develop an inclusive, productive, and supportive culture that grows human capital on the engineering team:
      But we have sub-bullets under culture. Could nest? The instruction didn't forbid nested lists but we can keep as separate bullets with dash? Might be okay to keep as separate bullet points. We could create a sublist under that bullet. But to keep simple, we can make separate bullets for each culture item. Thus:
      • Develop a culture of learning and growth; coach and support the team; create opportunities for people to take on new challenges, remain engaged, and grow their skills.
      • Reduce knowledge silos and learning curves across the stack to make the team resilient to changes, turnover, and disruptions.
      • Design and implement inclusive interview processes and structures; attract and pitch exciting candidates.
      • Support team experimentation and innovation with a culture of psychological safety and first‑principles thinking.
      • Build rapport with all team members, lead performance reviews for all engineers, calibrating compensation, recognizing contributions fairly, and developing plans for continued growth.
      That covers. Next: Compensation (Pay). Use heading "Pay". The instruction includes Pay as possible heading. We'll do:

      Pay

      $180,000–$225,000 base salary plus equity.

      But we need to preserve exact phrasing: "$180-225k + equity". We'll output that. Next: Benefits. Use heading "Benefits". List bullet points. We need to include all benefits listed: - Health, dental, and vision insurance. We offer two medical plans, both through Cigna. The company’s contribution is set at the Base Plan: Albert covers 100% of the employee-only premium and 50% of the dependent premium for the Cigna OAP PPO Base Plan. If you elect the Buy-Up Plan, Albert contributes the same dollar amount it would have contributed toward the Base Plan and you pay the difference. Dental and vision are also through Cigna, with Albert covering 90% of the employee premium and 50% of the dependent premium. - Insurance concierge through Nava. Our insurance broker, Nava, will help you file claims, find doctors, and answer coverage questions. - Flexible Spending Account and Dependent Care FSA. Set aside pre-tax dollars for medical and dependent care costs. - One Medical membership. Same-day appointments, virtual care, and a real primary care relationship. - Paid parental leave. Twelve weeks of fully paid leave after one year of service. - 401(k). A fully managed plan with a 1% company match. - Flexible, guilt-free vacation. No fixed allotment and no approval theater. Most people take three to four weeks a year, and we mean it. - Half-day Fridays. Every week, year round. - A deep-work culture. Few meetings and long uninterrupted blocks, because the work we do rewards focus. - Pay that does not depend on your zip code. The same bands apply wherever you live, with raises tied to performance rather than tenure. We need to preserve all that. Could break into multiple bullets for readability but must preserve info. We'll create bullet for each benefit. Potentially combine some sentences but keep meaning. We'll do:

      Benefits

      • Health, dental, and vision insurance through Cigna (two medical plans). Albert covers 100% of employee‑only premium and 50% of dependent premium for the Base Plan; for the Buy‑Up Plan Albert contributes the same dollar amount as the Base Plan and you pay the difference. Dental and vision: Albert covers 90% of employee premium and 50% of dependent premium.
      • Insurance concierge through Nava – help filing claims, finding doctors, answering coverage questions.
      • Flexible Spending Account and Dependent Care FSA – set aside pre‑tax dollars for medical and dependent care costs.
      • One Medical membership – same‑day appointments, virtual care, real primary care relationship.
      • Paid parental leave – 12 weeks fully paid after one year of service.
      • 401(k) – fully managed plan with 1% company match.
      • Flexible, guilt‑free vacation – no fixed allotment, no approval theater; most take three to four weeks per year.
      • Half‑day Fridays – every week, year‑round.
      • Deep‑work culture – few meetings, long uninterrupted blocks to reward focus.
      • Pay that does not depend on zip code – same bands wherever you live, raises tied to performance