Senior Technical Operations Manager
for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Remove boilerplate, navigation, legal, EEO, equal-opportunity, scam-warning, duplicated lines, application instructions. Include a section ONLY when posting has real, specific content for it — never emit heading with filler/placeholder text. Prefer few substantive sections over many thin ones.
We need to parse the posting and extract sections.
Let's read the posting:
Title: Senior Technical Operations Manager, DV+ New York, NY Los Angeles, CA Boston, MA Broomfield, CO Hybrid Schedule (M/F remote, T/W/TH in-office)
Then paragraph: At Magnite, we cultivate... (intro)
Then "About This Team" paragraph.
Then "In This Role You Will" bullet list (actually sentences separated by periods). Then "We’re Looking For Someone With" list of bullet points.
Then "In the US, the base salary range for this role is $80,000 – $110,000. Actual compensation will be determined based on location, experience, skills, and internal equity. This Role Is Also Eligible For Annual performance-based bonus Equity (NASDAQ: MGNI) Comprehensive benefits package During the interview process, candidates will receive more specific information about the salary range applicable to their experience and location."
Then "For Los Angeles-based Applicants Qualified applications with arrest or conviction records will be considered for employment in accordance with the Los Angeles County Fair Chance Ordinance for Employers and the California Fair Chance Act." This is EEO/legal, we should remove.
Then "Job Duties The material job duties of this specific job position for which Magnite reasonably believes that a criminal history may have a direct, adverse, and negative relationship include: Having access to the Company’s Confidential Information or trade secrets including data related to customers, clients, vendors, business partners, or suppliers Work with cross teams to access datasets, databases, formulas, algorithms, tools, products, prototypes, systems applications, and technologies in any stage of development" This seems like legal boilerplate about criminal history; we should remove as it's likely EEO/legal.
Then "Perks And Benefits Comprehensive Healthcare Coverage from Day One Generous Time Off Holiday Breaks and Quarterly Wellness Days Equity and Employee Stock Purchase Plan Family-Focused Benefits and Parental Leave 401k Retirement Savings Plan with Employer Match Disability and Life Insurance Cell Phone Subsidy Monthly Fitness and Reimbursement"
Then "Career Growth We support internal mobility, skill development, and leadership pathways through structured career frameworks and learning programs."
Then "Company Culture Magnite’s culture is rooted in collaboration and connection, recognizing that both are essential to success. Our hybrid schedule includes two remote workdays (Monday and Friday) and three in-office days (Tuesday through Thursday), where employees can take advantage of catered lunches, beverages, snacks, training opportunities, and engaging office events that enhance the work experience. In addition, we support our team through meaningful benefits and programs, including community service and volunteer opportunities, company-matched charitable contributions, access to mental health resources, structured career development initiatives and growth frameworks, culture and inclusion programs, and our Bonusly peer-to-peer recognition platform."
Then "About Us The world's leading agencies and brands trust our platform to access brand-safe, high-quality ad inventory and execute billions of advertising transactions each month. Anchored in bustling New York City, sunny Los Angeles, mile-high Denver, historic London, and down under in Sydney, Magnite has offices across North America, EMEA, LATAM, and APAC."
Then "Magnite is an Equal Opportunity Employer and does not discriminate against applicants due to race, color, religion, national origin, age, sex, marital status, ancestry, physical or mental disability, veteran status, gender identity, sexual orientation or any other federal, state or local protected class. Our Commitment: We aim to incorporate a wide range of voices into our Magnite culture, cultivating an environment where employees feel welcomed, cared for, and encouraged to freely share ideas. We are committed to employee growth, collaboration, inclusion, and innovation. We invest in Magnite’s local communities. We seek talent from all backgrounds to champion corporate values of seeing the big picture and being catalysts of change. Want to learn more about us? Check out our blog for Magnite announcements and Ad Tech industry news! Recruiting Agency Notice Magnite does not accept agency resumes and is not responsible for any fees related to unsolicited resumes."
We need to remove all EEO/legal boilerplate, navigation, duplicated lines, application instructions.
We need to keep substantive info: About the team, responsibilities, requirements/qualifications/skills, benefits, pay, schedule.
We need to decide sections.
We have:
- About This Team (maybe "About the role"? Actually "About This Team" is a section describing the team. Could map to "About the role". We'll use heading
About the role
and put that paragraph.
- Responsibilities: The "In This Role You Will" list. We'll make Responsibilities
with - items.
- Requirements/Qualifications/Skills: The "We’re Looking For Someone With" list includes many items: 4+ years experience, Bachelor's degree, strong technical knowledge, proficiency in SQL and Excel, interest in AI, technical writing, analytical troubleshooting, cross-functional collaboration, communication, ability to work independently, analytical mindset. These could be split into Requirements, Qualifications, Skills but we can combine into one section maybe "Requirements". However the instruction says use headings for those specific categories if we have content. We could create separate sections if we have distinct content. But we have a mixed list; we could split into Requirements (experience, education), Qualifications (technical knowledge, SQL/Excel, AI interest), Skills (communication, collaboration, etc). But we need to avoid thin sections. Perhaps better to have one section "Requirements" covering all. But the instruction says "Prefer a few substantive sections over many thin ones." So we could have sections: About the role, Responsibilities, Requirements, Benefits, Pay, Schedule. That's six sections.
We need to extract Benefits: from "Perks And Benefits" list and also from Company Culture paragraph about benefits (but we should avoid duplication). We'll combine.
Pay: salary range $80,000 – $110,000, plus mention of annual performance-based bonus, equity. We'll include that.
Schedule: hybrid schedule details: M/F remote, T/W/TH in-office. Also from Company Culture: "Our hybrid schedule includes two remote workdays (Monday and Friday) and three in-office days (Tuesday through Thursday)". We'll include that.
Now we need to remove any filler/placeholder text. Ensure we don't include sections with only generic phrases like "commensurate with experience". We have concrete info.
Now produce HTML fragment.
We must not include or . Just the fragment.
We'll structure:
About the role
... (the About This Team paragraph plus maybe intro? The intro about Magnite cultivating environment etc could be part of About the role? The instruction says use
for section headings (e.g. About the role, Responsibilities...). The intro paragraph "At Magnite, we cultivate an environment..." is generic company description; could be part of About the role or maybe we could omit as it's not specific to role. But we need to preserve ALL substantive information; do NOT invent or summarize away detail. The intro is substantive about company culture but not role-specific. However we already have Company Culture section later; we might include that under Company Culture but we are not using that heading. We could include it under About the role as it's about the company environment. But we also have a separate Company Culture paragraph later. To avoid duplication, we could combine them. However the instruction says "Prefer a few substantive sections over many thin ones." So we could have About the role include the intro and About This Team. That seems fine.
Thus About the role paragraph: combine the intro sentence(s) and About This Team.
Let's extract:
Intro: "At Magnite, we cultivate an environment of continuous growth and collaboration. Our work impacts what millions of people read, watch, and buy, and we’re looking for people to help us tackle that responsibility with creativity and focus. Magnite (NASDAQ: MGNI) is the world’s largest independent sell-side advertising platform. Publishers use our technology to monetize their content across all screens and formats including CTV / streaming, online video, display, and audio. Our tech fuels billions of transactions per day!"
About This Team: "The Senior Technical Operations Manager, DV+ is a critical individual contributor role focused on the DV+ platform, where publishers monetize omnichannel inventory — spanning display, video, native, audio, and DOOH — through sophisticated, AI-enhanced programmatic solutions. This role serves as a key cross-functional partner and primary internal escalation point, operating at the intersection of Account Management, Product, and Engineering to drive technical resolution and support our platform's evolving capabilities. A core component involves leveraging modern AI tools and advanced analytics to identify repeatable challenges, design scalable solutions, and drive operational efficiency across large datasets."
We'll combine into one
maybe two paragraphs? The instruction says use
for prose. Could have multiple
elements under the heading. That's fine.
Now Responsibilities: list items from "In This Role You Will". Let's extract each sentence ending with a period.
- Handle a queue of technical escalations with high standards of organization, responsiveness, and stakeholder communication.
- Query and analyze large datasets across multiple systems using SQL to identify trends, diagnose issues, and support operational decision-making.
- Leverage modern AI tools and emerging technologies to identify repeatable challenges, design scalable solutions, automate workflows, and improve operational efficiency.
- Troubleshoot complex technical issues spanning multiple platforms, systems, reporting pipelines, APIs, and integrations.
- Investigate ambiguous problems proactively, asking thoughtful questions and driving issues to resolution with minimal oversight.
- Learn new platforms, systems, and technical concepts quickly while demonstrating strong ownership and long-term retention of operational knowledge.
- Collaborate cross-functionally when needed, coordinating efforts across Technical Operations, Product, Engineering, Account Management, and external partners to resolve issues and execute initiatives.
We'll put each as
- .
Now Requirements: from "We’re Looking For Someone With". Let's extract each bullet (they are separated by line breaks). We'll list:
- 4+ years in technical operations or a related role
- Bachelor's degree or equivalent (advanced degree a plus)
- Strong technical knowledge of the programmatic ecosystem
- Strong proficiency in SQL and Excel for data analysis, troubleshooting, and workflow automation
- Genuine interest in emerging AI technologies, with the ability to apply them to operational workflows and problem-solving
- Excellent technical writing and documentation skills
- Strong analytical and troubleshooting abilities, with experience diagnosing complex issues
- Strong cross-functional collaboration and coordination skills
- Excellent communication skills, with the ability to explain technical concepts clearly, identify root causes, and drive issues to resolution
- Able to work independently, prioritize effectively, and thrive in a fast-paced environment
- Analytical mindset with the ability to balance immediate needs with long-term scalable solutions
We'll put as
- under
Requirements
.
Now Benefits: from "Perks And Benefits" list and also Company Culture benefits.
Perks And Benefits list:
- Comprehensive Healthcare Coverage from Day One
- Generous Time Off
- Holiday Breaks and Quarterly Wellness Days
- Equity and Employee Stock Purchase Plan
- Family-Focused Benefits and Parental Leave
- 401k Retirement Savings Plan with Employer Match
- Disability and Life Insurance
- Cell Phone Subsidy
- Monthly Fitness and Reimbursement
Company Culture also mentions
for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Remove boilerplate, navigation, legal, EEO, equal-opportunity, scam-warning, duplicated lines, application instructions. Include a section ONLY when posting has real, specific content for it — never emit heading with filler/placeholder text. Prefer few substantive sections over many thin ones. We need to parse the posting and extract sections. Let's read the posting: Title: Senior Technical Operations Manager, DV+ New York, NY Los Angeles, CA Boston, MA Broomfield, CO Hybrid Schedule (M/F remote, T/W/TH in-office) Then paragraph: At Magnite, we cultivate... (intro) Then "About This Team" paragraph. Then "In This Role You Will" bullet list (actually sentences separated by periods). Then "We’re Looking For Someone With" list of bullet points. Then "In the US, the base salary range for this role is $80,000 – $110,000. Actual compensation will be determined based on location, experience, skills, and internal equity. This Role Is Also Eligible For Annual performance-based bonus Equity (NASDAQ: MGNI) Comprehensive benefits package During the interview process, candidates will receive more specific information about the salary range applicable to their experience and location." Then "For Los Angeles-based Applicants Qualified applications with arrest or conviction records will be considered for employment in accordance with the Los Angeles County Fair Chance Ordinance for Employers and the California Fair Chance Act." This is EEO/legal, we should remove. Then "Job Duties The material job duties of this specific job position for which Magnite reasonably believes that a criminal history may have a direct, adverse, and negative relationship include: Having access to the Company’s Confidential Information or trade secrets including data related to customers, clients, vendors, business partners, or suppliers Work with cross teams to access datasets, databases, formulas, algorithms, tools, products, prototypes, systems applications, and technologies in any stage of development" This seems like legal boilerplate about criminal history; we should remove as it's likely EEO/legal. Then "Perks And Benefits Comprehensive Healthcare Coverage from Day One Generous Time Off Holiday Breaks and Quarterly Wellness Days Equity and Employee Stock Purchase Plan Family-Focused Benefits and Parental Leave 401k Retirement Savings Plan with Employer Match Disability and Life Insurance Cell Phone Subsidy Monthly Fitness and Reimbursement" Then "Career Growth We support internal mobility, skill development, and leadership pathways through structured career frameworks and learning programs." Then "Company Culture Magnite’s culture is rooted in collaboration and connection, recognizing that both are essential to success. Our hybrid schedule includes two remote workdays (Monday and Friday) and three in-office days (Tuesday through Thursday), where employees can take advantage of catered lunches, beverages, snacks, training opportunities, and engaging office events that enhance the work experience. In addition, we support our team through meaningful benefits and programs, including community service and volunteer opportunities, company-matched charitable contributions, access to mental health resources, structured career development initiatives and growth frameworks, culture and inclusion programs, and our Bonusly peer-to-peer recognition platform." Then "About Us The world's leading agencies and brands trust our platform to access brand-safe, high-quality ad inventory and execute billions of advertising transactions each month. Anchored in bustling New York City, sunny Los Angeles, mile-high Denver, historic London, and down under in Sydney, Magnite has offices across North America, EMEA, LATAM, and APAC." Then "Magnite is an Equal Opportunity Employer and does not discriminate against applicants due to race, color, religion, national origin, age, sex, marital status, ancestry, physical or mental disability, veteran status, gender identity, sexual orientation or any other federal, state or local protected class. Our Commitment: We aim to incorporate a wide range of voices into our Magnite culture, cultivating an environment where employees feel welcomed, cared for, and encouraged to freely share ideas. We are committed to employee growth, collaboration, inclusion, and innovation. We invest in Magnite’s local communities. We seek talent from all backgrounds to champion corporate values of seeing the big picture and being catalysts of change. Want to learn more about us? Check out our blog for Magnite announcements and Ad Tech industry news! Recruiting Agency Notice Magnite does not accept agency resumes and is not responsible for any fees related to unsolicited resumes." We need to remove all EEO/legal boilerplate, navigation, duplicated lines, application instructions. We need to keep substantive info: About the team, responsibilities, requirements/qualifications/skills, benefits, pay, schedule. We need to decide sections. We have: - About This Team (maybe "About the role"? Actually "About This Team" is a section describing the team. Could map to "About the role". We'll use heading
About the role
and put that paragraph. - Responsibilities: The "In This Role You Will" list. We'll makeResponsibilities
with- items.
- Requirements/Qualifications/Skills: The "We’re Looking For Someone With" list includes many items: 4+ years experience, Bachelor's degree, strong technical knowledge, proficiency in SQL and Excel, interest in AI, technical writing, analytical troubleshooting, cross-functional collaboration, communication, ability to work independently, analytical mindset. These could be split into Requirements, Qualifications, Skills but we can combine into one section maybe "Requirements". However the instruction says use headings for those specific categories if we have content. We could create separate sections if we have distinct content. But we have a mixed list; we could split into Requirements (experience, education), Qualifications (technical knowledge, SQL/Excel, AI interest), Skills (communication, collaboration, etc). But we need to avoid thin sections. Perhaps better to have one section "Requirements" covering all. But the instruction says "Prefer a few substantive sections over many thin ones." So we could have sections: About the role, Responsibilities, Requirements, Benefits, Pay, Schedule. That's six sections.
We need to extract Benefits: from "Perks And Benefits" list and also from Company Culture paragraph about benefits (but we should avoid duplication). We'll combine.
Pay: salary range $80,000 – $110,000, plus mention of annual performance-based bonus, equity. We'll include that.
Schedule: hybrid schedule details: M/F remote, T/W/TH in-office. Also from Company Culture: "Our hybrid schedule includes two remote workdays (Monday and Friday) and three in-office days (Tuesday through Thursday)". We'll include that.
Now we need to remove any filler/placeholder text. Ensure we don't include sections with only generic phrases like "commensurate with experience". We have concrete info.
Now produce HTML fragment.
We must not include or . Just the fragment.
We'll structure:
About the role
... (the About This Team paragraph plus maybe intro? The intro about Magnite cultivating environment etc could be part of About the role? The instruction says use
for section headings (e.g. About the role, Responsibilities...). The intro paragraph "At Magnite, we cultivate an environment..." is generic company description; could be part of About the role or maybe we could omit as it's not specific to role. But we need to preserve ALL substantive information; do NOT invent or summarize away detail. The intro is substantive about company culture but not role-specific. However we already have Company Culture section later; we might include that under Company Culture but we are not using that heading. We could include it under About the role as it's about the company environment. But we also have a separate Company Culture paragraph later. To avoid duplication, we could combine them. However the instruction says "Prefer a few substantive sections over many thin ones." So we could have About the role include the intro and About This Team. That seems fine. Thus About the role paragraph: combine the intro sentence(s) and About This Team. Let's extract: Intro: "At Magnite, we cultivate an environment of continuous growth and collaboration. Our work impacts what millions of people read, watch, and buy, and we’re looking for people to help us tackle that responsibility with creativity and focus. Magnite (NASDAQ: MGNI) is the world’s largest independent sell-side advertising platform. Publishers use our technology to monetize their content across all screens and formats including CTV / streaming, online video, display, and audio. Our tech fuels billions of transactions per day!" About This Team: "The Senior Technical Operations Manager, DV+ is a critical individual contributor role focused on the DV+ platform, where publishers monetize omnichannel inventory — spanning display, video, native, audio, and DOOH — through sophisticated, AI-enhanced programmatic solutions. This role serves as a key cross-functional partner and primary internal escalation point, operating at the intersection of Account Management, Product, and Engineering to drive technical resolution and support our platform's evolving capabilities. A core component involves leveraging modern AI tools and advanced analytics to identify repeatable challenges, design scalable solutions, and drive operational efficiency across large datasets." We'll combine into one
maybe two paragraphs? The instruction says use
for prose. Could have multiple
elements under the heading. That's fine. Now Responsibilities: list items from "In This Role You Will". Let's extract each sentence ending with a period. - Handle a queue of technical escalations with high standards of organization, responsiveness, and stakeholder communication. - Query and analyze large datasets across multiple systems using SQL to identify trends, diagnose issues, and support operational decision-making. - Leverage modern AI tools and emerging technologies to identify repeatable challenges, design scalable solutions, automate workflows, and improve operational efficiency. - Troubleshoot complex technical issues spanning multiple platforms, systems, reporting pipelines, APIs, and integrations. - Investigate ambiguous problems proactively, asking thoughtful questions and driving issues to resolution with minimal oversight. - Learn new platforms, systems, and technical concepts quickly while demonstrating strong ownership and long-term retention of operational knowledge. - Collaborate cross-functionally when needed, coordinating efforts across Technical Operations, Product, Engineering, Account Management, and external partners to resolve issues and execute initiatives. We'll put each as
- . Now Requirements: from "We’re Looking For Someone With". Let's extract each bullet (they are separated by line breaks). We'll list: - 4+ years in technical operations or a related role - Bachelor's degree or equivalent (advanced degree a plus) - Strong technical knowledge of the programmatic ecosystem - Strong proficiency in SQL and Excel for data analysis, troubleshooting, and workflow automation - Genuine interest in emerging AI technologies, with the ability to apply them to operational workflows and problem-solving - Excellent technical writing and documentation skills - Strong analytical and troubleshooting abilities, with experience diagnosing complex issues - Strong cross-functional collaboration and coordination skills - Excellent communication skills, with the ability to explain technical concepts clearly, identify root causes, and drive issues to resolution - Able to work independently, prioritize effectively, and thrive in a fast-paced environment - Analytical mindset with the ability to balance immediate needs with long-term scalable solutions We'll put as
- under
Requirements
. Now Benefits: from "Perks And Benefits" list and also Company Culture benefits. Perks And Benefits list: - Comprehensive Healthcare Coverage from Day One - Generous Time Off - Holiday Breaks and Quarterly Wellness Days - Equity and Employee Stock Purchase Plan - Family-Focused Benefits and Parental Leave - 401k Retirement Savings Plan with Employer Match - Disability and Life Insurance - Cell Phone Subsidy - Monthly Fitness and Reimbursement Company Culture also mentions