Roamly - Actuary

We need to output HTML fragment with sections: About the role? Actually the posting includes "About Us", "About Roamly", "About The Role", "Requirements", "Key Responsibilities & Deliverables", "Who You Are", "What You'll Bring", "Benefits". We need to use

for section headings (e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We should not repeat job title as heading. We need to include sections only when posting has real specific content. We need to preserve all substantive info, remove boilerplate, navigation, legal, EEO, etc. The posting includes "About Us", "About Roamly", "About The Role". Those are not required headings per list but we can treat them as sections? The instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It suggests we can use those headings if they exist. "About the role" is present as "About The Role". We'll make

About the Role

. Also we have "Key Responsibilities & Deliverables" which maps to Responsibilities. We'll use

Responsibilities

. "Who You Are" maps to Qualifications? Could be Qualifications. We'll use

Qualifications

. "What You'll Bring" maybe Skills? Could be Skills. We'll use

Skills

. "Benefits" maps to Benefits. We'll use

Benefits

. Also we have "Compensation & Benefits:" includes Pay info. We could include Pay section if posting states compensation. It does: Base salary $125,000 to $150,000 DOE. So we should include Pay section. Also maybe Schedule? Not mentioned. So we omit Schedule. We need to not repeat job title as heading. Not needed. We need to use

• for any list of duties/requirements/benefits, and

  for prose. We need to preserve all substantive information. So we need to include details from each section. We need to remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The posting does not have those except maybe "While a cover letter is not mandatory..." that's not boilerplate; it's part of role description. Keep. We need to output only HTML fragment, no /, no markdown fences. Let's structure:

  About the Role

  Reporting to the Head of Insurance Programs, the Actuary is the analytical engine behind Roamly's program portfolio. You will build and maintain the pricing, reserving, and performance analysis that tells us how each program is actually doing — and you'll be in the room when those numbers turn into decisions about rate, appetite, and whether a new program gets built. This is a high-visibility seat at a rapidly growing company. You won't be handed a narrow slice of a large actuarial department's workflow. You'll touch loss cost modeling, rate indications, reserve reviews, carrier and reinsurance submissions, filing support, and the reporting that goes to executive leadership and carrier partners. When we launch a new program, you'll help build the rating structure from scratch and then watch it earn out in real time. You'll work across P&C auto, carshare and rideshare, RV, and adjacent mobility lines, and you'll partner closely with Underwriting, Claims, Finance, Product, and Engineering. We also expect you to bring modern tooling to the work — automating recurring analyses and applying AI where it genuinely speeds up the cycle, rather than rebuilding the same spreadsheet every quarter. While a cover letter is not mandatory, for a role as nuanced as this, it might help us better understand your qualifications. Preference will be given to candidates in Austin, TX or San Francisco, CA. There is, however, an opportunity for a remote hire for those who meet 100% of the job criteria.

  Then Responsibilities:

  Responsibilities

  • New Program Development: Build initial rating structures and pricing models for new programs, including where internal data is thin and external benchmarks or judgment are required; Model program economics — expected loss ratio, commission structure, fronting costs, and profitability under different scenarios; Support implementation by validating rating logic in production systems before launch.
  • Program Performance Reporting: Produce the recurring loss ratio, frequency, severity, and trend reporting that drives monthly and quarterly program reviews; Build and maintain dashboards that give Underwriting and leadership a current view of portfolio performance without waiting on a request; Investigate emerging trends and adverse development, and translate findings into a clear recommendation rather than a chart.
  • Carrier & Reinsurance Support: Prepare the loss data, exhibits, and experience analysis that go into carrier submissions, renewal proposals, and reinsurance placements; Support bordereaux accuracy, delegated authority reporting, and carrier audit requests.
  • Pricing & Rate Analysis: Build and maintain rate indications, loss cost models, and rate level analyses across the program portfolio; Support segmentation and risk selection analysis; identify which segments are performing, which aren't, and what the rate response should be; Perform competitive and market analysis to test pricing adequacy and positioning; Prepare rate, rule, and form filing exhibits and supporting actuarial materials; respond to regulator objections.
  • Underwriting Partnership: Provide analytical support on underwriting referrals, account-level pricing questions, and appetite decisions; Help maintain and refine underwriting guidelines with data behind the thresholds.
  Qualifications:

  Qualifications

  • ACAS, FCAS, or equivalent experience
  • 4+ years of P&C actuarial experience, ideally in personal or commercial auto, specialty, or program business
  • Strong technical foundation in ratemaking, loss reserving, and trend analysis
  • Advanced Excel skills plus working proficiency in SQL and at least one of Python or R
  • Experience building reports or dashboards in a BI tool (Tableau, Looker, Power BI, or similar)
  • Comfortable working with imperfect, incomplete, or newly created data — and honest about the resulting uncertainty
  • Able to explain an analysis clearly to underwriters, executives, and carrier partners who are not actuaries
  • Experience with insurtech, MGA, or program business is a plus
  • Exposure to rate filings and state regulatory processes is a plus
  • Bachelor's degree in actuarial science, mathematics, statistics, economics, or a related quantitative field
  Skills:

  Skills

  • Genuine curiosity about why a number moved, and the persistence to chase it down
  • Bias toward automating recurring work instead of repeating it
  • Strong attention to detail with the judgment to know when precision matters and when speed matters more
  • Comfort in a fast-paced environment with shifting priorities and limited precedent
  • Collaborative style — willing to sit with underwriters and claims adjusters to understand the business behind the data
  • Clear written and verbal communication, including the ability to summarize a complex analysis in a paragraph
  Pay:

  Pay

  Base salary of $125,000 to $150,000 DOE

  Benefits:

  Benefits

  • Competitive Compensation: Base salary of $125,000 to $150,000 DOE (already covered but we can keep)
  • Growth Opportunity: Join a company in its early stages and help build its foundation for success
  • Equity: Opportunity to earn equity compensation
  • Comprehensive Benefits: 100% company-paid medical premiums for employees, 401(k) match, and Flexible PTO
  • Vibrant Culture: Work at either our Austin, TX, or San Francisco, CA, HQ with catered lunches, happy hours, and team-building events
  • Work-Life Balance: We offer marketplace discounts and maintain a culture that values the balance between work and adventure
  But note we already have Pay section with salary; Benefits section may duplicate salary. Could combine but instruction: prefer few substantive sections over many thin ones. Could merge Pay into Benefits? But they said include Pay section only if posting actually states them. It does state salary. Could keep Pay separate. Benefits section can exclude salary duplication. Let's adjust Benefits to not repeat salary. Benefits:
  • Growth Opportunity: Join a company in its early stages and help build its foundation for success
  • Equity: Opportunity to earn equity compensation
  • Comprehensive Benefits: 100% company-paid medical premiums for employees, 401(k) match, and Flexible PTO
  • Vibrant Culture: Work at either our Austin, TX, or San Francisco, CA, HQ with catered lunches, happy hours, and team-building events
  • Work-Life Balance: We offer marketplace discounts and maintain a culture that values the balance between work and adventure
  We need to ensure we didn't miss any substantive info: The "About Us" and "About Roamly" sections are descriptive but not required headings. Should we include them? 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 says "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It implies those are the expected headings. It also says "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". So we could include About Us and About Roamly as sections if we want, but they are not in the list of examples. However they are substantive. The instruction didn't forbid other headings, but the examples are just examples. Safer to include them as

  About Us

  and

  About Roamly

  maybe. But the instruction says "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't say you cannot use other headings, but the e.g. list suggests those are the typical sections. However the posting includes About Us and About Roamly which are descriptive. I'd include them as sections to preserve all substantive info. The instruction: "Prefer a few substantive sections over many thin ones." Including About Us and About Roamly adds two sections; but they are substantive. Could combine them into a single "About the Company" section? But we must not invent headings not present. However we could create a heading "About the Company" that merges both. But that would be inventing a heading not in the posting. The instruction says do NOT repeat the job title as a heading and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it. It doesn't forbid creating new headings, but says "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It seems they expect us to map content to those headings. So we should map About Us and About Roamly under maybe "About the Role"? No