Staff Software Engineer, Python

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. Remove boilerplate. We need to parse the posting: It includes sections: About Northbeam (company description) - maybe not needed? The instruction: "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we should include headings for sections that have content. The posting includes "About The Role" (with description). Then "Your Impact" (responsibilities). Then "What You Bring" (requirements/qualifications/skills). Then "Bonus Skills & Experience". Then "Base Salary Range" (pay). Then benefits described: equity package, healthcare, 401(k), flexible PTO, 12 company-paid holidays, 12 weeks paid parental leave, $500 work-from-home stipend. Also mention remote-friendly, offices. Also interview process (but we should drop application instructions and interview process? The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." Interview process might be considered application instructions? Probably we should drop it as it's not part of role description. The instruction says to remove application instructions. Interview process is part of hiring process, could be considered application instructions. Safer to omit. We also have "About Northbeam" company description - maybe we could include as a brief intro? Not required heading. Could be placed as a

before sections? The instruction: "Output ONLY the HTML fragment — no /, no markdown code fences." It didn't forbid extra paragraphs outside sections. But they said use headings for sections. We could include a brief intro paragraph about the company before the headings. That's okay. We need to preserve all substantive information. So we need to include details from About Northbeam, About The Role, Your Impact, What You Bring, Bonus Skills & Experience, Base Salary Range, Benefits. We must not fabricate sections like Schedule if not present. No schedule info given. So omit Schedule section. Pay section: we have Base Salary Range $190,000—$220,000 USD. Also mention equity package etc. That's benefits. Pay section should contain salary range. Could also mention that actual compensation may vary based on experience, skills, location. That's substantive. Benefits section: equity package, comprehensive healthcare benefits (medical, dental, vision), 401(k) plan, flexible PTO policy, 12 company-paid holidays, 12 weeks paid parental leave, $500 work-from-home stipend. Also remote-friendly, offices in SF and LA (maybe could be part of benefits or a separate note). We'll include in benefits. Now structure:

About Northbeam ...

About the role

Northbeam is fundamentally a data product ... (the paragraph about role).

Responsibilities

• Architect our new incrementality product into a reliable, repeatable experimentation platform, and own the technical decisions that determine whether it scales.
• Set the direction for near-real-time ingestion and processing as we move beyond batch workflows.
• Define the patterns for AI-powered workflows that help marketers evaluate performance and act on insights — the first version and the framework that follows it.
• Lead work on connection-state systems and the partner ecosystem across data ingestion and exports.
• Shape technical approach in adjacent product areas such as role-based access control (RBAC).
• Multiply the team: design review, mentorship, and raising the standard for what ships.

Requirements

• 8+ years designing and building distributed backend systems, microservices, APIs, and/or data processing systems in Python.
• Deep experience owning system architecture, including the tradeoffs that only surface at scale.
• A track record of partnering with product managers, designers, and data scientists to shape what gets built, not only how.
• Startup experience, or experience in an environment demanding breadth, sound judgment, and strong problem-solving under ambiguity.
• Demonstrated ability to turn ambiguous product needs into sound technical architecture and production-ready solutions — repeatedly, across different problem spaces.
• Fluency navigating complex datasets and interconnected tables to investigate issues, trace dependencies, and find the right path forward.
• Working frontend experience with React and TypeScript; deep frontend specialization is NOT required.
• Strong coding fundamentals, with AI used as an accelerator rather than a substitute for core capabilities.
• A generalist mindset and willingness to work across backend, frontend, pipelines, and infrastructure when the product requires it.
• Experience mentoring engineers and improving how a team operates.

We could also have Qualifications separate but we can combine. The instruction: prefer few substantive sections over many thin ones. So we could merge Requirements and Qualifications into one section, maybe "Requirements". But they listed both as possible headings. We could include "Qualifications" if we have distinct content. The "What You Bring" includes both requirements and qualifications. Could split into Requirements (years experience, architecture) and Qualifications (partnering, startup experience, etc.) but that may be thin. Better to have one section "Requirements" covering all. Skills: we could have a Skills section for frontend experience, AI usage, generalist mindset, mentoring. But again could be thin. Perhaps we can include Skills within Requirements. But the instruction says prefer few substantive sections over many thin ones. So we could have just Requirements covering all. However they explicitly mention Skills as a possible heading; but we can omit if not enough distinct content. The "What You Bring" includes skills like fluency navigating datasets, frontend experience, AI usage, generalist mindset, mentoring. Those could be considered skills. But we can still put them under Requirements. Bonus Skills & Experience: could be a separate section "Bonus Skills". That's substantive. Pay: Base Salary Range. Benefits: as described. Thus final HTML:

