Jobs · OTHR · North Carolina

Complaint's Specialist

TEKsystems · Charlotte, NC · 3 wk ago
On-siteOTHR$25–$30/hrContract
We need to output HTML fragment with sections: About the role? Actually description includes "Description Key Responsibilities ..." then "Top Skills Details", "Qualifications Additional Skills & Qualifications", "Experience Level", "Job Type & Location", "Pay And Benefits", "Workplace Type", "Application Deadline", "About TEKsystems", etc. We must not repeat job title as heading. Use

for section headings: e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. But we can use other headings if they match content? The instruction: "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It suggests we should use those headings when appropriate. Probably we should map content to those headings. We need to include sections only when posting has real, specific content. We have: - Responsibilities: list of duties (Manage customer complaints, etc.) -> use

Responsibilities

with
  • . - Skills: "Top Skills Details" list of skills ->

    Skills

    with
      . - Qualifications: "Qualifications Additional Skills & Qualifications" ->

      Qualifications

      with
        . - Experience Level: "Experience Level Intermediate Level" -> maybe a

        not a heading? Could be part of Qualifications? But we could have a short

        for metadata. - Job Type & Location: "This is a Contract to Hire position based out of Charlotte, NC." -> could be a

        . - Pay And Benefits: includes pay range and benefits list -> we need Pay and Benefits sections? The instruction: "Prefer a few substantive sections over many thin ones." Also "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state pay range and benefits. So we could have

        Pay

        with

        for pay range, and

        Benefits

        with
          for benefits. Or combine Pay and Benefits? The instruction gave examples of headings: Benefits, Pay, Schedule. So we can separate. - Workplace Type: "This is a fully onsite position in Charlotte,NC." Could be part of Job Type & Location or separate. Could be a

          under Job Type & Location. - Application Deadline: "This position is anticipated to close on Sep 30, 2026." Could be a

          . - About TEKsystems: description of company. Could be

          About the company

          but not in list. 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 suggests we use those. However "About TEKsystems" is not exactly "About the role". Might be considered boilerplate? It's company description, maybe we should keep as

          under a generic heading? The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." The "About TEKsystems" is not exactly boilerplate but could be considered company overview; maybe we keep it as a

          under a heading like "About the company"? Not sure. The instruction says "Prefer a few substantive sections over many thin ones." So maybe we combine company description into a

          under a heading like "About TEKsystems" but that's not in the list. However we could treat it as a section with heading

          About TEKsystems

          though not in examples. The instruction didn't forbid other headings, just gave examples. It says "use

          for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That implies we should use those headings when appropriate, but we could also use other headings if needed? Safer to stick to those headings. So we might not include a separate "About TEKsystems" heading; we could incorporate that info into a

          under maybe "About the role"? But that seems odd. However the instruction says "Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

          or drop it." It doesn't forbid other headings. I'd include a heading for company description maybe as

          About TEKsystems

          . It's substantive. But we need to ensure we don't create sections with filler like "commensurate with experience". We have real content. Let's extract content: Responsibilities bullet points: - Manage customer complaints, escalations, and complex life insurance cases - Research issues and determine appropriate next steps based on company policies and regulatory requirements - Draft professional written responses, including correspondence that may be reviewed by Legal or Compliance - Assess potential business, customer, compliance, and regulatory risk - Manage approximately 10+ active cases at various stages while maintaining accuracy and urgency - Partner with Compliance, Legal, peers, and senior leadership to resolve complex cases - Explain complicated insurance processes and decisions in a clear, customer-friendly way - Support increased case volume related to organizational growth and change - Make timely decisions while working effectively in a fast-paced, "controlled chaos" environment Skills list: - Strong knowledge of life insurance products and processes - Excellent business writing and written communication - Strong problem-solving and critical-thinking skills - Ability to assess risk and compliance considerations - Comfortable handling escalated or sensitive customer situations - Strong computer skills and ability to navigate multiple systems - Ability to multitask and make quick, thoughtful decisions - Adaptable and comfortable with changing priorities - Strong research skills - Ability to connect information across multiple teams and determine the bigger picture - Comfortable communicating with senior-level stakeholders Qualifications: - Previous experience in life insurance, annuities, brokerage, financial services, compliance, or a related environment preferred - College degree preferred - Previous experience handling high level complaints - Candidates with strong financial services sales experience and knowledge of life insurance may also be considered - FINRA licensing, including Series 6, may be preferred or required depending on responsibilities (NICE TO HAVE) - Experience Level Intermediate Level - Job Type & Location: This is a Contract to Hire position based out of Charlotte, NC. - Pay And Benefits: The pay range for this position is $25.00 - $30.00/hr. Individual compensation offered for this position within this range will depend on many factors, including qualifications, skills, relevant experience, job knowledge, geographic location, internal equity, and other pertinent job-related factors. Eligibility requirements apply to some benefits and may depend on your job classification and length of employment. Benefits are subject to change and may be subject to specific elections, plan, or program terms. If eligible, the benefits available for this temporary role may include the following: - Medical, dental & vision - Critical Illness, Accident, and Hospital - 401(k) Retirement Plan – Pre-tax and Roth post-tax contributions available - Life Insurance (Voluntary Life & AD&D for the employee and dependents) - Short and long-term disability - Health Spending Account (HSA) - Transportation benefits - Employee Assistance Program - Time Off/Leave (PTO, Vacation or Sick Leave) - Workplace Type: This is a fully onsite position in Charlotte,NC. - Application Deadline: This position is anticipated to close on Sep 30, 2026. - About TEKsystems: two paragraphs describing company. We need to remove boilerplate: The duplicated "About TEKsystems" appears twice with similar content; we should keep only one copy? The instruction: remove duplicated lines. So we should keep one instance. Also remove EEO etc. The paragraphs at end about equal opportunity, San Francisco Fair Chance, Massachusetts Lie Detector, Use of AI are boilerplate/legal; remove them. Also remove "Application Deadline" maybe we keep as a

          under a heading? Not in list but we could treat as metadata. We need to output only HTML fragment. Let's structure:

          Responsibilities

            ...

          Skills

            ...

          Qualifications

            ...
          Maybe combine Experience Level, Job Type & Location, Workplace Type, Application Deadline into a

          or separate

          Details>? But we could create a

          Details

          with

          containing those lines. However instruction says prefer few substantive sections over many thin ones. So we could have a section "Details" with those metadata. But we also have Pay and Benefits sections. Thus sections: - Responsibilities - Skills - Qualifications - Details (includes Experience Level, Job Type & Location, Workplace Type, Application Deadline) - Pay - Benefits - About TEKsystems (maybe as

          About TEKsystems

          ) Check if any of those sections have filler: Details will have real content. Pay: we have pay range. Benefits: list. Now we need to ensure we don't include headings with empty content. Let's craft HTML. We'll need to escape any special characters? Not needed. Let's write:

          Responsibilities

          • Manage customer complaints, escalations, and complex life insurance cases
          • Research issues and determine appropriate next steps based on company policies and regulatory requirements
          • Draft professional written responses, including correspondence that may be reviewed by Legal or Compliance
          • Assess potential business, customer, compliance, and regulatory risk
          • Manage approximately 10+ active cases at various stages while maintaining accuracy and urgency
          • Partner with Compliance, Legal, peers, and senior leadership to resolve complex cases
          • Explain complicated insurance processes and decisions in a clear, customer-friendly way
          • Support increased case volume related to organizational growth and change
          • Make timely decisions while working effectively in a fast-paced, "controlled chaos" environment

          Skills

          • Strong knowledge of life insurance products and processes
          • Excellent business writing and written communication
          • Strong problem-solving and critical-thinking skills
          • Ability to assess risk and compliance considerations
          • Comfortable handling escalated or sensitive customer situations
          • Strong computer skills and ability to navigate multiple systems
          • Ability to multitask and make quick, thoughtful decisions
          • Adaptable and comfortable with changing priorities
          • Strong research skills
          • Ability to connect information across multiple teams and determine the bigger picture
          • Comfortable communicating with senior-level stakeholders

          Qualifications

          • Previous experience in life insurance, annuities, brokerage, financial services, compliance, or a related environment preferred
          • College degree preferred
          • Previous experience handling high level complaints
          • Candidates with strong financial services sales experience and knowledge of life insurance may also be considered
          • FINRA licensing, including Series 6, may be preferred or required depending on responsibilities (NICE TO HAVE)

          Details

          Experience Level: Intermediate Level

          Job Type & Location: Contract to Hire position based out of Charlotte, NC.

          Workplace Type: Fully onsite position in Charlotte, NC.

          Application Dead

Similar jobs