eDiscovery Technical Advisor (Top Secret Clearance Required)

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections where there is real specific content. Must not repeat job title. Must not include Job ID etc. Must preserve all substantive info. Remove boilerplate like EEO, contact info, application instructions, navigation, etc. Must not include placeholder like "commensurate with experience". Must not create Pay/Schedule/Benefits unless posting actually states them. The posting includes a benefits list: "Health, Dental, and Vision Life Insurance 401k Flexible Spending Account (Health, Dependent Care, and Commuter) Paid Time Off and Observance of State/Federal Holidays". Also includes Pay: "#CJ$137,200 - $186,200 a year". That's a pay range. So we can include Pay section. Schedule? Not mentioned explicitly; only "Full-Time". Could we include Schedule section with "Full-Time"? The rule: never create Pay/Schedule/Benefits sections unless posting actually states them. It does state Full-Time under Employment Type. So we can include Schedule with Full-Time. However we must avoid filler like "not specified". It's specified. So include Schedule. We need sections: About the role (intro paragraph), Responsibilities (list of duties), Requirements (maybe qualifications?), Skills, Benefits, Pay, Schedule. Qualifications maybe separate from Requirements? The posting has "Qualifications" bullet list. Also "Skills And Attributes For Success" is a long paragraph describing responsibilities. Actually the "Skills And Attributes For Success" section is a list of contractor responsibilities (many bullet-like sentences). That seems like Responsibilities. Then there is a "Qualifications" section with bullet points. Then there is "Our Commitment" etc which is boilerplate; we can drop. Also there is a paragraph about CGS mission etc which could be About the role. We need to preserve all substantive info; not invent or summarize away detail. Must not repeat job title. Must not include navigation/legal/EEO etc. Must drop contact info, application instructions, etc. Also drop the AI disclaimer? That's maybe boilerplate but it's about hiring process; could be considered boilerplate? It's not EEO but still maybe considered generic. The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The AI disclaimer is not exactly those but could be considered part of hiring process; maybe keep? It's not essential to job description; but it's about hiring process. Might be considered boilerplate; safer to remove. We must output only HTML fragment. Let's extract: About the role: The paragraph after "eDiscovery Technical Advisor Employment Type: Full-Time, Executive-Level Department: Legal CGS is seeking a dedicated eDiscovery Technical Advisor to join a fast-paced and hard-working team to assist with any legal accounts. As an eDiscovery Technical Advisor, you will play a key role in supporting various aspects of the company's portfolio. CGS brings motivated, highly skilled, and creative people together to solve the government’s most dynamic problems with cutting-edge technology. To carry out our mission, we are seeking candidates who are excited to contribute to government innovation, appreciate collaboration, and can anticipate the needs of others. Here at CGS, we offer an environment in which our employees feel supported, and we encourage professional growth through various learning opportunities." That's substantive. Responsibilities: The "Skills And Attributes For Success" block contains many duties. Let's list each sentence as a bullet. We need to parse them: - Contractor shall provide expertise in identifying, preserving, collecting, processing, and producing ESI in support of civil and criminal litigation, select FOIA requests, Congressional requests and other inquiries; - Contractor shall provide expertise specifically in criminal discovery support to include identifying, preserving, collecting, processing, and producing ESI; - Contractor shall serve as the expert technical user of the available electronic discovery applications, which include Enterprise Vault, Discovery Accelerator, Legal Hold Management Tool (LHMT) and the Veritas eDiscovery Platform; - Contractor shall work with the litigation team to develop a discovery plan which documents the electronic discovery search parameters (e.g., date range, key words and custodians) for a particular case; - Contractor shall use electronic discovery software applications to collect data from various FBI storage locations on FBI IT systems (e.g., MS-Exchange servers, shared drives, desktops, text and instant messages) in accordance with the discovery plan, to support OGC attorneys, paralegal specialists, Information Management Division personnel and case agents who are responsible for responding to pre-trial discovery motions, requests, subpoenas related to civil and criminal matters, congressional inquiries, FOIA requests and other inquiries; - Contractor shall analyze search/collection results for data gaps; - Contractor shall administer data inputs into an electronic discovery review platform (i.e. eDP), which includes, but is not limited to: creating cases; adding collected source data; handling user access rights; uploading data logs; de-duplicating collected source data; identifying data gaps; merging/verifying data; and assuring electronic discovery production quality in Bates numbering and load file creation; - Contractor shall coordinate electronic discovery collection results with FBI units responsible for processing discovery for review/redaction/release; - Contractor shall adhere to polices and technical procedures for use of available electronic discovery software applications and provide agency attorneys, paralegals, and other users of the FBI's electronic discovery review platform with training and other technical assistance; - Contractor shall provide information and advise on instructions regarding the FBI's process for identifying, preserving, collecting, analyzing, and organizing ESI, including the use of electronic discovery software programs; - Contractor shall provide ad hoc support to end users of the electronic discovery review platform repository; - Contractor shall document electronic discovery plans and procedures for each individual case; - Contractor shall facilitate requests for legal hold implementation, amendment, and/or lift that are submitted by various requesters in LHMT; - Contractor shall provide eDiscovery collections on criminal cases. We should keep them as