About Northbeam ...

About the role

...

Responsibilities

...

Requirements

...

Bonus Skills & Experience

...

Pay

Base Salary Range $190,000—$220,000 USD. Actual compensation may vary based on experience, skills, and location.

Benefits

• Equity package
• Comprehensive healthcare benefits (medical, dental, and vision)
• 401(k) plan
• Flexible PTO policy
• 12 company-paid holidays
• 12 weeks of paid parental leave
• $500 work-from-home stipend
• Remote‑friendly with offices in San Francisco and Los Angeles

We need to ensure we didn't include any boilerplate like "Interview Process". Also we omitted "About Northbeam" as a paragraph before sections. That's fine. Check for any repeated lines: we must not duplicate. Ensure we captured all substantive info. From About Northbeam: "Northbeam is building the world's most advanced marketing intelligence platform, providing top eCommerce brands a unified view of their business data through powerful attribution modeling and customizable dashboards. Our technology helps customers accurately track ad spend, understand the full customer journey, and drive profitable growth. Machine learning has been at the heart of Northbeam since day one: our full suite of measurement, spanning multi-touch attribution, MMM+, and incrementality, is built on it, along with laser-accurate first-party data. Now we're taking that foundation further, using AI to help brands operationalize their data and turn Northbeam insights into automated decisions. We're experiencing rapid growth, have strong product-market fit, and are looking for the right people to help us scale. This is a rare chance to make a meaningful impact at a fast-moving, high-growth company. At Northbeam, you'll join a team of driven, collaborative, and talented individuals who value personal growth and excellence. We'd love for you to be part of our journey. We're a remote-friendly company with physical offices in San Francisco and Los Angeles." We included remote-friendly and offices in benefits. Good. About The Role paragraph: we need to include that content. Let's capture: "Northbeam is fundamentally a data product - the whole company. We don't sell shoes, ads, or games. We sell data: quality integrations with a variety of platforms, fresh and reliable data pulls, robust data ingest APIs, correct aggregations, and algorithmic insights on top of that data, all packaged up in a user-facing application. What this means for you is that high-quality, robust data integration is at the core of what we do, and your work will have a direct connection to the company's success. We're looking for a Staff-level Software Engineer who leans backend and can take product problems from ambiguity through architecture to production. You'll spend roughly 70% of your time on backend and distributed systems work and 20–30% on frontend, giving you the ability to own capabilities across the stack and to make architectural calls that hold up on both sides of it. You'll take new products from early traction to meaningful scale, and set the technical direction that gets them there. That includes architecting our new incrementality offering into a scalable experimentation platform, defining our approach to near real-time data infrastructure, and establishing how AI shows up in our marketing users' workflows. You'll partner closely with data scientists, product managers, and designers, and your influence on what gets built will be as real as your influence on how." We'll put that in

under About the role. Now Responsibilities: we have "Your Impact" bullet points. We'll convert to

• . What You Bring: we need to capture all bullet points. Let's list them: - 8+ years designing and building distributed backend systems, microservices, APIs, and/or data processing systems in Python. - Deep experience owning system architecture, including the tradeoffs that only surface at scale. - A track record of partnering with product managers, designers, and data scientists to shape what gets built, not only how. - Startup experience, or experience in an environment demanding breadth, sound judgment, and strong problem-solving under ambiguity. - Demonstrated ability to turn ambiguous product needs into sound technical architecture and production-ready solutions — repeatedly, across different problem spaces. - Fluency navigating complex datasets and interconnected tables to investigate issues, trace dependencies, and find the right path forward. - Working frontend experience with React and TypeScript; deep frontend specialization is NOT required. - Strong coding fundamentals, with AI used as an accelerator rather than a substitute for core capabilities. - A generalist mindset and willingness to work across backend, frontend, pipelines, and infrastructure when the product requires it. - Experience mentoring engineers and improving how a team operates. We'll put these in Requirements
  . Bonus Skills & Experience: - Most of your experience is in data-intensive backend engineering, but you've also shipped frontend work. - You've been the person a team turns to when the architecture question doesn't have an obvious answer. We'll put in Bonus Skills & Experience
  . Pay: Base Salary Range $190,000—$220,000 USD. Actual compensation may vary based on experience, skills, and location. Benefits: as above. Check for any mention of "Schedule": none. Now ensure we didn't include any boilerplate like "Interview Process". Good. Now produce