Client Services Lead, Finance

We need to output HTML fragment with sections: About the role? Actually the posting includes "About Mercor" description, then "What You'll Do", then "Experience What We're Looking For", then "Mindset & Skills", then "Nice to Have", then "Benefits", then "Compensation Range". We need to use

for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. However we must only include sections when posting has real specific content. The headings we can use: About the role (maybe we can use About Mercor? but spec says headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to map content accordingly. We have: - About Mercor (company description) could go under "About the role"? Actually "About the role" is about the job, not company. But we can still use "About the role" heading for company overview? The spec says use those headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid using other headings? It says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect those headings only. We should map content to those headings as appropriate. We have: - Responsibilities: "What You'll Do" bullet list. - Requirements/Qualifications: "Experience What We're Looking For" (5+ years etc) plus "Mindset & Skills" maybe as Skills. - Skills: could be "Mindset & Skills" and "Nice to Have" maybe as additional skills. - Benefits: list. - Pay: Compensation Range. - Schedule: Not mentioned; we should not include Schedule if not present. - About the role: maybe we can include a brief paragraph summarizing the role? The posting includes "About Mercor" which is company overview, not role. But we could treat that as "About the role" (maybe they want company description). However spec says do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it. It doesn't forbid using About the role for company description. We'll include About the role with the Mercor mission description. We must preserve ALL substantive information; do NOT invent or summarize away detail. Remove boilerplate etc. We need to output only HTML fragment, no /, no markdown fences. We'll produce:

About the role

Mercor's mission is to organize human intelligence to power the AI economy. We're a leading AI data company, building the layer between human expertise and frontier models. Millions of domain experts on the platform are paid over $4 million per day to train frontier AI models. Mercor's APEX benchmark family measures AI's real-world impact on professional work. Mercor Enterprise brings this same infrastructure to Fortune 500 companies: helping companies capture how their best people actually work, translating that expertise directly back into agents. Mercor is creating a new category of work where expertise powers AI advancement. Achieving this requires an ambitious, fast-paced and deeply committed team. You’ll work alongside researchers, operators, and AI companies at the forefront of shaping the systems that are redefining society. Mercor is a profitable Series C company valued at $10 billion. We work in-person five days a week in our San Francisco, NYC, or London offices.

Then Responsibilities:

Responsibilities

• Build the Finance Client Function (0 → 1): Identify, engage, and onboard financial services clients and partners
• Test and iterate on service models tailored to finance-sector needs (compliance, data sensitivity, procurement cycles)
• Create early playbooks for how Mercor serves finance clients
• Account Ownership & Growth: Lead client conversations end-to-end, from scoping through renewal and expansion; Qualify client needs, define mutual value, and drive engagements to close; Structure commercial terms suited to financial institutions' procurement and compliance norms
• Contracting & Negotiation: Own negotiations on pricing, scope, timelines, and obligations with finance clients; Work closely with Legal and Finance to move quickly without sacrificing rigor; Navigate data rights, compliance, and security requirements specific to financial services
• Stakeholder Management: Act as the primary point of contact for finance-sector clients and senior stakeholders; Manage complex, multi-party relationships (compliance, procurement, technical teams) with clarity and credibility; Align internal teams (Product, Research, Ops, Legal) around finance client priorities
• Operate Scrappily, Then Systematize: Start hands-on: build client lists, run outreach, draft docs, close deals yourself; Identify patterns and convert them into repeatable processes as the finance book of business scales

Then Requirements/Qualifications: We have Experience section and Mindset & Skills. Could combine into Requirements (maybe split into Requirements and Skills). Let's do:

Requirements

• 5+ years in Client Service, Account Management, or Commercial roles, serving financial services clients
• Proven experience negotiating and closing contracts
• Track record managing high-stakes external stakeholders, including compliance/procurement functions
• Direct experience working with data products

Skills

• Builder mentality: excited by ambiguity and 0→1 problems
• Scrappy, resourceful, comfortable with unglamorous work early on
• Strong commercial instincts and negotiation skills
• Clear, concise communicator with executive presence
• Able to operate independently while partnering closely with internal teams

Nice to Have could be additional Skills or maybe under Requirements as "Nice to Have". Since spec says we can include Skills section; we could add another

Skills

but duplicate heading not ideal. Could combine Nice to Have into Skills as bullet points prefixed with "Nice to have:" but better to add another section maybe "Preferred Qualifications". However spec only gave examples; but we can still use

for any section heading; not limited to those examples. It says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It implies those are typical but not exclusive? Safer to stick to those. We could incorporate Nice to Have into Skills as additional bullets. Thus Skills section will include both mindset & skills and nice to have. Let's list: - Builder mentality: excited by ambiguity and 0→1 problems - Scrappy, resourceful, comfortable with unglamorous work early on - Strong commercial instincts and negotiation skills - Clear, concise communicator with executive presence - Able to operate independently while partnering closely with internal teams - Nice to have: Experience in fintech, banking, asset management, or financial data platforms - Nice to have: Exposure to data-driven products, AI, or technical stakeholders - Nice to have: Background working cross-functionally with legal and finance teams - Nice to have: Familiarity with financial services compliance and data rights (e.g., SOC 2, GLBA) Now Benefits:

Benefits

• Bi-annual performance bonus structure
• Generous equity grant vested over 4 years
• Up to $15k relocation bonus
• $10K housing bonus (if you live within 0.5 miles of our office)
• $1.5K monthly stipend for meals
• Free Equinox membership
• $200 monthly laundry reimbursement
• $200 monthly personal wellness reimbursement
• Health, Dental, Vision insurance

Pay:

Pay

Compensation Range: $160K - $180K

Schedule: Not present, so omit. We must not include any boilerplate like EEO etc. Already removed. Now output only HTML fragment. Check for duplicate content: We included About the role with Mercor description repeated twice? The posting had duplicate paragraphs: "Mercor is creating a new category of work..." appears twice. We should preserve all substantive information but not repeat duplicated lines? The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." So we should remove duplicated lines. The Mercor description appears twice; we should include it only once. Also "Mercor is a profitable Series C company valued at $10 billion. We work in-person five days a week in our San Francisco, NYC, or London offices." appears twice as well. So we need to deduplicate. Thus About the role paragraph should contain unique content: mission, leading AI data company, millions of domain experts paid, APEX benchmark, Mercor Enterprise, creating new category of work, ambitious fast-paced team, work alongside researchers etc, profitable Series C valued at $10B, work in-person five days a week in SF/NYC/London. Ensure we don't repeat. Let's craft: Mercor's mission is to organize human intelligence to power the AI economy. We're a leading AI data company, building the layer between human expertise and frontier models. Millions of domain experts on the platform are paid over $4 million per day to train frontier AI models. Mercor's APEX benchmark family measures AI's real-world impact on professional work. Mercor Enterprise brings this same infrastructure to Fortune 500 companies: helping companies capture how their best people actually work, translating that expertise directly back into agents. Mercor is creating a new category of work where expertise powers AI advancement. Achieving this requires an ambitious, fast-paced and deeply committed team. You'll work alongside researchers, operators, and AI companies at the forefront of shaping the systems that are redefining society. Mercor is a profitable Series C company valued at $10 billion. We work in-person five days a week in our San Francisco, NYC, or London offices. That's all unique. Now ensure we didn't miss any substantive info: The "What You'll Do" section we captured fully. The "Experience What We're Looking For" we captured as Requirements. The "Mindset & Skills" we captured as Skills (plus nice to have). The "Nice to Have" we incorporated. Benefits captured. Compensation captured. Check for any other info: The posting also had "Mercor's mission..." repeated earlier; we used that. Also there was "Mercor is creating a new category of work..." repeated; we used once. Also "Achieving this requires an ambitious, fast-paced and deeply committed team." used. Also "You'll work alongside researchers..." used. Also "Mercor is a profitable Series C company valued at $10 billion." used. Also "We work in-person five days a week in our San Francisco, NYC, or London offices." used. All good. Now produce HTML. Be careful to close tags properly. Let's write:

About the role

Mercor's mission is to organize human intelligence to power the AI economy. We're a leading AI data company, building the layer between human expertise and frontier models. Millions of domain experts on the platform are paid over $4 million per day to train frontier AI models. Mercor's APEX benchmark family measures AI's real-world impact on professional work. Mercor Enterprise brings this same infrastructure to Fortune 500 companies: helping companies capture how their best people actually work, translating that expertise directly back into agents. Mercor is creating a new category of work where expertise powers AI advancement. Achieving this requires an ambitious