Frederick Fox

Operations Analyst I – Product &amp; Pricing Department: Product Development | Location: Charlotte, NC | Role: Individual contributor | Direct reports: None | Reports to: Sr. Director, Product Development &amp; Sales About the Role Our client runs its entire book on a single policy administration platform (PCMI PCRS). Forms, coverage configuration, cancel rules, earning curves, rates, claims and cancels all live there, and every member of the Product &amp; Pricing team works in it daily. This seat doesn't take that work away from anyone. It answers for the platform itself: that what is loaded matches what was approved, that the platform and the subadministrator stay in sync, that launches close out proven rather than assumed, and that the loads, cutovers and provisioning the book depends on happen on time, every time. In-lane platform work stays where it is. Forms stay with the regulatory seat, test-rating and triage with the product analysts, program builds with their launch owners, and automation with the data seat. Anything that proves the platform is right, and the standards everyone builds against, sits here. This is an execute-and-verify seat with no direct reports. Pricing decisions, target loss ratios and client commitments sit elsewhere; this seat makes sure what was decided is what's actually running. Division of Work<ul style="margin:0px;padding-left:40px;">
<li style="line-height:1.2;font-family:Arial;font-size:14px;color:rgb(0, 0, 0);margin:0px;">
Pricing / Sr. Manager: Rate cards and reserves are built on the pricing side and approved by the Sr. Manager, who holds final rate authority. They are loaded, verified line by line and cut over here.</li>
<li style="line-height:1.2;font-family:Arial;font-size:14px;color:rgb(0, 0, 0);margin:0px;">
Sr. Regulatory &amp; Contract Specialist: Drafts, files and manages forms. Form profiles, form assignments and the configuration tying a form to its rate card are configured and audited here.</li>
<li style="line-height:1.2;font-family:Arial;font-size:14px;color:rgb(0, 0, 0);margin:0px;">
Launch owners: Run their launches and carry the go-live date. Launch-eve configuration audits, day-one support and post-launch closeout audits run here.</li>
<li style="line-height:1.2;font-family:Arial;font-size:14px;color:rgb(0, 0, 0);margin:0px;">
Data seat: Builds automation, analytics and AI tooling. System administration, user and store provisioning, vendor tickets and UAT sit here, including systems-administration duties scheduled to fold into this function in 2027.</li>
<li style="line-height:1.2;font-family:Arial;font-size:14px;color:rgb(0, 0, 0);margin:0px;">Corrections found here pass back to the owning seat as work product. Rate and class questions settle with the Sr. Manager; the Sr. Director settles cross-team boundary questions.</li>
</ul> Key ResponsibilitiesRate Loads &amp; Effective-Date Cutovers (~25%)<ul style="margin:0px;padding-left:40px;">
<li style="line-height:1.2;font-family:Arial;font-size:14px;color:rgb(0, 0, 0);margin:0px;">Execute every rate load from an approved load package (schedule, effective-dated ranges, diff and expected test-contract results). Verify loaded values line by line and publish exceptions with required corrections.</li>
<li style="line-height:1.2;font-family:Arial;font-size:14px;color:rgb(0, 0, 0);margin:0px;">Run month-boundary and program-effective-date cutovers against hard dates, confirm test contracts rate correctly, and maintain the single load calendar so no two changes collide.</li>
<li style="line-height:1.2;font-family:Arial;font-size:14px;color:rgb(0, 0, 0);margin:0px;">Take over the rate-load, re-rate, rate-change verification and form loading queues currently carried as side duties by other seats, on written transfer lists.</li>
</ul>Configuration Verification &amp; Reconciliation (~25%)<ul style="margin:0px;padding-left:40px;">
<li style="line-height:1.2;font-family:Arial;font-size:14px;color:rgb(0, 0, 0);margin:0px;">Build and run a standing configuration audit cadence across every client program: naming conventions, tax setup, obligor crosswalk, coverage and earning setup, no-chargeback rules.</li>
<li style="line-height:1.2;font-family:Arial;font-size:14px;color:rgb(0, 0, 0);margin:0px;">Stand up platform-to-subadministrator reconciliation as a scheduled control for every client program (it exists for one client today).</li>
<li style="line-height:1.2;font-family:Arial;font-size:14px;color:rgb(0, 0, 0);margin:0px;">Own the coverage crosswalk and reconciliation of the downstream contract feed against the platform of record.</li>
<li style="line-height:1.2;font-family:Arial;font-size:14px;color:rgb(0, 0, 0);margin:0px;">Keep a defect log tracing every live configuration error to the rate-card, surcharge, class-guide or form defect behind it.</li>
</ul>Launch Configuration &amp; Closeout (~20%)<ul style="margin:0px;padding-left:40px;">
<li style="line-height:1.2;font-family:Arial;font-size:14px;color:rgb(0, 0, 0);margin:0px;">Run launch-eve configuration audits and day-one go-live support for every new program launch and store wave.</li>
<li style="line-height:1.2;font-family:Arial;font-size:14px;color:rgb(0, 0, 0);margin:0px;">Build and run the launch checklist and 30-day post-launch audit proving every rated product is built, every form assigned and every store provisioned. Neither control exists today, so the first pass is a build.</li>
<li style="line-height:1.2;font-family:Arial;font-size:14px;color:rgb(0, 0, 0);margin:0px;">Drive closeout for open dealer formations (entity, trust and agreement setup) on a dated path to first sale.</li>
</ul>Platform Administration &amp; Change Control (~20%)<ul style="margin:0px;padding-left:40px;">
<li style="line-height:1.2;font-family:Arial;font-size:14px;color:rgb(0, 0, 0);margin:0px;">Own user and store provisioning; dealer, seller and servicer setup (labor rates, tax rules); portal access and internal packs.</li>
<li style="line-height:1.2;font-family:Arial;font-size:14px;color:rgb(0, 0, 0);margin:0px;">Set and enforce configuration standards: naming conventions, change control, load ownership, and test-contract standards for proving a change.</li>
<li style="line-height:1.2;font-family:Arial;font-size:14px;color:rgb(0, 0, 0);margin:0px;">Manage enhancement requests and support tickets with the platform vendor, and run UAT on vendor changes before production.</li>
<li style="line-height:1.2;font-family:Arial;font-size:14px;color:rgb(0, 0, 0);margin:0px;">Absorb systems-administration duties as they fold into this function.</li>
</ul>Runbooks &amp; Cross-Training (~10%)<ul style="margin:0px;padding-left:40px;"><li style="line-height:1.2;font-family:Arial;font-size:14px;color:rgb(0, 0, 0);margin:0px;">Write the runbook for every discipline this seat owns and cross-train so at least two people can execute each one. The measure of this seat is that platform knowledge stops being single-person anywhere in the group.</li></ul> A Representative Week<ul style="margin:0px;padding-left:40px;">
<li style="line-height:1.2;font-family:Arial;font-size:14px;color:rgb(0, 0, 0);margin:0px;">Load a first-of-month effective-date rate change from the approved package, verify it line by line, and publish two exceptions with corrections.</li>
<li style="line-height:1.2;font-family:Arial;font-size:14px;color:rgb(0, 0, 0);margin:0px;">Run the scheduled platform-to-subadministrator reconciliation for two clients and trace one break to its class-guide defect.</li>
<li style="line-height:1.2;font-family:Arial;font-size:14px;color:rgb(0, 0, 0);margin:0px;">Run a launch-eve configuration audit for a wave of new stores and support go-live the next morning.</li>
<li style="line-height:1.2;font-family:Arial;font-size:14px;color:rgb(0, 0, 0);margin:0px;">Close out one dealer formation, provision four portal users, and clear three vendor tickets, including UAT on one platform change.</li>
<li style="line-height:1.2;font-family:Arial;font-size:14px;color:rgb(0, 0, 0);margin:0px;">Attend the weekly new-business implementation checkpoint and flag a store-setup blocker early.</li>
<li style="line-height:1.2;font-family:Arial;font-size:14px;color:rgb(0, 0, 0);margin:0px;">Write the re-rate runbook and walk a product analyst through it.</li>
</ul> Required Qualifications<ul style="margin:0px;padding-left:40px;">
<li style="line-height:1.2;font-family:Arial;font-size:14px;color:rgb(0, 0, 0);margin:0px;">3–6 years configuring or administering an F&amp;I policy administration platform (PCMI PCRS strongly preferred; comparable systems considered), or equivalent admin-system work in warranty, service-contract or insurance administration.</li>
<li style="line-height:1.2;font-family:Arial;font-size:14px;color:rgb(0, 0, 0);margin:0px;">Has personally executed rate loads or configuration changes into production against hard effective dates, and can describe exactly how they proved the load was right.</li>
<li style="line-height:1.2;font-family:Arial;font-size:14px;color:rgb(0, 0, 0);margin:0px;">Working SQL: pull a contract or claims extract, reconcile it against a feed, and find the wrong row without help.</li>
<li style="line-height:1.2;font-family:Arial;font-size:14px;color:rgb(0, 0, 0);margin:0px;">Advanced Excel, including large multi-sheet workbooks with effective-dated ranges and diffs.</li>
<li style="line-height:1.2;font-family:Arial;font-size:14px;color:rgb(0, 0, 0);margin:0px;">A verification habit and standards discipline: checklists, change logs and runbooks come naturally, and structural questions get escalated rather than settled quietly.</li>
<li style="line-height:1.2;font-family:Arial;font-size:14px;color:rgb(0, 0, 0);margin:0px;">Bachelor's degree or equivalent experience.</li>
</ul> Preferred Qualifications<ul style="margin:0px;padding-left:40px;">
<li style="line-height:1.2;font-family:Arial;font-size:14px;color:rgb(0, 0, 0);margin:0px;">Subadministrator or obligor feed experience, including reconciliation across an admin system, a subadministrator and a data warehouse.</li>
<li style="line-height:1.2;font-family:Arial;font-size:14px;color:rgb(0, 0, 0);margin:0px;">Working knowledge of regulated-state requirements, Florida in particular.</li>
<li style="line-height:1.2;font-family:Arial;font-size:14px;color:rgb(0, 0, 0);margin:0px;">Python or BI tooling (Sigma, Tableau) for recurring audits and scheduled checks.</li>
<li style="line-height:1.2;font-family:Arial;font-size:14px;color:rgb(0, 0, 0);margin:0px;">Systems-administration exposure: user management, permissions, environment hygiene.</li>
</ul> Systems &amp; Tools PCMI PCRS • SQL Server / Snowflake • Excel • Sigma and Tableau • Microsoft 365 • Asana • DocuSign • AI agent tooling﻿What Success Looks Like<ul style="margin:0px;padding-left:40px;">
<li style="line-height:1.2;font-family:Arial;font-size:14px;color:rgb(0, 0, 0);margin:0px;">
90 days: The load calendar exists and every load ships from an approved package with line-by-line verification; transfer lists are executed and other seats are back in their own scope; the first subadministrator reconciliation beyond the pilot client has run.</li>
<li style="line-height:1.2;font-family:Arial;font-size:14px;color:rgb(0, 0, 0);margin:0px;">
6 months: Reconciliation covers every client program on schedule; the defect log traces every break to a root cause; open formations are closed or on a dated path; the launch checklist and 30-day audit have run on a live launch.</li>
<li style="line-height:1.2;font-family:Arial;font-size:14px;color:rgb(0, 0, 0);margin:0px;">
12 months: Every discipline this seat owns has a runbook and a trained second; systems-administration duties have folded in without disruption; configuration exposure surfaces in a scheduled check rather than a claims review or client call.</li>
</ul>

