Skip to main content

Internal Systems & Enablement

Find out how we design and automate the systems Skylight runs on, and the skills you need at each level.

Introduction

Internal Systems & Enablement practitioners design, document, and automate the internal systems, workflows, and content Skylight runs on. They turn operational needs into clear, reliable ways of working that people adopt. They make sure the systems that result get used, make work simpler across functions, and let the company operate efficiently as it grows.

Core craft

Systems mapping and design

Mapping how internal systems work — across people, process, tooling, data, and governance — and designing better workflows that can scale, with explicit decision rights, handoffs, and escalation paths

Operational content and documentation

Turning complex workflows, policies, and system changes into clear, usable content — standard operating procedures (SOPs), guides, templates, and reusable assets — with strong version control, consistent terminology, and findable structure

Operations automation and tooling

Building reliable automation and internal tooling — scripts, integrations, APIs, AI-assisted workflows — that work with existing systems and respect which system holds the official record

Governance and decision-making

Establishing the standards, change-control discipline, and decision rights that keep internal systems consistent — who decides what, what information they need, and how issues are escalated

Adoption and measurable impact

Making sure redesigned systems are used and showing the improvement they make — running rollouts, feedback loops, and the measures that show friction and rework went down

Associate

Develop foundational internal-systems, content, or automation skills while supporting the function reliably.

Scope: what you decide and own
Executes defined internal-systems, content, or automation tasks with guidance from more experienced practitioners
Relationships: working with stakeholders
Responds to internal-stakeholder requests with guidance; contributes to shared operational documentation
Reach: what changes because of you
Their assigned internal-systems work is done reliably, with little rework
Calibration question
Can they deliver defined internal-systems tasks reliably, with guidance?
What success looks like
  • Completes well-scoped systems, documentation, or automation tasks with guidance
  • Produces clear operational documentation that follows existing patterns and terminology
  • Implements feedback without repeated rework
  • Collaborates effectively with internal stakeholders and asks for help at the right moments
  • Learns the team's practices for governance, official records, and adoption
Example outcomes
  • An SOP or template drafted from an existing pattern and adopted without major revision
  • A scoped workflow change mapped and documented cleanly
  • A small automation or integration built under guidance and validated before deployment
  • A terminology or version-control cleanup that reduced confusion in an internal doc set

Level I

Own a well-scoped internal workflow, content area, or automation, deciding the approach within a larger effort.

Scope: what you decide and own
Decides approach for well-scoped internal-systems work; owns a defined workflow, content area, or automation within a larger effort
Relationships: working with stakeholders
Builds solid working relationships with direct internal counterparts; communicates changes and progress clearly
Reach: what changes because of you
The internal-systems work they own is done well and on pace
Calibration question
Can they be trusted to own a well-scoped internal-systems area without close oversight?
What success looks like
  • Owns a defined piece of internal-systems work — a workflow, a content area, an automation — end-to-end within a larger effort
  • Decides the approach for well-scoped work and delivers what they own well and on pace
  • Produces operational documentation with clean structure, version control, and consistent terminology without being prompted
  • Communicates changes, progress, and tradeoffs clearly to internal stakeholders
  • Identifies basic governance, accuracy, and adoption issues in their work and addresses them
  • Works effectively with counterparts in Operations, People Operations, Finance, Contracts, Growth, or IT on shared work
Example outcomes
  • A recurring internal workflow improved end-to-end with documentation and a clean handoff
  • An SOP set or guide that measurably reduced repeat questions or handoff errors
  • An automation that removed a manual step and ran reliably with logging and a rollback path
  • A content area kept current and consistent so other teams could rely on it

Level II

Lead an internal system, process, content set, or automation end-to-end, including the ambiguous parts.

Scope: what you decide and own
Decides approach for ambiguous internal-systems problems; owns a system, process, content set, or automation end-to-end
Relationships: working with stakeholders
Proactively manages internal-stakeholder expectations and facilitates working sessions; produces process maps, SOPs, and automations that stakeholders can use without heavy revision
Reach: what changes because of you
Their work measurably improves an internal system or process they own — clarity, cycle time, error rate, or adoption
Calibration question
Can they own ambiguous internal-systems work end-to-end and make the calls without escalating?
What success looks like
  • Owns a system, process, content set, or automation end-to-end, including the design decisions
  • Makes sound tradeoff calls on approach, scope, and sequencing without escalating routine choices
  • Produces process maps, SOPs, decision records, and automations that stakeholders can use without heavy revision
  • Runs rollout and feedback loops so the work is actually adopted, not just shipped
  • Builds governance, accuracy, clear ownership of records, and adoption into the design rather than after the fact
  • Facilitates working sessions that settle who decides what and move decisions forward
  • Mentors Associates and Level I practitioners through pairing and review
