Enterprise Account Executive

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. Must not include Job ID etc. Must preserve all substantive info. Remove boilerplate. Must not create sections with filler like "commensurate with experience". So we need to parse the posting. Let's extract content. First paragraph: About ObinAI ... description of company. That's about the company, not role. Could be "About the role"? Actually "About ObinAI" is company overview. The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to map content to these headings. The posting includes sections: "The role", "Who you work with", "How the commercial model works", "What you will own", "What success looks like", "What we are looking for", "Compensation". Also earlier description about company maybe could go under "About the role"? But "About the role" usually describes the role itself. The posting has "The role" heading. So we can put that under About the role? Or we could treat "About the role" as the company description? The instruction says use those headings as examples; we can include only those that have real content. So we need to decide which sections have content. Let's map: - About the role: Could include description of the role: "You are our first dedicated net-new seller...". That's under "The role". Also "Who you work with" maybe part of role. Could combine. - Responsibilities: Could be "What you will own" list: New logo revenue, Target account strategy, Outbound, Committee navigation, Qualification discipline, Commercial construction, Clean handoff, The playbook. - Requirements: Could be "What we are looking for" bullet list: Must have A number you have personally carried and hit... etc. - Qualifications: Could be overlapping with Requirements; maybe we separate: Must have (requirements) and Strongly preferred (qualifications). So Requirements = must-have; Qualifications = strongly preferred. - Skills: Could be skills like "Sold into financial institutions", "Committee selling", "Comfortable without a brand", etc. But those are also in requirements. Might be better to put skills under Skills. - Benefits: Not explicitly listed besides compensation? There's mention of equity, non-recoverable draw. That's compensation. Benefits maybe not given. So we may omit Benefits if no specific content. - Pay: Compensation section: "Compensation: 160-200K Base/ 360-400K OTE, uncapped, OTE, plus equity. Non-recoverable draw for the first two quarters." That's pay. - Schedule: Not mentioned. So omit. Also we have "What success looks like" with 90 days, 6 months, 12 months. That could be under Responsibilities or maybe a separate section like "Expectations". Not in list; we could put under Responsibilities or maybe under About the role? But we need to stick to given headings. Could treat as part of Responsibilities (what success looks like). Or we could create a separate section not in list? Instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says e.g., implying those are examples but we could use others? It says "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect only those headings. So we should map content to those. Thus we need to decide where to put "What success looks like". Could be under Responsibilities (as expectations). Or maybe under About the role? I'd put under Responsibilities as part of what you will own? Actually "What you will own" is responsibilities. Success looks like is outcomes. Could be under Responsibilities as well. Also "How the commercial model works" maybe part of Responsibilities? Could be under Responsibilities as well (commercial construction). Might be okay. We need to preserve all substantive information. So we need to include details: company description, founder info, advisors, production stats, etc. Where to put? Possibly under About the role (company overview). The instruction says "About the role" heading for section headings (e.g. About the role...). So we can use About the role to include company overview and role description. Thus structure:

About the role

Company description: ObinAI ... (the first paragraph). Then role description: "You are our first dedicated net-new seller..." etc. Also include "Who you work with" maybe as part of this paragraph or separate

. Could break into multiple

but still under same heading. Then

Responsibilities

• New logo revenue...
etc list from "What you will own". Also include "How the commercial model works" maybe as a responsibility? Could add as separate bullet: "Navigate commercial model: selling one-time solution build, platform fee, recurring maintenance on multi-year terms; price from first principles." Also include success metrics? Could add bullet: "Achieve 90‑day milestones: working target account list, first meetings booked, at least two qualified opportunities sourced; 6‑month pipeline covering number with first closed‑won; 12‑month repeatable motion." But that's more expectations; could be under Responsibilities as well. Then

Requirements

• Must have A number you have personally carried and hit.
• Enterprise quota, seven‑figure deals, and a quarter you missed that you can discuss honestly.
• Net‑New Logo Sales: builder that originates new deals, can do so with little support or inbound.
• Sold into financial institutions: banks, insurers, or asset managers; know what compliance, model risk, and procurement do to a timeline.
• Committee selling: expert at navigating multi‑threaded, multi‑stakeholder deals at large global enterprises.
• Comfortable without a brand: evangelizing new technology and working with limited brand recognition is exciting, not scary.
Then

Qualifications

