Staff Software Engineer

We need to produce HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Need to parse the posting. Let's extract content. The posting begins with "What we do" description of company. Then "Why this is a hard engineering problem". Then "What you'll own". Then "How we work". Then "Who you'll work with". Then "What we need from you". Then "Helpful, not required". Then "What we offer". Then visa note. We need to map to sections: About the role (maybe description of role), Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide what content belongs where. "About the role": could be summary of role: "You'll set technical direction for our core platform and API, raise the bar on how we design and operate systems, and ship. This is a hands-on role: you'll write a lot of code, and the decisions you make about architecture, reliability and developer experience will define the product for years." Also maybe "We're a small company at an inflection point...". That's about role. "Responsibilities": could be "You'll set technical direction for our core platform and API, raise the bar on how we design and operate systems, and ship. This is a hands-on role: you'll write a lot of code, and the decisions you make about architecture, reliability and developer experience will define the product for years." Also "We're AI native...". Actually responsibilities could be: set technical direction, write code, design architecture, ensure reliability, developer experience, work with AI agents, own problems end to end, work with product, ops, customers, report to VP of Engineering. "Requirements": maybe the "What we need from you" list: Deep TypeScript, production depth in Node (NestJS) and React, built and operated systems at scale in cloud (AWS), designed systems with real-world messiness (integrations, async workflows, consistency), build software with AI agents daily, strong product judgment. "Qualifications": maybe overlapping with requirements; but we could treat "Qualifications" as education/experience? Not given. Could skip if no specific. "Skills": maybe list of specific tech: TypeScript, Node.js, NestJS, React, AWS, SQS, EventBridge, AI agents, etc. "Benefits": from "What we offer": Generous base salary, equity, comprehensive health benefits, 401k, PTO policy, three days a week together in NYC office; rest flexible. "Pay": we have "Generous base salary, depending on experience, plus equity." That's pay info. Could be separate Pay section. "Schedule": "Three days a week together in our NYC office; the rest is up to you." That's schedule. We must not create sections with filler like "commensurate with experience". We have actual content. We need to avoid repeating job title as heading. No Job ID. We need to output only HTML fragment, using

for section headings,

