Consultant
for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to include sections only when posting has real specific content. Let's parse content.
We have:
- Intro about Veeva (mission-driven, etc.) Could be "About the role"? Actually that's about company. Could be "About the role" or maybe "About Veeva". The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can use "About the role" for the introductory paragraph describing the role and company.
- Responsibilities: The "What You'll Do" bullet list.
- Requirements: The "Requirements" bullet list.
- Nice to Have: Could be "Qualifications" or "Skills"? The Nice to Have could go under "Qualifications" or "Skills". We have "Nice to Have Experience in clinical data software..." etc. Could be placed under "Qualifications" or "Skills". Since we have separate "Skills" heading possible. But we need to avoid thin sections. We could combine Nice to Have into "Qualifications" or "Skills". Let's decide: Use "Qualifications" for required qualifications (the Requirements list). Use "Skills" for nice-to-have? Or maybe "Skills" for both required and nice? The instruction says we can use those headings; we need to include section only when posting has real specific content. We have content for Requirements (required). We have Nice to Have content. We could put that under "Qualifications" as additional qualifications, or under "Skills". Let's put under "Qualifications" both required and nice? But we already have a Requirements section; maybe we rename that to "Requirements". Then we can have a "Qualifications" section for nice-to-have. Or we could have "Skills" for nice-to-have. Let's do: Requirements (required), Qualifications (nice-to-have). Skills maybe not needed if we already covered. But we could also include "Skills" for communication etc. However the required list includes communication and problem-solving skills, attention to detail. Those are skills. But they are already in Requirements. So we could skip Skills section to avoid thin.
Benefits: The posting lists "Perks & Benefits" with items: Medical, dental, vision, and basic life insurance; Flexible PTO and company paid holidays; Retirement programs; 1% charitable giving program. That's specific content, so we can include Benefits section.
Pay: The posting includes "Compensation Base pay: $70,000 - $140,000". That's specific, so we include Pay section.
Schedule: The posting includes "Days and hours of work are generally Monday through Friday, 9:00 AM to 5:00 PM, however hours are dependent on customer needs and deliverables." That's specific, so we include Schedule section.
We must not include boilerplate like EEO, accommodation, etc. Remove those.
We must not repeat job title as heading. The job title is Project Management Consultant. We should not put that as heading.
We must not include Job ID/requisition numbers.
We must preserve all substantive information; do not invent or summarize away detail.
We need to output only HTML fragment, no /, no markdown fences.
We'll structure:
About the role
... (intro paragraph about Veeva and role)
Responsibilities
- ... ...
Requirements
- ... ...
Qualifications
- ... ...
Benefits
- ... ...
Pay
Base pay: $70,000 - $140,000
Schedule
Days and hours of work are generally Monday through Friday, 9:00 AM to 5:00 PM, however hours are dependent on customer needs and deliverables.
We need to ensure we preserve all substantive information from the posting. Let's extract the intro paragraph: "Veeva Systems is a mission-driven organization and pioneer in industry cloud, helping life sciences companies bring therapies to patients faster. As one of the fastest-growing SaaS companies in history, we surpassed $3B in revenue in our last fiscal year with extensive growth potential ahead. At the heart of Veeva are our values: Do the Right Thing, Customer Success, Employee Success, and Speed. We're not just any public company – we made history in 2021 by becoming a public benefit corporation (PBC), legally bound to balancing the interests of customers, employees, society, and investors. As a Work Anywhere company, we support your flexibility to work from home or in the office, so you can thrive in your ideal environment. Join us in transforming the life sciences industry, committed to making a positive impact on its customers, employees, and communities. The Role Veeva Systems, a leader in cloud-based solutions for the global life sciences industry, is looking for a Project Management Consultant to join our Clinical Data Professional Services team. Veeva’s Clinical Data Suite includes EDC (Electronic Data Capture), Coder, DQS (Data Quality System), and other applications. The Project Management Consultant will be responsible for managing project teams who implement Veeva Clinical Data Software with focus on maintaining timelines, budgets, deliverables, and overseeing customer adoption. This role requires attention to detail, communication, organization, problem-solving and software implementation skills." We need to keep that as prose in. Possibly split into multiple paragraphs? The instruction says use
for prose. Could be one paragraph but it's long; still okay. Now Responsibilities: The "What You'll Do" bullet list: - Work closely with cross-functional team members and customers to understand Clinical Data requirements - Develop timelines according to deliverables in contracted statements of work - Maintain project timelines, deliverables, and budgets using project management tools such as Jira, Smartsheet, etc. - Manage project teams, resource allocation, and cross-functional workstreams to ensure alignment across organizations - Identify technical and operational risks and develop and track mitigation strategies - Deliver regular progress reports and executive summaries regarding milestone completion and potential blockers - Oversee third-party software vendors, and integration partners - Coordinate with common teams within life science organizations such as Data Management (DM), IT, Programmers, Statisticians, Quality Assurance (QA), etc. on software implementation lifecycles (requirements gathering, development, user acceptance testing, etc.) - Collaborate with cross-functional teams to develop end-user training and change management materials - Oversee the transition from deployment to operational, post-implementation support We need to keep each as
containing: "Base pay: $70,000 - $140,000. This position may also be eligible for other types of compensation in addition to base salary, such as variable bonus and/or stock bonus." Also note about compensation based on qualifications etc. That is also substantive. So we could include: "We look at compensation for each individual and base our offer on your unique qualifications, experience, and expected contributions." That's also substantive. So we can combine. Thus Pay section
with all that. Now also the line: "The salary range listed here has been provided to comply with local regulations and represents a potential base salary range for this role. Please note that actual salaries may vary within the range above or below, depending on experience and location." That's also substantive about salary range. So include. Thus Pay section will have multiple sentences. Now also the line: "As a Work Anywhere company, we support your flexibility to work from home or in the office, so you can thrive in your ideal environment." Already in About the role. Now also the line: "Veeva’s headquarters is located in the San Francisco Bay Area with offices in more than 15 countries around the world." Include in About the role. Now also the line: "Veeva Systems is a mission-driven organization and pioneer in industry cloud, helping life sciences companies bring therapies to patients faster." etc. Now also the line: "As one of the fastest-growing SaaS companies in history, we surpassed $3B in revenue in our last fiscal year with extensive growth potential ahead." Include. Now also the line: "At the heart of Veeva are our values: Do the Right Thing, Customer Success, Employee Success, and Speed." Include. Now also the line: "We're not just any public company – we made history in 2021 by becoming a public benefit corporation (PBC), legally bound to balancing the interests of customers, employees, society, and investors." Include. Now also the line: "Join us in transforming the life sciences industry, committed to making a positive impact on its customers, employees, and communities." Include. Now also the line: "The Role Veeva Systems, a leader in cloud-based solutions for the global life sciences industry, is looking for a Project Management Consultant to join our Clinical Data