Staff Backend Engineer, Integrations

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. Must not include Job ID etc. Must remove boilerplate like EEO, application instructions, etc. Must preserve all substantive info. We need to parse the posting. Key sections: - About The Role: paragraph about joining Integrations team, reporting to Engineering Manager, team owns everything flowing in/out, building first-class Developer Platform, opening Vibe's full capabilities as a public API, Criteo first partner. - Three Reasons To Want This: bullet points? It's a list: "You'll be one of the most senior engineers on Integrations, setting technical direction for a team that's still small enough for one person's decisions to shape it", "You'll own the foundational architecture for a platform external partners are already building against", "AI-augmented development is the expectation here, not the experiment". This could be under Responsibilities? Actually it's reasons to want the role, could be part of About the role or separate. But we need to map to allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have "What You'll Do": list of responsibilities: Build and ship integrations (with sub-bullets), Developer Platform (sub-bullets), Reliability and scale (sub-bullets), Technical leadership (sub-bullets). That's clearly Responsibilities. Then "What You Need": list of requirements: 8+ years building production backend systems..., Strong TypeScript backend experience, Direct ownership of a major project..., AWS and Terraform experience..., high-ownership background. That's Requirements. Then "Nice to Haves": list: Third-party integrations experience..., Python/C++/Rust..., Experience designing or contributing to developer-facing platforms..., Startup experience (~300 people or fewer). That could be Qualifications or Skills. Usually "Nice to Haves" could be under Qualifications or Skills. We'll decide: Qualifications maybe for required, Skills for nice-to-haves? But we have both Requirements and Qualifications headings allowed. We could put Requirements as required, Qualifications as nice-to-haves. Or we could put Skills for technical skills. Let's see: The posting has "What You Need" (requirements) and "Nice to Haves". So we can map: - Requirements: What You Need (mandatory) - Qualifications: Nice to Haves (preferred) Skills maybe not needed; we could omit Skills if no specific skills list separate. But we have TypeScript, AWS, Terraform etc already in Requirements. Could also put Skills as a separate section for specific technical skills like TypeScript, AWS, Terraform, etc. But we already have them in Requirements; we could still include Skills if we want but risk duplication. Better to follow instruction: Prefer few substantive sections over many thin ones. So we can combine Requirements and Qualifications maybe? But we need to follow headings only when posting has real specific content. We have content for Requirements and Nice to Haves (Qualifications). So we can include both. Benefits: The posting includes "What We Offer": variable pay, hybrid flexibility, full health coverage, 401(k) matching, unlimited PTO, parental leave, annual offsite. That's Benefits. Pay: "For candidates in New York, NY, the pay range for this role is $195,000–$265,000." That's Pay. Schedule: Not explicitly mentioned; hybrid flexibility mentions 3x a week in office, but that's more about work arrangement, not schedule. Could be considered Schedule? The posting says "Hybrid flexibility. We're in NYC's Flatiron District and our team is in 3x a week." That's about office presence, not schedule like hours. Could be considered Schedule? Might be okay to include Schedule as hybrid expectation. But instruction: include section ONLY when posting has real, specific content for it. The posting does mention hybrid flexibility and 3x a week. That's specific enough for Schedule? Might be considered Work arrangement rather than schedule. However we have no explicit schedule like "full-time", "hours". I'd argue we can omit Schedule because not explicit. But we could include Schedule as "Hybrid flexibility: expected in office 3 days per week". That is specific. I'd include Schedule. About the role: we have paragraph. Now we must not include boilerplate like EEO, referral instructions, equal opportunity, etc. Also remove "Our Values", "Our Interview Process", "Equal Opportunity", "Referral Instructions". Also remove "Today, more than 12,000 brands..." etc? That's company description; maybe part of About the role? It's not about the role; it's company overview. Should we keep? The instruction: 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. The company overview is not boilerplate; it's substantive about the company. However the allowed sections are limited; we could include it under About the role as context. The About the role section currently has paragraph about joining Integrations team. We could prepend company overview as part of About the role? The instruction: About the role heading for section headings (e.g. About the role, Responsibilities...). So we can put company overview under About the role as well. That seems okay. Thus About the role will contain: - Intro about Vibe.co: Streaming TV becoming core part of performance marketing, Vibe.co platform, Audience First Streaming TV Advertising, hyper-targeted segmentation, AI-powered recommendations, real-time optimization, incrementality measurement, 12k brands, 120M+ households, Walmart acquisition, etc. - Then description of role: joining Integrations team, reporting to Engineering Manager, team owns everything flowing in/out, building first-class Developer Platform, opening Vibe's full capabilities as public API, Criteo first partner. We must not repeat job title (not given). Good. Now Responsibilities: from "What You'll Do" with subpoints. We need to format as