• for lists,

  for prose. We need to preserve all substantive information, not invent or summarize away detail. So we need to include details like "You'll set technical direction for our core platform and API, raise the bar on how we design and operate systems, and ship. This is a hands-on role: you'll write a lot of code, and the decisions you make about architecture, reliability and developer experience will define the product for years." Also "We're a small company at an inflection point. The work you do in your first year will be visible in what customers can do with the product, not buried in a roadmap." Also "We're AI native. Every engineer works with Claude Code daily, and we treat AI agents as a core part of how software gets built here, not a productivity add-on. You'll help shape how that evolves." Also "Engineers own problems end to end, from a customer need through design, build, test and production. Cycle times are short and we deploy continuously. You'll work directly with product, operations and customers, not through layers." Also "You'll report to our VP of Engineering, who joined this year after ten years at Instagram, where he ran engineering for Reels. He came here for the same reason we hope you will: a small team, a real product with real customers, rapid growth, and problems that don't fit neatly inside one discipline." We need to decide where each piece goes. Let's structure:

  About the role

  You'll set technical direction for our core platform and API, raise the bar on how we design and operate systems, and ship. This is a hands-on role: you'll write a lot of code, and the decisions you make about architecture, reliability and developer experience will define the product for years. We're a small company at an inflection point. The work you do in your first year will be visible in what customers can do with the product, not buried in a roadmap.

  Responsibilities

  • Set technical direction for the core platform and API
  • Write production code (TypeScript, Node/NestJS, React)
  • Design and operate reliable systems, focusing on developer experience
  • Work with AI agents (Claude Code) daily and help shape AI‑native development practices
  • Own problems end‑to‑end: gather customer needs, design, build, test, and deploy to production
  • Collaborate directly with product, operations, and customers (no intermediary layers)
  • Report to the VP of Engineering (ex‑Instagram Reels engineering lead)

  Requirements

  • Deep expertise in TypeScript, with production‑level experience in Node.js (NestJS) and React
  • Experience building and operating scalable systems in a cloud environment (AWS)
  • Designed systems that handle real‑world messiness: integrations with external partners, asynchronous workflows, and data consistency across services
  • Daily use of AI agents in software development and opinions on best practices
  • Strong product judgment: ability to take a customer problem to a shipped solution and explain trade‑offs to non‑technical stakeholders

  Skills

  • TypeScript
  • Node.js / NestJS
  • React
  • AWS (EC2, S3, Lambda, etc.)
  • SQS and EventBridge (event‑driven systems)
  • AI‑assisted development (Claude Code)
  • Distributed systems, asynchronous workflows, data consistency

  Benefits

  • Generous base salary (depending on experience)
  • Meaningful equity (early‑stage)
  • Comprehensive health benefits
  • 401(k) plan
  • Paid time off (PTO) policy
  • Hybrid schedule: three days a week in the NYC office, remainder flexible

  Pay

  Generous base salary, depending on experience, plus equity.

  Schedule

  Three days a week together in our NYC office; the rest is up to you.

  We need to ensure we don't repeat content unnecessarily. The Pay section duplicates base salary info; but we already have base salary in Benefits. However the instruction: "Prefer a few substantive sections over many thin ones." Could combine Pay and Benefits? But they asked to include sections only when posting has real specific content. Pay is mentioned: "Generous base salary, depending on experience, plus equity." That's specific. Benefits also mention salary, equity, health, 401k, PTO, hybrid schedule. Could combine Pay into Benefits, but they said prefer few sections; maybe we can merge Pay into Benefits and not have separate Pay. However they also said include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. If we put Pay separate, it's not filler; it's specific. But we might be duplicating. The instruction: "Prefer a few substantive sections over many thin ones." So maybe better to not have separate Pay; incorporate salary info into Benefits. But they also listed Pay as a possible section heading. The rule: "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It's just examples; we can choose which to include. So we can omit Pay if we incorporate into Benefits. Similarly Schedule we have specific content; we could incorporate schedule into Benefits as bullet. But they gave Schedule as possible heading; we could keep separate if we want. However "Prefer a few substantive sections over many thin ones." Having many sections (About, Responsibilities, Requirements, Skills, Benefits, Pay, Schedule) is 7 sections; maybe okay. But we could combine Pay and Schedule into Benefits to reduce sections. However they said "include a section ONLY when the posting has real, specific content for it". Both Pay and Schedule have specific content. So we could keep them. But then we have many sections; still okay. But we need to avoid duplication: If we keep Pay separate, we should not repeat the same sentence in Benefits. We can adjust Benefits to not mention base salary/equity, but mention health, 401k, PTO, hybrid schedule? But schedule is separate. So Benefits could be health, 401k, PTO. Pay section: base salary + equity. Schedule section: hybrid schedule. Let's do that. Thus: Benefits: comprehensive health benefits, 401k, PTO policy. Pay: Generous base salary, depending on experience, plus equity. Schedule: Three days a week together in our NYC office; the rest is up to you. Now ensure we didn't miss any substantive info: "We're AI native. Every engineer works with Claude Code daily, and we treat AI agents as a core part of how software gets built here, not a productivity add-on. You'll help shape how that evolves." This is captured under Responsibilities (AI agents) and Skills (AI-assisted development). Good. "We operate worldwide, so it has to hold across regions, partners and edge cases we haven't seen yet." This is part of "Why this is a hard engineering problem". Could be included under Responsibilities or Requirements? Might be part of Requirements: designing systems that work worldwide. Could add a bullet under Requirements: "Experience building systems that operate globally across regions and partners." But we already have "Designed systems that handle real‑world messiness: integrations with external partners, asynchronous workflows, and data consistency across services." That covers worldwide? Not explicitly. Could add a bullet: "Experience building systems that operate worldwide across regions and partners." But we must not invent detail; we have statement: "We operate worldwide, so it has to hold across regions, partners and edge cases we haven't seen yet." That's a description of the problem, not a requirement. Could be included under Responsibilities: "Ensure the platform works correctly across regions, partners, and edge cases." Might be appropriate. Let's add a responsibility bullet: "Ensure the platform operates correctly worldwide across regions, partners, and edge cases." Now check for any other details: "You'll help shape how that evolves." Already covered. "Engineers own problems end to end, from a customer need through design, build, test and production. Cycle times are short and we deploy continuously. You'll work directly with product, operations and customers, not through layers." Already captured. "Who you'll work with: You'll report to our VP of Engineering, who joined this year after ten years at Instagram, where he ran engineering for Reels. He came here for the same reason we hope you will: a small team, a real product with real customers