Veeva Clinical Analyst
for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. Must preserve all substantive info, not invent or summarize away detail. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Also remove "The application window is anticipated to close..." etc. Also remove AI tools paragraph? That's maybe not boilerplate but it's about recruitment process; maybe considered boilerplate? It's not EEO but still about hiring process. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The AI tools paragraph is not exactly those categories, but could be considered part of recruitment process; but not explicitly prohibited. However it's not substantive about the job; it's about hiring process. Might be considered boilerplate? Safer to remove it as it's not essential job description. Also remove the equal opportunity statement at end. Also remove "We are committed to providing you with the tools..." etc. Also remove "ImmunityBio employees are as valuable..." etc. Also remove "We are committed to equal employment opportunity..." etc. Also remove "The application window is anticipated to close..." etc. Also remove "ImmunityBio uses artificial intelligence (AI) tools..." paragraph. Also remove "Important: AI is not used..." etc. Also remove "We are committed to equal employment opportunity..." etc. Also remove final EEO statement.
We need to keep company overview, why ImmunityBio? Opportunity to join... etc. That's substantive about company and role. Should we include as About the role? Possibly "About the role" heading could contain company overview and why ImmunityBio? The instructions: Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to include only those with real content.
Let's parse the posting:
Company Overview: description of ImmunityBio.
Why ImmunityBio? bullet points: Opportunity to join a publicly traded biopharmaceutical company with headquarters in Southern California. Work with a collaborative team with the ability to work across different areas of the company. Ability to join a growing company with professional development opportunities.
Position Summary: Veeva Clinical Vault Systems Analyst provides foundational technical and operational support for ImmunityBio’s cloud-based Veeva Clinical Vault applications. Working under manager guidance, this role assists in basic system configuration, user access management, and routine troubleshooting. This is an excellent opportunity for someone with a baseline understanding of life sciences software to develop specialized skills in a highly regulated GxP environment.
Essential Functions: list of duties (bulleted). Those are responsibilities.
Education & Experience: Bachelor’s degree ... required. 2+ years experience ... required. Prior exposure ... highly preferred.
Knowledge, Skills, & Abilities: list.
Working Environment / Physical Environment: This position works on site based in Dunkirk, NY. Regular work schedule is Monday – Friday, within standard business hours. Flexibility is available with manager approval. Must possess mobility to work in a standard office setting and to use standard office equipment, including a computer. Lift and carry materials weighing up to 20 pounds.
Pay: This position is eligible for a discretionary bonus and equity award. The hourly base pay range for this position is below. The specific rate will depend on the successful candidate’s qualifications, prior experience as well as geographic location. $42.20 (entry-level qualifications) to $47.12 (highly experienced) per hour.
Benefits: list of benefits.
Schedule: Already covered in Working Environment: Monday-Friday standard business hours, flexibility.
We need to avoid placeholder text like "commensurate with experience", "not specified", etc. The pay range is specific, so we can include Pay section. Benefits are specific, include Benefits section. Schedule: we have specific schedule (Monday-Friday, standard business hours, flexibility). So include Schedule section.
Now we need to decide which headings to use: About the role (could include company overview, why ImmunityBio, position summary). Responsibilities (essential functions). Requirements (education & experience). Qualifications (maybe knowledge, skills & abilities). Skills (maybe overlapping). But we should not create thin sections. Prefer few substantive sections over many thin ones. So we could combine some.
We have: About the role (company overview, why ImmunityBio, position summary). Responsibilities (essential functions). Requirements (education & experience). Qualifications (knowledge, skills & abilities). Benefits. Pay. Schedule.
That's 7 sections. Could we combine Qualifications and Skills? The instruction list includes Skills as a possible heading. But we have knowledge, skills, & abilities; we could put that under Skills heading. Qualifications could be education & experience. That seems fine.
Thus sections: About the role, Responsibilities, Requirements (Education & Experience), Skills (Knowledge, Skills, & Abilities), Benefits, Pay, Schedule.
We must not include headings with filler. All have content.
Now we need to output HTML fragment only, no /. Use for each heading. 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 must keep details exactly as given, but we can format into lists and paragraphs.
We must not repeat job title as heading. The job title is Veeva Clinical Vault Systems Analyst. Not to be used as heading.
We must not put Job ID/requisition numbers as headings; none present.
We must remove boilerplate: we already removed many.
Now let's extract content.
Company Overview paragraph:
"ImmunityBio is a vertically integrated commercial stage biotechnology company developing next-generation therapies that bolster the natural immune system to defeat cancers and infectious diseases. The Company’s range of immunotherapy and cell therapy platforms, alone and together, act to drive and sustain an immune response with the goal of creating durable and safe protection against disease. Designated an FDA Breakthrough Therapy, ANKTIVA is the first FDA-approved immunotherapy for non-muscle invasive bladder cancer CIS that activates NK cells, T cells, and memory T cells for a long-duration response. The Company is applying its science and platforms to treating cancers, including the development of potential cancer vaccines, as well as developing immunotherapies and cell therapies that we believe sharply reduce or eliminate the need for standard high-dose chemotherapy. These platforms and their associated product candidates are designed to be more effective, accessible, and easily administered than current standards of care in oncology and infectious diseases."
Why ImmunityBio? bullet points (converted to prose or list). The text: "Opportunity to join a publicly traded biopharmaceutical company with headquarters in Southern California. Work with a collaborative team with the ability to work across different areas of the company. Ability to join a growing company with professional development opportunities."
We could keep as list.
Position Summary paragraph:
"Veeva Clinical Vault Systems Analyst provides foundational technical and operational support for ImmunityBio’s cloud-based Veeva Clinical Vault applications. Working under manager guidance, this role assists in basic system configuration, user access management, and routine troubleshooting. This is an excellent opportunity for someone with a baseline understanding of life sciences software to develop specialized skills in a highly regulated GxP environment."
Now Essential Functions list (bulleted). Let's capture each bullet:
- Manage day-to-day user administration, including provisioning user accounts, assigning security profiles, and managing permission sets across Clinical Vault applications.
- Assist in executing low-to-medium complexity system configurations, such as modifying picklists, updating document types, and adjusting basic lifecycle states or workflows.
- Create basic reports and Dashboards based upon user provided requirements.
- Monitor the access email inbox, acting as the first line of triage for end-user support. Diagnose access issues, clarify system behavior for users, and escalate complex technical bugs to senior team members or Veeva support.
- Assist in drafting documentation for Computer Software Validation (CSV). Participate in executing User Acceptance Testing (UAT) scripts and documenting results in strict accordance with GxP and 21 CFR Part 11 regulations.
- Support the review process for Veeva’s routine software updates. Assist in testing new platform features in sandbox environments before they are pushed to production.
- Maintain data integrity within the Vault by running routine reports, identifying data entry inconsistencies, and assisting with bulk data uploads or clean-up tasks.
- Create, edit and adhere to Standard Operating Procedures (SOPs), process improvements, and standardization of templates.
- Performs ad-hoc and cross-functional duties and/or projects as assigned to support business needs and provide developmental opportunities.
Note: last bullet starts with "Performs". Keep as is.
Now Education & Experience:
"Bachelor’s degree in Information Technology, Computer Science, Bio-Informatics, Life Sciences, or a related field is required.
2+ years of experience in an IT support, data coordination, or application management role is required.
Prior exposure to software systems used in clinical trials, pharmaceutical manufacturing, or regulatory affairs is highly preferred."
We can make list.
Knowledge, Skills, & Abilities list:
- Foundational knowledge or academic exposure to cloud systems.
- Direct experience using or configuring Veeva Vault applications (such as eTMF, CTMS, CDMS/EDC or RIM) is a major plus but not strictly mandatory if the candidate has strong technical aptitude.
- Understanding GxP validation meaning and a willingness to learn the rigorous documentation standards required in the life sciences industry.
- Familiarity with Excel (for data mapping).
- Hands-on working knowledge of basic configurations, Veeva security, document types and reports in any of the Veeva vaults.
- Understanding of DIA Reference model, Submissions structures, EDC development principles, Software Development Life Cycle.
- Good communication skills and ability to collaborate with all levels of an organization.
- Ability to adapt quickly, work independently and manage competing priorities.
- Strong attention to detail.
- Strong research & analysis skills, creative thinker who can focus on the details without losing sight of the big picture.
Now Working Environment / Physical Environment:
"This position works on site based in Dunkirk, NY.
Regular work schedule is Monday – Friday, within standard business hours. Flexibility is available with manager approval.
Must possess mobility to work in a standard office setting and to use standard office equipment, including a computer.
Lift and carry materials weighing up to 20 pounds"
We can make schedule section from the schedule sentences: Monday-Friday standard business hours, flexibility with manager approval.
Physical environment: maybe not needed as separate section; but we could include in Schedule? The instruction says use Schedule heading only if posting actually states them. It does state schedule. So we can put schedule details there. The physical environment details (mobility, lift) could be omitted? They are substantive but not schedule. Could be part of Requirements? Not really. Could be omitted? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we must keep that info somewhere. Where to put? Could be under Requirements? Not exactly. Could be under About the role? Not ideal. Could be under a new heading like "Working Environment" but not in allowed headings list. The allowed headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We could put physical environment under Requirements? Not really. Could put under About the role? Might be okay as part of role description. But we need to preserve it. Perhaps we can include a brief paragraph under About the role after position summary that includes work location and physical requirements. That seems acceptable.
Thus About the role section will contain company overview, why ImmunityBio, position summary, and work location/physical environment.
Now Benefits list:
"Our competitive total rewards benefits package, for eligible employees, include:
Medical, Dental and Vision Plan Options
Health and Financial Wellness Programs
Employer Assistance Program (EAP)
Company Paid and
for each heading. 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 must keep details exactly as given, but we can format into lists and paragraphs.
We must not repeat job title as heading. The job title is Veeva Clinical Vault Systems Analyst. Not to be used as heading.
We must not put Job ID/requisition numbers as headings; none present.
We must remove boilerplate: we already removed many.
Now let's extract content.
Company Overview paragraph:
"ImmunityBio is a vertically integrated commercial stage biotechnology company developing next-generation therapies that bolster the natural immune system to defeat cancers and infectious diseases. The Company’s range of immunotherapy and cell therapy platforms, alone and together, act to drive and sustain an immune response with the goal of creating durable and safe protection against disease. Designated an FDA Breakthrough Therapy, ANKTIVA is the first FDA-approved immunotherapy for non-muscle invasive bladder cancer CIS that activates NK cells, T cells, and memory T cells for a long-duration response. The Company is applying its science and platforms to treating cancers, including the development of potential cancer vaccines, as well as developing immunotherapies and cell therapies that we believe sharply reduce or eliminate the need for standard high-dose chemotherapy. These platforms and their associated product candidates are designed to be more effective, accessible, and easily administered than current standards of care in oncology and infectious diseases."
Why ImmunityBio? bullet points (converted to prose or list). The text: "Opportunity to join a publicly traded biopharmaceutical company with headquarters in Southern California. Work with a collaborative team with the ability to work across different areas of the company. Ability to join a growing company with professional development opportunities."
We could keep as list.
Position Summary paragraph:
"Veeva Clinical Vault Systems Analyst provides foundational technical and operational support for ImmunityBio’s cloud-based Veeva Clinical Vault applications. Working under manager guidance, this role assists in basic system configuration, user access management, and routine troubleshooting. This is an excellent opportunity for someone with a baseline understanding of life sciences software to develop specialized skills in a highly regulated GxP environment."
Now Essential Functions list (bulleted). Let's capture each bullet:
- Manage day-to-day user administration, including provisioning user accounts, assigning security profiles, and managing permission sets across Clinical Vault applications.
- Assist in executing low-to-medium complexity system configurations, such as modifying picklists, updating document types, and adjusting basic lifecycle states or workflows.
- Create basic reports and Dashboards based upon user provided requirements.
- Monitor the access email inbox, acting as the first line of triage for end-user support. Diagnose access issues, clarify system behavior for users, and escalate complex technical bugs to senior team members or Veeva support.
- Assist in drafting documentation for Computer Software Validation (CSV). Participate in executing User Acceptance Testing (UAT) scripts and documenting results in strict accordance with GxP and 21 CFR Part 11 regulations.
- Support the review process for Veeva’s routine software updates. Assist in testing new platform features in sandbox environments before they are pushed to production.
- Maintain data integrity within the Vault by running routine reports, identifying data entry inconsistencies, and assisting with bulk data uploads or clean-up tasks.
- Create, edit and adhere to Standard Operating Procedures (SOPs), process improvements, and standardization of templates.
- Performs ad-hoc and cross-functional duties and/or projects as assigned to support business needs and provide developmental opportunities.
Note: last bullet starts with "Performs". Keep as is.
Now Education & Experience:
"Bachelor’s degree in Information Technology, Computer Science, Bio-Informatics, Life Sciences, or a related field is required.
2+ years of experience in an IT support, data coordination, or application management role is required.
Prior exposure to software systems used in clinical trials, pharmaceutical manufacturing, or regulatory affairs is highly preferred."
We can make list.
Knowledge, Skills, & Abilities list:
- Foundational knowledge or academic exposure to cloud systems.
- Direct experience using or configuring Veeva Vault applications (such as eTMF, CTMS, CDMS/EDC or RIM) is a major plus but not strictly mandatory if the candidate has strong technical aptitude.
- Understanding GxP validation meaning and a willingness to learn the rigorous documentation standards required in the life sciences industry.
- Familiarity with Excel (for data mapping).
- Hands-on working knowledge of basic configurations, Veeva security, document types and reports in any of the Veeva vaults.
- Understanding of DIA Reference model, Submissions structures, EDC development principles, Software Development Life Cycle.
- Good communication skills and ability to collaborate with all levels of an organization.
- Ability to adapt quickly, work independently and manage competing priorities.
- Strong attention to detail.
- Strong research & analysis skills, creative thinker who can focus on the details without losing sight of the big picture.
Now Working Environment / Physical Environment:
"This position works on site based in Dunkirk, NY.
Regular work schedule is Monday – Friday, within standard business hours. Flexibility is available with manager approval.
Must possess mobility to work in a standard office setting and to use standard office equipment, including a computer.
Lift and carry materials weighing up to 20 pounds"
We can make schedule section from the schedule sentences: Monday-Friday standard business hours, flexibility with manager approval.
Physical environment: maybe not needed as separate section; but we could include in Schedule? The instruction says use Schedule heading only if posting actually states them. It does state schedule. So we can put schedule details there. The physical environment details (mobility, lift) could be omitted? They are substantive but not schedule. Could be part of Requirements? Not really. Could be omitted? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we must keep that info somewhere. Where to put? Could be under Requirements? Not exactly. Could be under About the role? Not ideal. Could be under a new heading like "Working Environment" but not in allowed headings list. The allowed headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We could put physical environment under Requirements? Not really. Could put under About the role? Might be okay as part of role description. But we need to preserve it. Perhaps we can include a brief paragraph under About the role after position summary that includes work location and physical requirements. That seems acceptable.
Thus About the role section will contain company overview, why ImmunityBio, position summary, and work location/physical environment.
Now Benefits list:
"Our competitive total rewards benefits package, for eligible employees, include:
Medical, Dental and Vision Plan Options
Health and Financial Wellness Programs
Employer Assistance Program (EAP)
Company Paid and
for prose. We need to preserve all substantive information; do not invent or summarize away detail. So we must keep details exactly as given, but we can format into lists and paragraphs. We must not repeat job title as heading. The job title is Veeva Clinical Vault Systems Analyst. Not to be used as heading. We must not put Job ID/requisition numbers as headings; none present. We must remove boilerplate: we already removed many. Now let's extract content. Company Overview paragraph: "ImmunityBio is a vertically integrated commercial stage biotechnology company developing next-generation therapies that bolster the natural immune system to defeat cancers and infectious diseases. The Company’s range of immunotherapy and cell therapy platforms, alone and together, act to drive and sustain an immune response with the goal of creating durable and safe protection against disease. Designated an FDA Breakthrough Therapy, ANKTIVA is the first FDA-approved immunotherapy for non-muscle invasive bladder cancer CIS that activates NK cells, T cells, and memory T cells for a long-duration response. The Company is applying its science and platforms to treating cancers, including the development of potential cancer vaccines, as well as developing immunotherapies and cell therapies that we believe sharply reduce or eliminate the need for standard high-dose chemotherapy. These platforms and their associated product candidates are designed to be more effective, accessible, and easily administered than current standards of care in oncology and infectious diseases." Why ImmunityBio? bullet points (converted to prose or list). The text: "Opportunity to join a publicly traded biopharmaceutical company with headquarters in Southern California. Work with a collaborative team with the ability to work across different areas of the company. Ability to join a growing company with professional development opportunities." We could keep as list. Position Summary paragraph: "Veeva Clinical Vault Systems Analyst provides foundational technical and operational support for ImmunityBio’s cloud-based Veeva Clinical Vault applications. Working under manager guidance, this role assists in basic system configuration, user access management, and routine troubleshooting. This is an excellent opportunity for someone with a baseline understanding of life sciences software to develop specialized skills in a highly regulated GxP environment." Now Essential Functions list (bulleted). Let's capture each bullet: - Manage day-to-day user administration, including provisioning user accounts, assigning security profiles, and managing permission sets across Clinical Vault applications. - Assist in executing low-to-medium complexity system configurations, such as modifying picklists, updating document types, and adjusting basic lifecycle states or workflows. - Create basic reports and Dashboards based upon user provided requirements. - Monitor the access email inbox, acting as the first line of triage for end-user support. Diagnose access issues, clarify system behavior for users, and escalate complex technical bugs to senior team members or Veeva support. - Assist in drafting documentation for Computer Software Validation (CSV). Participate in executing User Acceptance Testing (UAT) scripts and documenting results in strict accordance with GxP and 21 CFR Part 11 regulations. - Support the review process for Veeva’s routine software updates. Assist in testing new platform features in sandbox environments before they are pushed to production. - Maintain data integrity within the Vault by running routine reports, identifying data entry inconsistencies, and assisting with bulk data uploads or clean-up tasks. - Create, edit and adhere to Standard Operating Procedures (SOPs), process improvements, and standardization of templates. - Performs ad-hoc and cross-functional duties and/or projects as assigned to support business needs and provide developmental opportunities. Note: last bullet starts with "Performs". Keep as is. Now Education & Experience: "Bachelor’s degree in Information Technology, Computer Science, Bio-Informatics, Life Sciences, or a related field is required. 2+ years of experience in an IT support, data coordination, or application management role is required. Prior exposure to software systems used in clinical trials, pharmaceutical manufacturing, or regulatory affairs is highly preferred." We can make list. Knowledge, Skills, & Abilities list: - Foundational knowledge or academic exposure to cloud systems. - Direct experience using or configuring Veeva Vault applications (such as eTMF, CTMS, CDMS/EDC or RIM) is a major plus but not strictly mandatory if the candidate has strong technical aptitude. - Understanding GxP validation meaning and a willingness to learn the rigorous documentation standards required in the life sciences industry. - Familiarity with Excel (for data mapping). - Hands-on working knowledge of basic configurations, Veeva security, document types and reports in any of the Veeva vaults. - Understanding of DIA Reference model, Submissions structures, EDC development principles, Software Development Life Cycle. - Good communication skills and ability to collaborate with all levels of an organization. - Ability to adapt quickly, work independently and manage competing priorities. - Strong attention to detail. - Strong research & analysis skills, creative thinker who can focus on the details without losing sight of the big picture. Now Working Environment / Physical Environment: "This position works on site based in Dunkirk, NY. Regular work schedule is Monday – Friday, within standard business hours. Flexibility is available with manager approval. Must possess mobility to work in a standard office setting and to use standard office equipment, including a computer. Lift and carry materials weighing up to 20 pounds" We can make schedule section from the schedule sentences: Monday-Friday standard business hours, flexibility with manager approval. Physical environment: maybe not needed as separate section; but we could include in Schedule? The instruction says use Schedule heading only if posting actually states them. It does state schedule. So we can put schedule details there. The physical environment details (mobility, lift) could be omitted? They are substantive but not schedule. Could be part of Requirements? Not really. Could be omitted? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we must keep that info somewhere. Where to put? Could be under Requirements? Not exactly. Could be under About the role? Not ideal. Could be under a new heading like "Working Environment" but not in allowed headings list. The allowed headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We could put physical environment under Requirements? Not really. Could put under About the role? Might be okay as part of role description. But we need to preserve it. Perhaps we can include a brief paragraph under About the role after position summary that includes work location and physical requirements. That seems acceptable. Thus About the role section will contain company overview, why ImmunityBio, position summary, and work location/physical environment. Now Benefits list: "Our competitive total rewards benefits package, for eligible employees, include: Medical, Dental and Vision Plan Options Health and Financial Wellness Programs Employer Assistance Program (EAP) Company Paid and