Operations Analyst I – Product & Pricing

Department: Product Development | Location: Charlotte, NC | Role:
Individual contributor | Direct reports: None | Reports to: Sr.
Director, Product Development & Sales

About the Role

Our client runs its entire book on a single policy
administration platform (PCMI PCRS). Forms, coverage
configuration, cancel rules, earning curves, rates, claims and
cancels all live there, and every member of the Product & Pricing
team works in it daily. This seat doesn't take that work away
from anyone. It answers for the platform itself: that what is
loaded matches what was approved, that the platform and the
subadministrator stay in sync, that launches close out proven
rather than assumed, and that the loads, cutovers and
provisioning the book depends on happen on time, every time.

In-lane platform work stays where it is. Forms stay with the
regulatory seat, test-rating and triage with the product
analysts, program builds with their launch owners, and automation
with the data seat. Anything that proves the platform is right,
and the standards everyone builds against, sits here.

This is an execute-and-verify seat with no direct reports.
Pricing decisions, target loss ratios and client commitments sit
elsewhere; this seat makes sure what was decided is what's
actually running.

Division of Work

* Pricing / Sr. Manager: Rate cards and reserves are built on the
pricing side and approved by the Sr. Manager, who holds final
rate authority. They are loaded, verified line by line and cut
over here.
* Sr. Regulatory & Contract Specialist: Drafts, files and manages
forms. Form profiles, form assignments and the configuration
tying a form to its rate card are configured and audited here.
* Launch owners: Run their launches and carry the go-live date.
Launch-eve configuration audits, day-one support and post-launch
closeout audits run here.
* Data seat: Builds automation, analytics and AI tooling. System
administration, user and store provisioning, vendor tickets and
UAT sit here, including systems-administration duties scheduled
to fold into this function in 2027.
* Corrections found here pass back to the owning seat as work
product. Rate and class questions settle with the Sr. Manager;
the Sr. Director settles cross-team boundary questions.

