Operations Manager | San Francisco

We need to output HTML fragment with sections: About the role? Actually the posting includes "Who We Are Is What We Do." That's company description. We need to use

for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include sections only when posting has real specific content. We have content: company description (Who We Are Is What We Do) maybe "About the role"? Actually "Who We Are Is What We Do." is company overview. Could be "About the role"? Not exactly. But we can treat as "About the role" maybe? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can choose appropriate headings based on content. We have sections: "Who We Are Is What We Do." (company overview) maybe we can call it "About Deel" but not in list. But we could still use "About the role" heading and put company description? Might be misaligned. Better to follow the spirit: include sections for which we have content: Responsibilities (What You'll Do), Requirements/Qualifications (What We're Looking For), Benefits, maybe Pay? There's a section about Total Rewards and salary ranges but no specific numbers. It says "Our salary range reflects gross base salary..." but no actual numbers. According to rule: never create Pay/Schedule/Benefits sections unless the posting actually states them. Benefits are stated (list). So we can include Benefits section. Pay: they mention salary range but no specific numbers; they say "Our salary range reflects gross base salary." No actual range. That's vague; maybe we should not include Pay because no specific numbers. Schedule: not mentioned. So we include Responsibilities, Requirements/Qualifications (maybe combine), Benefits. Also maybe "About the role" could be company overview. But we could also include a short intro paragraph before headings. The instruction: do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings. So we can start with a

containing the company overview "Who We Are Is What We Do..." then sections. We need to preserve all substantive information, remove boilerplate like EEO, legal, application instructions, etc. Also remove duplicated lines. We must keep the substantive content: company description, why you should be part, why this role, what you'll do, what we're looking for, what success looks like, benefits, total rewards (maybe part of benefits). Also note "PLEASE NOTE: This is a remote role based in San Francisco, CA." That's location info; we could incorporate into a short

maybe under a heading? Not a heading. Could be part of intro. We must not include application deadline, etc. Also remove "Application Deadline for U.S. Applicants..." etc. Also remove "Benefits:" heading? We'll make our own

Benefits

and list. We must not include cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So remove the long EEO paragraph, the accommodation paragraphs, the AI stuff, the NYC Local Law, etc. We must preserve all substantive information: that includes the bullet list of responsibilities, the bullet list of what we're looking for, the success looks like, benefits list, total rewards description (maybe we can incorporate into benefits). Also the company overview paragraphs. We need to output only HTML fragment, no /, no markdown fences. Let's craft:

Who We Are Is What We Do. Deel is the all-in-one payroll and HR platform for global teams. Our vision is to unlock global opportunity for every person, team, and business. Built for the way the world works today, Deel combines HRIS, payroll, compliance, benefits, performance, and equipment management into one seamless platform. With AI-powered tools and a fully owned payroll infrastructure, Deel supports every worker type in 150+ countries—helping businesses scale smarter, faster, and more compliantly. Among the largest globally distributed companies in the world, our team of 7,000 spans more than 100 countries, speaks 74 languages, and brings a connected and dynamic culture that drives continuous learning and innovation for our customers. Why should you be part of our success story? As the fastest-growing Software as a Service (SaaS) company in history, Deel is transforming how global talent connects with world-class companies – breaking down borders that have traditionally limited both hiring and career opportunities. We're not just building software; we're creating the infrastructure for the future of work, enabling a more diverse and inclusive global economy. In 2024 alone, we paid $11.2 billion to workers in nearly 100 currencies and provided healthcare and benefits to workers in 109 countries—ensuring people get paid and protected, no matter where they are. Our momentum is reflected in our achievements and customer satisfaction: CNBC Disruptor 50, Forbes Cloud 100, Deloitte Fast 500, and repeated recognition on Y Combinator's top companies list – all while maintaining a 4.83 average rating from 15,000 reviews across G2, Trustpilot, Captera, Apple and Google. Your experience at Deel will be a career accelerator. At the forefront of the global work revolution, you'll tackle complex challenges that impact millions of people's working lives. With our momentum—backed by a $17.3 billion valuation and $1 B in Annual Recurring Revenue (ARR) in just over five years—you'll drive meaningful impact while building expertise that makes you a sought-after leader in the transformation of global work. Why this role? Enterprise customers expect flawless execution at scale. As an Operations Manager you'll own the operational outcome of some of Deel's most strategic customers, ensuring they launch successfully and continue to operate efficiently as they grow. This role is designed for exceptional early-career operators who thrive in fast-paced environments, enjoy solving complex operational problems, and want to accelerate their careers through ownership and continuous learning. You'll gain deep exposure across onboarding, customer operations, payroll, product, and process improvement while helping build the operating model that supports Deel's largest customers. PLEASE NOTE: This is a remote role based in San Francisco, CA.

