DAN QC Analyst

We need to output HTML fragment with sections only if real specific content. Use

for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must not repeat job title. No Job ID. Remove boilerplate, navigation, legal, EEO, etc. Preserve substantive info. We need to parse the posting. Key sections: - Intro paragraph about Epiq: "At Epiq, your work contributes..." etc. That's about the role? Could be "About the role" or maybe "About the company". The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can put the introductory paragraph under

About the role

. - Job Summary: "The Senior Operations Analyst is a specialist Subject Matter Expertise (SME) in one or more areas of the eDiscovery operational workflow as practiced at Epiq. The purpose of this position is to provide SME to Associates, support learning and development, ensure best practices and quality standards in their SME area are applied and adhered to, whilst also acting as an individual contributor within Operations on the full range of activities and tasks." That's also part of About the role. - Essential Job Responsibilities: list of responsibilities. Use

• . - Qualifications & Characteristics: list of requirements. Could be under Requirements or Qualifications. The instruction: we have both Requirements and Qualifications headings. We need to decide where to put content. Usually "Qualifications & Characteristics" could be Qualifications. The "Requirements for this role:" list is likely Requirements. Then "Education & Experience" maybe Qualifications? Or we could combine. But we need to avoid thin sections. Let's see content: Under "Qualifications & Characteristics Requirements for this role:" then bullet list of requirements (experience, desire to learn, communication, teamwork, process improvement, lead/manage productivity, facilitate solutions, anticipate problems, tight deadlines, communication, situational awareness, organizational agility, self-directed, foster initiative, translate goals, training/developing team). That's a list of requirements. Then "Education & Experience": Bachelor's degree etc, OR law degree etc. Then "Preferred Requirements & Certifications": hands-on experience with databases, etc. That's also qualifications/skills. We could have: -

  Requirements

  with the list from "Requirements for this role:" (the bullet list). -

  Qualifications

  with Education & Experience and Preferred Requirements & Certifications combined maybe as a list. But we need to avoid duplication. Also we have Skills heading; maybe we can put technical skills under Skills. Let's extract specific content: From "Preferred Requirements & Certifications": - Hands-on experience with databases, search logic and a foundational understanding of database file structure is required. - A minimum of two years industry-related experience, including a solid understanding of the data processing, litigation support and document review processes, is required; experience of collaborating across shifts is desired. - A solid understanding of all Microsoft Office applications, basic UNIX, Windows, hardware, networking, and delimited files is required; Experience with SQL database and other database applications preferred. - Familiarity with the eDiscovery industry – Electronic Discovery Reference Model (EDRM), technology, global legal framework and competitive landscape – is required. - Knowledge of litigation support software, including any of the following: DocuMatrix, Relativity, Concordance, Summation, Ipro, Ringtail, and Introspect, is required. - Deep experience of one of more SME areas required by Epiq Systems – including formal certifications if available – is required. These are qualifications/skills. Education & Experience: - Bachelor’s degree in Computer Science, Business Management or a closely related field of study or an equivalent combination of education and experience, OR; - A degree or certification in law or a legal field (complemented by suitable technical expertise) We could put Education & Experience under Qualifications. Now Benefits: The posting includes "Click Here To Learn About Epiq's Benefits." but no actual benefits listed. So we should NOT create a Benefits section because no specific content. Similarly Pay: they have a paragraph about salary determination but no specific numbers. The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. They state "Your specific salary will be determined based on several factors: Location-based market rate for the role Your abilities in relation to the job specification Performance during screening and interview Pay parity with the wider team in the considered location Further details about the package will be provided during the initial screening call with the Talent Acquisition Team." That's generic, not specific numbers. It says "Further details about the package will be provided..." but not actual benefits. The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. Does stating that salary will be determined based on factors count as stating Pay? It's not a specific amount or range. Likely we should not create Pay section because it's not concrete. Similarly Schedule: none. Thus we will have sections: About the role, Responsibilities, Requirements, Qualifications, Skills maybe. But we need to avoid thin sections. Could combine Qualifications and Skills? But we have headings list; we can choose to include only those with substantive content. We have: - About the role: intro + job summary. - Responsibilities: list. - Requirements: list of requirements (the "Requirements for this role:" bullet list). - Qualifications: Education & Experience + Preferred Requirements & Certifications (maybe as combined list). - Skills: maybe we could extract technical skills from Preferred Requirements & Certifications (databases, SQL, MS Office, UNIX, etc.) but that overlaps with Qualifications. Could instead put those under Skills and keep Qualifications for education/experience. Let's see. We have education/experience (Bachelors, law degree). That's Qualifications. We have technical skills: hands-on experience with databases, search logic, database file structure, MS Office, basic UNIX, Windows, hardware, networking, delimited files, SQL, eDiscovery industry knowledge, litigation support software list, deep experience in SME areas. Those could be Skills. Thus:

  Qualifications

  Bachelor’s degree in Computer Science, Business Management or a closely related field of study or an equivalent combination of education and experience, OR; A degree or certification in law or a legal field (complemented by suitable technical expertise)

  Skills

  • Hands-on experience with databases, search logic and a foundational understanding of database file structure
  • A minimum of two years industry-related experience, including a solid understanding of the data processing, litigation support and document review processes; experience of collaborating across shifts is desired
  • A solid understanding of all Microsoft Office applications, basic UNIX, Windows, hardware, networking, and delimited files; Experience with SQL database and other database applications preferred
  • Familiarity with the eDiscovery industry – Electronic Discovery Reference Model (EDRM), technology, global legal framework and competitive landscape
  • Knowledge of litigation support software, including DocuMatrix, Relativity, Concordance, Summation, Ipro, Ringtail, and Introspect
  • Deep experience of one or more SME areas required by Epiq Systems – including formal certifications if available
  Now Requirements: list from "Requirements for this role:" bullet list. Let's extract that list exactly: - At least three years’ experience working in an IT/technical role that is production-based, deadline driven and outcome oriented. - Must possess a strong desire to learn new skills. - Must display excellent verbal and written communication. - Must work well in a team environment. - Demonstrated experience implementing process improvement and compliance is required. - Must have a demonstrable ability to effectively lead and manage the productivity of the team, incidents, and drive to problem resolutions. - Must be able to facilitate solutions across departments and teams in a collaborative manner. - Must be able to anticipate and prevent problems while assisting in managing incidents to resolution. - Experience of working under tight deadlines in a fast-paced environment. - Strong communication, situational awareness and organizational agility skills. - Must be self-directed and foster initiative in others. - Must be able to translate larger business goals into actionable items for their team. - Demonstrable experience with training and developing team members using an inspirational and motivational approach that aligns with Epiq’s unique organizational culture. We'll put each as