Key Responsibilities

Rate Loads & Effective-Date Cutovers (~25%)

* Execute every rate load from an approved load package
(schedule, effective-dated ranges, diff and expected
test-contract results). Verify loaded values line by line and
publish exceptions with required corrections.
* Run month-boundary and program-effective-date cutovers against
hard dates, confirm test contracts rate correctly, and maintain
the single load calendar so no two changes collide.
* Take over the rate-load, re-rate, rate-change verification and
form loading queues currently carried as side duties by other
seats, on written transfer lists.
Configuration Verification & Reconciliation (~25%)

* Build and run a standing configuration audit cadence across
every client program: naming conventions, tax setup, obligor
crosswalk, coverage and earning setup, no-chargeback rules.
* Stand up platform-to-subadministrator reconciliation as a
scheduled control for every client program (it exists for one
client today).
* Own the coverage crosswalk and reconciliation of the downstream
contract feed against the platform of record.
* Keep a defect log tracing every live configuration error to the
rate-card, surcharge, class-guide or form defect behind it.
Launch Configuration & Closeout (~20%)

* Run launch-eve configuration audits and day-one go-live support
for every new program launch and store wave.
* Build and run the launch checklist and 30-day post-launch audit
proving every rated product is built, every form assigned and
every store provisioned. Neither control exists today, so the
first pass is a build.
* Drive closeout for open dealer formations (entity, trust and
agreement setup) on a dated path to first sale.
Platform Administration & Change Control (~20%)