Then responsibilities:

Responsibilities

• Own the onboarding and operational delivery for a portfolio of enterprise customers.
• Partner cross-functionally with Product, Sales, Payroll, Legal, and Support to resolve operational challenges.
• Drive operational excellence by identifying bottlenecks, improving processes, and implementing scalable solutions.
• Build trusted relationships with customers while ensuring a high-quality operational experience.
• Analyze operational data to identify trends, risks, and opportunities for improvement.
• Take ownership of increasingly complex customer environments as your expertise grows.
• Contribute to building new operational playbooks that improve efficiency across the Operations organization.

Then requirements/qualifications: we have "What We're Looking For" and "What Success Looks Like". Could combine into Requirements and Qualifications? The instruction says use headings like Requirements, Qualifications, Skills. We have content for what we're looking for (experience, traits) and what success looks like (outcomes). Could make two sections: Requirements and Qualifications? Or maybe "Requirements" for what we're looking for, and "Qualifications" for success looks like? But success looks like is more about outcomes, not qualifications. Might be better to have a single section "Requirements" covering what we're looking for, and maybe another "Qualifications" for success looks like? However success looks like is not a qualification but expected outcomes. Could treat as "What Success Looks Like" as a separate section but not in allowed headings list. The instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings? It says use those for section headings (e.g...). Likely we should stick to those headings. So we can map: - Requirements: the bullet list of what we're looking for (experience, traits, etc.) - Qualifications: maybe the success looks like? Or we could omit Qualifications if not substantive. But we have success looks like content; we could put under Qualifications as expected outcomes? Might be okay. Alternatively we could have Requirements and Skills. Skills bullet list not explicit; we have traits like analytical ability, communication, etc. Could treat as Skills. Let's decide: We'll have:

Requirements

• approximately 1–3 years of professional experience.
• You don't want a career in investment banking or consulting, you want an accelerated career trajectory in tech.
• You’re attracted by high ownership, steep learning curves, and the chance to make an outsized impact early in your careers.
• Hold a strong technical or analytical degree, ideally in Engineering, Mathematics, Computer Science, Physics, Economics, or a related discipline.
• Enjoy solving difficult problems and bringing structure to ambiguity.
• Have outstanding communication and stakeholder management skills.
• Are highly organized, execution-oriented, and comfortable managing multiple priorities simultaneously.
• Learn quickly, embrace ownership, and consistently seek opportunities to improve how things work.

Then maybe

Skills

but we already covered communication etc. Could skip. Qualifications: we could put "What Success Looks Like" as qualifications? Actually success looks like are outcomes, not qualifications. But we could still put under Qualifications as expected achievements. Let's do:

Qualifications

• Deliver exceptional operational outcomes for enterprise customers.
• Build deep expertise across Deel's products and operational workflows.
• Continuously improve internal processes through automation and operational excellence.
• Take on increasingly complex customer portfolios as your experience grows.
• Develop into a trusted operational leader capable of owning large-scale enterprise operations.

Now Benefits:

Benefits

• Health Insurance Effective from Day 1 (Medical, Dental, & Vision)
• 401k Retirement Plan
• Disability Insurance
• Life Insurance
• Employee Assistance Program (EAP)
• Flexible Savings Account (FSA)
• Flexible time off (PTO)
• 12 paid holidays per year
• Parental leave: 16 weeks for the birthing parent and 8 weeks for the non-birthing parent

We might also include Total Rewards description as a paragraph under Benefits? Could add a

after list: "Total Rewards Our workforce deserves fair and competitive pay that meets them where they are. With scalable benefits, rewards, and perks, our total rewards programs reflect our commitment to inclusivity and access for all. Our salary range reflects gross base salary. For commercial roles with commission eligibility, this figure represents On-Target Earnings (OTE), inclusive of base salary and target commission.Salary ranges are quoted in USD as a consistent global reference. Your offer will be localized to your country's currency using a market-aligned conversion.Final pay is based on objective, job-related criteria including experience, skills, and location.We don't ask about salary history. Offers are based on the role and what you bring to it.Some things you'll enjoy Stock grant opportunities dependent on your role, employment status and locationAdditional perks and benefits based on your employment status and countryOptional flexible working office membership, with IWG". This is substantive; we should keep it. It's not a list but prose. So after Benefits list we can