• . Now Responsibilities list: extract from "Essential Job Responsibilities". The text after that heading includes sentences separated by periods. Let's list each duty: - Utilize proprietary software applications, 3rd party eDiscovery applications, electronic discovery and data recovery processes. - Load, Process and Search client data in many different file formats. - Work closely with team members to troubleshoot data issues (prior to escalation to operations senior management and/or IT/Development), research software and/or techniques to solve problems, and carry out complex data analysis tasks. - Communicate and collaborate with other company departments. - Generate reports from various database platforms for senior management. - Be a Subject Matter Expert (SME) in one or more areas of the eDiscovery operational workflow as practiced at Epiq Systems. Make SME available by consulting on projects, planning meetings, client requirements and solution design as required. - Create and lead training sessions for Associates in SME areas as requested by Management. - Be responsible for the creation and management of Standard Operating Procedures (SOPs) for their SME areas, including but not limited to policies, procedures, workflows and work instructions. - Ensure reference documentation is maintained and easily findable. - Contribute to the development and implementation of a Knowledge Management (KM) strategy. - Manage, drive, and implement department initiatives around planning, documentation, procedures and Continuous Improvement, and ensure compliance with policies, procedures and work instructions. - Promote the company’s culture and values through leadership-by-example, group interaction, and frequent one-on-one coaching with associates at every level. We'll put each as
• . Now About the role: combine intro paragraph and Job Summary. Intro: "At Epiq, your work contributes to complex, global legal outcomes. You’ll join a values‑driven community where integrity guides decisions, relentless service sets the bar, and we thrive on big challenges together. We invest in your growth with enterprise‑wide learning and mobility. We celebrate who you are, and we respect life beyond work with flexibility that’s recognized externally. Enabled by modern platforms and AI, you’ll do the most meaningful work of your career and see your impact at scale." Job Summary: "The Senior Operations Analyst is a specialist Subject Matter Expertise (SME) in one or more areas of the eDiscovery operational workflow as practiced at Epiq. The purpose of this position is to provide SME to Associates, support learning and development, ensure best practices and quality standards in their SME area are applied and adhered to, whilst also acting as an individual contributor within Operations on the full range of activities and tasks." We can combine into a

  or two

  s. Use

  for prose. Thus:

  About the role

  At Epiq, your work contributes to complex, global legal outcomes. You’ll join a values‑driven community where integrity guides decisions, relentless service sets the bar, and we thrive on big challenges together. We invest in your growth with enterprise‑wide learning and mobility. We celebrate who you are, and we respect life beyond work with flexibility that’s recognized externally. Enabled by modern platforms and AI, you’ll do the most meaningful work of your career and see your impact at scale.

  The Senior Operations Analyst is a specialist Subject Matter Expertise (SME) in one or more areas of the eDiscovery operational workflow as practiced at Epiq. The purpose of this position is to provide SME to Associates, support learning and development, ensure best practices and quality standards in their SME area are applied and adhered to, whilst also acting as an individual contributor within Operations on the full range of activities and tasks.

  Now we must not include any boilerplate like EEO, legal, etc