Epic Certified Beaker CP (Laboratory) Consultant

We need to output HTML fragment with sections: About the role? The posting includes "We Are:" description about Accenture. That's about the company, maybe "About the role"? Actually "We Are:" is company description. Could be "About the role"? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use

• for any list of duties/requirements/benefits, and

  for prose. 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. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. We need to decide which sections to include based on content. Content: - "We Are: Accenture is a global professional services company..." This is company overview. Could be "About the role"? Actually it's about the company, not role. Could be "About Accenture"? Not in list. But we can use "About the role" maybe to include description of role? The posting includes "You Are: An experienced Epic skilled and certified analyst in Epic Beaker CP". That's role description. So we could have "About the role" section containing that description. - Responsibilities: list of duties under "Core Responsibilities:" bullet points. - Requirements: "Here is what you need:" includes minimum experience, certification, degree, etc. Also "Bonus points if you have:" additional qualifications. - Benefits: "Accenture offers a market competitive suite of benefits including medical, dental, vision, life, and long-term disability coverage, a 401(k) plan, bonus opportunities, paid holidays, and paid time off." That's specific benefits. - Pay: "Compensation at Accenture varies depending on a wide array of factors..." plus a table of salary ranges by location. That's specific pay info. So we should include Pay section with that table? The instruction: Use

  • for any list of duties/requirements/benefits, and

    for prose. For pay table, it's not a list but a table of ranges. Could we represent as

    • each line? Probably better to use

      for prose and maybe a ? Not specified but we can use

      • for list. The salary ranges could be presented as list items. That seems acceptable. - Schedule: "This role is located in one of the following locations and will require on-site 3 days per week. Nashville, TN; Atlanta, GA; Columbus, OH; Dallas, TX". That's schedule/location info. Could be Schedule section? It mentions on-site 3 days per week (schedule) and locations. Could combine location and schedule. The instruction: include Schedule section only if posting actually states them. It does state on-site 3 days per week. So we can include Schedule section with that info. We must not include boilerplate like EEO, accommodation request, etc. Remove those. We must not include duplicated lines. We must not include application instructions. We must not include "Requesting an Accommodation", "Equal Employment Opportunity Statement", etc. We must not include "See more information on our benefits here: ..." maybe we can keep benefits description but not the link? The link is part of benefits but it's a URL; we could keep as prose but maybe it's okay. However it's a link to benefits page; it's not boilerplate but it's a reference. Might be okay to keep. We must not include "We anticipate this job posting will be posted until 11/07/2026." That's metadata; maybe we can drop as minor metadata? It's not a heading; we could fold into a short

        or drop. Probably drop. We must not include "Visit us at www.accenture.com." That's minor metadata; could drop. We must not include "Accenture offers a market competitive suite of benefits including ..." that's benefits. We must not include "Compensation at Accenture varies depending on a wide array of factors..." that's pay. We must not include the table of salary ranges; we need to include that as pay. We must not include "Requesting an Accommodation" etc. We must not include "Equal Employment Opportunity Statement" etc. We must not include "Other Employment Statements" etc. We must not include "Applicants for employment in the US must have work authorization..." etc. We must not include "California requires additional notifications..." etc. We must not include "Please read Accenture’s Recruiting and Hiring Statement..." etc. Now produce HTML fragment. Structure:

        About the role

        An experienced Epic skilled and certified analyst in Epic Beaker CP.

        But also we have "We Are:" description about Accenture. Could be included in About the role? Might be better to have a section "About Accenture"? Not in allowed headings. Could incorporate into About the role as company overview. But the instruction: "About the role" is example; we can use it for role description. The "We Are:" is about company, not role. However we could still include it as part of About the role? Might be odd but acceptable. Alternatively we could omit company description? But we must preserve ALL substantive information. The company description is substantive. So we need to include it somewhere. Since we don't have a heading for company, we could put it in a

        under About the role or maybe under a generic heading like "About the company"? Not allowed. But we could embed it in About the role section as a paragraph preceding role description. That would preserve it. Thus About the role section: first paragraph about Accenture, second paragraph about role. Alternatively we could have two sections: "About the role" and "About Accenture"? Not allowed headings. So we stick with one. Now Responsibilities: list of duties under Core Responsibilities. We need to extract each bullet: - Document current state business workflows. - Assist with the analysis and design of new business workflows. - Identify and define detailed product requirements and use cases. - Provide input into high level functional specifications. - Work with project managers, architects, business analysts and other team members to define metrics and performance goals for the application. - Participate in transitioning the requirements and use cases to ensure a clear and complete understanding of the requirements. - Assist in translating requirements and use cases into test conditions and expected results for product, performance, and user acceptance testing. - Participate in quality management reviews of the design and performance of work products to ensure they fulfill the requirements. - Perform or advise on system configuration and integration setup and assist with testing activities. - Serve as an intermediary with client's Epic team and Accenture tech leads to support bilateral understanding of data structures, workflows and technology capabilities and limitations. - Assist in the development and documentation of data requests and source to target mapping. - Other duties as assigned. - This work may include implementation, optimization, upgrades, and application support. We should keep all. Now Requirements: "Here is what you need:" includes: - Minimum of 2 years experience in Healthcare IT in an Epic Beaker CP Analyst role - Experience and certification in Epic Beaker CP - Bachelor's degree or equivalent (minimum 12 years) work experience. (If Associate Degree, must have minimum 6 years work experience) We could list as

        • . Bonus points: "Bonus points if you have:" includes: - Minimum of 1 year of experience working for a consulting firm - Experience in at least 1 full implementation of Epic - Experience in Anatomic Pathology Laboratory - Lab Instrument experience We could include under Requirements or maybe a separate "Qualifications" section. The instruction includes Qualifications as possible heading. We could put minimum requirements under Requirements, and bonus under Qualifications. Or we could combine. Let's follow typical: Requirements = mandatory; Qualifications = preferred. So we can have:

          Requirements

          ... mandatory ...

          Qualifications

          ... bonus ...
          Now Benefits: we have benefits description. We could have

          Benefits

          • medical
          • dental
          • vision
          • life
          • long-term disability coverage
          • 401(k) plan
          • bonus opportunities
          • paid holidays
          • paid time off
          Also maybe include link? Could add a

          See more information on our benefits here: U.S. Employee Benefits | Accenture

          but that's a link; we could keep as

          See more information on our benefits here: U.S. Employee Benefits | Accenture

          . Not a list. Now Pay: we have compensation varies and table of salary ranges by location. We need to include Pay section. Could be

          Pay

          Compensation at Accenture varies depending on a wide array of factors, which may include but are not limited to the specific office location, role, skill set, and level of experience. As required by local law, Accenture provides a reasonable range of compensation for roles that may be hired as set forth below.

          • California: $70,350 to $196,000
          • Colorado: $63,800 to $169,300
          • Connecticut: $63,800 to $169,300
          • District of Columbia: $68,000 to $180,300
          • Illinois: $59,100 to $169,300
          • Maine: $54,400 to $144,300
          • Maryland: $63,800 to $169,300
          • Massachusetts: $63,800 to $180,300
          • Minnesota: $63,800 to $169,300
          • New York: $66,300 to $196,000
          • New Jersey: $68,000 to $196,000
          • Ohio: $59,100 to $156,800
          • Virginia: $59,100 to $180,300
          • Washington: $80,200 to $180,300
          We could also note that the posting will be until date but we drop. Now Schedule: "This role is located in one of the following locations and will require on-site 3 days per week. Nashville, TN; Atlanta, GA; Columbus, OH; Dallas, TX" We could have

          Schedule

          On-site 3 days per week. Locations: Nashville, TN; Atlanta, GA; Columbus, OH; Dallas, TX.

          Alternatively we could list locations as
          . But it's fine. Now we must ensure we don't include any boilerplate like EEO etc. Now produce final HTML fragment. Check for any duplicated lines: we have not repeated.