Software Engineer in Test

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, maybe Benefits, etc. Must not repeat job title as heading. Must include only sections with real content. Must not include boilerplate like application instructions, etc. Must preserve all substantive info. We need to extract content: From posting: - Intro: "All roles San Francisco, CA Software Engineer in Test San Francisco, CAFull-timeMid-levelOn-site Zof AI is hiring for this role in San Francisco, CA. This is a full-time opportunity for candidates who want to contribute directly to the development of ambitious AI products in a high-performance environment. Must work with AI agents daily to write, maintain, and scale test coverage. Compensation Competitive salary Plus meaningful equity Apply for this role" But we should not include "Apply for this role" etc. Also we should not include compensation if it's vague? It says "Compensation Competitive salary Plus meaningful equity". That's actual compensation info, so we can include a Pay section? The rule: include Pay section only if posting actually states them. It does state "Competitive salary Plus meaningful equity". That's specific enough? It's not a number but it's still content. Should we include? The rule says: 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. Here they state "Competitive salary Plus meaningful equity". That's not placeholder; it's actual statement. So we can include Pay section with that sentence. But also they have "Benefits may depend on role and final offer terms." That's vague; maybe not include Benefits section because it's not specific. They also list "What we provide in San Francisco" with items: MacBook Pro, Premium AI development tools Cursor Ultra, Claude Code Ultra, OpenAI Codex Max or equivalent advanced AI tooling, Access to a high-performance AI product environment, Close collaboration with leadership, engineering, and customers, Opportunity to work in the San Francisco AI ecosystem, Wellness and productivity support where applicable, Competitive startup environment, High ownership, Direct product impact. That's benefits-like content. Could be considered Benefits section. The rule: include Benefits section only if posting actually states them. They do list benefits. So we can include Benefits section with those items as list. Also there is "Schedule"? Not mentioned. So no Schedule. We need sections: About the role (maybe "About This Role" heading). Responsibilities, Requirements, Benefits, Pay. Possibly also "Qualifications"? Not separate; requirements cover. We must not repeat job title as heading. So headings: About the role, Responsibilities, Requirements, Benefits, Pay. We need to use

for section headings. Use

