Staff Software Engineer (Applied AI)

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 need to parse the posting. First, we need to extract sections. The posting includes: - Intro about Traba (company description) maybe "About the role"? Actually "About You" and "You Will" etc. We need to produce sections with headings

. We need to use

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

  for prose. We must not repeat job title as heading (the page already shows it). No Job ID. We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. We must preserve all substantive information. We must not invent or summarize away detail. We must include a section only when posting has real specific content for it — never emit heading followed by filler/placeholder text. We must prefer few substantive sections over many thin ones. We need to decide which sections to include. Let's extract content: Company description: "Traba is building the AI operating system for the industrial supply chain..." This is about the company, maybe "About the role"? Actually "About the role" would be description of the role. The posting includes "You'll build Traba's product on top of AI agents..." etc. That's about the role. We have sections: - About the role (maybe combine company description and role description) - Responsibilities (maybe "You Will" bullet list) - Requirements/Qualifications/Skills (maybe "You Have" bullet list) - Benefits (list) - Pay (salary range) - Schedule (maybe not present) - About You (maybe part of qualifications) We need to decide. Let's parse the posting text: "Traba is building the AI operating system for the industrial supply chain - the network of warehouses, manufacturers, logistics providers, and workers behind the physical goods people rely on every day. We started by tackling labor, supplying industrial businesses with consistent, reliable temporary workforces, and quickly became the fastest growing staffing company in America. Since then, we've expanded our suite of AI agents to help logistics providers, manufacturers, 3PLs, and other industrial businesses fully automate their manual workflows, derive insights from their data streams, and transform their decision intelligence. Our mission is to build a world where the global supply chain operates at peak efficiency. We’re proud to be backed by some of the world’s best investors, including Founders Fund, Khosla Ventures, and General Catalyst. You'll build Traba's product on top of AI agents—and set the standard for how we do it. You'll put frontier models and existing agents to work across our staffing marketplace to automate the pipeline that sources, vets, matches, and places workers on millions of shifts—and own the core backend services and platform it all runs on. (Our AI Agents team builds the agent platform; you make it real across the stack.) This is a platform-engineering role first, so you'll go where the priorities are: the infrastructure an agent needs one quarter, a matching, data, or scaling problem the next. You'll join the founding team, partner with our CTO on key architectural decisions, iterate on the roadmap, and build the foundational platform that scales over the next several years." Then: "About You An applier who sets the bar. You wire frontier models and existing agents into real product across the stack—and set the standard for how the team does it. You don't need to own the orchestration internals; you make them real in production, and you know which corners are safe to cut at an early stage.Voracious learner. You move easily from API design to deployment infrastructure.Deep full-stack experience. You've designed performant, scalable applications with real expertise in APIs, data modeling, query optimization, and distributed systems." Then: "You Will Set the standard for how we apply agents across the stack to automate the staffing pipeline—and for how the team builds with AI-assisted tooling.Architect and lead core systems—from real-time matching to autonomous vetting pipelines powered by ML and agents.Own architecture for the platform, thinking ahead to what the company will need a year or two out.Drive backend performance, reliability, and scale." Then: "You Have 7+ years with TypeScript/Node.js or Python, PostgreSQL, and messaging (Kafka or RabbitMQ).A track record of shipping and leading projects at scale with high velocity.Experience building or integrating AI/LLM systems in production is a plus—what matters most is the judgment to lead the team into it.Comfort owning ambiguity and direction in an early-stage environment." Then benefits list: "Benefits 📈 Start-up equity💰 Competitive Salary🩺 100% Paid health, dental & vision coverage🍽️ Dinner Provided via DoorDash, free DashPass & stocked kitchen for NY employees🚍 Commuter benefit🏋🏽 Gympass Benefit✚✚ Additional: One Medical Membership, Gympass, HSA via Optum, Talkspace, HealthAdvocate, Teledoc Health" Then salary range: "Salary Range Details The compensation range for this position is set between $240,000 and $300,000, reflecting our market analysis and other relevant considerations. However, exceptions may be made for candidates with qualifications that significantly differ from those outlined in the job description." Then EEO etc (to remove). Thus we have content for: - About the role (maybe combine intro and "You'll build..."). - Responsibilities (the "You Will" list). - Requirements/Qualifications/Skills (the "You Have" list plus maybe "About You"). - Benefits (list). - Pay (salary range). - Schedule: not present, so omit. We need to decide whether to split Requirements, Qualifications, Skills separate or combine. The instruction says use those headings if content exists. We have content for qualifications (experience, skills). Could split into Requirements (maybe "You Have") and Skills (maybe technical skills). But we can combine into one section if we think it's thin? The instruction: "Prefer a few substantive sections over many thin ones." So we might combine Requirements, Qualifications, Skills into one section, maybe titled "Requirements" or "Qualifications". But we need to follow headings list: we can use any of those headings if we have content. If we combine, we could use "Requirements" and include all. Or we could have separate sections but they'd be thin. Better to combine. Thus sections: - About the role (intro + role description) - Responsibilities (You Will) - Requirements (You Have + About You) - Benefits - Pay We need to output HTML fragment only. We need to use

  for each section heading. Inside each section, we need to use

  for prose, and

  • for any list of duties/requirements/benefits. Thus: About the role: prose (maybe multiple paragraphs). We'll put as

    elements. Responsibilities: list of items from "You Will". Those are sentences separated by periods? Let's extract: "You Will Set the standard for how we apply agents across the stack to automate the staffing pipeline—and for how the team builds with AI-assisted tooling.Architect and lead core systems—from real-time matching to autonomous vetting pipelines powered by ML and agents.Own architecture for the platform, thinking ahead to what the company will need a year or two out.Drive backend performance, reliability, and scale." We need to split into list items. Likely each sentence is a responsibility. Thus: - Set the standard for how we apply agents across the stack to automate the staffing pipeline—and for how the team builds with AI-assisted tooling. - Architect and lead core systems—from real-time matching to autonomous vetting pipelines powered by ML and agents. - Own architecture for the platform, thinking ahead to what the company will need a year or two out. - Drive backend performance, reliability, and scale. We'll put each as

  • . Requirements: combine "About You" and "You Have". About You: "An applier who sets the bar. You wire frontier models and existing agents into real product across the stack—and set the standard for how the team does it. You don't need to own the orchestration internals; you make them real in production, and you know which corners are safe to cut at an early stage.Voracious learner. You move easily from API design to deployment infrastructure.Deep full-stack experience. You've designed performant, scalable applications with real expertise in APIs, data modeling, query optimization, and distributed systems." We need to parse into list items? Could be prose. But we have list of qualifications/experience: "7+ years with TypeScript/Node.js or Python, PostgreSQL, and messaging (Kafka or RabbitMQ). A track record of shipping and leading projects at scale with high velocity. Experience building or integrating AI/LLM systems in production is a plus—what matters most is the judgment to lead the team into it. Comfort owning ambiguity and direction in an early-stage environment." We could make a list for the hard requirements and maybe keep About You as prose. But we need to use
    • for any list of duties/requirements/benefits. So if we have a list of requirements, we should use
      • . The "About You" is more descriptive; could be prose. Thus we could have a

        for About You prose, then a

        • for the You Have list. Alternatively combine all into a list; but better to separate. Thus Requirements section: maybe heading

          Requirements

          . Inside:

          About You prose

          then
          • ... etc. Benefits: list of benefits with emojis. Need to extract each benefit. Benefits text: "Benefits 📈 Start-up equity💰 Competitive Salary🩺 100% Paid health, dental & vision coverage🍽️ Dinner Provided via DoorDash, free DashPass & stocked kitchen for NY employees🚍 Commuter benefit🏋🏽 Gympass Benefit✚✚ Additional: One Medical Membership, Gympass, HSA via Optum, Talkspace, HealthAdvocate, Teledoc Health" We need to split into items. Let's parse: - Start-up equity - Competitive Salary - 100% Paid health, dental & vision coverage - Dinner Provided via DoorDash, free DashPass & stocked kitchen for NY employees - Commuter benefit - Gympass Benefit - Additional: One Medical Membership, Gympass, HSA via Optum, Talkspace, HealthAdvocate, Teledoc Health But note "Gympass" appears twice; maybe it's a benefit and also additional. We'll keep as listed. We could combine "Additional: One Medical Membership, Gympass, HSA via Optum, Talkspace, HealthAdvocate, Teledoc Health" as a single item or split each. Probably better to list each as separate item. Thus benefits list items: - Start-up equity - Competitive Salary - 100% Paid health, dental & vision coverage - Dinner Provided via DoorDash, free DashPass & stocked kitchen for NY employees - Commuter benefit - Gympass Benefit - One Medical Membership - Gympass (maybe duplicate; but we can keep) - HSA via Optum - Talkspace - HealthAdvocate - Teledoc Health But we might want to avoid duplication; but we must preserve all substantive information. The text includes "Gympass Benefit" and then "Additional: One Medical Membership, Gympass, HSA via Optum, Talkspace, HealthAdvocate, Teledoc Health". So Gympass appears both as a benefit and in additional list. We'll keep both. Pay: salary range: "The