Skip to main content

Domain Expertise

Find out how we bring deep knowledge of a client's field into the work, and the skills you need at each level.

Introduction

Domain Expertise practitioners bring deep subject-matter knowledge to delivery teams and clients. They translate mission, policy, and program reality into guidance that product, design, engineering, and data partners can act on. They know how the work actually happens in their domain (clinical, regulatory, programmatic, operational) and how it differs across jurisdictions, agencies, and program contexts. They earn trust with both the mission experts on the client side and the technical teams on Skylight's side, and they sit at the seam where those two worlds have to align for digital services to work.

Core craft

Domain practice fluency

Deep working knowledge of how the domain operates in real organizations — including staffing constraints, decision rights, regulatory environment, and how the work differs across jurisdictions or program contexts

Workflow and policy translation

Converting policy, guidance, and standard practice into implementable workflows, role definitions, edge cases, and data requirements that delivery teams can build to

Stakeholder trust and influence

Building credibility with mission experts (federal program leaders, STLT counterparts, program staff, oversight bodies) and earning the standing to push back, reframe, and align them

Cross-functional partnership

Working with product, design, engineering, and data teams — bringing clear recommendations with tradeoffs and translating technical constraints back into language stakeholders can act on

Prioritization under constraint

Identifying the highest-impact problems given staffing, policy, and program realities; sequencing work responsibly when everything matters

Practice asset creation

Producing reusable artifacts — playbooks, workflow standards, decision records, briefing docs — that scale domain knowledge across teams and outlast any single engagement

Associate

Develop foundational domain strategy skills while supporting a delivery team.

Scope: what you decide and own
Executes defined domain research, documentation, and translation tasks, with guidance
Relationships: working with stakeholders
Responds to team and stakeholder requests with guidance; contributes to shared artifacts like workflow notes, policy summaries, and briefing docs
Reach: what changes because of you
Their assigned work is done reliably — notes, summaries, and draft artifacts are clear and ready to use, with little rework
Calibration question
Can they deliver defined domain analysis and documentation tasks reliably, with guidance?
What success looks like
  • Supports domain research, documentation, and translation work with reliable follow-through
  • Produces clear notes, summaries, and draft artifacts that capture policy or workflow detail accurately
  • Builds working relationships with teammates and observes how senior practitioners handle domain stakeholders
  • Communicates progress and questions clearly to the team
  • Asks questions to understand the domain, the mission, and how the work actually happens in practice
Example outcomes
  • A clean set of policy or guidance notes the team can rely on without re-reading the source
  • A workflow walkthrough or interview summary that captures what frontline staff actually do
  • A stakeholder briefing draft that holds up to senior review
  • Meeting notes and follow-ups that keep decisions and action items from getting lost

Level I

Apply domain expertise independently to a defined piece of the engagement.

Scope: what you decide and own
Decides the approach for well-scoped domain work; owns a defined piece of a larger effort — a workflow slice, a policy-to-practice translation, a stakeholder briefing, or a focused area of domain documentation
Relationships: working with stakeholders
Builds solid working relationships with direct counterparts on the team and with domain stakeholders; communicates findings and recommendations clearly
Reach: what changes because of you
The domain work they own is done well and on pace
Calibration question
Can they choose the right approach for well-scoped domain work without close oversight?
What success looks like
  • Owns a workflow slice, a policy-to-practice translation, a stakeholder briefing, or a focused area of domain documentation within a larger engagement
  • Conducts policy review, interviews, or workflow analysis with minimal guidance
  • Drafts workflow descriptions, briefings, or recommendations that hold up to senior and client review
  • Builds direct relationships with domain counterparts on the client side and communicates clearly with them
  • Identifies risks early — policy changes coming, stakeholder misalignment, workflow gaps — and escalates or resolves them
  • Articulates the value of their work to the team and the client
Example outcomes
  • A workflow document for a defined area (for example, one stage of case investigation, one piece of an enrollment process, one program function) that delivery teams use as a reliable reference
  • A policy-to-practice translation that gave a product team a clear, defensible set of requirements
  • A stakeholder briefing that closed a loop the team had been stuck on
  • A working session with domain stakeholders that surfaced a real gap leadership hadn't seen
  • A first piece of practice documentation — a glossary, a role description, a decision record — that other team members start using

