WC Claim Associate I LevelUP

CCMSI · Neptune City, NJ · 1 mo ago

Hybrid$25.64/hrFull-time

We need to output HTML fragment with sections: Overview? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Do NOT repeat the job title as a heading. Do NOT put Job ID / requisition numbers as headings. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove boilerplate etc. Include a section ONLY when posting has real, specific content for it — never emit heading followed by filler/placeholder text. Prefer a few substantive sections over many thin ones. We need to decide which sections to include based on content. We have: - Overview: description of program, location, schedule, salary range, etc. Could be "About the role" or "Overview". The instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can use "About the role" for overview. - Responsibilities: we have a detailed responsibilities section. - Qualifications: we have "Qualifications Who This Program Is For (Ideal candidates)" and "Required Qualifications" and "Nice To Have". Also "What We Expect (What It Takes)" and "How We Measure Success". Could combine into "Qualifications" or "Requirements". The instruction says we can use "Requirements" or "Qualifications". We need to decide. - Benefits: we have "Why You’ll Love Working Here" with PTO, holidays, benefits, retirement plans, etc. Also "Compensation & Compliance" includes benefits mention. So we can have Benefits section. - Pay: we have salary range, starting rate, phase 3 increase, upon program graduation salary. So we can have Pay section. - Schedule: we have schedule: Full-time, Monday–Friday 8:00 am-4:30 pm. So we can have Schedule section. - Skills: maybe not needed separate; could be included in Qualifications. We need to avoid filler like "commensurate with experience". Not present. We need to remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Also remove "Visa Sponsorship", "ADA Accommodations", "Equal Opportunity Employer", background checks, core values maybe? The core values might be considered boilerplate? It's not exactly EEO but could be considered fluff. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Core values maybe not required to remove but could be considered fluff. However we need to preserve ALL substantive information; core values might be considered substantive? It's more cultural. Might be okay to keep but could be considered filler. Safer to keep? The instruction says remove boilerplate; core values might be considered boilerplate but not explicitly listed. I'd lean to keep it as part of "Why You’ll Love Working Here" maybe. But we already have a Benefits section; we could incorporate culture there. However we need to avoid duplication. We need to output only HTML fragment, no /, no markdown fences. Let's structure:

About the role

Overview text: LevelUP Career Development Program – Claims Trainee (Paid Training) Location: Wall Township, NJ Schedule: Full-time, Monday–Friday 8:00 am-4:30 pm Salary Range: $25.64/hr Starting rate: $50,000/year equivalent (paid hourly) Phase 3 increase: $55,000/year equivalent (paid hourly) Upon program graduation: Promotion to a salaried Claims Representative I role, earning $60,000 annually This is an hourly, full-time paid training program. After successful completion (typically ~12–15 months), LevelUP graduates move into a salaried Claims Representative I position with continued career growth opportunities. Build Your Career With Purpose at CCMSI ... (the paragraph about CCMSI). Also Job Summary (Start Here) ... maybe include that as part of about role. We need to preserve all substantive info, so include the description about CCMSI, job summary, etc. Then

Responsibilities

with

items. The responsibilities section is lengthy with phases. We need to capture all responsibilities as list items. Could break into early phase, later phases etc. But we need to preserve all detail; we can create list items for each bullet. We have: Early Phase: - Learn CCMSI systems and everyday tools (email/calendar, shared drives, claim systems) - Process incoming documents and bills - Complete required forms and claim paperwork - Communicate by phone and email with people involved in a claim (injured employees, medical offices, employers, attorneys) - Support experienced Claims Professionals by assisting on claim files As you grow: - Set up new claims and gather key information - Make required contact with involved parties promptly (injured employee, employer, medical providers) - Conduct basic claim investigations and document findings clearly - Build action plans, track deadlines, and move claims forward - Work with a mentor and take on a growing claim workload as your skills develop - Prepare for and (if required for the work you’re assigned) pass a state licensing exam Later Phases: - Manage a larger group of active claim files with increased independence - Participate in claim reviews and legal reviews as part of your learning - Complete advanced best-practices training and prepare for promotion We'll put each as
. Then
Qualifications
maybe combine Required Qualifications and Nice To Have and What We Expect and How We Measure Success. But we need to avoid too thin sections. Could make one Qualifications section with subpoints? But we only allowed
- for list. Could have multiple

WC Claim Associate I LevelUP

About the role

Responsibilities

Qualifications

. We could use
for prose before each list. That's allowed. Thus:

Qualifications

Benefits

Pay

Schedule

Similar jobs