Personal Injury Operations Manager

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title as heading. No Job ID etc. Remove boilerplate. Preserve all substantive info. We need to parse the posting. Content: - Intro: Titan Law Firm description, location, hybrid schedule, salary, bonus, benefits. - About The Role: description. - Key Responsibilities: bullet list under subheadings (Operations & Office Management, Case Management Oversight, Legal Operations, Marketing & Business Development Support, Leadership & Team Development). Each subheading has bullet points. - Qualifications: Required list, Preferred list. - What We're Looking For: prose. We need to map to sections: About the role (h3), Responsibilities (h3), Requirements (h3) maybe combine Qualifications? The instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have multiple sections; we should include those that have content. We have About the role content. Responsibilities: we have Key Responsibilities with subpoints. Requirements: maybe Qualifications Required? Could be Requirements. Qualifications: maybe Preferred? But we could combine Required and Preferred under Qualifications? The instruction says we can have Qualifications section. We'll include Qualifications (maybe both required and preferred). Could also have Skills section? Not explicitly separate; we could put skills under Qualifications or Skills. But we have skills mentioned in qualifications (strong organizational, communication, leadership skills). Could create Skills section. Benefits: we have Benefits: Paid Time Off (PTO) and other benefits offered. That's vague but it's stated. It's not placeholder like "varies". It's specific: Paid Time Off (PTO) and other benefits offered. That's enough to include Benefits section. Pay: Salary range and bonus. So we have Pay section. Schedule: Hybrid: 3-4 Days In Office, 1-2 Days Remote. So Schedule section. We should not include sections with filler like "commensurate with experience". Not present. We must not repeat job title as heading. So no heading for Personal Injury Operations Manager. We must not include Job ID etc. We must output only HTML fragment, no /, no markdown fences. We need to use

for section headings. Use

