Founding 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 need to parse the job posting. Let's extract content: Company description: Workstream is a mission-driven company building the all-in-one HR, payroll, and hiring platform for managing the hourly workforce... etc. That's about the company, could be "About the role"? Actually "About the role" is typical heading for description of role. The posting includes "Day In The Life" and description of responsibilities. So we can put that under "About the role" maybe. Responsibilities: list of duties: Build and operate production agents and agentic workflows..., Work forward-deployed with design customers..., Build the evaluation harness..., Build the human-review layer..., Run shadow-mode parallel runs..., Turn customer-specific work into reusable agents..., Handle production incidents..., Help set the technical bar... Requirements/Qualifications/Skills: The "Who You Are" section includes bullet-like sentences. We can treat as Requirements or Qualifications. Could split: Requirements: have personally built and operated at least one AI agent or agentic workflow in production; can clearly explain... Strong engineering judgment across models, orchestration, APIs, data and integrations, permissions, observability, and evaluations; Worked directly with customers or end users—discovery, implementation, or incident resolution—and communicate clearly with non-technical people; Can break a messy workflow into deterministic steps, agentic decisions, human judgment, and exception paths—and define how each part will be tested; Care about keeping plausible but wrong AI output away from customers: grounded context, constrained actions, verification, evals, review, monitoring; Thrive in zero-to-one ambiguity: shipping weekly, owning outcomes, and doing whatever the service needs—including unglamorous review tooling and data plumbing; Exposure to a regulated domain (payroll, payments, tax, benefits, labor compliance) is a plus, not a requirement; Demonstrated production experience matters more than title or years. We can put these under "Requirements" or "Qualifications". Since they ask for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can combine overlapping. Perhaps we put "Requirements" for the bullet list, and "Skills" maybe not needed. But we need to avoid empty sections. We have Benefits: "What We Offer" includes mission-driven, early employee opportunity, competitive salary and equity, comprehensive health coverage (medical, dental, vision, they pay 95% of premiums for employees and 85% for dependents), in office amenities and stocked kitchen, 401K Plan, Flexible PTO. That's benefits. Pay: Not explicitly stated; they say competitive salary and equity but no numbers. According to rules, we should not create Pay section unless posting actually states them. It says "competitive salary and equity" but no specific numbers. That's vague; maybe we should not include Pay because it's not specific. The rule: never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. "Competitive salary and equity" is vague but still states that there is competitive salary and equity. Is that considered stating them? It's not a specific number but it's stating that they offer competitive salary and equity. Might be acceptable? The rule says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state that they offer competitive salary and equity, so we could include Pay section with that statement. However, they also say "Prefer a few substantive sections over many thin ones." Might be okay to include Pay with that line. Schedule: They say "This is a full-time, hybrid position with 1 to 2 days a week in-office to support close cross-functional collaboration." That's schedule info. So we can include Schedule section. Now About the role: Could be the introductory paragraph about Workstream and mission. Or we could treat that as "About the role" describing the role. Let's put the initial paragraphs under About the role. Responsibilities: list as above. Requirements: list of who you are. Qualifications: maybe we could combine with Requirements; but we need to avoid duplication. Could put Requirements as the bullet list, and Qualifications maybe empty -> we should not create empty heading. So we omit Qualifications. Skills: maybe we could extract skills like "AI agent orchestration, tool use, data connections, deterministic logic, state, permissions, evaluation harness, human-review layer, incident management, productization, cross-functional collaboration". But that's already in responsibilities. Might be thin. Better to omit Skills if not distinct. Thus sections: About the role, Responsibilities, Requirements, Benefits, Pay, Schedule. Now we need to format:

About the role

then

... prose ...

. For lists:

• ...

. We must preserve all substantive information, not invent or summarize away detail. So we need to include all details from the posting. Let's extract About the role content: The first paragraph(s) before "Day In The Life". Let's capture: "Workstream is a mission-driven company building the all-in-one HR, payroll, and hiring platform for managing the hourly workforce. There are 2.7 billion hourly workers, making up 80% of the global workforce, but this market has been heavily underserved by technology and deserves better. Workstream has been purpose-built for the hourly workforce from day one so that these businesses and their employees can thrive. Our customers include leading brands from multiple sectors, including Burger King, Carl's Jr./Hardee's, IHOP, KFC, and Culvers. We are a high growth series B company and quickly expanding our product portfolio to deliver on our vision. We are backed by legendary VCs and industry experts like Founders Fund, BOND, and Coatue." That's about the company. Could be considered About the role? Might be okay. Then "Day In The Life Workstream is building AI-native services that deliver completed business outcomes—mature service categories businesses already pay for, delivered by AI agents plus a small human review layer at materially better margins than the traditional alternative. We are validating the first service now with design customers from our existing base. You will be the first engineering hire on the delivery team, reporting to the Head of Delivery, AI-Native Services. This is a forward-deployed builder role. You will embed with design customers, map their real workflows, and build the production agents, integrations, evaluations, and review tooling that turn that work into a reliable, repeatable service. You will see your systems do real work with real consequences for real people—and you will be on the hook when they misbehave. You will not own pricing, deal acceptance, or the margin model—those sit with the Head of Delivery and the Head of GTM. You will own the components: whether they work, how they fail, and how fast bespoke work becomes reusable." That's more role-specific. We'll combine into About the role paragraph(s). Ensure we keep all details. Now Responsibilities: list each bullet as