items. Requirements: Might be overlapping with Qualifications. The posting has "Qualifications" bullet list. Could treat that as Requirements. But we also have Skills section maybe separate. The instruction: Use headings for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need both Requirements and Qualifications and Skills if content exists. We have Qualifications bullet list: - 5 (five) years of eDiscovery/litigation support experience with a focus on client solutions. - 3 (three) years of progressive more responsible experience on major lit support projects. - 2 years in Relativity, beyond document review coding. - Excellent communication, presentation, and interpersonal skills with both eDiscovery technical teams and non-technical business leaders and team players. - Ability to work in a fast-paced environment and agile work environment. - Experience and familiarity with eDiscovery Services covering all realms of the EDRM (File to Trial). - Must be a U.S. Citizen. - The ability to obtain a U.S. Government security clearance (active clearance preferred). - BS/BA degree or equivalent work experience (JD highly preferred). We could split: Requirements could be the experience/skills, Qualifications could be education/citizenship/clearance. But we can also just put all under Qualifications and leave Requirements empty? But we must not emit a heading followed by filler/placeholder text. So if we include Requirements heading, we must have substantive content. We could treat the first few bullet points as Requirements (years of experience, Relativity, etc.) and the rest as Qualifications (citizenship, clearance, degree). Or we could combine them under Qualifications and not include Requirements. But the instruction says prefer a few substantive sections over many thin ones. So maybe we combine experience and skills into Responsibilities and Qualifications, and not include Requirements separately. However we have a Skills section maybe for soft skills etc. The posting includes "Excellent communication, presentation, and interpersonal skills..." which is a skill. Also "Ability to work in a fast-paced environment and agile work environment." That's also a skill. Could be under Skills. Thus we can have: - About the role (paragraph) - Responsibilities (list of duties from Skills And Attributes For Success) - Skills (list of soft skills: communication, presentation, interpersonal; ability to work fast-paced agile; maybe also experience with eDiscovery Services covering EDRM? That's more experience.) - Qualifications (years of experience, Relativity, citizenship, clearance, degree) - Benefits (list) - Pay (range) - Schedule (Full-Time) We must ensure we don't duplicate content. Let's extract skills: From Qualifications bullet list: "Excellent communication, presentation, and interpersonal skills with both eDiscovery technical teams and non-technical business leaders and team players." That's a skill. "Ability to work in a fast-paced environment and agile work environment." That's a skill. "Experience and familiarity with eDiscovery Services covering all realms of the EDRM (File to Trial)." That's experience but could be under Qualifications as well. We could put that under Qualifications. Thus Skills section will have two items. Now Benefits: list: Health, Dental, and Vision Life Insurance 401k Flexible Spending Account (Health, Dependent Care, and Commuter) Paid Time Off and Observance of State/Federal Holidays. We need to format as

• each benefit? Could be one string but better split: Health, Dental, and Vision; Life Insurance; 401k; Flexible Spending Account (Health, Dependent Care, and Commuter); Paid Time Off; Observance of State/Federal Holidays. Pay: "$137,200 - $186,200 a year". The posting shows "#CJ$137,200 - $186,200 a year". We'll strip the "#CJ". So Pay: $137,200 - $186,200 a year. Schedule: Full-Time. Now produce HTML. We must not include any extra text outside HTML. No markdown fences. Let's craft:

  About the role

  CGS is seeking a dedicated eDiscovery Technical Advisor to join a fast-paced and hard-working team to assist with any legal accounts. As an eDiscovery Technical Advisor, you will play a key role in supporting various aspects of the company's portfolio. CGS brings motivated, highly skilled, and creative people together to solve the government’s most dynamic problems with cutting-edge technology. To carry out our mission, we are seeking candidates who are excited to contribute to government innovation, appreciate collaboration, and can anticipate the needs of others. Here at CGS, we offer an environment in which our employees feel supported, and we encourage professional growth through various learning opportunities.

  Responsibilities

  • Provide expertise in identifying, preserving, collecting, processing, and producing ESI in support of civil and criminal litigation, select FOIA requests, Congressional requests and other inquiries.
  • Provide expertise specifically in criminal discovery support to include identifying, preserving, collecting, processing, and producing ESI.
  • Serve as the expert technical user of the available electronic discovery applications, which include Enterprise Vault, Discovery Accelerator, Legal Hold Management Tool (LHMT) and the Veritas eDiscovery Platform.
  • Work with the litigation team to develop a discovery plan which documents the electronic discovery search parameters (e.g., date range, key words and custodians) for a particular case.
  • Use electronic discovery software applications to collect data from various FBI storage locations on FBI IT systems (e.g., MS-Exchange servers, shared drives, desktops, text and instant messages) in accordance with the discovery plan, to support OGC attorneys, paralegal specialists, Information Management Division personnel and case agents who are responsible for responding to pre-trial discovery motions, requests, subpoenas related to civil and criminal matters, congressional inquiries, FOIA requests and other inquiries