• for any list of duties/requirements/benefits. Use

  for prose. We need to preserve all substantive information; do not invent or summarize away detail. We need to remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. There's none. We need to ensure we don't create empty sections. Let's extract content. Intro paragraph: "Titan Law Firm is a boutique personal injury law firm located in the heart of Beverly Hills, in a busy, energetic professional building surrounded by everything the city has to offer. We consist of ...". Actually the intro includes description of firm, location, hybrid schedule, salary, bonus, benefits. We'll need to split: location/hybrid schedule goes to Schedule? Actually schedule is hybrid. Location maybe part of About the role? But we can include location in About the role? The instruction: About the role section should contain description of role. The intro includes firm description; we could put that in About the role as context? But we should preserve all substantive info. Could include firm description in About the role? Might be okay. However About the role heading already has content: "We are seeking an experienced Personal Injury Operations Manager to serve as the right hand to the Managing Attorney..." That's the role description. The firm description could be placed before that as a

  maybe not under a heading? But we need to output only sections with headings? The instruction: "Output ONLY the HTML fragment — no /, no markdown code fences." It doesn't say we must wrap everything in headings; we can have

  outside headings. But they said use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have headings for those sections, and other paragraphs outside headings are okay. Thus we can have an introductory

  about the firm, location, hybrid schedule, salary, bonus, benefits? But schedule, pay, benefits have their own sections; we might want to avoid duplication. Better to put firm description and location in intro

  , then schedule, pay, benefits sections later. Let's parse: Firm description: "Titan Law Firm is a boutique personal injury law firm located in the heart of Beverly Hills, in a busy, energetic professional building surrounded by everything the city has to offer. We consist of a small, close-knit team that takes our work seriously while maintaining a positive, supportive, and genuinely enjoyable office environment. Our office offers comfortable, modern workstations, a casual and collaborative atmosphere, and a team-first culture where we help one another and our successes are shared." Location/hybrid: "Personal Injury Operations Manager Location: Beverly Hills, CA Area (Hybrid: 3-4 Days In Office, 1-2 Days Remote)". So location and schedule. Salary: "Salary: $75,000 - $95,000 Base Salary (Based on Experience) Bonus: Unlimited Performance-Based Bonus Opportunity (Bonus typical range $5,000-$50,000, but can be higher)" Benefits: "Benefits: Paid Time Off (PTO) and other benefits offered" Now About The Role section: paragraph. Key Responsibilities: multiple subheadings with bullet points. Qualifications Required list. Preferred list. What We're Looking For: paragraph. We need to map to sections: - About the role: include the paragraph under About The Role. - Responsibilities: include the Key Responsibilities content. Could keep subheadings as

  ? But instruction only mentions using

  for section headings. It didn't forbid other headings, but we can just use

  • for the responsibilities, maybe grouping under subheadings as or

    . However to preserve structure, we could keep subheadings as

    or . But instruction only says use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't say we cannot use other headings; but to be safe, we can just use

    for main sections and inside we can use

    or

    • . For subheadings within Responsibilities, we could use

      Operations & Office Management: then

      • ... etc. That preserves info. - Requirements: maybe combine Required qualifications? Could be Requirements section. - Qualifications: maybe Preferred qualifications? But we could also have Skills section for skills like organizational, communication, leadership. However we have skills listed in Required qualifications: "Strong organizational, communication, and leadership skills." Could put that in Skills section. But we have both Required and Preferred qualifications. We could have Requirements section for Required, and Qualifications section for Preferred. Or we could combine both under Qualifications. The instruction gave examples: Requirements, Qualifications, Skills. So we can split. Thus: - Requirements: Required qualifications list. - Qualifications: Preferred qualifications list. - Skills: maybe we can extract skills like "Strong organizational, communication, and leadership skills." Also "Experience working directly with attorneys, clients, and prelitigation teams." That's more experience. But we can put skills like "Strong organizational, communication, and leadership skills." Also "Experience managing complex, high-volume caseloads." That's experience. Might be okay to put under Skills. But we need to avoid duplication. Let's think: Required qualifications already include many items: 5+ years of Personal Injury case management experience, extensive knowledge of Personal Injury pre-litigation processes, pre-litigation and/or litigation experience, experience managing complex high-volume caseloads, legal operations or law firm management experience, strong organizational, communication, and leadership skills, proven ability to improve processes and drive operational efficiency, experience working directly with attorneys, clients, and prelitigation teams. Preferred qualifications: prior management or leadership experience, experience referring or generating cases for a Personal Injury law firm, experience managing legal support staff or case management teams, bilingual Spanish-English capabilities, experience with CRM, case management, and legal technology platforms. Thus we can have: Requirements (h3) with ul of required items. Qualifications (h3) with ul of preferred items. Skills (h3) maybe we can list specific skills like "Strong organizational, communication, and leadership skills." But that's already in required. Could still include but would duplicate. Better to not have Skills section if it duplicates. However we could extract skills not covered elsewhere: maybe "Experience with CRM, case management, and legal technology platforms." That's a skill. But it's in preferred. So we could skip Skills section. But the instruction says we can include Skills section if there is real specific content. We have skills mentioned: "Strong organizational, communication, and leadership skills." That's a skill. It's already in required; but we could still include it under Skills, but that would duplicate content. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. Duplication is not prohibited but could be considered redundant. Safer to not duplicate; we can put skill under Requirements or Qualifications. Thus we may omit Skills section. Now Benefits: we have "Paid Time Off (PTO) and other benefits offered". That's not detailed but it's specific enough. We'll create Benefits section with
        • Paid Time Off (PTO)
        • Other benefits offered
        . However "other benefits offered" is vague but it's what's stated. We'll keep. Pay: Salary and bonus. We'll create Pay section with

        containing details. Schedule: Hybrid schedule. We'll create Schedule section with

        containing location and hybrid details? Location maybe separate but we can include location in schedule or intro. Let's put location in Schedule section: "Location: Beverly Hills, CA Area. Hybrid: 3-4 days in office, 1-2 days remote." Now About the role: we have paragraph. Now Responsibilities: we need to include all bullet points under each subheading. Let's extract bullet points: Operations & Office Management: - Serve as the second-in-command to the Managing Attorney. - Oversee daily office operations and administrative functions. - Develop and improve systems, workflows, and standard operating procedures. - Ensure accountability and performance across legal support staff. - Monitor key performance indicators and operational goals. Case Management Oversight: - Oversee Personal Injury case management from intake through resolution. - Assist with escalated client matters and case strategy discussions. - Ensure case files are properly managed and deadlines are met. - Support attorneys and case managers with workflow management and resource allocation. Legal Operations: - Manage and optimize legal processes, technology, and systems. - Coordinate communication between attorneys, case managers, intake staff, and support teams. - Ensure compliance with firm procedures and best practices. - Support litigation teams as needed with case flow management and operational support. Marketing & Business Development Support: - Assist with referral partner relationships and business development initiatives. - Support intake and marketing teams to maximize signed cases. - Help develop strategies to increase referral opportunities and client acquisition. - Track and report on referral and marketing performance metrics. Leadership & Team Development: - Mentor and develop staff members. - Assist with hiring, onboarding, training, and performance management. - Foster a positive, high-performance culture focused on client service and results. - Lead by example through accountability, professionalism, and teamwork. We'll need to represent these as lists. Could do

        for each subheading or

        ...: then

        . We'll use

        ...