Service Operations Program Lead
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat the job title as a heading. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — 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. Prefer a few substantive sections over many thin ones.
We need to include sections only if there is real specific content.
Let's parse the posting:
- Intro paragraph: mission, organization, seeking organized and proactive Service Operations Program Lead... This could be "About the role" or maybe "Overview". We can use "About the role" heading.
- Essential Functions And Responsibilities: a long list of responsibilities. That's a section "Responsibilities". Should be a list.
- Education And Experience: qualifications. Could be "Qualifications" or "Requirements". We'll use "Qualifications". It includes bullet-like sentences but not explicit list. We can convert to
- .
- Physical Requirements: mention flexible hours, location, travel. Could be "Schedule" or "Location". The instruction says we can have Schedule section if posting actually states them. It mentions "Must be flexible in working hours as this position may require customer support during non-regular business hours" and "Location: San Diego - onsite" and "Travel Up to 10%". That's schedule/location info. Could be under "Schedule" or maybe "Location". Since they gave schedule heading example, we can use "Schedule" for flexible hours and travel. But also location is not schedule. Could combine location into a short
maybe under "About the role". However they said we can fold minor metadata into a short
or drop it. Location is maybe minor metadata. Travel up to 10% could be schedule.
- Job Type Full-time, Exempt: that's schedule/type. Could be part of Schedule.
- Base Compensation Pay Range $97,000 - $118,000: That's Pay. So we need a Pay section.
- Benefits: "In addition to base compensation noted above, you will be eligible for stock options, discretionary annual bonus, no cost health insurance plans, 401k with company match, and flexible paid time off." That's Benefits.
- EEO statement: remove.
Thus we have sections: About the role (intro), Responsibilities, Qualifications (Education And Experience), Benefits, Pay, Schedule (flexible hours, location, travel, job type). Possibly also "Requirements" but we used Qualifications.
We must not repeat job title as heading. Good.
We must not include duplicated lines. Ensure we preserve all substantive info.
We need to format responsibilities as
- . The responsibilities list is long; we need to break into items. The text includes many sentences separated by periods. We'll need to parse into logical items. Could keep each sentence as a list item. Ensure we don't lose any detail.
Let's extract responsibilities paragraph:
"Own the Global Service & Support operating cadence, including Sprint Release Updates, Manager Service Ops Syncs, Office Hours, and Global Service & Support (GSS) Monthly meetings. Drive agenda development, action tracking, decision documentation, Jira-Commercial Operations Management (COPM) review, and follow-through across stakeholdersOwn Service & Support release readiness and communications for system and process changes, including SFDC release communications, stakeholder readiness, UAT coordination, and post-release follow-upRun the GSS Monthly process end-to-end, from Teams thread and shared deck to recording and recap summaryOwn Service Operations demand intake and portfolio management through Jira-COPM, including triage, business requirements, prioritization recommendations, assignment, dependencies, sprint readiness, escalation, and status reporting. Partner with Business Systems through development, UAT, release, and adoptionPartner with Business Systems to translate Service & Support requirements into prioritized system enhancements; coordinate UAT, business validation, release readiness, and adoptionMaintain Service Ops collateral on SharePoint and keep the Service Playbook current as processes evolveLead onboarding and offboarding for Service & Support: team records, RingCentral, Service Resource setup, and SFDC permission checksAct as a cross-functional liaison between Service Operations, Sales, and Commercial leadership, representing the voice of the fieldPartner with the Manager, Global Customer & Service Operations to maintain the GSS operational roadmap, translating organizational priorities into defined programs, milestones, owners, dependencies, and measurable outcomesTrack Service & Support KPIs and identify opportunities to automate and improve data qualityParticipate in both product extension and new product introduction teams to scope and implement changes to business systems to support product launches"
We need to split into items. There's some missing spaces (like "...stakeholdersOwn" should be "stakeholders. Own". We'll just treat as separate sentences.
Let's manually split:
1. Own the Global Service & Support operating cadence, including Sprint Release Updates, Manager Service Ops Syncs, Office Hours, and Global Service & Support (GSS) Monthly meetings.
2. Drive agenda development, action tracking, decision documentation, Jira-Commercial Operations Management (COPM) review, and follow-through across stakeholders.
3. Own Service & Support release readiness and communications for system and process changes, including SFDC release communications, stakeholder readiness, UAT coordination, and post-release follow-up.
4. Run the GSS Monthly process end-to-end, from Teams thread and shared deck to recording and recap summary.
5. Own Service Operations demand intake and portfolio management through Jira-COPM, including triage, business requirements, prioritization recommendations, assignment, dependencies, sprint readiness, escalation, and status reporting.
6. Partner with Business Systems through development, UAT, release, and adoption.
7. Partner with Business Systems to translate Service & Support requirements into prioritized system enhancements; coordinate UAT, business validation, release readiness, and adoption.
8. Maintain Service Ops collateral on SharePoint and keep the Service Playbook current as processes evolve.
9. Lead onboarding and offboarding for Service & Support: team records, RingCentral, Service Resource setup, and SFDC permission checks.
10. Act as a cross-functional liaison between Service Operations, Sales, and Commercial leadership, representing the voice of the field.
11. Partner with the Manager, Global Customer & Service Operations to maintain the GSS operational roadmap, translating organizational priorities into defined programs, milestones, owners, dependencies, and measurable outcomes.
12. Track Service & Support KPIs and identify opportunities to automate and improve data quality.
13. Participate in both product extension and new product introduction teams to scope and implement changes to business systems to support product launches.
That seems comprehensive.
Now Education And Experience:
"Bachelor's degree or equivalent practical experience plus 3-5+ years in service operations, program management, or commercial operations, ideally in life sciences or medical device instrumentationHands-on Salesforce experience (cases, work orders, service resources)Experience with Jira or similar ticketing/project systemsStrong meeting and program management skills across multiple recurring cadencesExcellent written and verbal communicator, comfortable with executive-ready materialsPreferred: experience supporting a field service org at a genomics or lab instrumentation companyPreferred: experience with service playbooks, onboarding SOPs, or team mergers/restructuring"
We need to split into items. There's missing spaces again. We'll parse:
- Bachelor's degree or equivalent practical experience plus 3-5+ years in service operations, program management, or commercial operations, ideally in life sciences or medical device instrumentation.
- Hands-on Salesforce experience (cases, work orders, service resources).
- Experience with Jira or similar ticketing/project systems.
- Strong meeting and program management skills across multiple recurring cadences.
- Excellent written and verbal communicator, comfortable with executive-ready materials.
- Preferred: experience supporting a field service org at a genomics or lab instrumentation company.
- Preferred: experience with service playbooks, onboarding SOPs, or team mergers/restructuring.
We could treat "Preferred:" as part of item.
Now Benefits:
"In addition to base compensation noted above, you will be eligible for stock options, discretionary annual bonus, no cost health insurance plans, 401k with company match, and flexible paid time off."
We can make a list:
- stock options
- discretionary annual bonus
- no cost health insurance plans
- 401k with company match
- flexible paid time off
Now Pay:
"Base Compensation Pay Range $97,000 - $118,000"
Also note: "Please note: Base compensation will depend on multiple factors, including geographic location, qualifications, and experience." That's also part of Pay section.
Thus Pay section includes range and note.
Now Schedule:
We have: "Must be flexible in working hours as this position may require customer support during non-regular business hours", "Location: San Diego - onsite", "Travel Up to 10%", "Job Type Full-time, Exempt". Also maybe "Physical Requirements" heading but we treat as schedule.
We can create list:
- Flexible working hours; may require customer support during non-regular business hours.
- Onsite location in San Diego, CA.
- Travel up to 10%.
- Full-time, exempt position.
We could also include "Physical Requirements" but it's just flexible hours.
Now About the role: The introductory paragraph: "At Element Biosciences, we are passionate about our mission to empower the scientific community with more freedom and flexibility to accelerate our collective impact on humanity. We have built a highly efficient product-driven organization where employees can learn, grow, and thrive in a challenging but encouraging environment. We are committed to scientific integrity, collegiality, honesty, objectivity, and openness. We are seeking an organized and proactive Service Operations Program Lead to own the operational backbone of our Service & Support organization. This role manages the systems, meeting cadences, and cross-functional programs that keep Technical Support, Customer Support Specialists, Field Application Scientists, and Field Service Engineers running smoothly as Element scales its install base and product portfolio. This role will report to the Manager, Customer Service and Operations and will be a daily onsite role based in San Diego, CA. If you possess the following and want to make a meaningful impact, we invite you to explore this role."
We need to preserve all substantive info. We'll put that as
under About the role.
We must not repeat job title as heading; we are not.
Now ensure we don't include boilerplate like EEO etc. We removed.
Now output HTML fragment: sections with
headings, each containing either
or
- . Use proper HTML.
We'll produce:
About the role
...
Responsibilities
- ...
...
Qualifications
- ...
...
Benefits
- ...
...
Pay
Base compensation pay range: $97,000 - $118,000. Please note: Base compensation will depend on multiple factors, including geographic location, qualifications, and experience.
Schedule
- Flexible working hours; may require customer support during non‑regular business hours.
- Onsite location in San Diego
for prose. Do NOT repeat the job title as a heading. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — 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. Prefer a few substantive sections over many thin ones. We need to include sections only if there is real specific content. Let's parse the posting: - Intro paragraph: mission, organization, seeking organized and proactive Service Operations Program Lead... This could be "About the role" or maybe "Overview". We can use "About the role" heading. - Essential Functions And Responsibilities: a long list of responsibilities. That's a section "Responsibilities". Should be a list. - Education And Experience: qualifications. Could be "Qualifications" or "Requirements". We'll use "Qualifications". It includes bullet-like sentences but not explicit list. We can convert to
- .
- Physical Requirements: mention flexible hours, location, travel. Could be "Schedule" or "Location". The instruction says we can have Schedule section if posting actually states them. It mentions "Must be flexible in working hours as this position may require customer support during non-regular business hours" and "Location: San Diego - onsite" and "Travel Up to 10%". That's schedule/location info. Could be under "Schedule" or maybe "Location". Since they gave schedule heading example, we can use "Schedule" for flexible hours and travel. But also location is not schedule. Could combine location into a short
maybe under "About the role". However they said we can fold minor metadata into a short
or drop it. Location is maybe minor metadata. Travel up to 10% could be schedule. - Job Type Full-time, Exempt: that's schedule/type. Could be part of Schedule. - Base Compensation Pay Range $97,000 - $118,000: That's Pay. So we need a Pay section. - Benefits: "In addition to base compensation noted above, you will be eligible for stock options, discretionary annual bonus, no cost health insurance plans, 401k with company match, and flexible paid time off." That's Benefits. - EEO statement: remove. Thus we have sections: About the role (intro), Responsibilities, Qualifications (Education And Experience), Benefits, Pay, Schedule (flexible hours, location, travel, job type). Possibly also "Requirements" but we used Qualifications. We must not repeat job title as heading. Good. We must not include duplicated lines. Ensure we preserve all substantive info. We need to format responsibilities as
- . The responsibilities list is long; we need to break into items. The text includes many sentences separated by periods. We'll need to parse into logical items. Could keep each sentence as a list item. Ensure we don't lose any detail.
Let's extract responsibilities paragraph:
"Own the Global Service & Support operating cadence, including Sprint Release Updates, Manager Service Ops Syncs, Office Hours, and Global Service & Support (GSS) Monthly meetings. Drive agenda development, action tracking, decision documentation, Jira-Commercial Operations Management (COPM) review, and follow-through across stakeholdersOwn Service & Support release readiness and communications for system and process changes, including SFDC release communications, stakeholder readiness, UAT coordination, and post-release follow-upRun the GSS Monthly process end-to-end, from Teams thread and shared deck to recording and recap summaryOwn Service Operations demand intake and portfolio management through Jira-COPM, including triage, business requirements, prioritization recommendations, assignment, dependencies, sprint readiness, escalation, and status reporting. Partner with Business Systems through development, UAT, release, and adoptionPartner with Business Systems to translate Service & Support requirements into prioritized system enhancements; coordinate UAT, business validation, release readiness, and adoptionMaintain Service Ops collateral on SharePoint and keep the Service Playbook current as processes evolveLead onboarding and offboarding for Service & Support: team records, RingCentral, Service Resource setup, and SFDC permission checksAct as a cross-functional liaison between Service Operations, Sales, and Commercial leadership, representing the voice of the fieldPartner with the Manager, Global Customer & Service Operations to maintain the GSS operational roadmap, translating organizational priorities into defined programs, milestones, owners, dependencies, and measurable outcomesTrack Service & Support KPIs and identify opportunities to automate and improve data qualityParticipate in both product extension and new product introduction teams to scope and implement changes to business systems to support product launches"
We need to split into items. There's some missing spaces (like "...stakeholdersOwn" should be "stakeholders. Own". We'll just treat as separate sentences.
Let's manually split:
1. Own the Global Service & Support operating cadence, including Sprint Release Updates, Manager Service Ops Syncs, Office Hours, and Global Service & Support (GSS) Monthly meetings.
2. Drive agenda development, action tracking, decision documentation, Jira-Commercial Operations Management (COPM) review, and follow-through across stakeholders.
3. Own Service & Support release readiness and communications for system and process changes, including SFDC release communications, stakeholder readiness, UAT coordination, and post-release follow-up.
4. Run the GSS Monthly process end-to-end, from Teams thread and shared deck to recording and recap summary.
5. Own Service Operations demand intake and portfolio management through Jira-COPM, including triage, business requirements, prioritization recommendations, assignment, dependencies, sprint readiness, escalation, and status reporting.
6. Partner with Business Systems through development, UAT, release, and adoption.
7. Partner with Business Systems to translate Service & Support requirements into prioritized system enhancements; coordinate UAT, business validation, release readiness, and adoption.
8. Maintain Service Ops collateral on SharePoint and keep the Service Playbook current as processes evolve.
9. Lead onboarding and offboarding for Service & Support: team records, RingCentral, Service Resource setup, and SFDC permission checks.
10. Act as a cross-functional liaison between Service Operations, Sales, and Commercial leadership, representing the voice of the field.
11. Partner with the Manager, Global Customer & Service Operations to maintain the GSS operational roadmap, translating organizational priorities into defined programs, milestones, owners, dependencies, and measurable outcomes.
12. Track Service & Support KPIs and identify opportunities to automate and improve data quality.
13. Participate in both product extension and new product introduction teams to scope and implement changes to business systems to support product launches.
That seems comprehensive.
Now Education And Experience:
"Bachelor's degree or equivalent practical experience plus 3-5+ years in service operations, program management, or commercial operations, ideally in life sciences or medical device instrumentationHands-on Salesforce experience (cases, work orders, service resources)Experience with Jira or similar ticketing/project systemsStrong meeting and program management skills across multiple recurring cadencesExcellent written and verbal communicator, comfortable with executive-ready materialsPreferred: experience supporting a field service org at a genomics or lab instrumentation companyPreferred: experience with service playbooks, onboarding SOPs, or team mergers/restructuring"
We need to split into items. There's missing spaces again. We'll parse:
- Bachelor's degree or equivalent practical experience plus 3-5+ years in service operations, program management, or commercial operations, ideally in life sciences or medical device instrumentation.
- Hands-on Salesforce experience (cases, work orders, service resources).
- Experience with Jira or similar ticketing/project systems.
- Strong meeting and program management skills across multiple recurring cadences.
- Excellent written and verbal communicator, comfortable with executive-ready materials.
- Preferred: experience supporting a field service org at a genomics or lab instrumentation company.
- Preferred: experience with service playbooks, onboarding SOPs, or team mergers/restructuring.
We could treat "Preferred:" as part of item.
Now Benefits:
"In addition to base compensation noted above, you will be eligible for stock options, discretionary annual bonus, no cost health insurance plans, 401k with company match, and flexible paid time off."
We can make a list:
- stock options
- discretionary annual bonus
- no cost health insurance plans
- 401k with company match
- flexible paid time off
Now Pay:
"Base Compensation Pay Range $97,000 - $118,000"
Also note: "Please note: Base compensation will depend on multiple factors, including geographic location, qualifications, and experience." That's also part of Pay section.
Thus Pay section includes range and note.
Now Schedule:
We have: "Must be flexible in working hours as this position may require customer support during non-regular business hours", "Location: San Diego - onsite", "Travel Up to 10%", "Job Type Full-time, Exempt". Also maybe "Physical Requirements" heading but we treat as schedule.
We can create list:
- Flexible working hours; may require customer support during non-regular business hours.
- Onsite location in San Diego, CA.
- Travel up to 10%.
- Full-time, exempt position.
We could also include "Physical Requirements" but it's just flexible hours.
Now About the role: The introductory paragraph: "At Element Biosciences, we are passionate about our mission to empower the scientific community with more freedom and flexibility to accelerate our collective impact on humanity. We have built a highly efficient product-driven organization where employees can learn, grow, and thrive in a challenging but encouraging environment. We are committed to scientific integrity, collegiality, honesty, objectivity, and openness. We are seeking an organized and proactive Service Operations Program Lead to own the operational backbone of our Service & Support organization. This role manages the systems, meeting cadences, and cross-functional programs that keep Technical Support, Customer Support Specialists, Field Application Scientists, and Field Service Engineers running smoothly as Element scales its install base and product portfolio. This role will report to the Manager, Customer Service and Operations and will be a daily onsite role based in San Diego, CA. If you possess the following and want to make a meaningful impact, we invite you to explore this role."
We need to preserve all substantive info. We'll put that as
under About the role. We must not repeat job title as heading; we are not. Now ensure we don't include boilerplate like EEO etc. We removed. Now output HTML fragment: sections with
headings, each containing either
or
- . Use proper HTML.
We'll produce:
About the role
...
Responsibilities
- ... ...
Qualifications
- ... ...
Benefits
- ... ...
Pay
Base compensation pay range: $97,000 - $118,000. Please note: Base compensation will depend on multiple factors, including geographic location, qualifications, and experience.
Schedule
- Flexible working hours; may require customer support during non‑regular business hours.
- Onsite location in San Diego
- . Use proper HTML.
We'll produce:
- . The responsibilities list is long; we need to break into items. The text includes many sentences separated by periods. We'll need to parse into logical items. Could keep each sentence as a list item. Ensure we don't lose any detail.
Let's extract responsibilities paragraph:
"Own the Global Service & Support operating cadence, including Sprint Release Updates, Manager Service Ops Syncs, Office Hours, and Global Service & Support (GSS) Monthly meetings. Drive agenda development, action tracking, decision documentation, Jira-Commercial Operations Management (COPM) review, and follow-through across stakeholdersOwn Service & Support release readiness and communications for system and process changes, including SFDC release communications, stakeholder readiness, UAT coordination, and post-release follow-upRun the GSS Monthly process end-to-end, from Teams thread and shared deck to recording and recap summaryOwn Service Operations demand intake and portfolio management through Jira-COPM, including triage, business requirements, prioritization recommendations, assignment, dependencies, sprint readiness, escalation, and status reporting. Partner with Business Systems through development, UAT, release, and adoptionPartner with Business Systems to translate Service & Support requirements into prioritized system enhancements; coordinate UAT, business validation, release readiness, and adoptionMaintain Service Ops collateral on SharePoint and keep the Service Playbook current as processes evolveLead onboarding and offboarding for Service & Support: team records, RingCentral, Service Resource setup, and SFDC permission checksAct as a cross-functional liaison between Service Operations, Sales, and Commercial leadership, representing the voice of the fieldPartner with the Manager, Global Customer & Service Operations to maintain the GSS operational roadmap, translating organizational priorities into defined programs, milestones, owners, dependencies, and measurable outcomesTrack Service & Support KPIs and identify opportunities to automate and improve data qualityParticipate in both product extension and new product introduction teams to scope and implement changes to business systems to support product launches"
We need to split into items. There's some missing spaces (like "...stakeholdersOwn" should be "stakeholders. Own". We'll just treat as separate sentences.
Let's manually split:
1. Own the Global Service & Support operating cadence, including Sprint Release Updates, Manager Service Ops Syncs, Office Hours, and Global Service & Support (GSS) Monthly meetings.
2. Drive agenda development, action tracking, decision documentation, Jira-Commercial Operations Management (COPM) review, and follow-through across stakeholders.
3. Own Service & Support release readiness and communications for system and process changes, including SFDC release communications, stakeholder readiness, UAT coordination, and post-release follow-up.
4. Run the GSS Monthly process end-to-end, from Teams thread and shared deck to recording and recap summary.
5. Own Service Operations demand intake and portfolio management through Jira-COPM, including triage, business requirements, prioritization recommendations, assignment, dependencies, sprint readiness, escalation, and status reporting.
6. Partner with Business Systems through development, UAT, release, and adoption.
7. Partner with Business Systems to translate Service & Support requirements into prioritized system enhancements; coordinate UAT, business validation, release readiness, and adoption.
8. Maintain Service Ops collateral on SharePoint and keep the Service Playbook current as processes evolve.
9. Lead onboarding and offboarding for Service & Support: team records, RingCentral, Service Resource setup, and SFDC permission checks.
10. Act as a cross-functional liaison between Service Operations, Sales, and Commercial leadership, representing the voice of the field.
11. Partner with the Manager, Global Customer & Service Operations to maintain the GSS operational roadmap, translating organizational priorities into defined programs, milestones, owners, dependencies, and measurable outcomes.
12. Track Service & Support KPIs and identify opportunities to automate and improve data quality.
13. Participate in both product extension and new product introduction teams to scope and implement changes to business systems to support product launches.
That seems comprehensive.
Now Education And Experience:
"Bachelor's degree or equivalent practical experience plus 3-5+ years in service operations, program management, or commercial operations, ideally in life sciences or medical device instrumentationHands-on Salesforce experience (cases, work orders, service resources)Experience with Jira or similar ticketing/project systemsStrong meeting and program management skills across multiple recurring cadencesExcellent written and verbal communicator, comfortable with executive-ready materialsPreferred: experience supporting a field service org at a genomics or lab instrumentation companyPreferred: experience with service playbooks, onboarding SOPs, or team mergers/restructuring"
We need to split into items. There's missing spaces again. We'll parse:
- Bachelor's degree or equivalent practical experience plus 3-5+ years in service operations, program management, or commercial operations, ideally in life sciences or medical device instrumentation.
- Hands-on Salesforce experience (cases, work orders, service resources).
- Experience with Jira or similar ticketing/project systems.
- Strong meeting and program management skills across multiple recurring cadences.
- Excellent written and verbal communicator, comfortable with executive-ready materials.
- Preferred: experience supporting a field service org at a genomics or lab instrumentation company.
- Preferred: experience with service playbooks, onboarding SOPs, or team mergers/restructuring.
We could treat "Preferred:" as part of item.
Now Benefits:
"In addition to base compensation noted above, you will be eligible for stock options, discretionary annual bonus, no cost health insurance plans, 401k with company match, and flexible paid time off."
We can make a list:
- stock options
- discretionary annual bonus
- no cost health insurance plans
- 401k with company match
- flexible paid time off
Now Pay:
"Base Compensation Pay Range $97,000 - $118,000"
Also note: "Please note: Base compensation will depend on multiple factors, including geographic location, qualifications, and experience." That's also part of Pay section.
Thus Pay section includes range and note.
Now Schedule:
We have: "Must be flexible in working hours as this position may require customer support during non-regular business hours", "Location: San Diego - onsite", "Travel Up to 10%", "Job Type Full-time, Exempt". Also maybe "Physical Requirements" heading but we treat as schedule.
We can create list:
- Flexible working hours; may require customer support during non-regular business hours.
- Onsite location in San Diego, CA.
- Travel up to 10%.
- Full-time, exempt position.
We could also include "Physical Requirements" but it's just flexible hours.
Now About the role: The introductory paragraph: "At Element Biosciences, we are passionate about our mission to empower the scientific community with more freedom and flexibility to accelerate our collective impact on humanity. We have built a highly efficient product-driven organization where employees can learn, grow, and thrive in a challenging but encouraging environment. We are committed to scientific integrity, collegiality, honesty, objectivity, and openness. We are seeking an organized and proactive Service Operations Program Lead to own the operational backbone of our Service & Support organization. This role manages the systems, meeting cadences, and cross-functional programs that keep Technical Support, Customer Support Specialists, Field Application Scientists, and Field Service Engineers running smoothly as Element scales its install base and product portfolio. This role will report to the Manager, Customer Service and Operations and will be a daily onsite role based in San Diego, CA. If you possess the following and want to make a meaningful impact, we invite you to explore this role."
We need to preserve all substantive info. We'll put that as