• Strongly preferred: 7 to 15 years in enterprise software or services sales.
• Insurance, private credit, or asset management domain experience specifically.
• Enough fluency in AI architecture, security, and governance to be credible with technology and risk leaders.
• Early‑stage experience, or a track record as a first or early sales hire.
• Experience selling services‑plus‑product rather than pure subscription.
• Experience selling with or through a hyperscaler.
Then

Skills

Maybe we can list skills like "Outbound prospecting", "Target account strategy", "Committee navigation", "Qualification discipline (MEDDPICC)", "Commercial construction (scope, price, negotiate, close)", "Clean handoff to delivery pod", "Playbook iteration". But these are already responsibilities. Might be redundant. Could instead put skills like "Consultative selling", "Solution selling", "Technical fluency", "Stakeholder management". But we need to preserve all substantive info; we already captured them in responsibilities/requirements. If we add Skills section, we must ensure not to repeat same content verbatim? It's okay to repeat but better to avoid duplication. However instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. It doesn't forbid duplication, but we should aim to not create thin sections. Skills could be thin if we just list a few items. Might be better to omit Skills if no distinct content beyond what's already covered. But we need to decide: The instruction says prefer a few substantive sections over many thin ones. So we could omit Skills if it would be thin. However we have no explicit skills list besides those already in responsibilities/requirements. So we can omit Skills. Benefits: Not specified besides equity and draw (which is compensation). So we could omit Benefits. Pay: We have compensation details. So include Pay. Schedule: Not mentioned, omit. Thus final HTML:

About the role

ObinAI is the agentic workforce for regulated finance. We build AI agents trained on how a specific firm actually works — its operating logic, its edge cases, its regulatory framework — that run inside the client's own cloud and governance boundary. Every agent we build belongs to the client: their cloud, their model, their IP. Outputs are auditable, traceable, and reversible. We help leading institutions rethink critical workflows across insurance, private credit, private equity, and commercial lending. And with our platform and expert services we can deliver, fast; our clients have seen the time to production reduced from 18 months to 6 or less. Our founders are Apoorv Saxena (Global Head of AI at JPMorgan Chase, Managing Director at Silver Lake, Head of Product for Cloud AI at Google) and Lak Lakshmana (Data & AI operating executive at Silver Lake, Head of Data Analytics & AI at Google). Our advisors include Fei‑Fei Li and Lukasz Kaiser. We are in production at institutions representing over $1 trillion in assets, profitable since seed, and closing a Series A.

You are our first dedicated net‑new seller. Today our revenue comes from a small number of very large relationships that our founders opened. Your job is to build the next set. You will originate and close new logos at banks, insurance carriers, asset managers, and alternative managers. Deals are seven and eight figures in total contract value, sold to buying committees that include a business owner, a CIO, model risk, third‑party risk, InfoSec, legal, and procurement.

Who you work with: The founders (Apoorv and Lak still open doors and still sit in rooms). A sales engineer, who validates the ROI hypothesis against real client data before we commit to a build. Domain experts — practitioners in insurance, credit, and real estate who make the pitch land with the people who will actually use the agent. Forward‑deployed engineers and PMs, who scope what you sell and then go build it. Partner channels, including our Google Cloud relationship and Marketplace listing.

Responsibilities

• Own new‑logo revenue – own a number and build the pipeline that supports it.
• Define and execute target‑account strategy across insurance, private credit, PE, and commercial lending.
• Conduct outbound prospecting via founder network, partner channels, events, and your own cold origination.
• Navigate multi‑threaded committees (business, technology, risk, procurement) to drive deals forward.
• Apply qualification discipline (MEDDPICC) against real exit criteria; kill deals that will not close.
• Perform commercial construction: scope with engineering, price from first principles, negotiate, and close.
• Ensure clean handoff: deliver a signed scope the delivery pod can actually build.
• Feed learned insights back into positioning, objection handling, and the sales process to refine the playbook.
• Understand and sell the commercial model: one‑time solution build, platform fee, recurring maintenance on multi‑year terms, priced deal‑by‑deal from first principles.
• Achieve success milestones: 90 days – working target account list, first meetings booked, at least two qualified opportunities you sourced; 6 months – pipeline covering your quota with sourced deals and first closed‑won; 12 months – repeatable motion that a second AE could run.

Requirements

• Must have a number you