Jobs · Manufacturing · California

Director, Head of Revenue Operations

RevOps Report · Mountain View, CA · 4 wk ago
ManufacturingFull-time
We need to output HTML fragment with sections: About the role, Responsibilities (maybe "What You'll Do"), Requirements/Qualifications (maybe "What You'll Bring"), maybe Benefits, Pay, Schedule if present. The posting includes: About The Role (description), Why This Role Matters (maybe part of About the role?), What You'll Do (list of responsibilities), What You'll Bring (requirements). Also includes Company Overview (maybe not needed as separate heading? It says use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can map: About the role = "About The Role" plus maybe "Why This Role Matters". Responsibilities = "What You'll Do". Requirements/Qualifications = "What You'll Bring". Skills maybe part of that. No explicit Benefits, Pay, Schedule. So we should not create those sections. We must not repeat job title as heading. No Job ID etc. Remove boilerplate like EEO, privacy, etc. Also remove navigation, cookie, legal. Also remove "About This Role Company Overview ID.me is the next‑generation..." That's company overview; maybe we can include as part of About the role? But the instruction: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should have headings for sections that have content. Likely we need About the role (including company overview and why role matters). Responsibilities (What You'll Do). Requirements (What You'll Bring). Possibly also Skills (but we can embed in Requirements). We'll not create empty sections. We need to preserve all substantive information, not invent or summarize away detail. So we need to keep the details from the posting. We need to format lists with
  • . For prose use

    . For headings use

    . We must output only HTML fragment, no /, no markdown fences. Let's extract content. Company Overview paragraph: "ID.me is the next‑generation digital identity wallet that simplifies how individuals securely prove their identity online. Consumers can verify their identity with ID.me once and seamlessly login across websites without having to create a new login and verify their identity again. Over 152 million users experience streamlined login and identity verification with ID.me at 20 federal agencies, 45 state government agencies, and 70+ healthcare organizations. More than 600+ consumer brands use ID.me to verify communities and user segments to honor service and build more authentic relationships. ID.me's technology meets the federal standards for consumer authentication set by the Commerce Department and is approved as a NIST 800‑63‑3 IAL2 / AAL2 credential service provider by the Kantara Initiative. ID.me is committed to "No Identity Left Behind" to enable all people to have a secure digital identity. To learn more, visit https://network.id.me/. ID.me is a full‑time, in‑office culture. Unless a specific job description explicitly states otherwise, all roles are on‑site five days per week at one of our offices in McLean, VA; Mountain View, CA; New York City, NY; or Tampa, FL. Certain roles — such as field‑based sales or other remote‑by‑design positions — may have different work arrangements as noted in their individual postings. At ID.me, we embrace the thoughtful use of AI tools in our daily work and there are even occasions where we leverage AI in our hiring process. However, during the interview process, we want to understand your individual skills and experiences. Therefore, we have guidelines on how AI can be appropriately used during your application and interviews which can be found here." That's a lot; but we need to preserve all substantive information. However, we should remove boilerplate like EEO etc. The company overview is substantive? It's about the company. Probably we should keep it as part of About the role. Then "About The Role" paragraph: "ID.me is looking for a Director of Revenue Operations to build and lead the function that connects our go‑to‑market motion to the financial engine of the business. This is a newly scoped, high‑visibility role reporting directly to the CFO, with significant partnership across Sales, Finance, Legal, and People teams. ID.me's consumption‑based revenue model — where usage, verification volume, and contract structure all drive top‑line outcomes — makes Revenue Operations a strategic function rather than a purely administrative one. You'll own the systems, analytics, and incentive structures that make revenue predictable, deals efficient, and sales performance fairly and effectively rewarded. This role is ideal for someone who has operated at the intersection of sales, finance, and analytics — someone equally comfortable structuring a deal desk workflow, building a bookings‑to‑revenue bridge, or designing a compensation plan that actually motivates the right behavior." Then "Why This Role Matters": "This position sits at the center of ID.me's growth strategy — with direct visibility into the CFO's office and a mandate to shape how the company measures, forecasts, and rewards revenue performance. You'll have the opportunity to build the operating rhythm and infrastructure for a scaling, consumption‑based business from a genuinely influential sea" (cut off maybe "sea"? Actually original: "from a genuinely influential sea". Probably truncated but we keep as is.) Then "What You'll Do": list of responsibilities with bullet points. Let's extract bullet points: - Own and continuously improve the deal desk function — pricing approvals, non‑standard terms, discounting governance, and contract structuring for a consumption‑based pricing model - Serve as the operational backbone for the sales organization: CRM architecture (Salesforce), pipeline hygiene, territory and quota planning, and sales process design - Partner with Legal and Finance to streamline the quote‑to‑cash process and reduce deal cycle friction without compromising margin or compliance - Build scalable playbooks for deal structuring, renewals, and expansion opportunities - Compensation & Incentive Design: Design, model, and administer sales compensation plans (quotas, accelerators, SPIFs) that align seller behavior with company revenue priorities - Partner with People/HR and Finance leadership on plan governance, approval workflows, and compensation committee materials - Run quarterly/annual plan reviews, using performance data to recommend structural changes as the business and pricing model evolve - Ensure compensation calculations are accurate, auditable, and defensible — including close partnership with Finance on accruals and payout reconciliation We need to keep each as list items. Then "What You'll Bring": requirements. List: - 8+ years of experience in Revenue Operations, Sales Operations, FP&A, or a related field, with at least 3+ years in a leadership capacity - Demonstrated experience owning deal desk and/or sales compensation design in a B2B SaaS or consumption/usage‑based revenue model - Strong financial and analytical fluency — comfortable building models independently, not just reviewing them - Deep familiarity with Salesforce (or comparable CRM) and modern BI/analytics tooling - Track record partnering cross‑functionally with Finance, Legal, and People leaders, ideally with direct exposure to executive or board‑level reporting - Excellent communication skills — able to translate complex revenue mechanics into clear narratives for non‑technical stakeholders - Experience operating in a high‑growth, fast‑changing environment where process is still being built, not just maintained Nice to Have (maybe we can include as a subsection under Requirements or separate "Nice to Have" but not required heading. Could be part of Requirements as a list but we could keep as a separate bullet list under "Nice to Have" but heading not in allowed list; but we could incorporate as part of Requirements with a note. However instruction: Prefer a few substantive sections over many thin ones. We could include Nice to Have as part of Requirements section, maybe as a sub-list with a note. But we must not invent headings not allowed. Could add a

    saying "Nice to have:" then a list. That's okay. Nice to Have items: - Experience in identity verification, fraud/risk, cybersecurity, or another trust‑and‑safety‑adjacent SaaS category - Prior experience supporting a company through M&A, corporate restructuring, or investor/board reporting cycles - Experience standing up a Revenue Operations function from scratch or significantly re‑architecting one We'll keep them. Now we need to output HTML. Structure:

    About the role

    Company overview paragraph + About The Role paragraph + Why This Role Matters paragraph (maybe combine). Ensure we keep all sentences. We must not include repetitive or boilerplate like EEO etc. Already removed. We need to ensure we don't include any navigation etc. Let's craft the About the role content: Combine: Company overview: "ID.me is the next‑generation digital identity wallet that simplifies how individuals securely prove their identity online. Consumers can verify their identity with ID.me once and seamlessly login across websites without having to create a new login and verify their identity again. Over 152 million users experience streamlined login and identity verification with ID.me at 20 federal agencies, 45 state government agencies, and 70+ healthcare organizations. More than 600+ consumer brands use ID.me to verify communities and user segments to honor service and build more authentic relationships. ID.me's technology meets the federal standards for consumer authentication set by the Commerce Department and is approved as a NIST 800‑63‑3 IAL2 / AAL2 credential service provider by the Kantara Initiative. ID.me is committed to "No Identity Left Behind" to enable all people to have a secure digital identity. To learn more, visit https://network.id.me/. ID.me is a full‑time, in‑office culture. Unless a specific job description explicitly states otherwise, all roles are on‑site five days per week at one of our offices in McLean, VA; Mountain View, CA; New York City, NY; or Tampa, FL. Certain roles — such as field‑based sales or other remote‑by‑design positions — may have different work arrangements as noted in their individual postings. At ID.me, we embrace the thoughtful use of AI tools in our daily work and there are even occasions where we leverage AI in our hiring process. However, during the interview process, we want to understand your individual skills and experiences. Therefore, we have guidelines on how AI can be appropriately used during your application and interviews which can be found here." Then About The Role paragraph: "ID.me is looking for a Director of Revenue Operations to build and lead the function that connects our go‑to‑market motion to the financial engine of the business. This is a newly scoped, high‑visibility role reporting directly to the CFO, with significant partnership across Sales, Finance, Legal, and People teams. ID.me's consumption‑based revenue model — where usage, verification volume, and contract structure all drive top‑line outcomes — makes Revenue Operations a strategic function rather than a purely administrative one. You'll own the systems, analytics, and incentive structures that make revenue predictable, deals efficient, and sales performance fairly and effectively rewarded. This role is ideal for someone who has operated at the intersection of sales, finance, and analytics — someone equally comfortable structuring a deal desk workflow, building a bookings‑to‑revenue bridge, or designing a compensation plan that actually motivates the right behavior." Then Why This Role Matters: "This position sits at the center of ID.me's growth strategy — with direct visibility into the CFO's office and a mandate to shape how the company measures, forecasts, and rewards revenue performance. You'll have the opportunity to build the operating rhythm and infrastructure for a scaling, consumption‑based business from a genuinely influential sea" We need to keep the truncated sentence as is. Now Responsibilities section:

    Responsibilities

    • Own and continuously improve the deal desk function — pricing approvals, non‑standard terms, discounting governance, and contract structuring for a consumption‑based pricing model
    • Serve as the operational backbone for the sales organization: CRM architecture (Salesforce), pipeline hygiene, territory and quota planning, and sales process design
    • Partner with Legal and Finance

Similar jobs