Example outcomes
  • An ambiguous cross-team workflow redesigned and adopted, with a measurable drop in cycle time or rework
  • A documentation system restructured for findability and consistency that other functions adopted
  • An automation shipped to real users with monitoring and validation that reduced errors
  • A decision record and escalation path that ended a recurring ownership stall

Senior

Own the design of an internal system or capability a function depends on — making the consequential calls and lifting the team's craft.

Scope: what you decide and own
Makes consequential internal-systems tradeoff calls; owns the design of an internal system or capability that a function depends on
Relationships: working with stakeholders
Navigates competing internal priorities and reframes operational problems into clear choices for function leaders; aligns stakeholders on operational change
Reach: what changes because of you
Internal operations in their area are measurably more efficient or scalable because of decisions they made, not just work they delivered
Calibration question
If they stepped away, would internal operations lose judgment, not just capacity?
What success looks like
  • Sets the design direction for an internal system or capability — an operating model, a documentation system, an automation platform, a governance standard
  • Makes consequential tradeoff decisions on design, sequencing, governance, and adoption under real constraints
  • Leads the function through complex change like a system redesign, a platform migration, or reworking a difficult process
  • Reframes operational problems into clear choices for function leaders and aligns stakeholders on change
  • Mentors junior and mid-level practitioners through review, pairing, and direct coaching
  • Strengthens the team's craft alongside their own work — documentation standards, review practices, change-control discipline
  • Holds adoption and measurable impact as the bar for what "done" means
Example outcomes
  • A system redesign that made a function measurably more efficient or scalable, with adoption to prove it
  • An internal platform or documentation system that multiple teams in a function built on without rework
  • A governance and change-control standard the function adopted that stopped recurring coordination breakdowns
  • A difficult cross-team process brought back to running smoothly through hands-on involvement
  • A mid-level practitioner who grew measurably under their mentorship into independent ownership

Staff

Improve internal-operations quality and efficiency across multiple functions through shared systems, standards, and direction.

Scope: what you decide and own
Sets internal-systems direction across functions; owns the operational standards, platforms, or automation strategy multiple functions run on
Relationships: working with stakeholders
Gets functions across the company pulling in the same operational direction; clears cross-function blockers no single function can clear
Reach: what changes because of you
Multiple functions run better because of the systems, standards, or automation they put in place, and it travels beyond the function that originated it
Calibration question
If they stepped away, would cross-function operational standards lose direction, not just a strong contributor?
What success looks like
  • Sets internal-systems direction across functions, not just within one
  • Identifies systemic operational gaps no single function would see and addresses them
  • Owns shared systems, standards, or initiatives — operating models, documentation standards, automation strategy, governance frameworks — adopted across functions
  • Resolves cross-function disagreements about operations and who decides what, and unblocks coordination
  • Influences company-level operational strategy with leadership
  • Mentors practitioners across functions and helps Seniors grow into cross-function thinking
  • Establishes operational practices that other functions adopt
Example outcomes
  • A company-wide documentation or workflow standard adopted across functions that reduced duplicate work
  • An automation strategy rolled out across functions that cut cycle time or eliminated a class of manual error
  • A cross-function governance framework that clarified decision rights and stopped recurring escalation stalls
  • An operating-model change across several functions that improved delivery predictability or financial visibility

Principal

Reframe how Skylight runs internally at the company level, and help Skylight grow as an operating organization.

Scope: what you decide and own
Reframes how Skylight runs internally at the company level, diagnosing root causes with leadership; shares ownership of the company's internal operating health and contributes meaningfully to Skylight's growth
Relationships: working with stakeholders
A trusted authority on internal operations up to company leadership; aligns leadership around operational direction and earns their buy-in
Reach: what changes because of you
How the company operates is materially better because of their systems and direction, and Skylight is stronger and able to scale because of it
Calibration question
If they'd never been here, would Skylight's internal operating model be on a different path?
What success looks like
  • Reframes how the company operates internally — its operating model, systems direction, governance, or automation strategy at the enterprise level
  • Diagnoses root-cause operational problems with leadership and brings the organization along
  • Aligns company leadership around operational direction and earns their buy-in
  • Guides major operational tradeoffs across functions — build versus buy, sequencing of enterprise change, automation and governance investment
  • Contributes to the Internal Systems & Enablement practice area through hiring, leveling, craft standards, and developing Staff-level practitioners
  • Contributes to Skylight's growth by making the company able to scale — delivery predictability, financial visibility, growth coordination, employee experience
  • Connects internal-systems work to measurable enterprise impact leadership can act on
Example outcomes
  • An enterprise operating-model change leadership adopted that measurably improved how the company runs and scales
  • An internal-systems or governance strategy that changed how multiple functions coordinate and decide
  • An automation or platform direction adopted company-wide that removed a structural source of friction
  • A practice area hiring bar, craft standard, or operational framework adopted across Skylight

We’re hiring!

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