E-Discovery Project Coordinator
for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to include only sections that have real specific content. The posting includes: "Who We Are" (description of company) maybe corresponds to About the role? Actually "Who We Are" is about company, not role. Could map to About the role? Might be better to have "About the role" section summarizing role description: "What You Will Be Doing". That is responsibilities. Also "Who We Are Looking For" includes requirements/qualifications/skills. Also "Where Your Career is Going" maybe not needed. "Why TransPerfect" includes benefits. Also mention overtime etc. Pay and schedule not specified, so we should NOT include Pay or Schedule sections because no specific content. Benefits: they mention comprehensive benefits package including medical, dental, vision insurance, 401k matching, membership to child-care providers, other TransPerks, birthday off. That's specific, so include Benefits section.
We need to avoid repeating job title as heading. No job title given explicitly; ignore.
We need to use - for any list of duties/requirements/benefits. Use
for prose.
We must preserve all substantive information, not invent or summarize away detail. Remove boilerplate: EEO, legal, etc. Also remove duplicated lines (e.g., "Excellent customer service & teamwork skills (restaurant & retail experience is great!)" appears twice). Keep only one.
We need to include sections only when posting has real specific content.
Let's extract content:
- Who We Are: description of TLS electronic discovery division, what they do, etc. This is about the company/team. Could be placed under "About the role"? Actually "About the role" would be about the position. But we have "What You Will Be Doing" which is responsibilities. "Who We Are" could be considered "About the company" but not a required heading. The allowed headings are limited to those list. We could put company description under "About the role" as a brief intro? But that might misrepresent. However instructions: use those headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't say we must only use those exact headings, but they are examples. Likely we should use those headings where appropriate. So we can have:
About the role
- maybe include description of TLS and team? Could be okay.
Responsibilities
- from "What You Will Be Doing": bullet points: Communication, Task Management, Learning & Creative Thinking, Team Work, Quality Assurance. We need to preserve details.
Requirements
- maybe "Must haves" list.
Qualifications
- maybe Bachelor's degree etc. But requirements and qualifications may overlap. Could combine? But we need to avoid thin sections. Perhaps we can have Requirements covering must-haves, and Qualifications covering nice-to-have? Or Skills covering technical skills. Let's think.
The posting: "Who We Are Looking For: Must haves: ..." then list. Then "Nice to have, but not necessary: ..." So we could map Must haves to Requirements, Nice to have to Qualifications or Skills. Also there is list of skills: Comfortable navigating basic MS Office applications, Comfortable with learning new technology platforms, Ability to work under pressure, etc. Those are skills.
We could structure:
- About the role: description of TLS and team (Who We Are)
- Responsibilities: What You Will Be Doing (with subpoints)
- Requirements: Must haves (list)
- Skills: Nice to have (list) plus maybe MS Office etc? But MS Office is a must-have? It's listed under Must haves: "Comfortable navigating basic MS Office applications (Excel, Word, PPT)" and "Comfortable with learning new technology platforms". Those are skills. Could be under Skills.
But we need to avoid duplication. Let's extract all Must haves items:
- Excellent organizational + communication skills to handle high volumes of emails in a timely manner
- Excellent customer service & teamwork skills (restaurant & retail experience is great!)
- Bachelor’s Degree from a 4-year college or university or equivalent work experience
- Comfortable navigating basic MS Office applications (Excel, Word, PPT)
- Comfortable with learning new technology platforms
- Available to work overtime, including evenings and weekends as needed
- Ability to work well under pressure and meet tight deadlines in a team environment
- Excellent customer service & teamwork skills (restaurant & retail experience is great!) [duplicate]
- Must be a high-level problem solver and have high multi-tasking skills
- The ability to think “outside the box”
- Maintain a self-motivated attitude and strive for advancement
- High level customer service experience
We need to deduplicate: remove duplicate "Excellent customer service & teamwork skills (restaurant & retail experience is great!)". Also maybe "High level customer service experience" similar to that; but keep both? Might be considered similar but we can keep both as they are slightly different phrasing. However we should preserve all substantive information; we can keep both but maybe they are redundant. I'd keep both but note it's duplicate? The instruction: remove duplicated lines. So we should remove duplicate lines. The duplicate is exactly same phrase appears twice. Remove one. Keep one.
Now "High level customer service experience" is not exactly same phrase; it's similar but not duplicate. Keep.
Now Nice to have list:
- Business Administration, Computer Science, Mathematics, Communications, Hospitality majors
- Data analysis experience
- Experience in the legal field
- Knowledge of SQL and/or Visual Basic
Now Benefits: from Why TransPerfect: comprehensive benefits package including medical, dental, and vision insurance, 401k matching, membership to child-care providers, and other TransPerks. You even get your birthday off because let's face it, we're stoked that you were born.
Also maybe mention "We also offer a comprehensive benefits package..." That's it.
Now About the role: we can use "Who Are We" description: The TransPerfect Legal Solutions (TLS) electronic discovery division is responsible for managing the electronic & physical evidence relevant to legal matters originating from law firms and/or corporations who engage us directly. TLS can forensically collect source data (laptops, desktops, e-mail accounts, local servers, fileshares, message apps, mobile phones, etc), electronically process & standardize that data for searching, promote the “relevant” pool of documents to a review tool, establish review workflows (at times using data analytics), and help the customer determine what scope would be produced (or disclosed) to the opposing party in the matter. TransPerfect Legal Solutions is a division part of the family of companies that form TransPerfect. The TLS E-Discovery Project Management team is involved in all aspects of the matter. Project Managers are running searches in our processing environment, advising clients on complex data analytics workflows, conferring with government agencies on production specifications, and addressing problems as needed. Customer service is a cornerstone of success here. We work closely together as a tight knit team, pushing ego aside so that we can be agile in meeting our customers’ needs because no two days are alike here.
That's substantive.
Now Responsibilities: from "What You Will Be Doing:" with bullet points: Communication, Task Management, Learning & Creative Thinking, Team Work, Quality Assurance. Need to preserve details under each.
Let's extract each:
Communication: the PC is responsible for monitoring customer communications. We do not use a “ticketing system” when working with our customers so it is up to the PM team to collectively manage requests as they arise in real-time. In addition, you will be communicating directly with several other internal departments (Digital Forensics, Data Processing, Hosting Support, etc.). Being able to creatively resolve conflicts is a very important aspect of this position.
Task Management: as a PC you will be helping the team to ensure that deadlines are being monitored proactively and that customers are being given the perception that we are exceeding expectations.
Learning & Creative Thinking: because no two days are alike here, as a PC you will largely “learn by doing” and be expected to think on your feet and outside of the box. That being said, we do provide a full & engaging training curriculum (including group classes, 1 on 1 sessions, and a library of video documentation) to all new PC’s which is administered by seasoned TLS Project Managers.
Team Work: after you “graduate” from the entry level PM training program, you will be in direct contact with your team in-person, over messaging apps, video-conferencing, or over e-mail to ensure that you have as many resources as possible at your fingertips.
Quality Assurance: because of the complexity of the projects we handle, QC (“quality checking”) our work product is absolutely necessary. We strive to create an open environment where questions are encouraged so that we can address mistakes internally before they reach the customer. That being said, we very much understand that human beings make mistakes!
We need to put these as list items (
- ) each containing the prose. Could also keep headings inside li? Probably each li contains the paragraph.
Now Requirements: Must haves list (deduplicated). We'll output as
- each item.
Now Skills: Nice to have list plus maybe MS Office etc? But MS Office etc are must-haves but could be considered skills. However we already have them in Requirements. To avoid thin sections, maybe we combine Must haves and Nice to have into Requirements and Skills sections. Let's decide:
- Requirements: Bachelor's degree, organizational/communication skills, customer service/teamwork, ability to work overtime, ability to work under pressure, high-level problem solver, multi-tasking, think outside box, self-motivated, high level customer service experience. Also maybe "Excellent organizational + communication skills to handle high volumes of emails in a timely manner" etc.
- Skills: Comfortable navigating basic MS Office applications, Comfortable with learning new technology platforms, Knowledge of SQL and/or Visual Basic (nice to have), Data analysis experience (nice to have), Experience in legal field (nice to have), Business Administration etc majors (nice to have). Also maybe "Ability to work well under pressure" is skill but already in requirements.
We need to avoid duplication. Let's list Must haves items (excluding duplicates) and categorize.
Must haves list (unique):
1. Excellent organizational + communication skills to handle high volumes of emails in a timely manner
2. Excellent customer service & teamwork skills (restaurant & retail experience is great!)
3. Bachelor’s Degree from a 4-year college or university or equivalent work experience
4. Comfortable navigating basic MS Office applications (Excel, Word, PPT)
5. Comfortable with learning new technology platforms
6. Available to work overtime, including evenings and weekends as needed
7. Ability to work well under pressure and meet tight deadlines in a team environment
8. Must be a high-level problem solver and have high multi-tasking skills
9. The ability to think “outside the box”
10. Maintain a self-motivated attitude and strive for advancement
11. High level customer service experience
Now Nice to have:
- Business Administration, Computer Science, Mathematics, Communications, Hospitality majors
- Data analysis experience
- Experience in the legal field
- Knowledge of SQL and/or Visual Basic
Now we need to map to headings. The allowed headings include Requirements, Qualifications, Skills. We could use Requirements for the must-haves (including education, experience, soft skills). Qualifications could be for nice-to-have? Or Skills for technical skills. But we have both nice-to-have and technical skills. Perhaps we can have:
Requirements
- list of must-haves
for prose. We must preserve all substantive information, not invent or summarize away detail. Remove boilerplate: EEO, legal, etc. Also remove duplicated lines (e.g., "Excellent customer service & teamwork skills (restaurant & retail experience is great!)" appears twice). Keep only one. We need to include sections only when posting has real specific content. Let's extract content: - Who We Are: description of TLS electronic discovery division, what they do, etc. This is about the company/team. Could be placed under "About the role"? Actually "About the role" would be about the position. But we have "What You Will Be Doing" which is responsibilities. "Who We Are" could be considered "About the company" but not a required heading. The allowed headings are limited to those list. We could put company description under "About the role" as a brief intro? But that might misrepresent. However instructions: use those headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't say we must only use those exact headings, but they are examples. Likely we should use those headings where appropriate. So we can have:
About the role
- maybe include description of TLS and team? Could be okay.
Responsibilities
- from "What You Will Be Doing": bullet points: Communication, Task Management, Learning & Creative Thinking, Team Work, Quality Assurance. We need to preserve details.
Requirements
- maybe "Must haves" list.
Qualifications
- maybe Bachelor's degree etc. But requirements and qualifications may overlap. Could combine? But we need to avoid thin sections. Perhaps we can have Requirements covering must-haves, and Qualifications covering nice-to-have? Or Skills covering technical skills. Let's think.
The posting: "Who We Are Looking For: Must haves: ..." then list. Then "Nice to have, but not necessary: ..." So we could map Must haves to Requirements, Nice to have to Qualifications or Skills. Also there is list of skills: Comfortable navigating basic MS Office applications, Comfortable with learning new technology platforms, Ability to work under pressure, etc. Those are skills.
We could structure:
- About the role: description of TLS and team (Who We Are)
- Responsibilities: What You Will Be Doing (with subpoints)
- Requirements: Must haves (list)
- Skills: Nice to have (list) plus maybe MS Office etc? But MS Office is a must-have? It's listed under Must haves: "Comfortable navigating basic MS Office applications (Excel, Word, PPT)" and "Comfortable with learning new technology platforms". Those are skills. Could be under Skills.
But we need to avoid duplication. Let's extract all Must haves items:
- Excellent organizational + communication skills to handle high volumes of emails in a timely manner
- Excellent customer service & teamwork skills (restaurant & retail experience is great!)
- Bachelor’s Degree from a 4-year college or university or equivalent work experience
- Comfortable navigating basic MS Office applications (Excel, Word, PPT)
- Comfortable with learning new technology platforms
- Available to work overtime, including evenings and weekends as needed
- Ability to work well under pressure and meet tight deadlines in a team environment
- Excellent customer service & teamwork skills (restaurant & retail experience is great!) [duplicate]
- Must be a high-level problem solver and have high multi-tasking skills
- The ability to think “outside the box”
- Maintain a self-motivated attitude and strive for advancement
- High level customer service experience
We need to deduplicate: remove duplicate "Excellent customer service & teamwork skills (restaurant & retail experience is great!)". Also maybe "High level customer service experience" similar to that; but keep both? Might be considered similar but we can keep both as they are slightly different phrasing. However we should preserve all substantive information; we can keep both but maybe they are redundant. I'd keep both but note it's duplicate? The instruction: remove duplicated lines. So we should remove duplicate lines. The duplicate is exactly same phrase appears twice. Remove one. Keep one.
Now "High level customer service experience" is not exactly same phrase; it's similar but not duplicate. Keep.
Now Nice to have list:
- Business Administration, Computer Science, Mathematics, Communications, Hospitality majors
- Data analysis experience
- Experience in the legal field
- Knowledge of SQL and/or Visual Basic
Now Benefits: from Why TransPerfect: comprehensive benefits package including medical, dental, and vision insurance, 401k matching, membership to child-care providers, and other TransPerks. You even get your birthday off because let's face it, we're stoked that you were born.
Also maybe mention "We also offer a comprehensive benefits package..." That's it.
Now About the role: we can use "Who Are We" description: The TransPerfect Legal Solutions (TLS) electronic discovery division is responsible for managing the electronic & physical evidence relevant to legal matters originating from law firms and/or corporations who engage us directly. TLS can forensically collect source data (laptops, desktops, e-mail accounts, local servers, fileshares, message apps, mobile phones, etc), electronically process & standardize that data for searching, promote the “relevant” pool of documents to a review tool, establish review workflows (at times using data analytics), and help the customer determine what scope would be produced (or disclosed) to the opposing party in the matter. TransPerfect Legal Solutions is a division part of the family of companies that form TransPerfect. The TLS E-Discovery Project Management team is involved in all aspects of the matter. Project Managers are running searches in our processing environment, advising clients on complex data analytics workflows, conferring with government agencies on production specifications, and addressing problems as needed. Customer service is a cornerstone of success here. We work closely together as a tight knit team, pushing ego aside so that we can be agile in meeting our customers’ needs because no two days are alike here.
That's substantive.
Now Responsibilities: from "What You Will Be Doing:" with bullet points: Communication, Task Management, Learning & Creative Thinking, Team Work, Quality Assurance. Need to preserve details under each.
Let's extract each:
Communication: the PC is responsible for monitoring customer communications. We do not use a “ticketing system” when working with our customers so it is up to the PM team to collectively manage requests as they arise in real-time. In addition, you will be communicating directly with several other internal departments (Digital Forensics, Data Processing, Hosting Support, etc.). Being able to creatively resolve conflicts is a very important aspect of this position.
Task Management: as a PC you will be helping the team to ensure that deadlines are being monitored proactively and that customers are being given the perception that we are exceeding expectations.
Learning & Creative Thinking: because no two days are alike here, as a PC you will largely “learn by doing” and be expected to think on your feet and outside of the box. That being said, we do provide a full & engaging training curriculum (including group classes, 1 on 1 sessions, and a library of video documentation) to all new PC’s which is administered by seasoned TLS Project Managers.
Team Work: after you “graduate” from the entry level PM training program, you will be in direct contact with your team in-person, over messaging apps, video-conferencing, or over e-mail to ensure that you have as many resources as possible at your fingertips.
Quality Assurance: because of the complexity of the projects we handle, QC (“quality checking”) our work product is absolutely necessary. We strive to create an open environment where questions are encouraged so that we can address mistakes internally before they reach the customer. That being said, we very much understand that human beings make mistakes!
We need to put these as list items (
- each item.
Now Skills: Nice to have list plus maybe MS Office etc? But MS Office etc are must-haves but could be considered skills. However we already have them in Requirements. To avoid thin sections, maybe we combine Must haves and Nice to have into Requirements and Skills sections. Let's decide:
- Requirements: Bachelor's degree, organizational/communication skills, customer service/teamwork, ability to work overtime, ability to work under pressure, high-level problem solver, multi-tasking, think outside box, self-motivated, high level customer service experience. Also maybe "Excellent organizational + communication skills to handle high volumes of emails in a timely manner" etc.
- Skills: Comfortable navigating basic MS Office applications, Comfortable with learning new technology platforms, Knowledge of SQL and/or Visual Basic (nice to have), Data analysis experience (nice to have), Experience in legal field (nice to have), Business Administration etc majors (nice to have). Also maybe "Ability to work well under pressure" is skill but already in requirements.
We need to avoid duplication. Let's list Must haves items (excluding duplicates) and categorize.
Must haves list (unique):
1. Excellent organizational + communication skills to handle high volumes of emails in a timely manner
2. Excellent customer service & teamwork skills (restaurant & retail experience is great!)
3. Bachelor’s Degree from a 4-year college or university or equivalent work experience
4. Comfortable navigating basic MS Office applications (Excel, Word, PPT)
5. Comfortable with learning new technology platforms
6. Available to work overtime, including evenings and weekends as needed
7. Ability to work well under pressure and meet tight deadlines in a team environment
8. Must be a high-level problem solver and have high multi-tasking skills
9. The ability to think “outside the box”
10. Maintain a self-motivated attitude and strive for advancement
11. High level customer service experience
Now Nice to have:
- Business Administration, Computer Science, Mathematics, Communications, Hospitality majors
- Data analysis experience
- Experience in the legal field
- Knowledge of SQL and/or Visual Basic
Now we need to map to headings. The allowed headings include Requirements, Qualifications, Skills. We could use Requirements for the must-haves (including education, experience, soft skills). Qualifications could be for nice-to-have? Or Skills for technical skills. But we have both nice-to-have and technical skills. Perhaps we can have:
Requirements
- list of must-haves