Staff Software Engineer

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 boilerplate like EEO, etc. Must preserve all substantive info. We need to parse the posting. First, there is a long intro about Monstro, then "About The Role" heading. Then "What You'll Do" (list of responsibilities). Then "What We're Looking For" (requirements/qualifications). Then "Preferred But Not Required" (preferred qualifications). Then "Why Monstro?" (benefits? includes impact, ownership, experienced team, principles-driven culture, in person, compensation and benefits). Then "Compensation and benefits: Competitive cash compensation and meaningful equity, plus 100% employer-paid medical, dental, and vision coverage, disability coverage, flexible PTO, paid parental leave, and catered meals. Base Compensation Range (New York City): $224,000 - $264,000". Also "A Note on Interviewing:" etc (should be removed as boilerplate? It's about interview process, maybe considered application instructions? It says "A Note on Interviewing: We sometimes use AI note-takers...". This is not application instructions but could be considered meta. The instruction says remove application instructions. This is about interviewing, maybe considered part of process but not application instructions. However it's not substantive content about the job; it's about interview. Likely we should drop it as it's not needed. Also "Ready to Build With Us?" etc is call to action, remove. We need sections: - About the role: maybe a short paragraph summarizing role? The posting has "About The Role" then a paragraph: "We're looking for a Staff Software Engineer to support our AI application development team at the heart of the company's mission. This is a deeply technical role with real scope: you'll architect and ship systems that power AI-driven financial analysis, build the tooling and infrastructure that domain experts rely on, and set the engineering bar for how we build AI systems responsibly in a regulated industry. You'll influence how we design agents, how we validate and govern AI output, how we scale our modeling infrastructure, and how we think about auditability and compliance. This isn't a role where AI is a thin wrapper — the intelligence layer is the product." We can put that as

under

About the role

. - Responsibilities: from "What You'll Do". It's a list of bullet points (each line starts with a verb). We need to output

• for each. List: - Architect and build AI agent systems — including multi-agent workflows, orchestration layers, and the infrastructure that makes them reliable and auditable in production - Work at the edge of what’s possible with modern AI — rapidly evaluating new models, tools, and development patterns, and setting the technical direction for turning the most promising capabilities into robust production systems. - Design modeling and reasoning systems that meet the correctness and explainability requirements of financial services — where every recommendation needs to be traceable and defensible - Build internal applications and platforms (Python/React) that enable domain experts and engineers to author, validate, and deploy AI-powered analysis at scale - Document your decisions, ensure sufficient test coverage and generate AI native artifacts to share your work with others - Own distributed backend infrastructure: event-driven workers, job pipelines, and multi-stage processing systems that deliver AI outputs reliably under load - Establish patterns for AI output validation and quality assurance — including automated evaluation pipelines, hallucination detection, and compliance guardrails - Drive technical decisions across teams: schema design, API contracts, system boundaries, and service architecture - Contribute to full stack application development - Lead engineering initiatives across team members and cross functional partners - Establish and promote engineering and architecture best practices and the adoption of new AI technologies and techniques - Mentor senior engineers and raise the engineering bar across the organization We need to ensure each bullet is a
• . - Requirements: from "What We're Looking For". It includes a list of bullet-like sentences but not bullet formatting. We need to extract each requirement as list items. Paragraph: "8+ years of engineering experience, with a track record of leading complex systems from design to production. Deep curiosity about where AI-native software is heading, with the technical judgment to separate promising new capabilities from hype and help shape how emerging approaches are adopted across the engineering organization. Hands-on experience designing, building, and shipping production software systems using AI development tools, especially AI-powered software Strong software engineering skills and experience with a demonstrated track record contributing to best practices application architecture Python expertise — async services, type-safe code, and systems that scale Strong distributed systems fundamentals: event-driven architectures, message queues, job state machines, and worker patterns Relational database fluency and an instinct for data modeling Full-stack range — you can build product-quality React/TypeScript UIs when the problem calls for it Opinionated about how AI systems should be tested, evaluated, and monitored in production Experience leading technical teams or acting as a force multiplier across engineering" We can treat each line as a
• . Also note there is a line "Opinionated about how AI systems should be tested, evaluated, and monitored in production" appears twice? Actually appears once in this list and also in Preferred But Not Required. We'll keep as is. - Qualifications: maybe we can combine Requirements and Qualifications? The instruction says use headings for sections like Qualifications, Skills, Benefits, Pay, Schedule. We have Requirements already. Could also have Qualifications (maybe same as Requirements). But we should not create thin sections. We have Requirements covered. Could also have Skills (maybe list of technical skills). But we already have many skill items in Requirements. Could create a Skills section summarizing technical skills: Python, React/TypeScript, distributed systems, relational DB, AI/ML, etc. However we must not invent or summarize away detail; we must preserve ALL substantive information. If we create a Skills section, we need to extract skill statements from the posting. The posting already includes many skill statements in Requirements and Preferred. We could keep them under Requirements and not create separate Skills to avoid duplication. The instruction: "Prefer a few substantive sections over many thin ones." So we can have About the role, Responsibilities, Requirements, Benefits, Pay. Possibly also Qualifications if distinct. But we can treat Requirements as qualifications. We'll not create separate Qualifications. - Benefits: from "Why Monstro?" includes Impact, Ownership, Experienced team, Principles-driven culture, In person, in New York: ... Compensation and benefits: Competitive cash compensation and meaningful equity, plus 100% employer-paid medical, dental, and vision coverage, disability coverage, flexible PTO, paid parental leave, and catered meals. We need to extract benefits: medical/dental/vision, disability, flexible PTO, paid parental leave, catered meals, meaningful equity, maybe also "Competitive cash compensation". However compensation is separate Pay section. Benefits should be non-compensation: medical, dental, vision, disability, flexible PTO, paid parental leave, catered meals, maybe equity? Equity is compensation but could be considered benefit. We'll put equity under Pay? The instruction: include Pay section only if posting actually states them. It does state base compensation range. So we will have Pay section with that range and mention competitive cash compensation and meaningful equity. Benefits section will list the other benefits. Thus: Benefits: 100% employer-paid medical, dental, and vision coverage; disability coverage; flexible PTO; paid parental leave; catered meals. Also maybe "In person, in New York: We are headquartered at The Spiral in Hudson Yards and work in the office four days a week, because our pace depends on fast collaboration." That's more about work arrangement, could be Schedule? Actually schedule: they work in office four days a week. That's schedule info. So we can create Schedule section: "Work in office four days a week at The Spiral in Hudson Yards, New York City." Pay: Base Compensation Range (New York City): $224,000 - $264,000. Also mention Competitive cash compensation and meaningful equity. We need to ensure we don't include filler like "commensurate with experience". Not present. Now we must not include boilerplate like "A Note on Interviewing:" etc. Remove. Now produce HTML fragment:

  About the role

  We're looking for a Staff Software Engineer to support our AI application development team at the heart of the company's mission. This is a deeply technical role with real scope: you'll architect and ship systems that power AI-driven financial analysis, build the tooling and infrastructure that domain experts rely on, and set the engineering bar for how we build AI systems responsibly in a regulated industry. You'll influence how we design agents, how we validate and govern AI output, how we scale our modeling infrastructure, and how we think about auditability and compliance. This isn't a role where AI is a thin wrapper — the intelligence layer is the product.

  Responsibilities

  • Architect and build AI agent systems — including multi-agent workflows, orchestration layers, and the infrastructure that makes them reliable and auditable in production
  • Work at the edge of what’s possible with modern AI — rapidly evaluating new models, tools, and development patterns, and setting the technical direction for turning the most promising capabilities into robust production systems.
  • Design modeling and reasoning systems that meet the correctness and explainability requirements of financial services — where every recommendation needs to be traceable and defensible
  • Build internal applications and platforms (Python/React) that enable domain experts and engineers to author, validate, and deploy AI-powered analysis at scale
  • Document your decisions, ensure sufficient test coverage and generate AI native artifacts to share your work with others
  • Own distributed backend infrastructure: event-driven workers, job pipelines, and multi-stage processing systems that deliver AI outputs reliably under load
  • Establish patterns for AI output validation and quality assurance — including automated evaluation pipelines, hallucination detection, and compliance guardrails
  • Drive technical decisions across teams: schema design, API contracts, system boundaries, and service architecture
  • Contribute to full stack application development
  • Lead engineering initiatives across team members and cross functional partners
  • Establish and promote engineering and architecture best practices and the adoption of new AI technologies and techniques
  • Mentor senior engineers and raise the engineering bar across the organization

  Requirements

  • 8+ years of engineering experience, with a track record of leading complex systems from design to production
  • Deep curiosity about where AI-native software is heading, with the technical judgment to separate promising new capabilities from hype and help shape how emerging approaches are adopted across the engineering organization
  • Hands-on experience designing, building, and shipping production software systems using AI development tools, especially AI-powered software
  • Strong software engineering skills and experience with a demonstrated track record contributing to best practices application architecture
  • Python expertise — async services, type-safe code, and systems that scale
  • Strong distributed systems fundamentals: event-driven architectures, message queues, job state machines, and worker patterns
  • Relational database fluency and an instinct for data modeling
  • Full-stack range — you can build product-quality React/TypeScript UIs when the problem calls for it
  • Opinionated about how AI systems should be tested, evaluated, and monitored in production
  • Experience leading technical teams or acting as a force multiplier across engineering

  Benefits

  • 100% employer-paid medical, dental, and vision coverage
  • Disability coverage
  • Flexible PTO
  • Paid parental leave