Graduate Data Consultant

We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Must not repeat job title. Must not include Job ID etc. Must preserve all substantive info. Remove boilerplate like cookie/navigation/legal/EEO etc. The posting includes sections: "Why Grayce?" (intro), "About Our Opportunities", "Skills", "What You’ll Be Doing", "What Makes a Great Grayce Consultant", "Technical Skills (Advantageous)", "Why Work for Us" with subpoints: Locations, Opportunity, Delivery, Mentoring, Progression, Wellbeing Support, Salary, Our Approach to AI, Requirements. We need to map to headings: About the role (maybe intro about role), Responsibilities (What You'll Be Doing), Requirements (Requirements), Qualifications (maybe education requirement), Skills (Skills and Technical Skills), Benefits (Why Work for Us subpoints like Opportunity, Delivery, Mentoring, Progression, Wellbeing Support, maybe Locations?), Pay (Salary), Schedule (maybe ability to work on site 5 days a week). Also maybe "Locations" could be part of Benefits? But we should only include sections with real specific content. We must not include filler like "commensurate with experience". We have specific content: Salary: "Our salaries are dictated by location and client Significant annual salary increases". That's specific enough? It mentions dictated by location and client, and significant annual salary increases. That's specific enough to include Pay section. Schedule: "Ability to work on site 5 days a week." That's specific. Benefits: we have "Opportunity Gain hands-on experience working full-time, on-site with leading organisations, supported by structured training and industry-aligned development." "Delivery Work directly with a client, delivering high-quality outcomes in a professional, client-facing environment." "Mentoring Receive dedicated coaching and support throughout your placement and development journey." "Progression Complete a minimum of six industry-recognised accreditations, with clear pathways for career progression and salary growth." "Wellbeing Support Access our Employee Assistance Programme, offering 24/7 confidential support across financial, legal, health, and wellbeing areas." Also "Locations Locations are updated regularly based on client demand, with opportunities currently available across the UK. Greater geographical flexibility gives you access to a broader range of client projects." That could be part of Benefits or separate but we can include under Benefits. Qualifications: maybe "Minimum 2:1 or above in a STEM (Science, Technology, Engineering, and Math) subject" and "Right to work in the UK unsponsored for the duration of the programme." Those are requirements but could be qualifications. We'll put them under Qualifications. Requirements: maybe "Ability to work on site 5 days a week." but that's schedule. Actually Requirements could be things like "Minimum 2:1 or above in a STEM subject", "Right to work in the UK unsponsored". But we already used those for Qualifications. Let's think: The posting has a "Requirements" section at the end: Minimum 2:1 or above in a STEM subject; Ability to work on site 5 days a week; Right to work in the UK unsponsored. So we can put those under Requirements. Qualifications maybe not needed separately if we don't have distinct qualifications beyond requirements. But we could still have Qualifications for education? However the instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We should include sections only when posting has real specific content. We have content for About the role (intro about Grayce and opportunities), Responsibilities (What You'll Be Doing), Requirements (the list at end), Skills (Skills and Technical Skills), Benefits (Why Work for Us subpoints), Pay (Salary), Schedule (Ability to work on site 5 days a week). Qualifications maybe not needed separately because we don't have separate qualifications beyond requirements; but we could treat the education requirement as Qualifications. However the Requirements section already includes education. To avoid duplication, we could put education under Qualifications and other items under Requirements. But the posting lumps them together. We need to preserve all substantive info; we can split them as we like as long as we don't lose info. Let's assign: - About the role: intro paragraph about Grayce, Accelerated Development Programme, data-focused roles. - Responsibilities: "What You’ll Be Doing" bullet list. - Requirements: "Ability to work on site 5 days a week." and "Right to work in the UK unsponsored for the duration of the programme." - Qualifications: "Minimum 2:1 or above in a STEM (Science, Technology, Engineering, and Math) subject" - Skills: "Skills By joining our Data pathway..." plus "Technical Skills (Advantageous)" list. - Benefits: "Why Work for Us" subpoints: Locations, Opportunity, Delivery, Mentoring, Progression, Wellbeing Support. - Pay: "Our salaries are dictated by location and client Significant annual salary increases." - Schedule: maybe we already used ability to work on site 5 days a week under Requirements; but we could also put under Schedule. However we need to avoid duplication. The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. If we put it under Requirements, we still have it. Schedule section would be empty if we don't have other schedule info. We could omit Schedule section because we already placed that info under Requirements. But the instruction says include a section ONLY when the posting has real, specific content for it. If we put schedule info under Requirements, we still have schedule info present, but we didn't create a Schedule heading. That's okay; we are not required to have a Schedule heading. However the example list includes Schedule as a possible heading; we can omit if no distinct schedule content beyond what's already captured. But we have schedule info; we could create a Schedule section with that info and remove from Requirements to avoid duplication. Which is better? The posting has a "Requirements" section that includes ability to work on site 5 days a week. If we move that to Schedule, we still preserve info. But then Requirements would lose that item. We could keep Requirements with the other two items (right to work, education) and move schedule to Schedule. However education is more qualification. Let's decide: - Qualifications: Minimum 2:1 or above in STEM. - Requirements: Right to work in the UK unsponsored; Ability to work on site 5 days a week. - Schedule: maybe we could also include something else? Not needed. But we could still have Schedule with the same ability to work on site 5 days a week, but that would duplicate. Better to keep it under Requirements and not have Schedule section. Since the instruction says include a section ONLY when the posting has real, specific content for it — we have schedule content, but we already placed it under Requirements. That's still specific content; we didn't create a Schedule heading, but we still have the info. The instruction doesn't require we must have a Schedule heading if we have schedule info; it's just an example of possible headings. So we can omit Schedule. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay. Now we need to format:

for each heading. Use

• for any list of duties/requirements/benefits. Use

  for prose. We need to preserve all substantive information. Let's extract paragraphs. About the role: Combine "Why Grayce?" intro and "About Our Opportunities". Let's craft a paragraph(s). We'll keep as prose maybe multiple

  tags. Responsibilities: list from "What You’ll Be Doing": Analysing and interpreting complex datasets; Building dashboards and visualisations; Supporting data pipelines and transformations; Ensuring data quality and governance; Communicating insights to stakeholders. Also maybe "What Makes a Great Grayce Consultant" includes attributes but those are more like skills/qualities; but we could treat them under Skills? Actually they are more like attributes; but we already have Skills section for technical and soft skills. We could include those under Skills as bullet list? But the instruction: Use

  • for any list of duties/requirements/benefits. Those are not duties/requirements/benefits but maybe skills. We'll keep them under Skills as list. Skills: includes "Skills By joining our Data pathway, you will have the opportunity to develop your skills across a range of data-focused roles. Depending on your strengths and interests, you may progress into roles such as: ..." plus "Technical Skills (Advantageous)" list. We need to preserve all specifics: list of possible roles: Advanced Analytics & Data Science: Data Scientist; Data Analysis & Insight: Data Analyst, BI Analyst, Insight Analyst, Reporting Analyst, Hybrid Data/Business Analyst; Data Engineering & Platforms: Data Engineer, Data Governance Analyst, Data Quality Analyst; Risk & Compliance: Risk & Compliance Analyst. Technical Skills: Excel, SQL, Python or R; Power BI, Tableau or similar tools; Data modelling and transformation concepts; Cloud platforms (AWS, Azure). Also "What Makes a Great Grayce Consultant": Strong analytical mindset; Attention to detail and accuracy; Ability to translate data into insight; Clear communication and storytelling. These are also skills/attributes. We'll include them under Skills as bullet list maybe separate. Benefits: Under "Why Work for Us": Locations, Opportunity, Delivery, Mentoring, Progression, Wellbeing Support. Also maybe "Our Approach to AI" but that's not a benefit; it's about AI usage. Could be omitted as not benefit? It's substantive but not fitting any heading; maybe we could include under About the role? But it's about AI approach. Could be included as a paragraph under About the role or maybe under Benefits? It's not a benefit. The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The AI approach is not boilerplate; it's substantive. We need to preserve it. Where to put? Could be under About the role as additional paragraph. Or we could create a separate section like "Our Approach to AI" but not in allowed headings. Since only allowed headings are those listed, we should not create other headings. So we must fold it into existing sections. Probably under About the role or Benefits. I'd put under About the role as a paragraph. Pay: "Our salaries are dictated by location and client Significant annual salary increases." Note there is missing punctuation; we keep as is. Now we need to ensure we don't include boilerplate like "Why Grayce?" heading (we are not using that as heading). We'll just use prose. Let's craft HTML. We'll start with

    About the role

    then paragraphs. Paragraph 1: Grayce specialises in delivering change and transformation for some of the UK’s most ambitious organisations. For over a decade, we have partnered with FTSE 100 and FTSE 250 companies to deploy high-performing early career talent across major programmes of work. Our Accelerated Development Programme offers a structured, fast-track route into industry. You will gain hands-on experience working on business transformation initiatives, supporting stakeholders, improving processes, and contributing to large-scale change programmes. You will typically work with one client at a time, delivering meaningful outcomes in a professional, client-facing environment. Alongside this, you will complete a minimum of six industry-recognised accreditations, with clear progression pathways and salary growth as you develop. Paragraph 2: We are recruiting graduates into a range of data-focused roles across analytics, engineering, and data science. Paragraph 3 (maybe AI): At Grayce, we embrace the responsible use of AI. We use AI-assisted screening to help assess eligibility and suitability for our roles, enabling us to review applications fairly and consistently. We also recognise that candidates may use AI tools when preparing their applications. We welcome the thoughtful use of AI