. Let's extract: - Build and operate production agents and agentic workflows: orchestration, tool use, data connections, deterministic logic, state, and permissions. - Work forward-deployed with design customers—sit in their workflow, map the messy reality, and build against live data. - Build the evaluation harness: eval datasets from real customer work, pre-launch thresholds, regression suites, and post-launch monitoring. - Build the human-review layer: exception queues, review tooling, escalation paths, and the tracing that makes every agent decision auditable. - Run shadow-mode parallel runs against the customer's existing process or provider and drive discrepancies to zero before go-live. - Turn customer-specific work into reusable agents, integrations, and playbooks—productization is the default, customization the exception. - Handle production incidents end to end, and feed every failure back into evals and controls so it cannot recur. - Help set the technical bar as the team grows. Now Requirements (Who You Are): list each bullet: - You have personally built and operated at least one AI agent or agentic workflow in production. You can clearly explain how it worked, where it failed, how you evaluated it, and what you kept deterministic or human-led. - Strong engineering judgment across models, orchestration, APIs, data and integrations, permissions, observability, and evaluations. - You have worked directly with customers or end users—discovery, implementation, or incident resolution—and communicate clearly with non-technical people. - You can break a messy workflow into deterministic steps, agentic decisions, human judgment, and exception paths—and define how each part will be tested. - You care about keeping plausible but wrong AI output away from customers: grounded context, constrained actions, verification, evals, review, monitoring. - You thrive in zero-to-one ambiguity: shipping weekly, owning outcomes, and doing whatever the service needs—including unglamorous review tooling and data plumbing. - Exposure to a regulated domain (payroll, payments, tax, benefits, labor compliance) is a plus, not a requirement. - Demonstrated production experience matters more than title or years. Now Benefits (What We Offer): list: - A mission-driven and value-based company dedicated to empower deskless workers and local businesses - An early employee opportunity at a Series B hyper-growth startup; work with the founding team and industry veterans to accelerate your career - Competitive salary and equity - Comprehensive health coverage: medical, dental, and vision. We pay 95% of your premiums for our employees and 85% for dependents - In office amenities and stocked kitchen - 401K Plan - Flexible PTO Now Pay: we could include "Competitive salary and equity" but that's already in Benefits. To avoid duplication, maybe we put Pay section with just "Competitive salary and equity" (though it's also in Benefits). But duplication is not ideal. However the rule says preserve ALL substantive information; we can include it in Benefits and not duplicate in Pay. Since Pay section is optional, we could omit Pay if we already covered salary in Benefits. But the rule says we should not create Pay section unless posting actually states them. It does state competitive salary and equity, but we already have that in Benefits. Could we still include Pay? Might be considered thin. Better to omit Pay and keep salary info in Benefits. Schedule: we have: "This is a full-time, hybrid position with 1 to 2 days a week in-office to support close cross-functional collaboration." Thus Schedule section with that sentence. Now we need to output HTML fragment only. Let's craft:

About the role

Workstream is a mission-driven company building the all-in-one HR, payroll, and hiring platform for managing the hourly workforce. There are 2.7 billion hourly workers, making up 80% of the global workforce, but this market has been heavily underserved by technology and deserves better. Workstream has been purpose-built for the hourly workforce from day one so that these businesses and their employees can thrive. Our customers include leading brands from multiple sectors, including Burger King, Carl's Jr./Hardee's, IHOP, KFC, and Culvers. We are a high growth series B company and quickly expanding our product portfolio to deliver on our vision. We are backed by legendary VCs and industry experts like Founders Fund, BOND, and Coatue. Day In The Life Workstream is building AI-native services that deliver completed business outcomes—mature service categories businesses already pay for, delivered by AI agents plus a small human review layer at materially better margins than the traditional alternative. We are validating the first service now with design customers from our existing base. You will be the first engineering hire on the delivery team, reporting to the Head of Delivery, AI-Native Services. This is a forward-deployed builder role. You will embed with design customers, map