Litigation Attorney with AI Experience (Remote Contract Engagement)
Latitude is seeking... etc.
We must not put Job ID/requisition numbers as headings.
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 must remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions.
Thus we need to strip out the About Latitude paragraphs? Those are about the company; maybe considered boilerplate? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. About Latitude is not explicitly listed to remove, but could be considered boilerplate? However it's substantive info about the company; but the instruction says "Preserve ALL substantive information; do NOT invent or summarize away detail." So we should keep About Latitude if it's substantive. However the sections we are allowed to output are limited to the headings list. About Latitude could go under "About the role"? No, that's about the role. There's no heading for "About the company". The allowed headings are: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we must fit all substantive info into those sections. If we have info about Latitude company, we could put it under "About the role"? That might be a stretch but maybe acceptable. However the instruction says "Prefer a few substantive sections over many thin ones." So we could combine company info into About the role or Requirements etc. But we need to preserve all substantive info; we can include it in a paragraph under About the role.
Similarly, the Latitude Contract Engagements & Secondments description could be considered part of About the role or maybe Benefits? Probably About the role.
The FAQ we should remove as application instructions.
Thus we will craft sections:
About the role
Latitude is seeking an attorney with 5+ years of sophisticated litigation experience to support the knowledge management team of one of its AmLaw 100 law firm clients with the implementation of a firm‑wide AI platform. The attorney will serve as the firm’s subject matter expert in litigation, leveraging both litigation background and platform training to guide attorneys at the firm on the effective use of the AI platform. The role involves becoming deeply proficient in the AI platform’s capabilities, collaborating on platform optimization, and acting as a trusted internal resource to answer substantive and practical questions related to litigation workflows and AI‑enabled solutions. This is a flexible, multi‑month contract engagement and candidates may work remotely from any location in the United States. Latitude is a full‑service flexible legal talent company serving corporate legal departments and law firms nationwide, providing top‑tier attorneys and legal professionals for flexible contract engagements and permanent positions.
Responsibilities
- Serve as the firm’s subject matter expert in litigation.
- Guide attorneys on the effective use of the AI platform.
- Become deeply proficient in the AI platform’s capabilities.
- Collaborate on platform optimization.
- Act as a trusted internal resource to answer substantive and practical questions related to litigation workflows and AI‑enabled solutions.
Requirements
- 5+ years of litigation experience, preferably at a mid‑to‑large size law firm.
- Hands‑on experience using AI legal platforms such as CoCounsel, Harvey, and/or Protégé is a plus.
- Licensed attorney in good standing in the state of residence.
- Outstanding references.
Qualifications
Prior experience handling litigation matters at a mid‑to‑large size law firm is preferred. Prior experience working with AI platforms, including CoCounsel, Harvey, and/or Protégé is a plus.
But note that Qualifications may overlap with Requirements; but we can keep both as they have slightly different nuance. However we might combine to avoid thin sections. The instruction says prefer a few substantive sections over many thin ones. So maybe we should merge Requirements and Qualifications into one section, maybe "Requirements". But we need to follow the allowed headings; we can omit Qualifications if it's thin. However we have content for Qualifications: prior experience handling litigation matters at mid-to-large size law firm preferred; prior experience with AI platforms is a plus. That's similar to Requirements but we could incorporate into Requirements. Let's keep Requirements only and drop Qualifications to avoid thin section.
Similarly Skills: we could include litigation experience, AI platform experience, etc. But that may be thin. Could merge into Requirements.
Thus we may have sections: About the role, Responsibilities, Requirements, Benefits, Pay, Schedule.
We need to include Benefits, Pay, Schedule.
Let's extract Benefits paragraph:
"In addition to pay, all Latitude contract professionals receive complimentary professional liability insurance coverage. Latitude contract professionals are usually W2 employees of Latitude and are eligible for full benefits when working in roles for 20 hours per week. Benefits-eligible Latitude contract professionals receive complimentary Group Life, LTD and AD&D. A qualified 401k plan is also available. Benefits-eligible Latitude Attorneys also receive a CLE and Professional Expense stipend. Confidentiality Latitude will not disclose your identity or propose you to prospective clients without your prior consent. Candidates selected for further consideration will be contacted."
We need to keep confidentiality statement? It's not boilerplate? It's about confidentiality; maybe keep as part of Benefits section.
We should remove duplicated lines? Not seeing duplicates.
Now Pay:
"Compensation Pay: The annualized pay for this contract position ranges from $180,000 to $200,000 or more when calculated on a full-time basis. Pay for contract engagements is based on multiple factors including but not limited to work experience, qualifications, credentials, location, market supply/demand, and the candidate’s preference (each candidate’s pay rate affects the client bill rate which can affect the candidate’s competitiveness for the position)."
Schedule:
"Type of role: Contract EngagementSchedule: Part-Time or Full-Time Location: Remote"
Also mention flexible, multi-month contract engagement.
Thus Schedule section: Part-Time or Full-Time; Remote; Multi-month contract engagement.
We could also include Location remote.
Now we need to ensure we don't include any application instructions like FAQ, "Candidates selected for further consideration will be contacted." That's maybe okay to keep as part of Benefits? It's about process; but it's not exactly boilerplate; but it's about next steps. Might be considered application instruction? It says "Candidates selected for further consideration will be contacted." That's generic; maybe we can keep it as part of Benefits or a separate section? But we have no section for "Next steps". Could include in Benefits as a note.
But the instruction says remove application instructions. That line is more about process; could be considered application instruction. Safer to remove it.
Thus we will omit "Candidates selected for further consideration will be contacted."
Confidentiality statement: "Latitude will not disclose your identity or propose you to prospective clients without your prior consent." That's not application instruction; it's about privacy. Could keep.
Now we need to ensure we don't repeat any content unnecessarily.
Let's craft final HTML.
We'll have:
About the role
...
Responsibilities
...
Requirements
...
Benefits
...
Pay
...
Schedule
...
Make sure no extra whitespace issues.
Now write the content precisely.
About the role paragraph: combine description and company info.
Let's draft:
"Latitude is seeking an attorney with 5+ years of sophisticated litigation experience to support the knowledge management team of one of its AmLaw 100 law firm clients with the implementation of a firm‑wide AI platform. The attorney will serve
- 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 must remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Thus we need to strip out the About Latitude paragraphs? Those are about the company; maybe considered boilerplate? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. About Latitude is not explicitly listed to remove, but could be considered boilerplate? However it's substantive info about the company; but the instruction says "Preserve ALL substantive information; do NOT invent or summarize away detail." So we should keep About Latitude if it's substantive. However the sections we are allowed to output are limited to the headings list. About Latitude could go under "About the role"? No, that's about the role. There's no heading for "About the company". The allowed headings are: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we must fit all substantive info into those sections. If we have info about Latitude company, we could put it under "About the role"? That might be a stretch but maybe acceptable. However the instruction says "Prefer a few substantive sections over many thin ones." So we could combine company info into About the role or Requirements etc. But we need to preserve all substantive info; we can include it in a paragraph under About the role. Similarly, the Latitude Contract Engagements & Secondments description could be considered part of About the role or maybe Benefits? Probably About the role. The FAQ we should remove as application instructions. Thus we will craft sections:
About the role
Latitude is seeking an attorney with 5+ years of sophisticated litigation experience to support the knowledge management team of one of its AmLaw 100 law firm clients with the implementation of a firm‑wide AI platform. The attorney will serve as the firm’s subject matter expert in litigation, leveraging both litigation background and platform training to guide attorneys at the firm on the effective use of the AI platform. The role involves becoming deeply proficient in the AI platform’s capabilities, collaborating on platform optimization, and acting as a trusted internal resource to answer substantive and practical questions related to litigation workflows and AI‑enabled solutions. This is a flexible, multi‑month contract engagement and candidates may work remotely from any location in the United States. Latitude is a full‑service flexible legal talent company serving corporate legal departments and law firms nationwide, providing top‑tier attorneys and legal professionals for flexible contract engagements and permanent positions.
Responsibilities
- Serve as the firm’s subject matter expert in litigation.
- Guide attorneys on the effective use of the AI platform.
- Become deeply proficient in the AI platform’s capabilities.
- Collaborate on platform optimization.
- Act as a trusted internal resource to answer substantive and practical questions related to litigation workflows and AI‑enabled solutions.
Requirements
- 5+ years of litigation experience, preferably at a mid‑to‑large size law firm.
- Hands‑on experience using AI legal platforms such as CoCounsel, Harvey, and/or Protégé is a plus.
- Licensed attorney in good standing in the state of residence.
- Outstanding references.
Qualifications
Prior experience handling litigation matters at a mid‑to‑large size law firm is preferred. Prior experience working with AI platforms, including CoCounsel, Harvey, and/or Protégé is a plus.
But note that Qualifications may overlap with Requirements; but we can keep both as they have slightly different nuance. However we might combine to avoid thin sections. The instruction says prefer a few substantive sections over many thin ones. So maybe we should merge Requirements and Qualifications into one section, maybe "Requirements". But we need to follow the allowed headings; we can omit Qualifications if it's thin. However we have content for Qualifications: prior experience handling litigation matters at mid-to-large size law firm preferred; prior experience with AI platforms is a plus. That's similar to Requirements but we could incorporate into Requirements. Let's keep Requirements only and drop Qualifications to avoid thin section. Similarly Skills: we could include litigation experience, AI platform experience, etc. But that may be thin. Could merge into Requirements. Thus we may have sections: About the role, Responsibilities, Requirements, Benefits, Pay, Schedule. We need to include Benefits, Pay, Schedule. Let's extract Benefits paragraph: "In addition to pay, all Latitude contract professionals receive complimentary professional liability insurance coverage. Latitude contract professionals are usually W2 employees of Latitude and are eligible for full benefits when working in roles for 20 hours per week. Benefits-eligible Latitude contract professionals receive complimentary Group Life, LTD and AD&D. A qualified 401k plan is also available. Benefits-eligible Latitude Attorneys also receive a CLE and Professional Expense stipend. Confidentiality Latitude will not disclose your identity or propose you to prospective clients without your prior consent. Candidates selected for further consideration will be contacted." We need to keep confidentiality statement? It's not boilerplate? It's about confidentiality; maybe keep as part of Benefits section. We should remove duplicated lines? Not seeing duplicates. Now Pay: "Compensation Pay: The annualized pay for this contract position ranges from $180,000 to $200,000 or more when calculated on a full-time basis. Pay for contract engagements is based on multiple factors including but not limited to work experience, qualifications, credentials, location, market supply/demand, and the candidate’s preference (each candidate’s pay rate affects the client bill rate which can affect the candidate’s competitiveness for the position)." Schedule: "Type of role: Contract EngagementSchedule: Part-Time or Full-Time Location: Remote" Also mention flexible, multi-month contract engagement. Thus Schedule section: Part-Time or Full-Time; Remote; Multi-month contract engagement. We could also include Location remote. Now we need to ensure we don't include any application instructions like FAQ, "Candidates selected for further consideration will be contacted." That's maybe okay to keep as part of Benefits? It's about process; but it's not exactly boilerplate; but it's about next steps. Might be considered application instruction? It says "Candidates selected for further consideration will be contacted." That's generic; maybe we can keep it as part of Benefits or a separate section? But we have no section for "Next steps". Could include in Benefits as a note. But the instruction says remove application instructions. That line is more about process; could be considered application instruction. Safer to remove it. Thus we will omit "Candidates selected for further consideration will be contacted." Confidentiality statement: "Latitude will not disclose your identity or propose you to prospective clients without your prior consent." That's not application instruction; it's about privacy. Could keep. Now we need to ensure we don't repeat any content unnecessarily. Let's craft final HTML. We'll have:About the role
...
Responsibilities
- ...
Requirements
- ...
Benefits
...
Pay
...
Schedule
...
Make sure no extra whitespace issues. Now write the content precisely. About the role paragraph: combine description and company info. Let's draft: "Latitude is seeking an attorney with 5+ years of sophisticated litigation experience to support the knowledge management team of one of its AmLaw 100 law firm clients with the implementation of a firm‑wide AI platform. The attorney will serve