Engineering Manager

We need to output HTML fragment with sections: About the role? Actually the posting includes "About Customer.io", "What We Value", "What You'll Do", "What We're Looking For", "Compensation & Benefits", "Our Process". The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We need to map sections accordingly. We should not repeat job title. We need to preserve all substantive info, remove boilerplate like cookie/navigation/legal/EEO etc. There's none. Also remove application instructions? The "Our Process" includes application steps; but instruction says remove application instructions. So we should drop the "Our Process" section entirely. Also we should not include Pay/Schedule/Benefits unless posting actually states them. Compensation & Benefits includes salary range and benefits, so we should include a Benefits section (maybe also Pay). The instruction: use headings like Benefits, Pay, Schedule. We have compensation details, so we can include a Pay section with salary range, and a Benefits section with benefits list. Or combine? It says prefer a few substantive sections over many thin ones. Could combine Pay and Benefits into one "Compensation & Benefits" but headings must be from list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We could use Benefits and Pay separate. But we might also have About the role (maybe "About Customer.io") as About the role? The instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should map content to those headings where appropriate. We have: - About Customer.io: description of company. Could map to "About the role"? Actually About the role is about the job, but we have About Customer.io. Could use "About the role" heading and put company description there? Might be okay. But we also have "What We Value" (ownership, AI-first mindset etc.) Could map to "Skills" or "Qualifications"? Might be better to use "Qualifications" for what we're looking for, "Responsibilities" for what you'll do, "Skills" for what we value? However we need to preserve all substantive info. Let's think: The posting includes: - About Customer.io (company overview) - What We Value (ownership, leaders who can do both, drive to execute through resistance, AI-first mindset, healthy skepticism) - What You'll Do (responsibilities) - What We're Looking For (requirements/qualifications) - Compensation & Benefits (pay and benefits) - Our Process (application steps) -> remove. We need to output sections only when posting has real specific content. So we will include: - About the role (maybe combine About Customer.io and What We Value? But better separate: About the role could be company overview; Responsibilities could be What You'll Do; Requirements could be What We're Looking For; Benefits could be benefits list; Pay could be salary range. We also have "What We Value" which is like skills/qualities. Could be placed under Skills or Qualifications. But we already have Requirements for What We're Looking For. Could merge values into Skills section. Thus sections:

About the role

-> company overview (About Customer.io)

Responsibilities

-> What You'll Do (list)

Skills

-> What We Value (list of values/qualities)

Requirements

-> What We're Looking For (list)

Pay

-> salary range

Benefits

-> benefits list We must not include empty sections. All have content. We need to use

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

  for prose. Thus: - About the role: prose (maybe a couple paragraphs). Use

  . - Responsibilities: list of duties (the bullet points under What You'll Do). Use

  • . - Skills: list of values (What We Value). Use
    • . - Requirements: list (What We're Looking For). Use
      • . - Pay: prose with salary range. Use

        . - Benefits: list of benefits. Use

        • . We must not include any extra headings like "About Customer.io". Use only the allowed headings. We must not include job ID etc. Not present. We must not include application instructions (Our Process). Remove. We must not add markdown fences. Output only HTML fragment. Let's extract content precisely. About Customer.io paragraph: "Over 9,000 companies—from scrappy startups to global brands—use our platform to send billions of emails, push notifications, in-app messages, and SMS every day. Customer.io powers automated communication that people actually want to receive. We help teams send smarter, more relevant messages using real-time behavioral data—what people do or don't do inside a web or mobile app. Under the hood: Go, React, and AI help us ship fast and scale with confidence." That's the prose. What We Value bullet points (as paragraphs): - Ownership. You set direction and see initiatives through. You create clarity when things are murky and set the path forward rather than waiting for one to be defined, and you're motivated by impact—not just intention. You hold yourself and your team accountable to shipping, not just staying busy. - Leaders who can do both. You operate at the strategic level and stay close to the technical work. You can align stakeholders on a plan and earn your engineers' respect in the same day—you don't choose between vision and execution, you hold both. - A drive to execute through resistance. Competing priorities, skeptical stakeholders, tired teams—you've moved work forward anyway. You name the resistance, make the call, and own the milestones and the misses. - An AI-first mindset. AI is central to how you build and how you lead your team to build. You have a real, concrete point of view on AI-native development, you use agentic tooling yourself, and you bring it into how your squad operates. A healthy skepticism for "the way things are done." You bring rigor and pragmatism. Best practices matter—but never more than forward motion. You know when to build, when to buy, and when to wait—and you're comfortable making the call with incomplete information, then adjusting as you learn. We could split each as separate
        • items. What You'll Do bullet points: - Care deeply about our customers and their outcomes - Lead your squad to deliver real customer value by owning projects end to end—from planning through delivery, quality, and follow-through - Drive execution: set milestones, keep work moving through ambiguity and competing priorities, and ship in small, observable increments rather than waiting for a release window - Make confident decisions when the path isn't obvious, and lead your team through them - Set the operating rhythm that helps your team move fastest, rather than defaulting to ceremony for its own sake - Ensure your squad's solutions are scalable, architecturally sound, flexible, and secure, with strong peer-review, QA, documentation, deployment, logging, and monitoring practices - Stay close to the work—jump into design reviews, architecture calls, and incidents rather than watching from a distance - Provide direct, timely, and specific coaching, and create meaningful development opportunities for your direct reports - Hire, onboard, and manage performance so the right people are in place to hit your squad's goals - Bring an AI-native perspective—use AI tools to accelerate the team's velocity and help everyone prototype faster and ship smarter - Partner across engineering and other departments to align efforts with customer success, and reach higher when our customers are having a bad day What We're Looking For bullet points: - 3+ years managing engineers at a SaaS company (B2B or B2C), ideally early-to-mid-stage - A track record of driving execution—concrete delivery outcomes with milestones, dates, and "I drove" ownership, especially in complex or fast-moving environments - A strong technical background—you can hold your own in architecture conversations and design reviews, represent your squad's technical choices across the company, and you've shipped real work recently enough to stay credible - Comfort operating with high autonomy and little prescribed structure—you create your own clarity and make difficult tradeoffs between competing priorities - Demonstrated AI-native leadership—not just personal fluency, but bringing AI-first practices into how your team builds - Experience building high-performing, inclusive, and collaborative teams - Clear, concise, and direct communication, both verbal and written Compensation & Benefits: - Starting salary for this role is $185,000-$215,000 USD (or equivalent in local currency) depending on experience and subject to market rate adjustment. - We know our people are what make us great, and we're committed to taking great care of them. Our inclusive benefits package supports your well-being and growth, including 100% coverage of medical, dental, vision, mental health, and supplemental insurance premiums for you and your family. We also offer 16 weeks paid parental leave, unlimited PTO, stipends for remote work and wellness, a professional development budget, and more. See full benefits here → (but we should remove the link? It's part of benefits; we can keep the text but maybe drop the "See full benefits here →" as it's a navigation link? It's not boilerplate but it's a link; we could keep but it's not substantive. Safer to omit the link phrase. We'll keep the benefits description.) Thus benefits list: - 100% coverage of medical, dental, vision, mental health, and supplemental insurance premiums for you and your family - 16 weeks paid parental leave - Unlimited PTO - Stipends for remote work and wellness - Professional development budget - (and more) but we can keep "and more" as part of prose? Might be vague. Better to list the specific items; we can include "and more" as part of prose but it's vague. We'll keep as a bullet: "and more" maybe not needed. We'll just list the specific ones. Pay: prose with salary range. Now construct HTML. We'll output:

          About the role

          Over 9,000 companies—from scrappy startups to global brands—use our platform to send billions of emails, push notifications, in-app messages, and SMS every day. Customer.io powers automated communication that people actually want to receive. We help teams send smarter, more relevant messages using real-time behavioral data—what people do or don't do inside a web or mobile app. Under the hood: Go, React, and AI help us ship fast and scale with confidence.

          Responsibilities

          • Care deeply about our customers and their outcomes
          • Lead your squad to deliver real customer value by owning projects end to end—from planning through delivery, quality, and follow-through
          • Drive execution: set milestones, keep work moving through ambiguity and competing priorities, and ship in small, observable increments rather than waiting for a release window
          • Make confident decisions when the path isn't obvious, and lead your team through them
          • Set the operating rhythm that helps your team move fastest, rather than defaulting to ceremony for its own sake
          • Ensure your squad's solutions are scalable, architecturally sound, flexible, and secure, with strong peer-review, QA, documentation, deployment, logging, and monitoring practices
          • Stay close to the work—jump into design reviews, architecture calls, and incidents rather than watching from a distance
          • Provide direct, timely, and specific coaching, and create meaningful development opportunities for your direct reports
          • Hire, onboard, and manage performance so the right people are in place to hit your squad's goals
          • Bring an