Product Operations Lead
for section headings (About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)
2. Use - for lists,
for prose
3. Do NOT repeat the job title as a heading
4. Do NOT put Job ID / requisition numbers as headings
5. Preserve ALL substantive information
6. Remove boilerplate (cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions)
7. Include a section ONLY when the posting has real, specific content for it
8. Never emit a heading followed by filler/placeholder text
9. Never create Pay/Schedule/Benefits sections unless the posting actually states them
10. Output ONLY the HTML fragment — no /, no markdown code fences
Let me analyze the job posting:
- Company info: "About Teal" - this is company background
- "The Opportunity" - this is about the role
- "What You'll Do:" - responsibilities
- "What We're Looking For:" - requirements/qualifications
- "Compensation:" - pay info
- "Location:" - schedule/location info
- EEO statement - boilerplate, remove
- JazzHR reference - boilerplate, remove
I need to structure this into appropriate sections. The posting has:
1. About the role (The Opportunity section)
2. Responsibilities (What You'll Do)
3. Requirements/Qualifications (What We're Looking For)
4. Pay (Compensation section)
5. Schedule/Location (Location section)
Benefits are mentioned briefly in Compensation: "comprehensive health benefits, and equity packages" - so I could include a Benefits section or fold into Pay. The rules say "never create Pay/Schedule/Benefits sections unless the posting actually states them" - it does state compensation and location, so those sections are warranted. Benefits are mentioned but briefly; I could include a Benefits section or combine with Pay. I'll create a Benefits section since it's mentioned.
I should not include the EEO statement or JazzHR code.
Now, let me write the HTML.
I'll use:
-
About the role
for "The Opportunity"
- Responsibilities
for "What You'll Do"
- Requirements
for "What We're Looking For"
- Pay
for "Compensation"
- Schedule
for "Location" (since it mentions in-office days)
- Benefits
for benefits mentioned
But note: The rules say "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". So I should use those exact headings where appropriate.
The posting has "What We're Looking For" which includes both requirements and qualifications. I'll use "Requirements" as heading.
Also, there's a "Software familiarity" list - that could be under Skills or Requirements. I'll include as part of Requirements.
Now, I need to preserve all substantive information. For lists, use - . For prose, use
.
Let me structure:
1. About the role: from "The Opportunity" paragraph(s)
2. Responsibilities: from "What You'll Do" - there are subsections: Product Operations Leadership, Owning the Product Operations Function, Owning Billing Configurations, Systems & Operations, Cross-Functional Reporting. I'll make a list of these duties.
3. Requirements: from "What We're Looking For" - list of bullet points.
4. Pay: from "Compensation" - includes salary range and note.
5. Benefits: from "Compensation" - health benefits, equity packages.
6. Schedule: from "Location" - Kirkland, WA, 2 days/week in person, limited travel.
I'll omit the company background "About Teal" as it's not about the role per se, but the rules say "Preserve ALL substantive information". However, the company description is not about the role; it's company info. The user said "reformat a job posting into clean, well-structured semantic HTML". The job posting includes "About Teal". Should I include it? The rules say "Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." Company background might be considered minor metadata? But it's substantive. However, the example headings don't include "About the company". The user might expect only role-related sections. I think I should include a brief company description under "About the role" or as a separate paragraph. But the rules say "include a section ONLY when the posting has real, specific content for it". The posting has "About Teal" which is company info. I could include it as a
under "About the role" or as a separate section. Since the heading "About the role" is for the role, not company. I'll include a brief company description as a
before the sections, or as part of "About the role". Let's see: The Opportunity starts with "We're looking for a Director of Product Operations...". The "About Teal" is separate. I'll include a short
at the beginning with company info, then the sections.
But the output should be only the HTML fragment. I'll start with a
for company overview, then sections.
Alternatively, I could make an "About the company" heading but not in the example list. The rules say "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It says "e.g.", so other headings are allowed? But they prefer those. I'll stick to the suggested headings.
I'll include company info as a
before the first heading.
Now, let's write the HTML.
Note: The responsibilities have sub-bullets. I'll flatten them into a single list or keep hierarchy? The rules say use
- for any list. I can use nested lists. But to keep simple, I'll make each top-level bullet a list item, and include sub-points as part of the same li or nested ul. I'll do nested ul for clarity.
Similarly for requirements.
Let's craft.
First, company paragraph:
Teal Communications, Inc. (“Teal”) is a high-growth technology company that builds cloud-native network software to connect Physical AI & IoT devices to data networks globally. Teal has been named to the Inc. 5000 and Deloitte Technology Fast 500 as one of the fastest-growing private companies in the United States (#1 in the Seattle metro area and #9 among U.S. software companies).
Then sections.
About the role:
About the role
We’re looking for a Director of Product Operations to shape the functional experience of our products to meet the needs of a high-growth customer base. The ideal candidate combines technical intuition with a data-oriented mindset and strong organizational skills. In this role, you will be the operational bridge between Product, Engineering, Finance, and our customers—turning product capabilities into repeatable, scalable processes so customers can launch quickly, devices connect reliably, and billing is accurate from day one. As Teal scales, you will build the systems, playbooks, and reporting that supports business growth while reducing friction. This role will report to our VP of Product, working closely with Teal’s VP of Engineering and Chief Executive Officer. You will also partner day to day with Customer Success, Sales, and Finance to make sure products are implemented, provisioned, and billed smoothly at scale.
Responsibilities:
Responsibilities
- Product Operations Leadership: Lead and develop the Product Operations team, including a Product Operations Manager and a team of individual contributors—setting priorities, defining clear ownership, coaching for growth, and building a high-performing, accountable culture.
- Owning the Product Operations Function:
- Streamline and manage customer implementation, owning the end-to-end onboarding process from signed contract to first live device and reducing time-to-launch through standardized playbooks and automation.
- Identify recurring operational friction points and partner with Product and Engineering to prioritize fixes and improvements on the roadmap.
- Support provisioning of eUICC cards and chips, coordinating with suppliers, carriers, and internal teams so inventory, profiles, and activations are delivered accurately and on schedule.
- Owning Billing Configurations: Own customer billing configuration in Teal’s bespoke product backend (BSS), ensuring pricing plans, rate structures, and usage data are set up correctly, so customers are invoiced accurately and on time.
- Systems & Operations: Build the processes and tooling the team runs on: document operating procedures, set service-level standards, and select or build internal tools that let the team scale as customer volume grows.
- Cross-Functional Reporting:
- Compile executive reports and dashboards that track key operational metrics—such as implementation timelines, device activations, connectivity usage, and billing accuracy—and surface insights that inform leadership decisions.
- Collaborate with finance and business team on structuring internal information for finance stakeholders or external customer presentations.
Requirements:
Requirements
- 5+ years of product operations experience in telecommunications software, ideally in connectivity, Physical AI, IoT, or SaaS environments.
- 5 years of telecommunications business operations experience, with exposure to areas such as carrier relationships, provisioning, or billing and revenue operations.
- Proven experience leading and developing teams.
- Strong analytical skills and comfort working hands-on with data; able to write queries, build reports, and turn findings into clear recommendations.
- Excellent written and verbal communication skills, with the ability to present to executives and work effectively across technical and non-technical teams.
- Technical project management certification (e.g., PMP or Agile/Scrum) or equivalent hands-on experience.
- Familiarity with eSIM/eUICC technology, mobile network operations, or BSS/OSS systems is a strong plus.
- Software familiarity: Excel, Claude, Databricks, Superset, MySQL.
Pay:
Pay
Total target compensation range is $100,000-200,000 depending on experience. Actual compensation will depend on experience, skills, and other job-related factors.
Benefits:
Benefits
Teal offers competitive salaries, comprehensive health benefits, and equity packages.
Schedule:
Schedule
Location: Kirkland, Washington. This role is expected to work closely with the team from our Kirkland headquarters at least two days per week in person, with limited travel as needed.
I should not include the EEO statement or JazzHR code.
Now, check rules: "Do NOT repeat the job title as a heading" - I didn't. "Do NOT put Job ID / requisition numbers as headings" - there's a JazzHR code at end, I omitted. "Preserve ALL substantive information" - I think I did. "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." - removed EEO and JazzHR. "Include a section ONLY when the posting has real, specific content for it"
for prose 3. Do NOT repeat the job title as a heading 4. Do NOT put Job ID / requisition numbers as headings 5. Preserve ALL substantive information 6. Remove boilerplate (cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions) 7. Include a section ONLY when the posting has real, specific content for it 8. Never emit a heading followed by filler/placeholder text 9. Never create Pay/Schedule/Benefits sections unless the posting actually states them 10. Output ONLY the HTML fragment — no /, no markdown code fences Let me analyze the job posting: - Company info: "About Teal" - this is company background - "The Opportunity" - this is about the role - "What You'll Do:" - responsibilities - "What We're Looking For:" - requirements/qualifications - "Compensation:" - pay info - "Location:" - schedule/location info - EEO statement - boilerplate, remove - JazzHR reference - boilerplate, remove I need to structure this into appropriate sections. The posting has: 1. About the role (The Opportunity section) 2. Responsibilities (What You'll Do) 3. Requirements/Qualifications (What We're Looking For) 4. Pay (Compensation section) 5. Schedule/Location (Location section) Benefits are mentioned briefly in Compensation: "comprehensive health benefits, and equity packages" - so I could include a Benefits section or fold into Pay. The rules say "never create Pay/Schedule/Benefits sections unless the posting actually states them" - it does state compensation and location, so those sections are warranted. Benefits are mentioned but briefly; I could include a Benefits section or combine with Pay. I'll create a Benefits section since it's mentioned. I should not include the EEO statement or JazzHR code. Now, let me write the HTML. I'll use: -
About the role
for "The Opportunity" -Responsibilities
for "What You'll Do" -Requirements
for "What We're Looking For" -Pay
for "Compensation" -Schedule
for "Location" (since it mentions in-office days) -Benefits
for benefits mentioned But note: The rules say "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". So I should use those exact headings where appropriate.
The posting has "What We're Looking For" which includes both requirements and qualifications. I'll use "Requirements" as heading.
Also, there's a "Software familiarity" list - that could be under Skills or Requirements. I'll include as part of Requirements.
Now, I need to preserve all substantive information. For lists, use - . For prose, use
.
Let me structure:
1. About the role: from "The Opportunity" paragraph(s)
2. Responsibilities: from "What You'll Do" - there are subsections: Product Operations Leadership, Owning the Product Operations Function, Owning Billing Configurations, Systems & Operations, Cross-Functional Reporting. I'll make a list of these duties.
3. Requirements: from "What We're Looking For" - list of bullet points.
4. Pay: from "Compensation" - includes salary range and note.
5. Benefits: from "Compensation" - health benefits, equity packages.
6. Schedule: from "Location" - Kirkland, WA, 2 days/week in person, limited travel.
I'll omit the company background "About Teal" as it's not about the role per se, but the rules say "Preserve ALL substantive information". However, the company description is not about the role; it's company info. The user said "reformat a job posting into clean, well-structured semantic HTML". The job posting includes "About Teal". Should I include it? The rules say "Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." Company background might be considered minor metadata? But it's substantive. However, the example headings don't include "About the company". The user might expect only role-related sections. I think I should include a brief company description under "About the role" or as a separate paragraph. But the rules say "include a section ONLY when the posting has real, specific content for it". The posting has "About Teal" which is company info. I could include it as a
under "About the role" or as a separate section. Since the heading "About the role" is for the role, not company. I'll include a brief company description as a
before the sections, or as part of "About the role". Let's see: The Opportunity starts with "We're looking for a Director of Product Operations...". The "About Teal" is separate. I'll include a short
at the beginning with company info, then the sections.
But the output should be only the HTML fragment. I'll start with a
for company overview, then sections.
Alternatively, I could make an "About the company" heading but not in the example list. The rules say "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It says "e.g.", so other headings are allowed? But they prefer those. I'll stick to the suggested headings.
I'll include company info as a
before the first heading.
Now, let's write the HTML.
Note: The responsibilities have sub-bullets. I'll flatten them into a single list or keep hierarchy? The rules say use
- for any list. I can use nested lists. But to keep simple, I'll make each top-level bullet a list item, and include sub-points as part of the same li or nested ul. I'll do nested ul for clarity.
Similarly for requirements.
Let's craft.
First, company paragraph:
Teal Communications, Inc. (“Teal”) is a high-growth technology company that builds cloud-native network software to connect Physical AI & IoT devices to data networks globally. Teal has been named to the Inc. 5000 and Deloitte Technology Fast 500 as one of the fastest-growing private companies in the United States (#1 in the Seattle metro area and #9 among U.S. software companies).
Then sections.
About the role:
About the role
We’re looking for a Director of Product Operations to shape the functional experience of our products to meet the needs of a high-growth customer base. The ideal candidate combines technical intuition with a data-oriented mindset and strong organizational skills. In this role, you will be the operational bridge between Product, Engineering, Finance, and our customers—turning product capabilities into repeatable, scalable processes so customers can launch quickly, devices connect reliably, and billing is accurate from day one. As Teal scales, you will build the systems, playbooks, and reporting that supports business growth while reducing friction. This role will report to our VP of Product, working closely with Teal’s VP of Engineering and Chief Executive Officer. You will also partner day to day with Customer Success, Sales, and Finance to make sure products are implemented, provisioned, and billed smoothly at scale.
Responsibilities:
Responsibilities
- Product Operations Leadership: Lead and develop the Product Operations team, including a Product Operations Manager and a team of individual contributors—setting priorities, defining clear ownership, coaching for growth, and building a high-performing, accountable culture.
- Owning the Product Operations Function:
- Streamline and manage customer implementation, owning the end-to-end onboarding process from signed contract to first live device and reducing time-to-launch through standardized playbooks and automation.
- Identify recurring operational friction points and partner with Product and Engineering to prioritize fixes and improvements on the roadmap.
- Support provisioning of eUICC cards and chips, coordinating with suppliers, carriers, and internal teams so inventory, profiles, and activations are delivered accurately and on schedule.
- Owning Billing Configurations: Own customer billing configuration in Teal’s bespoke product backend (BSS), ensuring pricing plans, rate structures, and usage data are set up correctly, so customers are invoiced accurately and on time.
- Systems & Operations: Build the processes and tooling the team runs on: document operating procedures, set service-level standards, and select or build internal tools that let the team scale as customer volume grows.
- Cross-Functional Reporting:
- Compile executive reports and dashboards that track key operational metrics—such as implementation timelines, device activations, connectivity usage, and billing accuracy—and surface insights that inform leadership decisions.
- Collaborate with finance and business team on structuring internal information for finance stakeholders or external customer presentations.
Requirements:
Requirements
- 5+ years of product operations experience in telecommunications software, ideally in connectivity, Physical AI, IoT, or SaaS environments.
- 5 years of telecommunications business operations experience, with exposure to areas such as carrier relationships, provisioning, or billing and revenue operations.
- Proven experience leading and developing teams.
- Strong analytical skills and comfort working hands-on with data; able to write queries, build reports, and turn findings into clear recommendations.
- Excellent written and verbal communication skills, with the ability to present to executives and work effectively across technical and non-technical teams.
- Technical project management certification (e.g., PMP or Agile/Scrum) or equivalent hands-on experience.
- Familiarity with eSIM/eUICC technology, mobile network operations, or BSS/OSS systems is a strong plus.
- Software familiarity: Excel, Claude, Databricks, Superset, MySQL.
Pay:
Pay
Total target compensation range is $100,000-200,000 depending on experience. Actual compensation will depend on experience, skills, and other job-related factors.
Benefits:
Benefits
Teal offers competitive salaries, comprehensive health benefits, and equity packages.
Schedule:
Schedule
Location: Kirkland, Washington. This role is expected to work closely with the team from our Kirkland headquarters at least two days per week in person, with limited travel as needed.
I should not include the EEO statement or JazzHR code.
Now, check rules: "Do NOT repeat the job title as a heading" - I didn't. "Do NOT put Job ID / requisition numbers as headings" - there's a JazzHR code at end, I omitted. "Preserve ALL substantive information" - I think I did. "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." - removed EEO and JazzHR. "Include a section ONLY when the posting has real, specific content for it"
. Let me structure: 1. About the role: from "The Opportunity" paragraph(s) 2. Responsibilities: from "What You'll Do" - there are subsections: Product Operations Leadership, Owning the Product Operations Function, Owning Billing Configurations, Systems & Operations, Cross-Functional Reporting. I'll make a list of these duties. 3. Requirements: from "What We're Looking For" - list of bullet points. 4. Pay: from "Compensation" - includes salary range and note. 5. Benefits: from "Compensation" - health benefits, equity packages. 6. Schedule: from "Location" - Kirkland, WA, 2 days/week in person, limited travel. I'll omit the company background "About Teal" as it's not about the role per se, but the rules say "Preserve ALL substantive information". However, the company description is not about the role; it's company info. The user said "reformat a job posting into clean, well-structured semantic HTML". The job posting includes "About Teal". Should I include it? The rules say "Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." Company background might be considered minor metadata? But it's substantive. However, the example headings don't include "About the company". The user might expect only role-related sections. I think I should include a brief company description under "About the role" or as a separate paragraph. But the rules say "include a section ONLY when the posting has real, specific content for it". The posting has "About Teal" which is company info. I could include it as a
under "About the role" or as a separate section. Since the heading "About the role" is for the role, not company. I'll include a brief company description as a
before the sections, or as part of "About the role". Let's see: The Opportunity starts with "We're looking for a Director of Product Operations...". The "About Teal" is separate. I'll include a short
at the beginning with company info, then the sections. But the output should be only the HTML fragment. I'll start with a
for company overview, then sections. Alternatively, I could make an "About the company" heading but not in the example list. The rules say "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It says "e.g.", so other headings are allowed? But they prefer those. I'll stick to the suggested headings. I'll include company info as a
before the first heading. Now, let's write the HTML. Note: The responsibilities have sub-bullets. I'll flatten them into a single list or keep hierarchy? The rules say use
- for any list. I can use nested lists. But to keep simple, I'll make each top-level bullet a list item, and include sub-points as part of the same li or nested ul. I'll do nested ul for clarity.
Similarly for requirements.
Let's craft.
First, company paragraph:
Teal Communications, Inc. (“Teal”) is a high-growth technology company that builds cloud-native network software to connect Physical AI & IoT devices to data networks globally. Teal has been named to the Inc. 5000 and Deloitte Technology Fast 500 as one of the fastest-growing private companies in the United States (#1 in the Seattle metro area and #9 among U.S. software companies).
Then sections. About the role:About the role
We’re looking for a Director of Product Operations to shape the functional experience of our products to meet the needs of a high-growth customer base. The ideal candidate combines technical intuition with a data-oriented mindset and strong organizational skills. In this role, you will be the operational bridge between Product, Engineering, Finance, and our customers—turning product capabilities into repeatable, scalable processes so customers can launch quickly, devices connect reliably, and billing is accurate from day one. As Teal scales, you will build the systems, playbooks, and reporting that supports business growth while reducing friction. This role will report to our VP of Product, working closely with Teal’s VP of Engineering and Chief Executive Officer. You will also partner day to day with Customer Success, Sales, and Finance to make sure products are implemented, provisioned, and billed smoothly at scale.
Responsibilities:Responsibilities
- Product Operations Leadership: Lead and develop the Product Operations team, including a Product Operations Manager and a team of individual contributors—setting priorities, defining clear ownership, coaching for growth, and building a high-performing, accountable culture.
- Owning the Product Operations Function:
- Streamline and manage customer implementation, owning the end-to-end onboarding process from signed contract to first live device and reducing time-to-launch through standardized playbooks and automation.
- Identify recurring operational friction points and partner with Product and Engineering to prioritize fixes and improvements on the roadmap.
- Support provisioning of eUICC cards and chips, coordinating with suppliers, carriers, and internal teams so inventory, profiles, and activations are delivered accurately and on schedule.
- Owning Billing Configurations: Own customer billing configuration in Teal’s bespoke product backend (BSS), ensuring pricing plans, rate structures, and usage data are set up correctly, so customers are invoiced accurately and on time.
- Systems & Operations: Build the processes and tooling the team runs on: document operating procedures, set service-level standards, and select or build internal tools that let the team scale as customer volume grows.
- Cross-Functional Reporting:
- Compile executive reports and dashboards that track key operational metrics—such as implementation timelines, device activations, connectivity usage, and billing accuracy—and surface insights that inform leadership decisions.
- Collaborate with finance and business team on structuring internal information for finance stakeholders or external customer presentations.
Requirements
- 5+ years of product operations experience in telecommunications software, ideally in connectivity, Physical AI, IoT, or SaaS environments.
- 5 years of telecommunications business operations experience, with exposure to areas such as carrier relationships, provisioning, or billing and revenue operations.
- Proven experience leading and developing teams.
- Strong analytical skills and comfort working hands-on with data; able to write queries, build reports, and turn findings into clear recommendations.
- Excellent written and verbal communication skills, with the ability to present to executives and work effectively across technical and non-technical teams.
- Technical project management certification (e.g., PMP or Agile/Scrum) or equivalent hands-on experience.
- Familiarity with eSIM/eUICC technology, mobile network operations, or BSS/OSS systems is a strong plus.
- Software familiarity: Excel, Claude, Databricks, Superset, MySQL.
Pay
Total target compensation range is $100,000-200,000 depending on experience. Actual compensation will depend on experience, skills, and other job-related factors.
Benefits:Benefits
Teal offers competitive salaries, comprehensive health benefits, and equity packages.
Schedule:Schedule
Location: Kirkland, Washington. This role is expected to work closely with the team from our Kirkland headquarters at least two days per week in person, with limited travel as needed.
I should not include the EEO statement or JazzHR code. Now, check rules: "Do NOT repeat the job title as a heading" - I didn't. "Do NOT put Job ID / requisition numbers as headings" - there's a JazzHR code at end, I omitted. "Preserve ALL substantive information" - I think I did. "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." - removed EEO and JazzHR. "Include a section ONLY when the posting has real, specific content for it"