Digital and Data Specialist Lead
for section headings (e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)
2. Use - for any list of duties/requirements/benefits, and
for prose
3. Do NOT repeat the job title as a heading (the page already shows it)
4. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it
5. Preserve ALL substantive information; do NOT invent or summarize away detail
6. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions
7. Include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD")
8. Never create Pay/Schedule/Benefits sections unless the posting actually states them
9. Prefer a few substantive sections over many thin ones
10. Output ONLY the HTML fragment — no /, no markdown code fences
Let me analyze the job posting content:
The posting is for a "Digital and Data Specialist Lead" role at PSD Scotland (Public Services Delivery Scotland), which is a merger of NSS and NES.
Key sections I can identify:
- About the organization (PSD Scotland, DEW team)
- The Opportunity / Role description
- What We Love To See (requirements/skills)
- Benefits
- Diversity and Inclusion
- Next Steps / Application process (but I should remove application instructions per rules)
- Work pattern details (Fixed Term/Secondment, Full Time, 36 hours/week until 31 March 2028)
- Location: Flexible/remote-friendly
- Eligibility to work in UK
I need to structure this into semantic HTML with appropriate headings.
Let me plan the sections:
1. About the Role / Organization (could be "About the Role" or "About the Organisation")
2. The Opportunity (role description)
3. Key Responsibilities (from "What We Love To See" and the questions asked)
4. Requirements / Skills (from "What We Love To See")
5. Benefits (explicitly listed)
6. Work Pattern / Schedule (explicitly stated: Fixed Term/Secondment, Full Time, 36 hours/week until 31 March 2028)
7. Location (Flexible/remote-friendly)
8. Eligibility (must have eligibility to work in UK)
But note: The rules say "never create Pay/Schedule/Benefits sections unless the posting actually states them." The posting does state Benefits explicitly, and Work Pattern is stated. Pay is not explicitly stated (no salary range mentioned). So I should include Benefits and Schedule/Work Pattern sections.
Also, the posting has "Why join us?" which is more marketing, but I can incorporate that into the role description.
The "What We Love To See" section lists bullet points - those are requirements/skills.
The "Do you have..." questions are also essentially requirements.
I should combine the requirements into a cohesive list.
Also, there's a "Next Steps" section with interview dates and process - but the rules say remove application instructions. However, the interview date (week commencing 02/11/2026) might be considered substantive information about the timeline. But it's part of application process. I'll include it as a note maybe under a "Recruitment Timeline" or similar, but the rules say remove application instructions. I'll skip the application process details, but maybe keep the interview date as it's specific.
The posting also has contact info for Paula Baird - that's application instruction, should remove.
The "Job Information Pack" reference - remove.
The closing date: "deadline for applications is 23:59 hours on the closing date" but no specific date given? Actually it says "Unless otherwise stated the deadline for applications is 23:59 hours on the closing date." But no closing date mentioned. So not specific.
The pre-employment checks and right to work details - that's boilerplate legal/EEO, should remove.
Diversity and Inclusion section - that's EEO boilerplate, but it's specific to this organization's commitment. The rules say remove EEO/equal-opportunity boilerplate. However, this is a specific statement about their diversity and inclusion approach. I'll include it as a section maybe "Diversity and Inclusion" but it's somewhat boilerplate. The rules say "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate". This is EEO boilerplate. I should remove it.
But the posting says "Developing a successful national service for Scotland means considering the diverse needs..." - it's part of the job posting. However, it's standard EEO language. I'll remove it per rules.
The "Why join us?" section is marketing but specific to this role. I'll incorporate into the role description.
Now, let's structure the HTML.
I'll start with a
for the metadata: work pattern, location, duration, eligibility.
Then sections:
About the Organisation
... about PSD Scotland and DEW team ...
About the Role
... the opportunity description ...
Key Responsibilities
- ... from the questions and description ...
Requirements
- ... from "What We Love To See" ...
Benefits
- ... listed benefits ...
Work Pattern
Fixed Term or Secondment, Full Time, 36 hours per week until 31 March 2028.
Location
Flexible/remote-friendly with staff based throughout Scotland; hybrid and office-based arrangements supported.
Eligibility
You must have eligibility and entitlement to work in the UK, maintained throughout employment.
But note: The rules say "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short or drop it." The work pattern, location, eligibility are metadata but substantive. I'll include them as short
under appropriate headings or as a combined metadata section.
Better to have a "Role Details" section with metadata.
Let me think: The rules say "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". So Schedule is a suggested heading. Work Pattern is essentially schedule.
I'll create:
- About the Organisation
- About the Role
- Responsibilities
- Requirements
- Benefits
- Schedule
- Location
- Eligibility
But that's many thin sections. The rules say "Prefer a few substantive sections over many thin ones." So maybe combine Schedule, Location, Eligibility into a "Role Details" section with
elements.
But the rules say use
for section headings like Schedule. However, they also say never create Schedule section unless posting actually states them. The posting does state work pattern explicitly. So I should include Schedule.
Similarly, Benefits is stated.
Location is stated.
Eligibility is stated.
I'll include them as separate sections but keep them concise.
Now, let's extract content.
First, the opening paragraph: "On 1 April 2026, NSS and NES became one national organisation... Public Services Delivery Scotland (PSD Scotland)." This is about the organisation.
Then "Flexible Location: PSD Scotland is a remote-friendly employer..." and "Work Pattern: Fixed Term or Secondment, Full Time, 36 hours per week until 31st March 2028. You must have eligibility and entitlement to work in the UK..."
Then "Who We Are" section describes PSD Scotland and DEW team.
Then "The Opportunity" describes the role.
Then "Why join us?" bullet points.
Then "What We Love To See" bullet points.
Then "Benefits Which Matter" bullet points.
Then "Diversity and Inclusion" paragraph.
Then "Next Steps" with interview date and process.
Then legal boilerplate about right to work.
I'll remove the legal boilerplate, application instructions (contact Paula, CVs not accepted, deadline, pre-employment checks, visa sponsorship details). Keep interview date? It's specific: "interviews will take place October 2026 week commencing 02/11/2026." That's a specific timeline. But it's part of application process. The rules say remove application instructions. I'll remove it.
But the interview date might be useful for candidates. However, the instruction is clear: remove application instructions. I'll remove.
Now, let's write the HTML.
I'll start with a
for the metadata: work pattern, location, duration, eligibility. But better to have separate sections.
I'll do:
About the Organisation
On 1 April 2026, NHS National Services Scotland (NSS) and NHS Education for Scotland (NES) merged to form Public Services Delivery Scotland (PSD Scotland), a new national organisation focused on continuity today and a stronger, more connected service for tomorrow. PSD Scotland unites expertise from NES and NSS to accelerate national programmes supporting the NHS to deliver better care. The organisation supports staff with education and training, provides tools and data that improve services, and runs vital national functions such as procurement, logistics, and blood, tissue and cell services.
The Digitally Enabled Workforce (DEW) team within PSD Scotland is a high-impact, delivery-focused, multi-award-winning team working remotely across the UK. Commissioned by the Scottish Government and COSLA, DEW delivers on national priorities from Scotland’s Digital Health and Care Strategy, the Health and Social Care Data Strategy, the Care in the Digital Age Delivery Plan, and the Health and Social Care Service Renewal Framework. The team enables transformation at scale by providing national learning resources, networks, and programmes for the entire health and social care sector, including NHS, local authorities, health and social care partnerships, social work, social care, care and support providers, housing, third and independent sectors.
About the Role
We are looking for an inspirational Digital and Data Specialist Lead to take forward a portfolio of national initiatives that support the wider workforce and drive the development and delivery of Scotland’s specialist Digital, Data and Technology (DDaT) workforce capability agenda. As part of the DEW team, you will be responsible for delivering key elements within a national programme that builds the digital, data, and leadership capability required for transformation, equipping the workforce, organisations, and leaders across Scotland's health and social care system to realise the opportunities presented by digital, data, AI, and emerging technologies.
Commissioned by the Scottish Government and COSLA, you will lead high-profile initiatives that turn national ambition into workforce digital and data capability, organisational readiness, and sustainable transformation. You will work in partnership across NHS Scotland, local authorities, health and social care partnerships, social care, housing, academia, and national organisations to maximise the impact of digital and data-enabled services. Through innovative learning experiences and strategic partnership working, you will help organisations build the confidence, capability, and leadership required to deliver lasting transformation.
This is a commissioned role supporting a high-profile programme; we are seeking a credible and experienced leader who can quickly establish themselves, take ownership from day one, and drive delivery, improvement, and measurable outcomes across a high-profile portfolio.
Responsibilities
- Lead and deliver digital and data workforce development programmes at scale
for prose 3. Do NOT repeat the job title as a heading (the page already shows it) 4. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it 5. Preserve ALL substantive information; do NOT invent or summarize away detail 6. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions 7. Include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD") 8. Never create Pay/Schedule/Benefits sections unless the posting actually states them 9. Prefer a few substantive sections over many thin ones 10. Output ONLY the HTML fragment — no /, no markdown code fences Let me analyze the job posting content: The posting is for a "Digital and Data Specialist Lead" role at PSD Scotland (Public Services Delivery Scotland), which is a merger of NSS and NES. Key sections I can identify: - About the organization (PSD Scotland, DEW team) - The Opportunity / Role description - What We Love To See (requirements/skills) - Benefits - Diversity and Inclusion - Next Steps / Application process (but I should remove application instructions per rules) - Work pattern details (Fixed Term/Secondment, Full Time, 36 hours/week until 31 March 2028) - Location: Flexible/remote-friendly - Eligibility to work in UK I need to structure this into semantic HTML with appropriate headings. Let me plan the sections: 1. About the Role / Organization (could be "About the Role" or "About the Organisation") 2. The Opportunity (role description) 3. Key Responsibilities (from "What We Love To See" and the questions asked) 4. Requirements / Skills (from "What We Love To See") 5. Benefits (explicitly listed) 6. Work Pattern / Schedule (explicitly stated: Fixed Term/Secondment, Full Time, 36 hours/week until 31 March 2028) 7. Location (Flexible/remote-friendly) 8. Eligibility (must have eligibility to work in UK) But note: The rules say "never create Pay/Schedule/Benefits sections unless the posting actually states them." The posting does state Benefits explicitly, and Work Pattern is stated. Pay is not explicitly stated (no salary range mentioned). So I should include Benefits and Schedule/Work Pattern sections. Also, the posting has "Why join us?" which is more marketing, but I can incorporate that into the role description. The "What We Love To See" section lists bullet points - those are requirements/skills. The "Do you have..." questions are also essentially requirements. I should combine the requirements into a cohesive list. Also, there's a "Next Steps" section with interview dates and process - but the rules say remove application instructions. However, the interview date (week commencing 02/11/2026) might be considered substantive information about the timeline. But it's part of application process. I'll include it as a note maybe under a "Recruitment Timeline" or similar, but the rules say remove application instructions. I'll skip the application process details, but maybe keep the interview date as it's specific. The posting also has contact info for Paula Baird - that's application instruction, should remove. The "Job Information Pack" reference - remove. The closing date: "deadline for applications is 23:59 hours on the closing date" but no specific date given? Actually it says "Unless otherwise stated the deadline for applications is 23:59 hours on the closing date." But no closing date mentioned. So not specific. The pre-employment checks and right to work details - that's boilerplate legal/EEO, should remove. Diversity and Inclusion section - that's EEO boilerplate, but it's specific to this organization's commitment. The rules say remove EEO/equal-opportunity boilerplate. However, this is a specific statement about their diversity and inclusion approach. I'll include it as a section maybe "Diversity and Inclusion" but it's somewhat boilerplate. The rules say "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate". This is EEO boilerplate. I should remove it. But the posting says "Developing a successful national service for Scotland means considering the diverse needs..." - it's part of the job posting. However, it's standard EEO language. I'll remove it per rules. The "Why join us?" section is marketing but specific to this role. I'll incorporate into the role description. Now, let's structure the HTML. I'll start with a
for the metadata: work pattern, location, duration, eligibility. Then sections:
About the Organisation
... about PSD Scotland and DEW team ...
About the Role
... the opportunity description ...
Key Responsibilities
- ... from the questions and description ...
Requirements
- ... from "What We Love To See" ...
Benefits
- ... listed benefits ...
Work Pattern
Fixed Term or Secondment, Full Time, 36 hours per week until 31 March 2028.
Location
Flexible/remote-friendly with staff based throughout Scotland; hybrid and office-based arrangements supported.
Eligibility
You must have eligibility and entitlement to work in the UK, maintained throughout employment.
But note: The rules say "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a shortor drop it." The work pattern, location, eligibility are metadata but substantive. I'll include them as short
under appropriate headings or as a combined metadata section. Better to have a "Role Details" section with metadata. Let me think: The rules say "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". So Schedule is a suggested heading. Work Pattern is essentially schedule. I'll create: - About the Organisation - About the Role - Responsibilities - Requirements - Benefits - Schedule - Location - Eligibility But that's many thin sections. The rules say "Prefer a few substantive sections over many thin ones." So maybe combine Schedule, Location, Eligibility into a "Role Details" section with
elements. But the rules say use
for section headings like Schedule. However, they also say never create Schedule section unless posting actually states them. The posting does state work pattern explicitly. So I should include Schedule. Similarly, Benefits is stated. Location is stated. Eligibility is stated. I'll include them as separate sections but keep them concise. Now, let's extract content. First, the opening paragraph: "On 1 April 2026, NSS and NES became one national organisation... Public Services Delivery Scotland (PSD Scotland)." This is about the organisation. Then "Flexible Location: PSD Scotland is a remote-friendly employer..." and "Work Pattern: Fixed Term or Secondment, Full Time, 36 hours per week until 31st March 2028. You must have eligibility and entitlement to work in the UK..." Then "Who We Are" section describes PSD Scotland and DEW team. Then "The Opportunity" describes the role. Then "Why join us?" bullet points. Then "What We Love To See" bullet points. Then "Benefits Which Matter" bullet points. Then "Diversity and Inclusion" paragraph. Then "Next Steps" with interview date and process. Then legal boilerplate about right to work. I'll remove the legal boilerplate, application instructions (contact Paula, CVs not accepted, deadline, pre-employment checks, visa sponsorship details). Keep interview date? It's specific: "interviews will take place October 2026 week commencing 02/11/2026." That's a specific timeline. But it's part of application process. The rules say remove application instructions. I'll remove it. But the interview date might be useful for candidates. However, the instruction is clear: remove application instructions. I'll remove. Now, let's write the HTML. I'll start with a
for the metadata: work pattern, location, duration, eligibility. But better to have separate sections. I'll do:
About the Organisation
On 1 April 2026, NHS National Services Scotland (NSS) and NHS Education for Scotland (NES) merged to form Public Services Delivery Scotland (PSD Scotland), a new national organisation focused on continuity today and a stronger, more connected service for tomorrow. PSD Scotland unites expertise from NES and NSS to accelerate national programmes supporting the NHS to deliver better care. The organisation supports staff with education and training, provides tools and data that improve services, and runs vital national functions such as procurement, logistics, and blood, tissue and cell services.
The Digitally Enabled Workforce (DEW) team within PSD Scotland is a high-impact, delivery-focused, multi-award-winning team working remotely across the UK. Commissioned by the Scottish Government and COSLA, DEW delivers on national priorities from Scotland’s Digital Health and Care Strategy, the Health and Social Care Data Strategy, the Care in the Digital Age Delivery Plan, and the Health and Social Care Service Renewal Framework. The team enables transformation at scale by providing national learning resources, networks, and programmes for the entire health and social care sector, including NHS, local authorities, health and social care partnerships, social work, social care, care and support providers, housing, third and independent sectors.
About the Role
We are looking for an inspirational Digital and Data Specialist Lead to take forward a portfolio of national initiatives that support the wider workforce and drive the development and delivery of Scotland’s specialist Digital, Data and Technology (DDaT) workforce capability agenda. As part of the DEW team, you will be responsible for delivering key elements within a national programme that builds the digital, data, and leadership capability required for transformation, equipping the workforce, organisations, and leaders across Scotland's health and social care system to realise the opportunities presented by digital, data, AI, and emerging technologies.
Commissioned by the Scottish Government and COSLA, you will lead high-profile initiatives that turn national ambition into workforce digital and data capability, organisational readiness, and sustainable transformation. You will work in partnership across NHS Scotland, local authorities, health and social care partnerships, social care, housing, academia, and national organisations to maximise the impact of digital and data-enabled services. Through innovative learning experiences and strategic partnership working, you will help organisations build the confidence, capability, and leadership required to deliver lasting transformation.
This is a commissioned role supporting a high-profile programme; we are seeking a credible and experienced leader who can quickly establish themselves, take ownership from day one, and drive delivery, improvement, and measurable outcomes across a high-profile portfolio.
Responsibilities
- Lead and deliver digital and data workforce development programmes at scale