Level II

Lead a domain area end to end through ambiguity.

Scope: what you decide and own
Decides the approach for ambiguous domain problems; owns a domain area end to end within an engagement — a workflow domain like case investigation, a data stream like electronic laboratory reporting (ELR), a program area like enrollment, or a regulatory area
Relationships: working with stakeholders
Manages stakeholder expectations proactively within their area; runs working sessions with domain stakeholders and delivery teams that end in decisions; produces artifacts — workflow standards, briefings, recommendations — stakeholders can use without heavy revision
Reach: what changes because of you
The domain area they own delivers its intended outcome
Calibration question
Can they own an ambiguous domain area end to end and make the calls without escalating?
What success looks like
  • Owns a domain area within an engagement — a workflow domain, a data stream, a program area, or a regulatory area — including scope, sequencing, and stakeholder management
  • Defines and tracks outcomes for their area — not just artifacts produced
  • Makes tradeoff decisions on how policy, practice, and constraints should shape the work, and explains the reasoning clearly
  • Runs the stakeholder conversation within their area without senior backup, including hard conversations about scope, feasibility, or jurisdictional variation
  • Produces client-ready artifacts — workflow standards, briefings, recommendations, decision records — that land without heavy revision
  • Adapts when policy or guidance changes mid-engagement — rebaselines the work and communicates impact clearly
  • Translates both ways — domain to delivery and delivery to domain — without losing nuance
Example outcomes
  • A workflow standard for a meaningful practice area (for example, a specific surveillance data stream, a specific eligibility or enrollment workflow, a regulatory reporting domain) that the product team builds to and stakeholders sign off on
  • A policy change navigated mid-engagement without team thrash — assumptions updated, scope adjusted, stakeholders aligned
  • A redesigned workflow or program process that improved a measurable user, staff, or program outcome
  • A briefing or decision record that aligned previously divergent stakeholders (for example, federal program staff and STLT counterparts, or central agency and field offices) on a shared definition
  • A reusable practice asset — a playbook, a workflow library, a decision tree — that another engagement adopted

Senior

Own the domain strategy for a product, program, or engagement and guide its direction.

Scope: what you decide and own
Makes the consequential tradeoff calls on how policy, practice, and program reality should shape the work; owns the domain strategy for a product, program, or engagement the team depends on
Relationships: working with stakeholders
Navigates competing priorities; turns messy policy, workflow, and jurisdictional situations in their area into clear choices for senior domain stakeholders and the team
Reach: what changes because of you
Outcomes in their product or program improve — what gets built, how it reflects practice reality, how stakeholders engage — because of decisions they made, not just the analysis they delivered
Calibration question
If they stepped away, would the team lose domain judgment, not just capacity?
What success looks like
  • Owns the domain strategy for a product, program, or engagement of meaningful scope and complexity
  • Sets the direction for how policy, practice, and program reality should shape the work; adjusts as conditions change
  • Makes consequential tradeoff calls on scope, sequencing, and how the work should reflect domain realities
  • Acts as a trusted advisor to senior domain stakeholders — federal program leaders, agency executives, STLT or jurisdictional counterparts, oversight bodies — and reframes problems for them
  • Runs the full domain conversation with the client for their product or program without senior backup
  • Anticipates policy, political, or jurisdictional risks before they hit the team
  • Builds alignment across product, design, engineering, data, and the client around a shared understanding of the domain
  • Mentors junior and mid-level practitioners on the team through working sessions and direct collaboration
  • Strengthens the team's domain judgment alongside their own work
  • Contributes to business development on the engagement — recompetes, scope expansions, or proposal input where domain expertise is the differentiator
Example outcomes
  • A product or program that delivered against a hard policy or rule-making deadline because the Senior anticipated the change and rebaselined the team's plan early
  • A domain strategy that aligned previously competing stakeholder groups (for example, federal and STLT, or central and field, or program and oversight) around a single direction
  • A redesigned workflow adopted across multiple jurisdictions or program offices after evidence of impact in a first one
  • A renewed or expanded engagement grounded in domain credibility the client trusts
  • A first-time domain lead on the team who's now running their own practice area
  • A reusable framework or playbook that other Skylight engagements in the domain started borrowing from

Staff

