Senior Channel Partner Manager, Strategic Advisory
Ramp · United States · 1 mo ago
RemoteRemoteBusiness DevelopmentFull-time
We need to output HTML fragment with sections: About the role (but note the page already shows job title, we should not repeat job title as heading). The posting includes "About Ramp" (company description) and "About The Role". Also sections: What You'll Do (responsibilities), What You Need (requirements/qualifications/skills), Benefits (list). Also maybe "Pay" and "Schedule" not present, so omit. Also "Skills" maybe part of What You Need. We'll include headings: About the role? Actually "About The Role" is a heading; we can use . We'll need to parse the posting.
Let's extract sections:
About Ramp paragraph: "Ramp is building the smart infrastructure for finance teams, embedded in the transaction flow of every dollar a business spends. We automate how over $200B in annualized spend flows in and out of 70,000+ companies: authorizing payments, flagging risk, categorizing spend, and closing books. The problems are high-stakes, data-dense, and unforgiving. We hire people with high agency and high urgency. We look for slope over intercept. We care less about where you trained and more about what you’ve built. At Ramp, everyone is a builder who owns problems end to end and makes consequential decisions that shape the outcome. The median Ramp customer saves 5% and grows revenue 16% in their first year – far in excess of businesses operating without Ramp. We believe every ambitious company deserves the same. If you want to build systems that directly shape how companies move and manage billions, Ramp is the place to do it."
That's substantive; we could include as a for section headings (e.g. About the role, Responsibilities...). It doesn't forbid other headings, but we could add a heading "About Ramp" as
About the role
. Also maybe "What You'll Do" as Responsibilities. "What You Need" as Requirements/Qualifications/Skills. Benefits as Benefits. We must not include boilerplate like Referral Instructions, Other Notices, etc. Also remove duplicated lines. Also remove cookie/navigation/legal/EEO etc. So we keep only substantive content: About Ramp (company description) maybe as a paragraph? The instruction: Usefor section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need headings for sections we include. The "About Ramp" is not in the list but could be considered "About the role"? Actually "About Ramp" is company overview; maybe we can include as a paragraph under a heading like "About Ramp"? Not in list but we could still include as a
without heading? 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, but suggests those are typical. Safer to include only those headings if content exists. We have content for About the role (the role description). We have Responsibilities (What You'll Do). We have Requirements/Qualifications/Skills (What You Need). We have Benefits. So we will output those four sections. We must not repeat the job title as a heading. The job title is likely "Partner Manager, Institutional Partnerships" or similar but not given explicitly; we just avoid. We need to preserve all substantive information; do not invent or summarize away detail. So we need to copy the text exactly? Probably we can keep the wording but ensure it's within
or
maybe under a heading "About Ramp"? Not required but we could include as a
without heading? The instruction says use
for section headings (e.g. About the role, Responsibilities...). It doesn't forbid other headings, but we could add a heading "About Ramp" as About Ramp
. However the list didn't include About Ramp; but it's okay to add? Might be safer to include as a
without heading? The instruction: "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It implies those are examples; we can still use other headings but they'd be non-standard. Probably they expect us to use those headings only. So we should not create a heading for About Ramp; we can just put it as a
at the start. Then About the role: The heading "About The Role". We'll use
About the role
and then acontaining the paragraph(s) under that heading. The "About The Role" paragraph: "Ramp is building institutional partnerships with top global strategy consulting firms that shape finance transformation and technology decisions for the CFOs and CEOs we serve. These firms influence clients before a buying process begins, advise on the operating and technology decisions that define transformation programs, and can help clients move from strategy to live operational capability. Ramp has an opportunity to build relationships that create value for the firm, its clients, and Ramp, across executive engagement, thought leadership, co-sell, and shared client work. This role will own those relationships and turn them into an institutional go-to-market motion: building credibility with firm leadership, identifying the right client and practice wedges, developing firm-specific plans, leveraging Ramp’s data to amplify firms’ thought leadership, and creating repeatable paths to joint client outcomes. This is a build from the ground up. Ramp's relationships across this ecosystem are early and largely informal today, and this person will be responsible for the relationship, the partnership thesis, and the operating motion that makes a firm a meaningful Ramp partner over time. It is a broader remit than a typical partnerships role." We'll put that in a
. Then Responsibilities: heading
Responsibilities
and a- list of duties from "What You'll Do". The bullet points: - Own Ramp's relationships with a portfolio of top-tier strategy and advisory firms (e.g., McKinsey, Bain, BCG), serving as the primary relationship owner and building credibility with senior firm leadership - Turn executive introductions into structured partnerships, developing the partnership thesis, relationship map, executive sponsor plan, target practices and client wedge for each firm - Negotiate and close the first formal agreements between Ramp and these firms - Build market-facing proof points with Ramp's leadership, marketing and product teams, including executive events, thought leadership and shared client stories - Coordinate execution across Ramp, bringing the right Account Executives, Customer Success Managers, Product, AI Solutions and executive sponsors into each firm relationship - Establish and maintain the operating cadence: relationship maps, firm plans, account maps and next steps We'll output each as
- .
Then Requirements/Qualifications/Skills: heading
Requirements
(or could split but we can combine). The "What You Need" bullet points: - 4+ years of experience at a leading strategy consulting firm (e.g., McKinsey, Bain, BCG) - Exceptional executive presence. You can hold a room with senior leaders, earn trust quickly, and be trusted to represent Ramp in meetings without support - Proven ability to run many work streams and complicated stakeholder management - A builder's instinct. You are energized by an empty page, comfortable without a playbook, and bring structure to ambiguity - Excellent written and verbal communication, and the judgment to calibrate between an executive conversation and a working session - Willingness to travel approximately 25% and to be based in a major metro. New York preferred We'll put each as - under
- .
Then Benefits: heading
- . We'll include all bullet points exactly as they appear. Let's extract benefits: From "Benefits Available To All Full-time Ramp Employees (Global)": - Flexible PTO - Centralized home-office equipment ordering - Health and wellness stipend - Budget for intra-office travel - Weekly coffee stipend Then "United States" benefits: - 100% medical, dental & vision insurance coverage for you, with partial coverage for dependents - One Medical annual membership - 401(k), including employer match on contributions made while employed by Ramp - Fertility HRA (up to $10,000 per year) - Parental leave: up to 16 weeks (birthing + bonding) or 8 weeks (bonding only) at 100% pay - Pet insurance - In-office perks: lunch, snacks, drinks, and more - Relocation expense coverage to NYC or SF (if needed) Then "Canada": - Group medical, dental, and vision coverage through Sun Life - Life, AD&D, and disability coverage - Fertility drug coverage (up to $4,000 lifetime) - Group Retirement Plan with employer match (RRSP + DPSP) - Parental leave: up to 16 weeks (birthing + bonding) or 8 weeks (bonding only) at 100% pay, with additional time available at reduced pay - Employee Assistance Program and virtual care through Lumino Health Then "United Kingdom": - Private medical insurance through Freedom Elite - Virtual GP and at-home care via eMed x Livi - Workplace pension through Penfold, with salary sacrifice option - Parental leave: up to 16 weeks (birthing + bonding) or 8 weeks (bonding only) at 100% pay with additional time available at reduced pay We'll include all as
- . Could also group with subheadings but not needed.
Now we need to output only HTML fragment, no /, no markdown fences.
Thus final output:
About Ramp paragraph...
About the role
About the role paragraph...
Responsibilities
- ... ...
Requirements
- ... ...
Benefits
- ... ...
Benefits
and list from "Benefits Available To All Full-time Ramp Employees (Global)" and then separate US, Canada, UK sections. We need to preserve all substantive information. We'll create a list with items; maybe sublists? But we can just list each benefit as a line item. However we need to keep structure: The benefits are grouped by region. We could keep headings inside the list? But we cannot add extra headings unless they are from the list; but we could embed region as part of the item text. Simpler: create a- with each benefit as