Business Analyst
for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to map content accordingly.
We have:
- About the role: description of Business Analyst responsibilities? Actually "About The Role" section includes description: "The Business Analyst will be responsible for gathering and analysing business and system requirements across the organisation . The Business Analyst will translate these into U se C ases that adequately communicate the requirements for the internal team to deliver against. At certain times, the Business Analyst may be required to evaluate technical solutions from an a nalysis and non-functional requirements perspective. This position will work in cross functional teams, be a driver of an Agile way of working and contribute to our operational offerings, managing projects from inception through to delivery ."
We can put that under About the role
with
. - Responsibilities: "What You'll Do" list bullet points. Use
- .
- Requirements: "About You" list of qualifications/skills. Could be under Requirements or Qualifications? The instructions: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Skills). We need to decide which sections to include based on content. We have content for About the role, Responsibilities, Requirements (maybe "About You" includes qualifications/skills), Benefits, Pay. No explicit Schedule info (though flexible working arrangements mentioned). Could we treat flexible working as Schedule? The posting says "Enjoy flexible working arrangements, including hybrid and remote work, along with the option to work from anywhere across the globe two weeks each year." That's schedule info. So we can create a Schedule section.
We also have Qualifications maybe overlapping with Requirements. But we can combine: maybe Requirements = "About You" bullet list (skills, experience). Qualifications maybe not needed separate. But we need to avoid empty sections. We'll include only sections with real content: About the role, Responsibilities, Requirements (or Qualifications?), Benefits, Pay, Schedule. Could also include Skills as separate if we want to split but not needed.
We must not invent or summarize away detail. Preserve all substantive information. So we need to include all bullet points from "What You'll Do" and "About You". Also include benefits details: 401K plan with employer match up to 4%, life insurance, disability coverage, medical dental vision, flexible working arrangements, hybrid/remote, option to work from anywhere across globe two weeks each year, 20 vacation days + one personal well-being day, 9 public holidays, gifted end-of-year holidays, early Summer Friday finish in June, July, August, free counselling via EAP, personalized health support, enhanced maternity/paternity/family leave and fertility policies, continuous opportunities to professionally develop with on-demand training, support, global mobility.
Also mention flexible approach to working earlier in company description but that's not part of benefits? Could include but it's already in benefits.
We must not include boilerplate like EEO, privacy notice, AI tools, etc. Remove those.
We must not include duplicated lines.
We must not include job ID/requisition numbers.
We must not include navigation/cookie/legal.
We must not include application instructions.
We must not include the "We encourage all applicants to read our candidate privacy notice..." etc. That's boilerplate; remove.
We must not include "We may use AI tools..." etc. Remove.
We must not include "Final hiring decisions are ultimately made by humans." Remove.
We must not include "If you would like more information about how your data is processed..." Remove.
We must not include "We are an accredited Fertility Friendly employer..." Actually that is part of company description earlier; but it's substantive about benefits? It's part of Avalere Health description. Should we keep? It's about company culture/benefits (fertility policy). It's substantive; we can keep it in About Avalere Health? But we are not to include a section for company description unless we have a heading? The instructions only list specific headings; we could include a brief paragraph under About the role? No, that's not appropriate. The company description is not required to be included? The instruction says "Preserve ALL substantive information; do NOT invent or summarize away detail." So we need to keep that info somewhere. However we are only allowed to output HTML fragment with headings from the list. We could put the company description in a
before any heading? The instructions: "Output ONLY the HTML fragment — no /, no markdown code fences." It didn't forbid extra paragraphs outside headings. It said use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use
- for any list of duties/requirements/benefits, and
for prose. So we can have prose paragraphs not under a heading? Probably okay but better to put them under a relevant heading. There's no heading for company overview; but we could treat the initial "About Avalere Health" as a prose paragraph before the headings. That's acceptable. Thus output:
About Avalere Health United by one profound purpose: to reach EVERY PATIENT POSSIBLE. ... (the whole company description up to "We are deeply invested in supporting professional growth for our employees through day-to-day career experiences, access to thousands of on-demand training sessions, regular career conversations, and the opportunity for global, cross-capability career moves. We take pride in being part of the Disability Confident Scheme. This helps make sure you can be interviewed fairly if you have a disability, long term health condition, or are neurodiverse. If you'd like to apply and need adjustments made, you can let us know in your application.")
ThenAbout the role
...
ThenResponsibilities
- list each bullet from "What You'll Do". Need to preserve each bullet exactly.
Bullet list:
- Perform business and systems analysis across multiple systems
- Requirements gathering and documentation for multiple systems
- Communicate and collaborate with internal and external stakeholders
- Facilitate requirements workshops with internal stakeholders
- Assist with user acceptance testing (UAT) as and when required
- Ensure that requirements are briefed in and fully understood by internal and external employees
- Take part in internal and client calls as and when required
- Assist in developing training material across multiple IT systems
- Perform system and data modelling using UML as and when required
- Take a Domain Driven Design (DDD) approach when gathering and documenting web based solutions requirements
- Design and document use cases as and when required
Make sure to keep punctuation.
Then
- . Some have trailing semicolons or periods; keep as is.
Then
Benefits
- list benefits.
Benefits list:
- 401K plan with an employer match contribution up to 4% (immediately vested)
- life insurance
- disability coverage
- medical, dental, and vision plans
- flexible working arrangements? Actually "medical, dental, and vision plans for peace of mind." We'll keep as "medical, dental, and vision plans"
- flexible working arrangements, including hybrid and remote work
- option to work from anywhere across the globe two weeks each year
- 20 vacation days plus one personal well-being day
- recognise 9 public holidays
- gifted end-of-year holidays
- early Summer Friday finish in June, July, and August
- access free counselling through our employee assistance program
- personalized health support
- enhanced maternity, paternity, family leave, and fertility policies
- continuous opportunities to professionally develop with on-demand training, support, and global mobility opportunities across the business
We might also include "We provide 20 vacation days plus one personal well-being day, recognise 9 public holidays, along with gifted end-of-year holidays and an early Summer Friday finish in June, July, and August." Already captured.
Also "Access free counselling through our employee assistance program and personalized health support." Already.
Also "Our enhanced maternity, paternity, family leave, and fertility policies provide support across every stage of your family-planning journey." Already.
Also "You can also benefit from continuous opportunities to professionally develop with on-demand training, support, and global mobility opportunities across the business." Already.
Also maybe "We encourage all applicants to read our candidate privacy notice before applying to Avalere Health." That's boilerplate; remove.
Also "We may use AI tools..." remove.
Also "Final hiring decisions are ultimately made by humans." remove.
Also "If you would like more information about how your data is processed, please review our candidate privacy policy." remove.
Now Pay:
Pay
$85,000 - $105,000 a year
Schedule:Schedule
Flexible working arrangements, including hybrid and remote work, with the option to work from anywhere across the globe two weeks each year.
But we already mentioned flexible working in benefits; but schedule section can capture that. However we must not duplicate content? The instruction says preserve ALL substantive information; duplication is okay if it's in original? But we should avoid repeating same info unnecessarily? It says "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." Duplicated lines refers to duplicated lines in the posting; we should not duplicate lines that appear multiple times in the posting. The flexible working appears both in company description and benefits; but it's not duplicated exactly same line? It appears in benefits as "Enjoy flexible working arrangements, including hybrid and remote work, along with the option to work from anywhere across the globe two weeks each year." Also earlier in company description: "Our flexible approach to working allows our global teams to decide where they want to work, whether in-office or at home based on team and client need." That's similar but not identical. It's okay to keep both; but we might just keep one. To avoid duplication, we could keep the flexible working description under Benefits and not repeat in Schedule. However Schedule section expects schedule info; we could put something like "Flexible working arrangements, including hybrid and remote work." But that duplicates
Requirements
(or Qualifications?). The "About You" list includes many items. We'll treat as Requirements. List: - User stories, wire framing, story boarding, UML and walkthroughs; - You must be a self-starter, a quick learner and be able to work in a fast paced, purposely unstructured environment whilst retaining a high level of integrity. - Solid understanding of Agile / Scrum and Waterfall methodologies; - Experience of working at enterprise level with system application design and development; - Must have excellent communication skills - Be proactive in the design and development of solutions - Has the ability to work as part of a team - Enthusiastic about the latest trends in technology - Has the ability to see the bigger picture - Exudes a level of professionalism at all times - Mentoring skills - Assertive – will defend their point of view if they believe it is correct - Has high standards and expects a high level of performance from others - Ability to work in matrix organisation environment assist in adding structure - Self-Driven - Ability to work well on own or within a small team environment - Good Interpersonal skills. - Problem solving skills - Friendly and approachable personality - Good planning and organisational skills - Happy to take ownership of the solution being developed We need to keep each as - . Some have trailing semicolons or periods; keep as is.
Then
- for any list of duties/requirements/benefits, and