Data Operations Associate
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. So we need to include all responsibilities as list items. Also skills/qualifications as list items. Benefits as list items? The benefits are described in paragraphs with bullet-like items. We can turn each benefit into
- . Pay: we have salary and bonus; we can put in
maybe. Schedule: office 5 days a week.
We must not create sections with filler like "commensurate with experience". Not present.
We need to decide which sections to include: About the role, Responsibilities, Skills and Qualifications, Benefits, Pay, Schedule. All have content.
We must not include duplicate lines. Ensure we capture all.
Let's extract About the role: The paragraph after "About The Role". It starts: "At PitchBook, we believe that the Data Operations team plays a vital role..." continues until "...invite you to join us at PitchBook." We'll put that as
.
Responsibilities: list items from "Primary Job Responsibilities". Each bullet starts with a bold phrase? Actually they are sentences starting with verbs. We'll extract each sentence as list item.
Let's list them:
- Become proficient in one of PitchBook’s core data areas of operation, including: private equity, venture capital, M&A, or Institutional Investors
- Leverage our in-house database, business intelligence reports, and other technology-based tools to ensure that proprietary data is audited and added to the PitchBook Platform efficiently while adhering to complex research tracking methodologies to ensure that data is of the utmost quality
- Consistently provide quality customer service and respond to requests from internal and external customers daily
- Provide training and ramping support to new members of the team, both locally and abroad
- Gather team feedback and utilize PowerBI reports to identify root causes of systemic data problems and drive operational, methodological, and RTS Database improvements
- Regularly collaborate with Secondary team and the broader Data Operations department to develop and improve processes, tools and methodologies; identifying opportunities to improve upon the core quality metrics (comprehensiveness, accuracy, and timeliness)
- Work closely with our Data Operations team in Mumbai to achieve profile production targets. This relationship includes auditing the Mumbai team’s work as well as joining calls to share best practices and process improvement ideas
- Communicate effectively and efficiently with your team and other stakeholders to provide updates on project progress, address roadblocks, and celebrate wins
- Assist senior members of the Data Operations department on the execution of strategic initiatives and achieving operational goals
- Support the vision and values of the company by setting an example and demonstrating desired behaviors
- Participate in various company initiatives and projects as requested
We need to keep each as
- .
Skills and Qualifications: list items from "Skills And Qualifications". Let's extract:
- Bachelor’s degree
- 1+ years of work experience, including any internship experience
- Exemplary verbal and written communication skills and comfortable engaging with a diverse array of audiences
- Ability to operate with a strong sense of urgency and deliver results
- Self-motivated and goal-oriented attitude and can work effectively as an individual or as part of a team
- Interest in financial markets or services, particularly private equity and venture capital
- Analytical and process-oriented with a dedication to continuous improvement
- Ability to problem solve and use judgment to make decisions within ambiguous research situations
- Approach each task with an entrepreneurial spirit and intellectual curiosity
- Strong organization skills with attention to detail
- Proficiency with the Microsoft Office suite including in-depth knowledge of Outlook, Word, and Excel with the ability to pick up new systems and software easily
- Exposure to SQL and/or Python is strongly preferred
We'll put each as
- .
Benefits: The section "Benefits + Compensation at PitchBook:" includes categories: Physical Health, Emotional Health, Social Health, Financial Health. We need to list each benefit item. Let's extract:
Physical Health:
- Comprehensive health benefits
- Additional medical wellness incentives
- STD, LTD, AD&D, and life insurance
Emotional Health:
- Paid sabbatical program after four years
- Paid family and paternity leave
- Annual educational stipend
- Ability to apply for tuition reimbursement
- CFA exam stipend
- Robust training programs on industry and soft skills
- Employee assistance program
- Generous allotment of vacation days, sick days, and volunteer days
Social Health:
- Matching gifts program
- Employee resource groups
- Subsidized emergency childcare
- Dependent Care FSA
- Company-wide events
- Employee referral bonus program
- Quarterly team building events
Financial Health:
- 401k match
- Shared ownership employee stock program
- Monthly transportation stipend
Also note: "Please be aware the above PitchBook benefit and perk offerings are subject to corresponding plan and policy documents and may change during the course of your employment." This is a disclaimer; we might include as a
after benefits list, but it's not a benefit; it's a note. Should we include? It's substantive info about benefits. We'll include as a
after the list.
Pay: "Compensation This position is non-exempt and paid a salary of $72,000-$72,000Target annual bonus percentage: 7.5%". There's a missing space; we can parse as salary $72,000-$72,000 (same) and target annual bonus percentage: 7.5%. We'll put in
.
Schedule: "Working Conditions ... This role is expected to be in the office 5 days a week." Also "Limited corporate travel may be required". We'll put schedule as
maybe with both.
We must not include heading for Working Conditions if we only have schedule; but we can put Schedule heading with that info.
We must not repeat job title. No markdown.
Now produce HTML fragment:
About the role
...
Responsibilities
- ...
...
Skills and Qualifications
...
Benefits
...
Please be aware the above PitchBook benefit and perk offerings are subject to corresponding plan and policy documents and may change during the course of your employment.
Pay
This position is non-exempt and paid a salary of $72,000-$72,000. Target annual bonus percentage: 7.5%.
Schedule
This role is expected to be in the office 5 days a week. Limited corporate travel may be required to remote offices or other business meetings and events.
Check for any duplicate content: Ensure we didn't miss any responsibilities like "Become proficient in one of PitchBook’s core data areas of operation, including: private equity, venture capital, M&A, or Institutional Investors". Good.
Check that we didn't include any boilerplate like "We are excited to get to know you..." etc. That's after Working Conditions; we should remove that as it's application instructions/boilerplate. Also "Concerned that you might not meet every requirement? We encourage you to still apply..." remove.
Also "At the heart of our company is a belief in the power of in-person collaboration..." we used part of it for schedule; but we should not include the preceding fluff about hallway conversations etc. We only need the schedule specifics. We extracted "This role is expected to be in the office 5 days a week." and "Limited corporate travel may be required to remote offices or other business meetings and events." That's from the Working Conditions paragraph. Good.
Now ensure we didn't include any fluff like "The job conditions for this position are in a standard office setting. Employees in this position use PC and phone on an on-going basis throughout the day." That's also part of Working Conditions but maybe we could include as schedule? It's not schedule but work environment. The instruction says include Schedule section only if posting actually states them. It does state schedule (5 days a week). The other details about standard office setting, PC/phone, limited travel are also part of Working Conditions but not schedule. Should we include them? The instruction: "Prefer a few substantive sections over many thin ones." We could incorporate those details into Schedule section as additional info, but they are not schedule. Could create a "Working Conditions" section but not requested headings list includes Schedule, Benefits, Pay, etc. The allowed headings are: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. They didn't list Working Conditions. So we should not create a Working Conditions heading. We could fold those details into Schedule section as extra context, but that might be mixing. However the instruction: "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". It doesn't forbid adding extra info under Schedule as long as it's relevant. The schedule is about office days; the other details about standard office setting, PC/phone, limited travel are also about working conditions but not schedule. Might be okay to include them under Schedule as they are part of Working Conditions but we lack a heading for it. Could we instead put them under About the role? No. Better to include them under Schedule as additional details, but we should not misrepresent. Perhaps we can create a Schedule section with the schedule info and then a separate paragraph about work environment under Schedule? Might be okay.
Alternatively we could omit those details to keep only schedule. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we must preserve all substantive information, including the standard office setting, PC/phone, limited travel. If we omit them, we lose info. So we need to include them somewhere. Since there is no explicit heading for Working Conditions, we could incorporate them into the Schedule section as additional context, but that might be considered stray. However the instruction says "Prefer a few substantive sections over many thin ones." So we could combine schedule and work environment under Schedule heading. That seems acceptable.
Thus Schedule section will contain: "This role is expected to be in the office 5 days a week. Limited corporate travel may be required to remote offices or other business meetings and events. The job conditions for this position are in a standard office setting. Employees in this position use PC and phone on an ongoing basis throughout the day."
We need to ensure we keep the exact phrasing? We can paraphrase slightly but must preserve meaning. Better to keep as close as possible.
Let's copy sentences:
- "This role is expected to be in the office 5 days a week."
- "Limited corporate travel may be required to remote offices or other business meetings and events."
- "The job conditions for this position are in a standard office setting."
- "Employees in this position use PC and phone on an on-going basis throughout the day."
We'll combine into a paragraph.
Now check for any other substantive info: The "About The Role" paragraph includes mention of specialized training and mentorship program tailored to Data Operations team. That's included.
Now ensure we didn't include any
for prose. We need to preserve all substantive information; do not invent or summarize away detail. So we need to include all responsibilities as list items. Also skills/qualifications as list items. Benefits as list items? The benefits are described in paragraphs with bullet-like items. We can turn each benefit into
maybe. Schedule: office 5 days a week. We must not create sections with filler like "commensurate with experience". Not present. We need to decide which sections to include: About the role, Responsibilities, Skills and Qualifications, Benefits, Pay, Schedule. All have content. We must not include duplicate lines. Ensure we capture all. Let's extract About the role: The paragraph after "About The Role". It starts: "At PitchBook, we believe that the Data Operations team plays a vital role..." continues until "...invite you to join us at PitchBook." We'll put that as
. Responsibilities: list items from "Primary Job Responsibilities". Each bullet starts with a bold phrase? Actually they are sentences starting with verbs. We'll extract each sentence as list item. Let's list them: - Become proficient in one of PitchBook’s core data areas of operation, including: private equity, venture capital, M&A, or Institutional Investors - Leverage our in-house database, business intelligence reports, and other technology-based tools to ensure that proprietary data is audited and added to the PitchBook Platform efficiently while adhering to complex research tracking methodologies to ensure that data is of the utmost quality - Consistently provide quality customer service and respond to requests from internal and external customers daily - Provide training and ramping support to new members of the team, both locally and abroad - Gather team feedback and utilize PowerBI reports to identify root causes of systemic data problems and drive operational, methodological, and RTS Database improvements - Regularly collaborate with Secondary team and the broader Data Operations department to develop and improve processes, tools and methodologies; identifying opportunities to improve upon the core quality metrics (comprehensiveness, accuracy, and timeliness) - Work closely with our Data Operations team in Mumbai to achieve profile production targets. This relationship includes auditing the Mumbai team’s work as well as joining calls to share best practices and process improvement ideas - Communicate effectively and efficiently with your team and other stakeholders to provide updates on project progress, address roadblocks, and celebrate wins - Assist senior members of the Data Operations department on the execution of strategic initiatives and achieving operational goals - Support the vision and values of the company by setting an example and demonstrating desired behaviors - Participate in various company initiatives and projects as requested We need to keep each as
after benefits list, but it's not a benefit; it's a note. Should we include? It's substantive info about benefits. We'll include as a
after the list. Pay: "Compensation This position is non-exempt and paid a salary of $72,000-$72,000Target annual bonus percentage: 7.5%". There's a missing space; we can parse as salary $72,000-$72,000 (same) and target annual bonus percentage: 7.5%. We'll put in
. Schedule: "Working Conditions ... This role is expected to be in the office 5 days a week." Also "Limited corporate travel may be required". We'll put schedule as
maybe with both. We must not include heading for Working Conditions if we only have schedule; but we can put Schedule heading with that info. We must not repeat job title. No markdown. Now produce HTML fragment:
About the role
...
Responsibilities
- ... ...
Skills and Qualifications
-
...
Benefits
-
...
Please be aware the above PitchBook benefit and perk offerings are subject to corresponding plan and policy documents and may change during the course of your employment.
Pay
This position is non-exempt and paid a salary of $72,000-$72,000. Target annual bonus percentage: 7.5%.
Schedule
This role is expected to be in the office 5 days a week. Limited corporate travel may be required to remote offices or other business meetings and events.
Check for any duplicate content: Ensure we didn't miss any responsibilities like "Become proficient in one of PitchBook’s core data areas of operation, including: private equity, venture capital, M&A, or Institutional Investors". Good. Check that we didn't include any boilerplate like "We are excited to get to know you..." etc. That's after Working Conditions; we should remove that as it's application instructions/boilerplate. Also "Concerned that you might not meet every requirement? We encourage you to still apply..." remove. Also "At the heart of our company is a belief in the power of in-person collaboration..." we used part of it for schedule; but we should not include the preceding fluff about hallway conversations etc. We only need the schedule specifics. We extracted "This role is expected to be in the office 5 days a week." and "Limited corporate travel may be required to remote offices or other business meetings and events." That's from the Working Conditions paragraph. Good. Now ensure we didn't include any fluff like "The job conditions for this position are in a standard office setting. Employees in this position use PC and phone on an on-going basis throughout the day." That's also part of Working Conditions but maybe we could include as schedule? It's not schedule but work environment. The instruction says include Schedule section only if posting actually states them. It does state schedule (5 days a week). The other details about standard office setting, PC/phone, limited travel are also part of Working Conditions but not schedule. Should we include them? The instruction: "Prefer a few substantive sections over many thin ones." We could incorporate those details into Schedule section as additional info, but they are not schedule. Could create a "Working Conditions" section but not requested headings list includes Schedule, Benefits, Pay, etc. The allowed headings are: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. They didn't list Working Conditions. So we should not create a Working Conditions heading. We could fold those details into Schedule section as extra context, but that might be mixing. However the instruction: "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". It doesn't forbid adding extra info under Schedule as long as it's relevant. The schedule is about office days; the other details about standard office setting, PC/phone, limited travel are also about working conditions but not schedule. Might be okay to include them under Schedule as they are part of Working Conditions but we lack a heading for it. Could we instead put them under About the role? No. Better to include them under Schedule as additional details, but we should not misrepresent. Perhaps we can create a Schedule section with the schedule info and then a separate paragraph about work environment under Schedule? Might be okay. Alternatively we could omit those details to keep only schedule. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we must preserve all substantive information, including the standard office setting, PC/phone, limited travel. If we omit them, we lose info. So we need to include them somewhere. Since there is no explicit heading for Working Conditions, we could incorporate them into the Schedule section as additional context, but that might be considered stray. However the instruction says "Prefer a few substantive sections over many thin ones." So we could combine schedule and work environment under Schedule heading. That seems acceptable. Thus Schedule section will contain: "This role is expected to be in the office 5 days a week. Limited corporate travel may be required to remote offices or other business meetings and events. The job conditions for this position are in a standard office setting. Employees in this position use PC and phone on an ongoing basis throughout the day." We need to ensure we keep the exact phrasing? We can paraphrase slightly but must preserve meaning. Better to keep as close as possible. Let's copy sentences: - "This role is expected to be in the office 5 days a week." - "Limited corporate travel may be required to remote offices or other business meetings and events." - "The job conditions for this position are in a standard office setting." - "Employees in this position use PC and phone on an on-going basis throughout the day." We'll combine into a paragraph. Now check for any other substantive info: The "About The Role" paragraph includes mention of specialized training and mentorship program tailored to Data Operations team. That's included. Now ensure we didn't include any