Software Engineer, Product
for headings. Use - for lists,
for prose. Do not repeat job title. Do not include Job ID etc. Remove boilerplate. Must preserve all substantive info.
We need to parse the posting: It's about a software engineer role at Sixfold. The content includes description of company, role, responsibilities, what success looks like, about you (requirements), additional info (salary, office, visa, etc). We need to extract sections.
We should not include navigation, legal, EEO, etc. The posting includes "Moments We're Proud Of", "Our Commitment", etc. Those are likely boilerplate or not needed? The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. "Moments We're Proud Of" maybe not boilerplate but could be considered marketing; but it's substantive? Might be okay to keep? However they said "Prefer a few substantive sections over many thin ones." So we may combine.
We need sections: About the role (maybe from "About The Role" paragraph). Responsibilities (list of duties). Requirements/Qualifications/Skills (maybe combine). Benefits, Pay, Schedule (if present). The posting includes "Expected salary: $150,000-180,000 + equity + benefits". Also mentions "About half the company works in the NYC office 3–4 days a week." That's schedule info (hybrid). Also "This position does not include visa sponsorship." That's maybe a note but not required.
We need to include Pay section only if posting actually states them. Yes salary range given. Benefits: mention equity + benefits. Could also mention benefits generally. Schedule: mention hybrid office expectation.
We need to avoid filler like "commensurate with experience". Not present.
We need to preserve all substantive info; do not invent or summarize away detail. So we need to keep details like: building and delivering quality software, write/test/deploy code across full stack primarily TypeScript, build new product capabilities in TypeScript stack and contribute to Ruby/Python services, work on team-level projects applying engineering best practices, develop AI engineering expertise, learn ML principles, work with LLMs, integrate AI capabilities, collaborate with AI engineers on prompt engineering, model evaluation, responsible AI development, collaborate with cross-functional partners (PM, designers, engineers), work in two-week cycles, release to production at least once a week, own software through lifecycle, assess pressing problems, identify/design solutions, write technical specs, scope and break down projects, spend approx one week per quarter on call, etc.
Also "What Success Looks Like" details for 30,60,90 days.
About You: 3+ years professional software engineering experience, familiar with web dev using React and TypeScript, understand React component lifecycle, state management, performance optimization, leverage TypeScript type system, extra credit for generics, utility types, TailwindCSS, familiar with Node and PostgreSQL, know patterns to build features in TS app without significant learning time, extra credit for WebSocket frameworks or background job processing frameworks, experience designing and developing APIs (RESTful and/or GraphQL) with strong understanding of auth, authz, versioning best practices, can build/document APIs intuitive scalable easy to integrate, want to work in early-stage fast-growth tech company, comfortable with ambiguity and change, can own problems and proactively devise solutions, love communication collaboration execution, value meaningful commit messages and PR descriptions, prefer to merge PRs within a day, appreciate healthy engineering debates but know how to make pragmatic decisions, take feedback well and candid with feedback you give, have experience with agentic coding as default workflow, ship real feature work through Claude Code or Codex, orchestrate parallel agents, design specs and prompts as primary craft, intuition around evals, tool use, context engineering. Insurance/insurtech/enterprise B2B background a plus but not required.
Additional Information: Expected salary: $150,000-180,000 + equity + benefits; Advertised and actual salary ranges may differ by geographic area, work experience, education, and/or skill level; About half the company works in the NYC office 3–4 days a week; This position does not include visa sponsorship. Candidates must be authorized to work in the United States without requiring employer sponsorship.
We need to omit visa sponsorship note? It's substantive but maybe not needed for sections. Could be included in a short paragraph under Additional Information but we are told to drop minor metadata into a short
or drop it. Visa sponsorship is minor metadata; we could drop it. The salary and benefits and schedule are substantive for Pay/Benefits/Sections.
We need to output only HTML fragment, no /, no markdown fences.
We'll create sections:
About the Role
with prose summarizing the role description (maybe combine the initial paragraphs about Sixfold and role). But we must not repeat job title. We'll include description: "Insurance underwriting runs on human judgment... Sixfold is building AI agents...". That's about company; could be part of About the Role.
Better: About the Role section includes the paragraph starting "About The Role As a software engineer at Sixfold, you will:" and the bullet list of responsibilities. We'll turn bullet list into - .
Responsibilities: maybe we separate responsibilities from About the Role? The instruction: Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have both About the role and Responsibilities sections. We'll need to split content.
About the role: maybe a brief overview of the role and company.
Responsibilities: list of duties.
Requirements/Qualifications/Skills: we can combine into one section "Requirements" or separate. Since they ask for headings e.g. Requirements, Qualifications, Skills. We could have Requirements (experience), Qualifications (technical), Skills (soft skills). But we can also combine into one Requirements section to avoid thin sections. The instruction: Prefer a few substantive sections over many thin ones. So maybe we have one "Requirements" section that includes all.
But we also need Benefits, Pay, Schedule sections if present.
Thus final sections: About the role, Responsibilities, Requirements, Benefits, Pay, Schedule.
We'll need to ensure we don't create empty sections.
Let's craft content.
About the role paragraph: combine company description and role overview.
From posting: "Insurance underwriting runs on human judgment, manual workflows, and knowledge locked in someone's head. It breaks when that person leaves and doesn't scale when the book doubles. Sixfold is building AI agents that understand risk the way a 20-year veteran underwriter does. Not summaries or flags, but systems that make real decisions on billions in premium for some of the world's largest carriers. AI is the product and the workflow. In this role, you will build and run the cloud infrastructure, Kubernetes environments, deployment tooling, and observability systems that enable Sixfold's engineers to develop, release, and operate our products."
Then "Who We Are" section includes product, team, traction. Could be part of About the role.
We'll include that.
Responsibilities: list from "About The Role As a software engineer at Sixfold, you will:" bullet points.
Let's extract bullet points:
- Build and deliver quality software. You will write, test, and deploy code across the full application stack, primarily using TypeScript. You will build new product capabilities in our TypeScript stack and contribute to established Ruby and Python services when needed.
- You’ll work on team-level projects, applying engineering best practices and contributing to the team’s technical decision-making.
- Develop AI engineering expertise. You'll have opportunities to learn and apply machine learning principles, work with large language models, and integrate AI capabilities into our products. You'll collaborate with our AI engineers to understand best practices for prompt engineering, model evaluation, and responsible AI development.
- Collaborate with cross-functional partners. Our teams include product managers, designers, and engineers working together to accomplish shared goals. You will collaborate with these partners, beginning with problem discovery through solution design and delivery. We work in two-week cycles and release to production at least once a week.
- Own your software through its entire lifecycle. In addition to shipping code, you will assess our most pressing product and engineering problems, identify and design solutions, write technical specs, and scope and break down projects. You will also spend approximately one week per quarter on call, serving as the first line of defense against service outages and critical bugs. If you don’t have experience with all of this yet, don’t worry - we’ll teach you!
We can turn each bullet into
- .
Requirements: combine "About You" and maybe "Additional Information" (except salary/benefits/schedule). Also include "What Success Looks Like" maybe as part of expectations but could be included in Requirements? It's more about success metrics; maybe we could include in a separate section but to avoid thin sections we could incorporate into Requirements as expectations.
But we have separate sections for Benefits, Pay, Schedule. So Requirements will contain experience, technical skills, soft skills, agentic coding, etc.
Let's list requirements:
- 3+ years of professional software engineering experience.
- Familiar with web development using React and TypeScript; understand React's component lifecycle, state management patterns, performance optimization techniques; can leverage TypeScript's type system effectively to create maintainable, type-safe code. Extra credit if comfortable with generics, utility types, and TailwindCSS.
- Familiar with Node and PostgreSQL; know their patterns well enough to build features in a TypeScript app without significant learning time. Extra credit if you have experience with WebSocket frameworks or background job processing frameworks.
- Experience designing and developing APIs (RESTful and/or GraphQL) with a strong understanding of authentication, authorization, and versioning best practices. Can build and document APIs that are intuitive, scalable, and easy to integrate with.
- Want to work in an early-stage, fast-growth tech company; comfortable with ambiguity and change; can own problems and proactively devise solutions, not just wait for somebody to feed you tasks.
- Love communication, collaboration, and execution; value meaningful commit messages and pull request descriptions; prefer to merge PRs within a day; appreciate healthy engineering debates but know how to make pragmatic decisions; take feedback well and are candid with the feedback you give.
- Have experience with agentic coding as your default workflow; ship real feature work through Claude Code or Codex, orchestrate parallel agents, design specs and prompts as a primary craft, and have intuition around evals, tool use, and context engineering.
- Insurance, insurtech, or enterprise B2B background is a plus but not required.
We could also include the success timeline as expectations but maybe not needed.
Benefits: The posting mentions equity + benefits, but not detailed benefits. It says "Expected salary: $150,000-180,000 + equity + benefits". Also "Our comprehensive compensation package includes competitive salaries, equity opportunities, and robust benefits". So we can mention equity and benefits.
Pay: salary range $150,000-180,000 + equity.
Schedule: About half the company works in the NYC office 3–4 days a week (hybrid). Could mention that.
We need to ensure we don't create sections with filler like "not specified". We have actual content.
Now produce HTML.
We'll wrap each section in
heading then content.
For lists, use - .
For prose, use
.
We must not include markdown fences.
Let's craft.
First, About the role:
About the Role
Insurance underwriting runs on human judgment, manual workflows, and knowledge locked in someone's head. It breaks when that person leaves and doesn't scale when the book doubles. Sixfold is building AI agents that understand risk the way a 20‑year veteran underwriter does—not summaries
for prose. Do not repeat job title. Do not include Job ID etc. Remove boilerplate. Must preserve all substantive info. We need to parse the posting: It's about a software engineer role at Sixfold. The content includes description of company, role, responsibilities, what success looks like, about you (requirements), additional info (salary, office, visa, etc). We need to extract sections. We should not include navigation, legal, EEO, etc. The posting includes "Moments We're Proud Of", "Our Commitment", etc. Those are likely boilerplate or not needed? The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. "Moments We're Proud Of" maybe not boilerplate but could be considered marketing; but it's substantive? Might be okay to keep? However they said "Prefer a few substantive sections over many thin ones." So we may combine. We need sections: About the role (maybe from "About The Role" paragraph). Responsibilities (list of duties). Requirements/Qualifications/Skills (maybe combine). Benefits, Pay, Schedule (if present). The posting includes "Expected salary: $150,000-180,000 + equity + benefits". Also mentions "About half the company works in the NYC office 3–4 days a week." That's schedule info (hybrid). Also "This position does not include visa sponsorship." That's maybe a note but not required. We need to include Pay section only if posting actually states them. Yes salary range given. Benefits: mention equity + benefits. Could also mention benefits generally. Schedule: mention hybrid office expectation. We need to avoid filler like "commensurate with experience". Not present. We need to preserve all substantive info; do not invent or summarize away detail. So we need to keep details like: building and delivering quality software, write/test/deploy code across full stack primarily TypeScript, build new product capabilities in TypeScript stack and contribute to Ruby/Python services, work on team-level projects applying engineering best practices, develop AI engineering expertise, learn ML principles, work with LLMs, integrate AI capabilities, collaborate with AI engineers on prompt engineering, model evaluation, responsible AI development, collaborate with cross-functional partners (PM, designers, engineers), work in two-week cycles, release to production at least once a week, own software through lifecycle, assess pressing problems, identify/design solutions, write technical specs, scope and break down projects, spend approx one week per quarter on call, etc. Also "What Success Looks Like" details for 30,60,90 days. About You: 3+ years professional software engineering experience, familiar with web dev using React and TypeScript, understand React component lifecycle, state management, performance optimization, leverage TypeScript type system, extra credit for generics, utility types, TailwindCSS, familiar with Node and PostgreSQL, know patterns to build features in TS app without significant learning time, extra credit for WebSocket frameworks or background job processing frameworks, experience designing and developing APIs (RESTful and/or GraphQL) with strong understanding of auth, authz, versioning best practices, can build/document APIs intuitive scalable easy to integrate, want to work in early-stage fast-growth tech company, comfortable with ambiguity and change, can own problems and proactively devise solutions, love communication collaboration execution, value meaningful commit messages and PR descriptions, prefer to merge PRs within a day, appreciate healthy engineering debates but know how to make pragmatic decisions, take feedback well and candid with feedback you give, have experience with agentic coding as default workflow, ship real feature work through Claude Code or Codex, orchestrate parallel agents, design specs and prompts as primary craft, intuition around evals, tool use, context engineering. Insurance/insurtech/enterprise B2B background a plus but not required. Additional Information: Expected salary: $150,000-180,000 + equity + benefits; Advertised and actual salary ranges may differ by geographic area, work experience, education, and/or skill level; About half the company works in the NYC office 3–4 days a week; This position does not include visa sponsorship. Candidates must be authorized to work in the United States without requiring employer sponsorship. We need to omit visa sponsorship note? It's substantive but maybe not needed for sections. Could be included in a short paragraph under Additional Information but we are told to drop minor metadata into a short
or drop it. Visa sponsorship is minor metadata; we could drop it. The salary and benefits and schedule are substantive for Pay/Benefits/Sections. We need to output only HTML fragment, no /, no markdown fences. We'll create sections:
About the Role
with prose summarizing the role description (maybe combine the initial paragraphs about Sixfold and role). But we must not repeat job title. We'll include description: "Insurance underwriting runs on human judgment... Sixfold is building AI agents...". That's about company; could be part of About the Role. Better: About the Role section includes the paragraph starting "About The Role As a software engineer at Sixfold, you will:" and the bullet list of responsibilities. We'll turn bullet list into- .
Responsibilities: maybe we separate responsibilities from About the Role? The instruction: Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have both About the role and Responsibilities sections. We'll need to split content. About the role: maybe a brief overview of the role and company. Responsibilities: list of duties. Requirements/Qualifications/Skills: we can combine into one section "Requirements" or separate. Since they ask for headings e.g. Requirements, Qualifications, Skills. We could have Requirements (experience), Qualifications (technical), Skills (soft skills). But we can also combine into one Requirements section to avoid thin sections. The instruction: Prefer a few substantive sections over many thin ones. So maybe we have one "Requirements" section that includes all. But we also need Benefits, Pay, Schedule sections if present. Thus final sections: About the role, Responsibilities, Requirements, Benefits, Pay, Schedule. We'll need to ensure we don't create empty sections. Let's craft content. About the role paragraph: combine company description and role overview. From posting: "Insurance underwriting runs on human judgment, manual workflows, and knowledge locked in someone's head. It breaks when that person leaves and doesn't scale when the book doubles. Sixfold is building AI agents that understand risk the way a 20-year veteran underwriter does. Not summaries or flags, but systems that make real decisions on billions in premium for some of the world's largest carriers. AI is the product and the workflow. In this role, you will build and run the cloud infrastructure, Kubernetes environments, deployment tooling, and observability systems that enable Sixfold's engineers to develop, release, and operate our products." Then "Who We Are" section includes product, team, traction. Could be part of About the role. We'll include that. Responsibilities: list from "About The Role As a software engineer at Sixfold, you will:" bullet points. Let's extract bullet points: - Build and deliver quality software. You will write, test, and deploy code across the full application stack, primarily using TypeScript. You will build new product capabilities in our TypeScript stack and contribute to established Ruby and Python services when needed. - You’ll work on team-level projects, applying engineering best practices and contributing to the team’s technical decision-making. - Develop AI engineering expertise. You'll have opportunities to learn and apply machine learning principles, work with large language models, and integrate AI capabilities into our products. You'll collaborate with our AI engineers to understand best practices for prompt engineering, model evaluation, and responsible AI development. - Collaborate with cross-functional partners. Our teams include product managers, designers, and engineers working together to accomplish shared goals. You will collaborate with these partners, beginning with problem discovery through solution design and delivery. We work in two-week cycles and release to production at least once a week. - Own your software through its entire lifecycle. In addition to shipping code, you will assess our most pressing product and engineering problems, identify and design solutions, write technical specs, and scope and break down projects. You will also spend approximately one week per quarter on call, serving as the first line of defense against service outages and critical bugs. If you don’t have experience with all of this yet, don’t worry - we’ll teach you! We can turn each bullet into
- .
Requirements: combine "About You" and maybe "Additional Information" (except salary/benefits/schedule). Also include "What Success Looks Like" maybe as part of expectations but could be included in Requirements? It's more about success metrics; maybe we could include in a separate section but to avoid thin sections we could incorporate into Requirements as expectations.
But we have separate sections for Benefits, Pay, Schedule. So Requirements will contain experience, technical skills, soft skills, agentic coding, etc.
Let's list requirements:
- 3+ years of professional software engineering experience.
- Familiar with web development using React and TypeScript; understand React's component lifecycle, state management patterns, performance optimization techniques; can leverage TypeScript's type system effectively to create maintainable, type-safe code. Extra credit if comfortable with generics, utility types, and TailwindCSS.
- Familiar with Node and PostgreSQL; know their patterns well enough to build features in a TypeScript app without significant learning time. Extra credit if you have experience with WebSocket frameworks or background job processing frameworks.
- Experience designing and developing APIs (RESTful and/or GraphQL) with a strong understanding of authentication, authorization, and versioning best practices. Can build and document APIs that are intuitive, scalable, and easy to integrate with.
- Want to work in an early-stage, fast-growth tech company; comfortable with ambiguity and change; can own problems and proactively devise solutions, not just wait for somebody to feed you tasks.
- Love communication, collaboration, and execution; value meaningful commit messages and pull request descriptions; prefer to merge PRs within a day; appreciate healthy engineering debates but know how to make pragmatic decisions; take feedback well and are candid with the feedback you give.
- Have experience with agentic coding as your default workflow; ship real feature work through Claude Code or Codex, orchestrate parallel agents, design specs and prompts as a primary craft, and have intuition around evals, tool use, and context engineering.
- Insurance, insurtech, or enterprise B2B background is a plus but not required.
We could also include the success timeline as expectations but maybe not needed.
Benefits: The posting mentions equity + benefits, but not detailed benefits. It says "Expected salary: $150,000-180,000 + equity + benefits". Also "Our comprehensive compensation package includes competitive salaries, equity opportunities, and robust benefits". So we can mention equity and benefits.
Pay: salary range $150,000-180,000 + equity.
Schedule: About half the company works in the NYC office 3–4 days a week (hybrid). Could mention that.
We need to ensure we don't create sections with filler like "not specified". We have actual content.
Now produce HTML.
We'll wrap each section in
heading then content. For lists, use
- .
For prose, use
. We must not include markdown fences. Let's craft. First, About the role:
About the Role
Insurance underwriting runs on human judgment, manual workflows, and knowledge locked in someone's head. It breaks when that person leaves and doesn't scale when the book doubles. Sixfold is building AI agents that understand risk the way a 20‑year veteran underwriter does—not summaries
- .
For prose, use