• for any list of duties/requirements/benefits. So each bullet list under Responsibilities should be
  • . For sub-bullets maybe nested
    . We'll keep simple: each main bullet as
    • and if subpoints we can nest. Requirements: from "What You Need": bullet list. Qualifications: from "Nice to Haves": bullet list. Benefits: from "What We Offer": bullet list. Pay: from pay range: we can put

      with the range. Schedule: from hybrid flexibility: maybe

      stating expected in office 3 days per week. We must not include markdown fences. Output only HTML fragment. Let's craft. Structure:

      About the role

      ... company overview ...

      ... role description ...

      Responsibilities

      • Build and ship integrations
        • Design and implement production-grade integrations with external platforms: CRMs, CDPs, measurement vendors, data partners
        • Own integration projects end to end, from scoping through production, with full accountability for outcomes
        • Work directly with external partners to define, validate, and evolve data contracts
      • Developer Platform
        • Drive the architecture of Vibe's public API: account, advertiser, and campaign management endpoints built to scale
        • Build the documentation, monitoring, and tooling that makes the developer experience genuinely good
        • Contribute to the MCP gateway and authentication layers that expose Vibe's capabilities externally
      • Reliability and scale
        • Find the weak points in existing pipelines and lead the rebuild
        • Set the standard for code quality on the team: your reviews move the bar, not just the diff
        • Use AI tooling to accelerate your own output and raise the team's
      • Technical leadership
        • Set engineering norms and technical direction as the Integrations team grows
        • Weigh in on architecture decisions across the team, not just your own projects
        • Partner with the Engineering Manager on technical direction and hiring calibration

      Requirements

      • 8+ years building production backend systems: APIs, data pipelines, distributed services at scale
      • Strong TypeScript backend experience
      • Direct ownership of a major project, start to finish, not just a contributor role on someone else's
      • AWS and Terraform experience, with real architectural decision-making, not just implementation
      • A high-ownership background: startup, scale-up, or anywhere you couldn't hand the hard problems to someone else

      Qualifications

      • Third-party integrations experience: ETL, webhooks, REST/GraphQL APIs
      • Python/C++/Rust, alongside your TS work
      • Experience designing or contributing to developer-facing platforms or public APIs
      • Startup experience (~300 people or fewer), current or past. Doesn't need to be your most recent role

      Benefits

      • Variable pay based on objectives you hit. No arbitrary targets.
      • Hybrid flexibility. We're in NYC's Flatiron District and our team is in 3x a week.
      • Full health coverage. Comprehensive medical, dental, and vision insurance.
      • 401(k) with matching. We invest in your future, not just your output.
      • Unlimited PTO. Take the time you need. We measure results, not hours.
      • Parental leave. Paid leave for all parents.
      • Annual offsite. The whole team, once a year, somewhere worth the trip.

      Pay

      For candidates in New York, NY, the pay range for this role is $195,000–$265,000.

      Schedule

      Hybrid flexibility: expected in the office 3 days per week.

      Check for any duplicated content: we have hybrid flexibility mentioned both in Benefits and Schedule. In Benefits we included "Hybrid flexibility. We're in NYC's Flatiron District and our team is in 3x a week." That's a benefit. In Schedule we repeat similar. Might be duplication. Better to keep only one. Since Benefits already includes hybrid flexibility, we could omit Schedule section. But we need to decide if Schedule is needed. The instruction: prefer few substantive sections over many thin ones. Having both Benefits and Schedule with similar content is thin. So we can drop Schedule and keep hybrid flexibility under Benefits. However the benefit list already includes that line; it's okay. Thus we will not include Schedule section. Now ensure we didn't include any boilerplate: removed Our Values, Interview Process, Equal Opportunity, Referral Instructions, etc. Check for any leftover like "Today, more than 12,000 brands..." we included in About the role. Check for any mention of "Criteo is the first partner live on it." included. Check for any mention of "Three Reasons To Want This" - we didn't include as separate section; its content could be considered part of About the role or Responsibilities? It's more about why you'd want the role, not duties. Could be omitted? But it's substantive. Could we incorporate into About the role? Might be okay to add as a paragraph under About the role. However we already have About the role with company overview and role description. Adding the three