* Own user and store provisioning; dealer, seller and servicer
setup (labor rates, tax rules); portal access and internal packs.
* Set and enforce configuration standards: naming conventions,
change control, load ownership, and test-contract standards for
proving a change.
* Manage enhancement requests and support tickets with the
platform vendor, and run UAT on vendor changes before production.
* Absorb systems-administration duties as they fold into this
function.
Runbooks & Cross-Training (~10%)

* Write the runbook for every discipline this seat owns and
cross-train so at least two people can execute each one. The
measure of this seat is that platform knowledge stops being
single-person anywhere in the group.

A Representative Week

* Load a first-of-month effective-date rate change from the
approved package, verify it line by line, and publish two
exceptions with corrections.
* Run the scheduled platform-to-subadministrator reconciliation
for two clients and trace one break to its class-guide defect.
* Run a launch-eve configuration audit for a wave of new stores
and support go-live the next morning.
* Close out one dealer formation, provision four portal users,
and clear three vendor tickets, including UAT on one platform
change.
* Attend the weekly new-business implementation checkpoint and
flag a store-setup blocker early.
* Write the re-rate runbook and walk a product analyst through
it.

Required Qualifications

* 3–6 years configuring or administering an F&I policy
administration platform (PCMI PCRS strongly preferred; comparable
systems considered), or equivalent admin-system work in warranty,
service-contract or insurance administration.
* Has personally executed rate loads or configuration changes
into production against hard effective dates, and can describe
exactly how they proved the load was right.
* Working SQL: pull a contract or claims extract, reconcile it
against a feed, and find the wrong row without help.
* Advanced Excel, including large multi-sheet workbooks with
effective-dated ranges and diffs.
* A verification habit and standards discipline: checklists,
change logs and runbooks come naturally, and structural questions
get escalated rather than settled quietly.
* Bachelor's degree or equivalent experience.

Preferred Qualifications

* Subadministrator or obligor feed experience, including
reconciliation across an admin system, a subadministrator and a
data warehouse.
* Working knowledge of regulated-state requirements, Florida in
particular.
* Python or BI tooling (Sigma, Tableau) for recurring audits and
scheduled checks.
* Systems-administration exposure: user management, permissions,
environment hygiene.

Systems & Tools

PCMI PCRS • SQL Server / Snowflake • Excel • Sigma and Tableau •
Microsoft 365 • Asana • DocuSign • AI agent tooling

﻿

What Success Looks Like

* 90 days: The load calendar exists and every load ships from an
approved package with line-by-line verification; transfer lists
are executed and other seats are back in their own scope; the
first subadministrator reconciliation beyond the pilot client has
run.
* 6 months: Reconciliation covers every client program on
schedule; the defect log traces every break to a root cause; open
formations are closed or on a dated path; the launch checklist
and 30-day audit have run on a live launch.
* 12 months: Every discipline this seat owns has a runbook and a
trained second; systems-administration duties have folded in
without disruption; configuration exposure surfaces in a
scheduled check rather than a claims review or client call.

Product Pricing Analyst I

About the role

Not the right role?