Improve domain outcomes across multiple engagements, programs, or jurisdictions.

Scope: what you decide and own
Sets domain direction across their whole operating context — the workstreams, engagements, or programs in it — and owns the systems and standards it runs on, such as workflow standards, jurisdictional playbooks, and cross-program decision records
Relationships: working with stakeholders
Gets teams across the operating context pulling in the same domain direction; clears organizational and policy blockers no single team can clear
Reach: what changes because of you
The whole operating context produces better domain-aligned work because of the standards, playbooks, or direction they put in place, and it travels to other engagements and teams
Calibration question
If they stepped away, would the operating context lose domain direction, not just a strong contributor?
What success looks like
  • Sets domain direction across multiple workstreams, engagements, or program areas
  • Identifies systemic issues across engagements — common workflow blockers, recurring policy interpretations, jurisdictional drift — that no single team would see
  • Establishes shared practices — workflow standards, jurisdictional playbooks, decision records, briefing templates — that other engagements adopt
  • Resolves cross-engagement tradeoffs around scope, sequencing, or how to navigate policy change
  • Mentors practitioners across engagements — and where Skylight has multiple domains, bridges across them to share approaches and develop people
  • Influences program-level strategy with senior client stakeholders across more than one program area
  • Strengthens cross-team decision-making on domain questions
  • Contributes to Skylight's growth through proposal contributions, scope expansions, or new opportunity development in their domain or in adjacent ones
Example outcomes
  • A domain playbook or workflow standard adopted across multiple engagements that reduced ramp-up time and improved consistency
  • A cross-engagement synthesis that revealed a shared domain challenge and shifted how Skylight approaches that area of the mission
  • A jurisdictional or program variation framework that helped multiple teams handle differences without re-doing the analysis each time
  • A new contract or scope expansion that came directly from domain credibility they built
  • A Senior practitioner on another engagement who's now operating at their level because of their coaching
  • A bridge to a new domain — a hire, a framework, or a body of work that established a second specialty within the practice area (where applicable)

Principal

Shape how clients approach their mission in the domain, and help open new opportunities for Skylight.

Scope: what you decide and own
Decides, with client leadership, how the domain should shape part of the mission — cutting through the noise to diagnose the root problem; shares ownership of the health of Skylight's Domain Expertise practice area
Relationships: working with stakeholders
A trusted advisor up to client leadership: aligns stakeholders across programs on a domain direction and earns their buy-in; a recognized voice in their domain through speaking, publishing, or community leadership
Reach: what changes because of you
Client leadership approaches part of its mission differently because of their work, and Skylight's domain capability is stronger for it — new opportunities open, and the practice area and its people grow
Calibration question
If they'd never been here, would the mission this engagement serves be on a different path?
What success looks like
  • Reframes problems and influences how the client thinks about part of its mission
  • Aligns client leadership around a domain direction that spans multiple programs
  • Guides major tradeoffs on portfolio investment, program design, or policy implementation
  • Acts as an external authority in the domain — through speaking, writing, recognized expertise, or domain community leadership
  • Contributes to Skylight's Domain Expertise practice area through hiring, leveling, craft standards, and supporting practitioners across the practice area
  • Shapes how Skylight develops domain expertise as a capability — including identifying which new domains to invest in and how to bring senior domain experts onto delivery teams effectively
  • Contributes to Skylight's growth through proposal contributions, expanded scope with existing clients, or new client opportunities where deep domain expertise is the differentiator
  • Improves organizational learning from how domain strategy work runs across engagements
Example outcomes
  • A program reorganized around a framing the Principal brought — changing how the client approaches part of its mission across multiple programs or jurisdictions
  • A new contract won at an existing client because of domain credibility built across prior engagements
  • A proposal effort they led or contributed to that brought in new mission work for Skylight in their domain or in an adjacent one
  • A domain approach adopted across a client portfolio that materially changed how the agency does the work
  • A change across the whole practice area at Skylight — a hiring rubric for domain experts, a model for embedding domain strategists on delivery teams, a leveling standard — that raised the bar for how Skylight develops and deploys domain expertise
  • An external presence (talks, publications, recognized expertise in the domain community) that brought new opportunities to Skylight

We’re hiring!

Let’s work together to change the way government
serves millions of people.