Staff Software Architect

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. We have: - About Taskrabbit: description of company, but not needed as a section? The instruction: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). The page already shows job title; we should not repeat job title as heading. We can include "About the role" heading if there is content. There's an "About the Role:" section with description. So we can put that under

About the role

with paragraphs. - Responsibilities: The bullet list under "You will be:" includes many responsibilities. So we can make a Responsibilities section with

• items. - Requirements: The "You should have:" list includes experience, etc. That's requirements. Also "Bonus Criteria:" could be considered qualifications or skills? Might be separate but we can include under Requirements or Qualifications. The instruction: prefer few substantive sections over many thin ones. We could combine Requirements and Qualifications into one? But they ask to use headings for those categories if content exists. We have both Requirements and Qualifications content. Could treat "You should have:" as Requirements, and "Bonus Criteria:" as Qualifications (or Skills). Also there is a list of specific tech skills (Kubernetes, NestJS, Helm charts, Spec-Driven Development tools, ArgoCD, Datadog, contract-first design using OpenAPI and AsyncAPI). Those could be Skills. - Benefits: The "You’ll love working here because:" includes bullet points about perks, health insurance, 401k match, time off, stipends, IKEA discounts, reproductive health support, etc. Also earlier "Compensation & Benefits:" includes description of total compensation and base pay range. So we have Pay and Benefits sections. - Pay: base pay range $150,000 - $200,000. Also mention total compensation consists of base pay + bonus + benefits + perks. So we can include Pay section with that info. - Schedule: The hybrid requirement: 2 days in office at SF hub every Tuesday & Wednesday. Also mention hybrid company. So we can include Schedule section with that. We must not include boilerplate like EEO, AI-Assisted Prescreening Notice, etc. Also remove duplicated lines, navigation, cookie/legal. Also remove "Prior to applying please note:" maybe part of schedule? It's about hybrid requirement. We'll keep that. We must not include sections with filler like "commensurate with experience". Not present. We must preserve all substantive information. So we need to include all details from the posting, but we can reorganize into sections. We must not invent or summarize away detail. So we need to keep specifics like "8+ years of professional experience in software development, with a primary focus on building and scaling backend systems." etc. We need to output only HTML fragment, no /, no markdown fences. Thus produce something like:

  About the role

  ...

  Responsibilities

  • Acting as the Architecture team's representative to assigned engineering teams, driving platform modernization projects in accordance with the TSA.
  ...

  Requirements

  • 8+ years of professional experience in software development, with a primary focus on building and scaling backend systems.
  ...

  Qualifications

  • Experience with Kubernetes (K8s).
  ...

  Skills

  • TypeScript/Node.js experience preferred; candidates with a background in another strongly typed language (e.g., Java, .NET) will also be considered.
  ...
  But note that some of those could overlap. We need to decide what goes where. Better to follow typical sections: About the role (description), Responsibilities (what you will do), Requirements (mandatory experience), Qualifications (bonus or preferred), Skills (specific tech skills), Benefits, Pay, Schedule. Let's extract content. About the role paragraph(s): The "About the Role:" block includes two paragraphs: first paragraph describing Architecture Team drives modernization, role as Staff Software Architect, etc. Second paragraph: "You will be:" then list. Actually the "You will be:" list is responsibilities. So we should separate: About the role: first paragraph up to "You will be:"? Let's capture: "The Architecture Team drives Taskrabbit's Platform Modernization efforts, guiding engineering teams toward our Target State Architecture (TSA). As a Staff Software Architect, you'll serve as an embedded representative of the Architecture team, partnering with engineering teams across the platform to accelerate their modernization work. You'll operate as a subject matter expert on platform modernization within a small team of architects, applying AI-assisted and Spec-Driven Development (SDD) practices to help teams build new components using our Target State Architecture stack of technologies. This role is hands-on and results-oriented: pairing directly with engineers and technical leads, not just advising from the sidelines." That's about the role. Then responsibilities list after "You will be:" includes many items. Thus we can put About the role as paragraphs (maybe two

  ). Responsibilities as

  • each item. Now Requirements: "You should have:" list includes: - 8+ years of professional experience in software development, with a primary focus on building and scaling backend systems. - Demonstrated experience with distributed systems and event-driven architecture. - TypeScript/Node.js experience preferred; candidates with a background in another strongly typed language (e.g., Java, .NET) will also be considered. - Experience with containerization and containerized application deployment. - An enthusiast for AI tooling and AI-assisted development practices, with a proven track record of applying them professionally. - Excellent communication skills, with the ability to build consensus and keep technical design discussions professional and productive, even when opinions differ strongly. - Willingness to lead, speak up, and be visible and vocal in Architecture and team design meetings. - Comfort pairing directly with engineers and technical leadership, not just producing documentation or recommendations. That's 8 items. Now Bonus Criteria: list: - Experience with Kubernetes (K8s). - Experience with the NestJS framework. - Experience designing or using Helm charts. - Experience with Spec-Driven Development tools such as SpecKit, OpenSpec, Intent, Kiro, or similar. - Experience with ArgoCD. - Experience with Datadog. - Experience with contract-first design using OpenAPI and AsyncAPI. These could be Qualifications or Skills. Since they are specific tech skills/experience, we could put them under Skills. But we also have a Skills section heading; we could put those there. However we also have TypeScript/Node.js experience etc already in Requirements; but that's okay. We could treat Requirements as mandatory, Qualifications as bonus (preferred). But the instruction says use headings for Qualifications if content exists. So we can have Qualifications for the bonus criteria. Skills could be maybe the specific technologies like TypeScript/Node.js, distributed systems, etc. But we already have those in Requirements. To avoid duplication, we could put the bonus criteria under Qualifications, and maybe not have a separate Skills section unless we have other skills not covered. However we have some skills like "Excellent communication skills" etc which are soft skills; could be under Requirements as well. Given the instruction to prefer few substantive sections over many thin ones, we could combine Qualifications and Skills into one section called "Qualifications & Skills". But they ask to use headings like Qualifications, Skills separately if content exists. However we can decide to only include sections that have real specific content; we could include Qualifications (bonus criteria) and maybe not include Skills if we feel it's redundant. But we have specific skills like TypeScript/Node.js, containerization, etc which are already in Requirements. So we could omit Skills section. But we need to ensure we preserve all substantive information. If we omit Skills heading, we still have the content elsewhere (in Requirements). That's fine. Thus sections: About the role, Responsibilities, Requirements, Qualifications (bonus), Benefits, Pay, Schedule. Now Benefits: We need to capture all benefits/perks described. From "You’ll love working here because:" includes: - Taskrabbit is a Hybrid Company. We value flexibility and choice but also stay committed to regular in-person connection. - The People. You will be surrounded by some of the most talented, supportive, smart, and kind leaders and teams -- people you can be proud to work with! - The Diverse Culture. We believe that we make better decisions when our workforce reflects the diversity of the communities in which we operate. Women make up half of our leadership team and our diversity representation is above that of the tech industry average. - The Perks. Taskrabbit offers our employees with employer-paid health insurance and a 401k match with immediate vesting for our US based employees. We offer all of our global employees generous and flexible time off with 2 company-wide closure weeks, Taskrabbit product stipends, wellness + productivity + education stipends, IKEA discounts, reproductive health support, and more. Benefits vary by country of employment. Also earlier "Compensation & Benefits:" includes description: total compensation consists of base pay + bonus + benefits + perks. The base pay range for this position is $150,000 - $200,000. This range is representative of base pay only, and does not include any other total cash compensation amounts, such as company bonus or benefits. Final offer amounts may vary from the amounts listed above and will be determined by factors including, but not limited to, relevant experience, qualifications, geography, and level. Thus Benefits section should include the perks and culture points. We could combine them into a Benefits section with paragraphs and maybe a list for perks. We need to avoid duplication: The "You’ll love working here because:" includes bullet-like paragraphs; we can turn each into

    or

  • . Probably better to use
    • for list of perks. But we also have culture points; could be paragraphs. We'll produce:

      Benefits

      Taskrabbit is a Hybrid Company. We value flexibility and choice but also stay committed to regular in-person connection.

      The People. You will be surrounded by some of the most talented, supportive, smart, and kind leaders and teams -- people you can be proud to work with!

      The Diverse Culture. We believe that we make better decisions when our workforce reflects the diversity of the communities in which we operate. Women make up half of our leadership team and our diversity representation is above that of the tech industry average.

      • Employer-paid health insurance and a 401k match with immediate vesting for US based employees.
      • Generous and flexible time off with 2 company-wide closure weeks.
      • Taskrabbit product stipends.
      • Wellness + productivity + education stipends.
      • IKEA discounts.
      • Reproductive health support.
      • Benefits vary by country of employment.
      Now Pay section: include base pay range and total compensation description.

      Pay

      Total compensation consists of base pay + bonus + benefits + perks. The base pay range for this position is $150,000 - $200,000. This range is representative of base pay only, and does not include any other total cash compensation amounts, such as company bonus or benefits. Final offer amounts may vary from the amounts listed above and will be determined by factors including, but not limited to, relevant experience, qualifications, geography, and level.

      Now Schedule section: hybrid requirement. From "Prior to applying please note: This role is hybrid requiring 2 days in office at our San Francisco hub every Tuesday & Wednesday (located at