Senior Analyst Revenue Assurance & Billing

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include only sections that have real specific content. The posting includes description, responsibilities, ideal candidate profile (requirements/qualifications/skills), work location, safety expectations, etc. No explicit Pay, Benefits, Schedule mentioned. So we should not create those sections. We need sections: About the role (maybe summary), Responsibilities, Requirements (or Qualifications and Skills). The posting includes "Ideal candidate profile" which can be Requirements/Qualifications/Skills. Also "Work style and culture fit" maybe part of requirements. Also "Work location" maybe part of About the role or a separate section? Not listed as allowed heading; allowed headings are About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can put work location under About the role or maybe under Requirements? Probably About the role includes location. We'll include About the role with summary and location. Responsibilities as list. Requirements (or Qualifications and Skills) maybe combine. Since we prefer few substantive sections, we can have About the role, Responsibilities, Requirements (covering ideal candidate profile, work style, location). No Benefits, Pay, Schedule. We must use

• for any list of duties/requirements/benefits. So responsibilities list as
  • . Also requirements list as
    • . Use

      for prose. We must preserve all substantive information, not invent or summarize away detail. Must not repeat job title as heading. Must not include boilerplate like EEO, safety expectations? Safety expectations is substantive? It's about compliance with safety policies; maybe we can include in About the role or Requirements? It's not a list but could be a paragraph. We'll include it in About the role as a paragraph. We must remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The posting includes a disclaimer at end: "Disclaimer: This job description is not intended to be an exhaustive list..." That's boilerplate; we should remove it. Also "Why this role matters" is substantive; we can include in About the role. Let's extract content. Original text: "The Sr. Analyst, Revenue Assurance and Billing owns whether what Dobson delivers, what Dobson bills, and what Dobson's systems say are the same thing. The role covers four lanes: tying out what was sold against what was installed, billed, and disconnected; auditing what is provisioned against what is billed; rate and pricing accuracy; and sales commissions. This role takes that work over at a higher level, puts one method behind it, and carries it from finding the gap through fixing the cause. Commissions come with it, because paying on an event and billing for an event are the same validation done twice. Success is measured by dollars identified and recovered, by how fast a gap is found after it opens, by whether the same gap comes back, and by commission accuracy with no rework after payment." Then "Key responsibilities" bullet list (actually sentences). We'll convert each to

    • . List: - Own the monthly tie out of what was sold against what was installed, connected, billed, and disconnected, on one documented method, with every difference explained. - Diagnose each gap as a people, process, or tool problem, name the owner of the fix, and track it to closure rather than reporting it again next month. - Audit what the network is actually delivering against what is being billed: service turned up and never billed, service still billing after it was turned off, speed tiers that do not match, and disconnects that never reached the bill in either direction. - Own rate and pricing accuracy. The rate on the customer's bill matches the rate in the system and the rate on their contract, in every market and on every channel. Own the calendar of customers on old pricing and promotional rates that are due to expire, and make sure rate changes land on the bill in the month they are supposed to. - Own sales commissions end to end: the monthly calculation, the supporting detail, and the accuracy of what gets paid. Validate every commissionable event against what was actually installed and actually billed before commission is paid. Apply chargebacks when an account disconnects inside the qualifying window, and document the basis for each one. Own commission dispute resolution with Sales, and trace recurring disputes back to the order entry or provisioning error that caused them. Partner with Sales Operations on the boundary between calculation and plan design. Plan design and rate setting stay with Sales Operations. - Own the billing data definitions used across the company so a term means the same thing in every report that uses it. Carry the authority to push remediation into provisioning, order management, and field, and escalate when a fix stalls. Put a dollar figure on revenue Dobson is not collecting, publish what has been recovered, and report both every month on a set schedule. Build the standing reporting and dashboards for billing accuracy rather than answering the same question by manual pull each time it is asked. Take over at a higher level the manual data pulls currently done by hand across Omnia360, ServiceNow, and CHR. Partner with Finance on credits, adjustments, and write offs so the accounting view and the operational view of revenue agree. Then "First-year priorities" list: - Publish one documented tie out method and run it monthly without exception. - Complete a full audit of what is provisioned against what is billed, and put a dollar figure on the service being delivered and not billed. - Deliver a first annual dollar figure for revenue Dobson is not collecting, with the method behind it written down. - Run the first full rate and pricing audit and clear every mismatch it finds. - Publish the old pricing and promotional expiration calendar twelve months forward. - Establish the commission validation and chargeback method in writing, with the Sales Operations boundary agreed. - Retire the manual pulls other teams do today and replace them with reporting that runs on its own. Then "Ideal candidate profile" bullet list: - Three or more years in revenue assurance, billing analysis, financial analysis, or operations analysis. - Strong SQL or equivalent ability to pull, join, and reconcile data across systems without waiting on someone else to build the extract. - Advanced Excel. - Comfortable building a tie out that another person can pick up and run. - Demonstrated ability to define metrics and stand up reporting where none existed. - Experience tracing an error back through order entry, provisioning, and billing to find the actual cause. - Able to hold a finding in front of a system owner who disagrees with it, and to be right. - Comfortable operating in a growing, evolving environment where not all processes and roles are fully defined. - Preferred: telecommunications, broadband, fiber, or cable billing experience. - Preferred: direct experience with a billing platform, an order management system, and a CRM in the same role. - Preferred: exposure to audit, internal controls, or a formal revenue assurance function. - Preferred: experience with sales commission calculation, validation, or chargeback administration. Then "Work style and culture fit" bullet list: - Builds structure where none exists, and documents it so it holds up without them in the room. - Follows a finding through to the fix instead of handing off a list and moving on. - Uses data to decide, and asks why a number moved before reporting it. - Works across departments without needing authority over them. - Communicates directly, in plain terms, with both peers and executive leadership. Then "Work location": "This role is on site in Oklahoma City. It supports a business that operates seven days a week and requires occasional availability outside standard hours around month end close and billing cycles." Then "Safety Expectations": "Compliance with company safety policies, PPE, safe driving, DOT requirements, etc." Then "Environmental/Working Conditions": "Occasional business travel may be required based on business needs." Then "Physical Requirements": "Ability to perform the essential functions of the position with or without reasonable accommodation. Requires the ability to communicate effectively and utilize standard office technology and equipment. May require remaining in a stationary position and moving throughout the work environment as needed to perform job responsibilities." Then "Why this role matters": paragraph. We need to include all substantive info. We'll incorporate safety expectations, environmental/working conditions, physical requirements maybe under About the role or a separate section? Not among allowed headings. Could be part of About the role as prose. We must not create Pay/Benefits/Schedule sections. Thus final HTML:

      About the role

      ... (summary + location + safety etc + why it matters)

      Responsibilities

      • ... each responsibility

      Requirements

      • ... ideal candidate profile + work style + maybe physical requirements?
      We need to ensure we don't lose any details. Let's craft About the role paragraph combining: - The Sr. Analyst, Revenue Assurance and Billing owns whether what Dobson delivers, what Dobson bills, and what Dobson's systems say are the same thing. The role covers four lanes: tying out what was sold against what was installed, billed, and disconnected; auditing what is provisioned against what is billed; rate and pricing accuracy; and sales commissions. This role takes that work over at a higher level, puts one method behind it, and carries it from finding the gap through fixing the cause. Commissions come with it, because paying on an event and billing for an event are the same validation done twice. Success is measured by dollars identified and recovered, by how fast a gap is found after it opens, by whether the same gap comes back, and by commission accuracy with no rework after payment. - Work location: This role is on site in Oklahoma City. It supports a business that operates seven days a week and requires occasional availability outside standard hours around month end close and billing cycles. - Safety Expectations: Compliance with company safety policies, PPE, safe driving, DOT requirements, etc. - Environmental/Working Conditions: Occasional business travel may be required based on business needs. - Physical Requirements: Ability to perform the essential functions of the position with or without reasonable accommodation. Requires the ability to communicate effectively and utilize standard office technology and equipment. May require remaining in a stationary position and moving throughout the work environment as needed to perform job responsibilities. - Why this role matters: Dobson bills what its systems say it delivered, and nobody today owns proving that those two things match. Every speed tier that was upgraded and never rebilled, every circuit that was disconnected and kept billing, every promotional rate that never expired is revenue either lost or owed back, and it is found today only by accident. The same is true on the way out: commission is paid on events nobody independently checked against what installed and billed. This role makes all of it visible, puts a dollar figure on it, and closes it at the cause. It is the difference between knowing what Dobson earned and paid, and assuming it. We must not include the disclaimer. Now Responsibilities list: include all bullet points from "Key responsibilities" and also "First-year priorities"? Those are also responsibilities but maybe separate. The instruction: "Use
      • for any list of duties/requirements/benefits". So we could combine all duty-like items into one responsibilities list. But we might want to separate first-year priorities as part of responsibilities? Could be separate section but not allowed heading. Could incorporate into responsibilities list as well. However, the first-year priorities are specific goals; they are still duties/responsibilities. We'll include them in the responsibilities list. Thus responsibilities list will have many items: the key responsibilities (7 items) plus first-year priorities (7 items). We'll keep them as separate
      • entries. Now Requirements list: include ideal candidate profile items (8 required + 4 preferred) plus work style and culture fit items (5). Also maybe we could include physical requirements? Already in About the role. We'll keep them in Requirements. We must not invent or summarize away detail. So we need to keep each bullet exactly as in text,