• for any list of duties/requirements/benefits. Use

  for prose. We must preserve ALL substantive information; do not invent or summarize away detail. Let's extract substantive content: About the role paragraph: "Zof AI is seeking a Software Engineer in Test to bring real test-engineering craft to the agent fleets that find, reproduce, and remediate defects in customer codebases. This role owns the practice our product automates: framework design, flake elimination, coverage strategy, and CI gates that engineering teams actually trust. If you have worked as an SDET, Test Automation Engineer, Quality Engineer, or Software Engineer in Test, this is that discipline at Zof AI. The ideal candidate has built suites that held up against messy real codebases and wants to encode that judgment into agents doing the same work at scale." That's the About This Role. Responsibilities list: - Design and maintain end-to-end test frameworks in Playwright, Cypress, or Selenium. - Build unit and integration coverage using pytest, Jest, and similar tooling. - Hunt down and eliminate flaky tests so the suite stays trustworthy. - Own coverage strategy across the unit, integration, and end-to-end layers. - Wire suites into CI with gates that block real defects before release. - Reproduce reported bugs as tight, deterministic failing tests. - Teach our agent fleets how a strong test engineer reasons and works. - Partner with engineering and product to raise the bar on what ships. Requirements list: - Experience writing automated tests for production software. - Working knowledge of a browser automation framework such as Playwright, Cypress, or Selenium. - Ability to write clean code in a language like Python, TypeScript, or Java. - Understanding of CI pipelines and how tests gate a release. - Instinct for the difference between a real failure and a flaky one. - Comfort reading unfamiliar code well enough to test it. - Clear written and verbal communication. - Comfort operating in a fast-moving environment. Nice to have list (maybe could be included under Requirements? But they are separate "Nice to have". Could be part of Requirements as additional but we could include as part of Requirements? The rule: Use

  • for any list of duties/requirements/benefits. So we could include Nice to have as part of Requirements list, but maybe better to keep as separate? The heading "Requirements" could encompass both required and nice-to-have? Might be okay to include them all under Requirements. However we must preserve all substantive info; we can include them as part of Requirements list. Nice to have items: - Experience building test infrastructure, fixtures, or test data tooling. - Experience testing APIs, mobile apps, or performance and load scenarios. - Experience defining quality metrics and reporting them to engineering leadership. - Experience with eval or benchmark harnesses for AI systems. Also there is a list of keywords: "QA AutomationTest EngineeringPlaywrightCISDET". That seems like tags; maybe not needed. Benefits list from "What we provide in San Francisco": - MacBook Pro - Premium AI development tools Cursor Ultra - Claude Code Ultra - OpenAI Codex Max or equivalent advanced AI tooling - Access to a high-performance AI product environment - Close collaboration with leadership, engineering, and customers - Opportunity to work in the San Francisco AI ecosystem - Wellness and productivity support where applicable - Competitive startup environment - High ownership - Direct product impact Also maybe "Benefits may depend on role and final offer terms." That's vague; we can omit as not specific. Pay: "Competitive salary Plus meaningful equity" We should not include location, schedule, etc. We must not include application instructions, forms, etc. Thus final HTML:

    About the role

    Zof AI is seeking a Software Engineer in Test to bring real test-engineering craft to the agent fleets that find, reproduce, and remediate defects in customer codebases. This role owns the practice our product automates: framework design, flake elimination, coverage strategy, and CI gates that engineering teams actually trust. If you have worked as an SDET, Test Automation Engineer, Quality Engineer, or Software Engineer in Test, this is that discipline at Zof AI. The ideal candidate has built suites that held up against messy real codebases and wants to encode that judgment into agents doing the same work at scale.

    Responsibilities

    • Design and maintain end-to-end test frameworks in Playwright, Cypress, or Selenium.
    • Build unit and integration coverage using pytest, Jest, and similar tooling.
    • Hunt down and eliminate flaky tests so the suite stays trustworthy.
    • Own coverage strategy across the unit, integration, and end-to-end layers.
    • Wire suites into CI with gates that block real defects before release.
    • Reproduce reported bugs as tight, deterministic failing tests.
    • Teach our agent fleets how a strong test engineer reasons and works.
    • Partner with engineering and product to raise the bar on what ships.

    Requirements

    • Experience writing automated tests for production software.
    • Working knowledge of a browser automation framework such as Playwright, Cypress, or Selenium.
    • Ability to write clean code in a language like Python, TypeScript, or Java.
    • Understanding of CI pipelines and how tests gate a release.
    • Instinct for the difference between a real failure and a flaky one.
    • Comfort reading unfamiliar code well enough to test it.
    • Clear written and verbal communication.
    • Comfort operating in a fast-moving environment.
    • Experience building test infrastructure, fixtures, or test data tooling.
    • Experience testing APIs, mobile apps, or performance and load scenarios.
    • Experience defining quality metrics and reporting them to engineering leadership.
    • Experience with eval or benchmark harnesses for AI systems.

    Benefits

    • MacBook Pro
    • Premium AI development tools Cursor Ultra
    • Claude Code Ultra
    • OpenAI Codex Max or equivalent advanced AI tooling
    • Access to a high-performance AI product environment
    • Close collaboration with leadership, engineering, and customers
    • Opportunity to work in the San Francisco AI ecosystem
    • Wellness and productivity support where applicable
    • Competitive startup environment
    • High ownership
    • Direct product impact

    Pay

    Competitive salary Plus meaningful equity

    Check: Did we include all substantive info? We omitted the line "Compensation Competitive salary Plus meaningful equity Apply for this role" but we captured compensation. We omitted "All roles San Francisco, CA Software Engineer in Test San Francisco, CAFull-timeMid-levelOn-site Zof AI is hiring for this role in San Francisco, CA. This is a full-time opportunity for candidates who want to contribute directly to the development of ambitious AI products in a high-performance environment. Must work with AI agents daily to write, maintain, and scale test coverage." That's some substantive info about location, full-time, onsite, mid-level, must work with AI agents daily. Should we include that? The rule: preserve ALL substantive information. That includes location, employment type, level, onsite, must work with AI agents daily. We have not included that. We need to incorporate that info somewhere. Perhaps we can add a short paragraph under About the role or a separate section like "Role overview". But we must not create a heading for job title. We could add a paragraph after About the role that includes those details. However the rule says: Use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we could add a section like "Overview" but not in the list? The list includes examples but not exclusive. It says use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It implies we should use those headings when appropriate, but we could also use other headings? Probably better to stick to those given headings. The info about full-time, onsite, mid-level, location, must work with AI agents daily could be placed in About the role paragraph. We can augment the About the role paragraph to include those details. Thus modify About the role paragraph to include: "This is a full-time, mid-level, on-site role in San Francisco, CA. You will work with AI agents daily to write, maintain, and scale test coverage." Combine with existing description. Let's craft: "Zof AI is seeking a Software Engineer in Test to bring real test-engineering craft to the agent fleets that find, reproduce, and remediate defects in customer codebases. This is a full-time, mid-level, on-site role in San Francisco, CA where you will work with AI agents daily to write, maintain, and scale test coverage. This role owns the practice our product automates: framework design