业务分析师：承运商数据、集成与自动化（商业保险）

About CoverForce

CoverForce is transforming how commercial insurance gets bought and sold. Thousands of insurance agents and corporate customers use our platform to quote, compare, and buy business insurance, and we partner with carriers like Travelers, Liberty Mutual, and Chubb to streamline underwriting and sales — cutting the time spent on a single policy by 60%.
Our platform includes a quote-and-bind experience trusted by several of the top 100 insurance distributors in the US, and an embedded insurance API used by partners like Walmart, Gusto, and Uber to offer business insurance directly inside their own products. We're building toward being the connective layer for insurance distribution — the Plaid of insurance.
Launched in 2022, CoverForce has raised over $18M from Insight Partners, NYCA Partners, QED Investors, and executives from Google, Uber, Walmart, and a co-founder of Plaid.
About the role
Every carrier CoverForce integrates with speaks its own dialect — its own industry codes, its own underwriting questions, its own appetite rules — and none of it lines up with anyone else's. This role exists to translate all of that carrier-specific chaos into one clean, standardized structure that our platform runs on, and to keep it accurate as carriers change their rules underneath us.
This isn't a project-management or requirements-gathering role. You won't be writing tickets or managing a backlog. You'll be doing the actual data work: opening a carrier's raw underwriting sheet, figuring out what it means, and turning it into something our system can use correctly. It's detailed, carrier-by-carrier work, and it rewards someone who gets faster at it over time by building tools and shortcuts rather than just grinding through the rows.
What you'll do
You'll be working against a few recurring problems, not a fixed checklist. How you solve them is up to you.

• Industry and class codes don't match across carriers. Every carrier has its own proprietary code list — often 1,000+ codes — mapped against standardized systems like NAICS, SIC, and NCCI. Someone needs to build and hold that mapping, and figure out an approach that scales as carriers revise their lists.

• Underwriting logic arrives as a mess. Carriers hand us their underwriting questions as a spreadsheet, an API spec, or a PDF — never in a form we can use directly. Figuring out what a question actually means, when it applies (which states, which class codes), what it depends on, and whether we already have the answer elsewhere, is a real problem to be solved for each carrier.

• Onboarding a new carrier and updating an existing one are the same problem. Carriers don't stand still — they revise codes, questions, and appetite on their own schedule, constantly, across 65+ live integrations. There's no meaningful difference between doing this work for a brand-new carrier versus an existing one that just changed something; it's the same kind of problem, repeated at scale.

• Carriers ask the same question in different words. We run a script that tries to flag underwriting questions that are effectively duplicates across carriers, so we only ask each one once. The script gets this wrong sometimes — someone needs to catch it.

• Carrier appetite isn't documented anywhere consistent. We need a reliable way to know, for a given industry, state, and policy type, which carriers will actually write the business — and to keep that current.

• Leadership will occasionally need a fast, accurate answer on a carrier, coverage, or data-quality question that doesn't fit neatly into the above.

The single biggest lever in this role is automation. This work is naturally repetitive, and we want someone who treats that repetition as a problem to solve rather than a task to grind through — building scripts, spreadsheet tooling, or AI-assisted workflows, and pulling in engineering help or third-party tools where that's the faster path. There's a lot of open scope here to explore what's possible.
What we're looking for
Must have

• Exceptional attention to detail. You're working in spreadsheets with thousands of rows where one wrong cell can break a carrier integration, and that has to bother you enough to catch it.

• A genuine drive to automate. When something's repetitive, you actively want to solve it — a formula, a script, an AI-assisted workflow, or looping in a developer or third-party tool to fix it properly — rather than just doing it faster by hand.

• Real ownership. You can take a messy, inconsistent source file from a carrier and turn it into clean, correct, structured output without needing much hand-holding.

• You like asking questions. Not just tolerate needing to — you actively seek out the person or source who can clarify something rather than guessing.

• A fast learner. You can pick up an unfamiliar domain quickly and get comfortable enough in it to be dangerous within weeks, not months.

• Able to work remotely from India.

Nice to have

• Experience in commercial P&C insurance (BOP, Workers' Comp, GL, Auto) — this helps you pick up underwriting language faster, but it's teachable, so it's not a hard requirement.

• Familiarity with NAICS, SIC, or NCCI coding systems.

• Background as a business analyst, product analyst, or data/systems analyst doing actual requirements-mapping or systems-integration work — as opposed to project coordination, sprint planning, or ticket triage. (Business analysts at banks or financial institutions doing systems integration and data mapping are a strong fit even without insurance experience.)

• Prior experience at a company integrating with multiple external partner APIs or carriers.

• Python or other scripting experience.

A note on fit: this role has real room to grow — as our carrier count keeps climbing, there's a lot of scope to build automation and eventually own larger pieces of this pipeline. But day one is hands-on, detailed data work, not strategy. It's a great fit for someone who wants to be excellent at something specific and build outward from there, not someone looking to skip straight to a senior, hands-off role.
Originally posted on Himalayas