Staff Software Engineer, Backend (Product)
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content.
We need to parse the posting.
Content:
- The Opportunity paragraph: description of role, responsibilities, impact. That's likely "About the role" or "Responsibilities". We need to decide.
We have sections: "Your Impact" bullet list. That's responsibilities/impact.
We have "We're Looking For Someone Who Has ..." bullet list: requirements/qualifications.
We have "Nice to haves ..." bullet list: nice-to-have skills.
We have "About Otter.ai" paragraph: company description.
We have "Salary range" with numbers: Pay section.
We have no explicit Benefits or Schedule.
Thus we will include sections: About the role (maybe overview), Responsibilities (Your Impact), Requirements (We're Looking For...), Nice to have (Nice to haves), About the company (About Otter.ai), Pay (Salary range). Possibly also Qualifications but we can combine Requirements.
We must not repeat job title as heading. No Job ID.
We must use for each section heading. Use - for any list of duties/requirements/benefits. Use
for prose.
We must preserve all substantive information, not invent or summarize away detail. Remove boilerplate: EEO, accessibility, accommodations, unsolicited resumes note, etc. Also remove "The Opportunity" heading? We need to include content but not as heading? The instruction: use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to decide headings based on content. The posting includes headings like "The Opportunity", "Your Impact", "We're Looking For Someone Who Has", "Nice to haves", "About Otter.ai", "Salary range". We can map those to our standard headings.
Thus:
- About the role: could be the introductory paragraph under "The Opportunity". We'll put that as About the role
then
... (the paragraph). Ensure we keep all sentences.
- Responsibilities: could be "Your Impact" bullet list. We'll put
Responsibilities
then - each bullet.
- Requirements: "We're Looking For Someone Who Has" bullet list. We'll put
Requirements
then - each bullet.
- Skills: maybe "Nice to haves" as Skills? Or we could have a separate "Nice-to-have Skills" but instruction says use Skills heading for skills. We'll put
Skills
then - each nice-to-have.
- About the company: "About Otter.ai" paragraph. Use
About the company
maybe but instruction list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. No About the company. However we could put it under About the role? But we already used About the role for intro. Could we add a section "About Otter.ai" as a heading? Not in list but maybe allowed? The instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). The "e.g." suggests those are examples, not exhaustive. But they say "Prefer a few substantive sections over many thin ones." Might be okay to add About Otter.ai as a section. However they said "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It implies those are typical headings; we can still use others if needed. Safer to include About Otter.ai as a section with heading About Otter.ai
. It's substantive.
- Pay: Salary range. Use Pay
then
with the salary range text.
We must not include Benefits or Schedule as they are not present.
We must remove boilerplate: EEO, accessibility, accommodations, unsolicited resumes note. Also remove "The Opportunity" heading? We'll not output that heading; we will output content under About the role.
We must preserve all substantive information: ensure we keep all bullet points exactly.
Let's extract text.
The Opportunity paragraph:
"The Opportunity We’re building the next generation of AI-native product experiences, where conversations turn directly into outcomes. As a Staff Software Engineer on our Product teams, you’ll define how these capabilities are translated into scalable systems and cohesive product experiences. You’ll operate across the full lifecycle of AI-driven features—from data ingestion and model orchestration to output structuring and delivery into user-facing product surfaces—but at a systems level. This includes shaping the architecture behind generation pipelines, defining how AI outputs are structured and persisted, and ensuring these systems are reliable, performant, and adaptable as both product requirements and underlying models evolve. This role goes beyond individual features. You’ll drive technical direction across product areas, aligning product, AI, and infrastructure teams on how to build AI-native systems that scale. You’ll help define patterns for how we evaluate, iterate on, and continuously improve AI-driven experiences, turning ambiguous opportunities into clear systems and execution plans. You’ll partner closely with product, design, and AI teams to identify high-leverage opportunities, prototype new approaches, and guide them into production—shaping both the product experience and the underlying systems that power it."
We need to keep that as a single paragraph? Could split into multiple
but instruction: use
for prose. Could keep as one
. Ensure we keep all sentences.
Your Impact bullet list:
- Define system architecture for AI-native product surfaces
- Design foundational systems (generation pipelines, data models, evaluation frameworks) that power multiple product areas.
- Drive cross-team technical strategy
Lead initiatives that span product, AI, and infrastructure teams, ensuring alignment on architecture and execution.
- Establish best practices for AI product engineering
Set standards for how we build with AI—covering areas like evaluation, reliability, iteration loops, and system design.
- Translate ambiguity into scalable systems and product direction
Take loosely defined opportunities and turn them into clear technical approaches and execution plans.
- Raise the bar across the organization
Influence engineering quality, system design, and product thinking beyond your immediate team.
- Shape how AI accelerates engineering velocity
Drive adoption and best practices for AI-assisted development, improving how teams design, build, and iterate on product.
Note formatting: some bullets have line breaks. We'll combine each bullet into a single
- preserving the text.
We need to ensure we keep the exact phrasing.
Let's copy each bullet exactly as in text:
"Define system architecture for AI-native product surfaces"
"Design foundational systems (generation pipelines, data models, evaluation frameworks) that power multiple product areas."
"Drive cross-team technical strategy
Lead initiatives that span product, AI, and infrastructure teams, ensuring alignment on architecture and execution."
"Establish best practices for AI product engineering
Set standards for how we build with AI—covering areas like evaluation, reliability, iteration loops, and system design."
"Translate ambiguity into scalable systems and product direction
Take loosely defined opportunities and turn them into clear technical approaches and execution plans."
"Raise the bar across the organization
Influence engineering quality, system design, and product thinking beyond your immediate team."
"Shape how AI accelerates engineering velocity
Drive adoption and best practices for AI-assisted development, improving how teams design, build, and iterate on product."
We'll keep line breaks inside
- maybe as space.
We can replace newline with space.
Now Requirements bullet list:
"We're Looking For Someone Who Has
10+ years of experience building and scaling complex systems
Has a strong track record of owning technical and product direction for large or ambiguous problem spaces
Demonstrates deep expertise in system design, especially in data-intensive or distributed systems
Has experience leading cross-team initiatives and influencing without direct authority
Brings strong product intuition and can balance user experience, system constraints, and business impact
Is comfortable operating at a high level of ambiguity and defining both the problem and the solution"
We need to keep each as separate
- . The first line "We're Looking For Someone Who Has" is like a heading; but we will treat as part of list? Actually it's a sentence introducing list. We could keep it as a
before list, but instruction: use
- for any list of duties/requirements/benefits. The list items are the bullet points after that. The introductory sentence could be a
. We'll keep it as a
before the list.
Thus:
We're Looking For Someone Who Has
- 10+ years of experience building and scaling complex systems
- Has a strong track record of owning technical and product direction for large or ambiguous problem spaces
- Demonstrates deep expertise in system design, especially in data-intensive or distributed systems
- Has experience leading cross-team initiatives and influencing without direct authority
- Brings strong product intuition and can balance user experience, system constraints, and business impact
- Is comfortable operating at a high level of ambiguity and defining both the problem and the solution
Now Nice to haves bullet list:
"Nice to haves
Experience building or experimenting with LLM-powered features (prompting, evaluation, RAG, etc.)
Experience designing systems that balance latency, cost, and quality
Exposure to user feedback loops, experimentation, or evaluation frameworks"
We'll treat similarly: Nice to haves
then items.
Now About Otter.ai paragraph:
"About Otter.ai
We are in the business of shaping the future of work. Our mission is to make conversations more valuable. With over 1B meetings transcribed, Otter.ai is the world’s leading tool for meeting transcription, summarization, and collaboration. Using artificial intelligence, Otter generates real-time automated meeting notes, summaries, and other insights from in-person and virtual meetings - turning meetings into accessible, collaborative, and actionable data that can be shared across teams and organizations. The company is backed by early investors in Google, DeepMind, Zoom, and Tesla."
We need to keep that as prose. Could be About Otter.ai
then ... (the paragraph after the heading). The heading "About Otter.ai" is part of the posting; we could treat it as heading but we already using
for section headings. We could either keep the heading as part of About Otter.ai
and then paragraph after. That seems fine.
Now Salary range:
"Salary range
Salary Range: $210,000 to $275,000 USD per year. This salary range represents the low and high end of the estimated salary range for this position. The actual base salary offered for the role is dependent on several factors. Our base salary is just one component of a comprehensive total rewards package."
We'll put Pay
then
... (the salary range text). Note we should not include the heading "Salary range" as separate; we incorporate into Pay section.
Now we must remove boilerplate: The paragraphs about equal opportunity employer, accessibility & accommodations, unsolicited resumes. We'll omit.
Now ensure we don't repeat job title as heading. Not present.
Now output only HTML fragment.
Let's construct:
About the role
The Opportunity We’re building the next generation of AI-native product experiences, where conversations turn directly into outcomes. As a Staff Software Engineer on our Product teams, you’ll define how these capabilities are translated into scalable systems and cohesive product experiences. You’ll operate across the full lifecycle of AI-driven features—from data ingestion and model orchestration to output structuring and delivery into user-facing product surfaces—but at
- for any list of duties/requirements/benefits. Use
for prose. We must preserve all substantive information, not invent or summarize away detail. Remove boilerplate: EEO, accessibility, accommodations, unsolicited resumes note, etc. Also remove "The Opportunity" heading? We need to include content but not as heading? The instruction: use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to decide headings based on content. The posting includes headings like "The Opportunity", "Your Impact", "We're Looking For Someone Who Has", "Nice to haves", "About Otter.ai", "Salary range". We can map those to our standard headings. Thus: - About the role: could be the introductory paragraph under "The Opportunity". We'll put that as
About the role
then... (the paragraph). Ensure we keep all sentences. - Responsibilities: could be "Your Impact" bullet list. We'll put
Responsibilities
then- each bullet.
- Requirements: "We're Looking For Someone Who Has" bullet list. We'll put
Requirements
then- each bullet.
- Skills: maybe "Nice to haves" as Skills? Or we could have a separate "Nice-to-have Skills" but instruction says use Skills heading for skills. We'll put
Skills
then- each nice-to-have.
- About the company: "About Otter.ai" paragraph. Use
About the company
maybe but instruction list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. No About the company. However we could put it under About the role? But we already used About the role for intro. Could we add a section "About Otter.ai" as a heading? Not in list but maybe allowed? The instruction says usefor section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). The "e.g." suggests those are examples, not exhaustive. But they say "Prefer a few substantive sections over many thin ones." Might be okay to add About Otter.ai as a section. However they said "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It implies those are typical headings; we can still use others if needed. Safer to include About Otter.ai as a section with heading
About Otter.ai
. It's substantive. - Pay: Salary range. UsePay
thenwith the salary range text. We must not include Benefits or Schedule as they are not present. We must remove boilerplate: EEO, accessibility, accommodations, unsolicited resumes note. Also remove "The Opportunity" heading? We'll not output that heading; we will output content under About the role. We must preserve all substantive information: ensure we keep all bullet points exactly. Let's extract text. The Opportunity paragraph: "The Opportunity We’re building the next generation of AI-native product experiences, where conversations turn directly into outcomes. As a Staff Software Engineer on our Product teams, you’ll define how these capabilities are translated into scalable systems and cohesive product experiences. You’ll operate across the full lifecycle of AI-driven features—from data ingestion and model orchestration to output structuring and delivery into user-facing product surfaces—but at a systems level. This includes shaping the architecture behind generation pipelines, defining how AI outputs are structured and persisted, and ensuring these systems are reliable, performant, and adaptable as both product requirements and underlying models evolve. This role goes beyond individual features. You’ll drive technical direction across product areas, aligning product, AI, and infrastructure teams on how to build AI-native systems that scale. You’ll help define patterns for how we evaluate, iterate on, and continuously improve AI-driven experiences, turning ambiguous opportunities into clear systems and execution plans. You’ll partner closely with product, design, and AI teams to identify high-leverage opportunities, prototype new approaches, and guide them into production—shaping both the product experience and the underlying systems that power it." We need to keep that as a single paragraph? Could split into multiple
but instruction: use
for prose. Could keep as one
. Ensure we keep all sentences. Your Impact bullet list: - Define system architecture for AI-native product surfaces - Design foundational systems (generation pipelines, data models, evaluation frameworks) that power multiple product areas. - Drive cross-team technical strategy Lead initiatives that span product, AI, and infrastructure teams, ensuring alignment on architecture and execution. - Establish best practices for AI product engineering Set standards for how we build with AI—covering areas like evaluation, reliability, iteration loops, and system design. - Translate ambiguity into scalable systems and product direction Take loosely defined opportunities and turn them into clear technical approaches and execution plans. - Raise the bar across the organization Influence engineering quality, system design, and product thinking beyond your immediate team. - Shape how AI accelerates engineering velocity Drive adoption and best practices for AI-assisted development, improving how teams design, build, and iterate on product. Note formatting: some bullets have line breaks. We'll combine each bullet into a single
- preserving the text. We need to ensure we keep the exact phrasing. Let's copy each bullet exactly as in text: "Define system architecture for AI-native product surfaces" "Design foundational systems (generation pipelines, data models, evaluation frameworks) that power multiple product areas." "Drive cross-team technical strategy Lead initiatives that span product, AI, and infrastructure teams, ensuring alignment on architecture and execution." "Establish best practices for AI product engineering Set standards for how we build with AI—covering areas like evaluation, reliability, iteration loops, and system design." "Translate ambiguity into scalable systems and product direction Take loosely defined opportunities and turn them into clear technical approaches and execution plans." "Raise the bar across the organization Influence engineering quality, system design, and product thinking beyond your immediate team." "Shape how AI accelerates engineering velocity Drive adoption and best practices for AI-assisted development, improving how teams design, build, and iterate on product." We'll keep line breaks inside
- maybe as space. We can replace newline with space. Now Requirements bullet list: "We're Looking For Someone Who Has 10+ years of experience building and scaling complex systems Has a strong track record of owning technical and product direction for large or ambiguous problem spaces Demonstrates deep expertise in system design, especially in data-intensive or distributed systems Has experience leading cross-team initiatives and influencing without direct authority Brings strong product intuition and can balance user experience, system constraints, and business impact Is comfortable operating at a high level of ambiguity and defining both the problem and the solution" We need to keep each as separate
- . The first line "We're Looking For Someone Who Has" is like a heading; but we will treat as part of list? Actually it's a sentence introducing list. We could keep it as a
before list, but instruction: use
- for any list of duties/requirements/benefits. The list items are the bullet points after that. The introductory sentence could be a
. We'll keep it as a
before the list. Thus:
We're Looking For Someone Who Has
- 10+ years of experience building and scaling complex systems
- Has a strong track record of owning technical and product direction for large or ambiguous problem spaces
- Demonstrates deep expertise in system design, especially in data-intensive or distributed systems
- Has experience leading cross-team initiatives and influencing without direct authority
- Brings strong product intuition and can balance user experience, system constraints, and business impact
- Is comfortable operating at a high level of ambiguity and defining both the problem and the solution
Nice to haves
then- items.
Now About Otter.ai paragraph:
"About Otter.ai
We are in the business of shaping the future of work. Our mission is to make conversations more valuable. With over 1B meetings transcribed, Otter.ai is the world’s leading tool for meeting transcription, summarization, and collaboration. Using artificial intelligence, Otter generates real-time automated meeting notes, summaries, and other insights from in-person and virtual meetings - turning meetings into accessible, collaborative, and actionable data that can be shared across teams and organizations. The company is backed by early investors in Google, DeepMind, Zoom, and Tesla."
We need to keep that as prose. Could be
About Otter.ai
then... (the paragraph after the heading). The heading "About Otter.ai" is part of the posting; we could treat it as heading but we already using
for section headings. We could either keep the heading as part of
About Otter.ai
and then paragraph after. That seems fine. Now Salary range: "Salary range Salary Range: $210,000 to $275,000 USD per year. This salary range represents the low and high end of the estimated salary range for this position. The actual base salary offered for the role is dependent on several factors. Our base salary is just one component of a comprehensive total rewards package." We'll putPay
then... (the salary range text). Note we should not include the heading "Salary range" as separate; we incorporate into Pay section. Now we must remove boilerplate: The paragraphs about equal opportunity employer, accessibility & accommodations, unsolicited resumes. We'll omit. Now ensure we don't repeat job title as heading. Not present. Now output only HTML fragment. Let's construct:
About the role
The Opportunity We’re building the next generation of AI-native product experiences, where conversations turn directly into outcomes. As a Staff Software Engineer on our Product teams, you’ll define how these capabilities are translated into scalable systems and cohesive product experiences. You’ll operate across the full lifecycle of AI-driven features—from data ingestion and model orchestration to output structuring and delivery into user-facing product surfaces—but at
- for any list of duties/requirements/benefits. The list items are the bullet points after that. The introductory sentence could be a
- each nice-to-have.
- About the company: "About Otter.ai" paragraph. Use
- each bullet.
- Skills: maybe "Nice to haves" as Skills? Or we could have a separate "Nice-to-have Skills" but instruction says use Skills heading for skills. We'll put
- each bullet.
- Requirements: "We're Looking For Someone Who Has" bullet list. We'll put