Skip to main content

Engineering

Find out how we build and run the software government services depend on, and the skills you need at each level.

Introduction

Engineering practitioners design, build, and operate the software systems that government services depend on. They turn product and policy intent into working, secure, accessible technology — making sure the systems that result are reliable in production, defensible under audit, and clear enough for the next team to maintain.

Core craft

Software development and delivery

Writing, reviewing, and shipping working code in a shared codebase, using leading version-control, testing, and release practices

System architecture and design

Designing how the pieces of a system fit together — services, data flow, interfaces, and integration with other systems

Delivery and operations

Running systems in production reliably — pipelines, deployments, observability, incident response, and on-call practice

Security, privacy, and compliance

Building secure systems and navigating government compliance requirements like FISMA, FedRAMP, HIPAA, and the Privacy Act

User and mission focus

Centering the people who use the system and the mission it serves — accessibility, usability, and equity of access

Cost and resource stewardship

Treating compute, storage, and licensing as a constrained public resource — sizing systems to real demand, making spend visible and attributable, and building guardrails that catch waste before it compounds

Associate

Develop foundational engineering skills while contributing reliably to a delivery team.

Scope: what you decide and own
Executes defined engineering tasks with guidance from more experienced engineers
Relationships: working with stakeholders
Responds to stakeholder and teammate requests with guidance; contributes to shared code, infrastructure, and documentation
Reach: what changes because of you
Their assigned engineering work is done reliably — code, configuration, or remediations land with little rework
Calibration question
Can they deliver defined engineering tasks reliably, with guidance?
What success looks like
  • Completes well-scoped coding, configuration, or remediation tasks with guidance
  • Implements feedback from code review without repeated rework
  • Writes basic tests and documentation for the work they ship
  • Collaborates effectively with teammates and asks for help at the right moments
  • Builds awareness of security, privacy, and accessibility practices on their team
Example outcomes
  • A bug fix or small feature shipped to production after passing code review
  • A pipeline configuration change or environment update completed cleanly
  • A documented remediation for a basic security finding flagged in scanning
  • An accessibility issue caught and fixed in a component before release

Level I

Contribute reliably within a feature area or service, deciding the approach for well-scoped pieces.

Scope: what you decide and own
Decides approach for well-scoped engineering work; owns a defined feature, service component, pipeline change, or remediation within a larger effort
Relationships: working with stakeholders
Builds working relationships with direct counterparts on the team; communicates technical progress and tradeoffs clearly
Reach: what changes because of you
The engineering work they own is done well and on pace
Calibration question
Can they be trusted to decide the approach for well-scoped engineering work without close oversight?
What success looks like
  • Owns a defined piece of work — a feature, a pipeline change, a security ticket, a network configuration — end-to-end within a larger effort
  • Writes tests, documentation, and clear commit history without being prompted
  • Implements code review feedback and gives useful feedback on others' work
  • Communicates progress, blockers, and tradeoffs clearly to the team
  • Identifies basic security, privacy, and accessibility issues in their work and addresses them
  • Works effectively with product, design, and delivery counterparts on shared work
Example outcomes
  • A feature delivered end-to-end with tests, documentation, and a clean handoff
  • A CI/CD improvement that reduces flaky builds or deployment friction
  • A security finding triaged, mitigated, and documented for the team
  • A front-end component built to meet accessibility requirements and adopted by other engineers

Level II

Own a feature, service, pipeline, or security area end-to-end, including the ambiguous parts.

Scope: what you decide and own
Decides approach for ambiguous engineering problems; owns a feature, service, pipeline, or security area end-to-end
Relationships: working with stakeholders
Proactively manages technical expectations and facilitates working sessions and design discussions; produces client-ready technical artifacts (designs, ADRs, demos) that land without heavy revision
Reach: what changes because of you
Their engineering work measurably improves the system in their area — performance, reliability, security posture, or delivery speed
Calibration question
Can they own ambiguous engineering work end-to-end and make decisions without escalating?
What success looks like
  • Owns a service component, feature, pipeline, or security area end-to-end, including design decisions
  • Makes sound tradeoff decisions on approach, scope, and sequencing without escalating routine choices
  • Produces technical artifacts — architecture sketches, ADRs, runbooks, demos — that land with clients and teammates without heavy revision
  • Participates meaningfully in on-call, incident response, or security review rotations
  • Considers security, privacy, accessibility, and operability as part of the design, not after the fact
  • Facilitates technical working sessions and reviews that move decisions forward
  • Mentors Associates and Level I engineers through pairing and code review
Example outcomes
  • A service component refactored to improve reliability or performance, with measurable results
  • An authentication or authorization flow designed and shipped end-to-end
  • A pipeline restructured to add automated security scanning or zero-downtime deployment
  • A network configuration change designed, tested, and rolled out without disruption
  • A security-finding remediation pattern documented and adopted by other engineers on the team

Senior

Lead the engineering work for a capability area on a delivery team — making the consequential calls and lifting the team's craft.

Scope: what you decide and own
Makes consequential architecture, security, and operational tradeoff decisions; owns a capability area such as a platform service, the CI/CD stack, or the team's security posture
Relationships: working with stakeholders
Navigates competing technical priorities and reframes problems for senior client stakeholders in their capability area; influences how the team approaches technical questions
Reach: what changes because of you
Engineering outcomes in their area improve because of decisions they made — system reliability, ATO readiness, deployment cadence, or developer productivity — not just the code they shipped
Calibration question
Would we lose meaningful technical judgment, not just capacity, if they stepped away?
What success looks like
  • Sets technical direction for a capability area — a service, a platform component, the CI/CD stack, the team's security posture, or a network domain
  • Makes consequential tradeoff decisions on architecture, security, operations, and delivery cadence
  • Leads the team through complex work like compliance milestones, incident response, modernization, or platform migrations
  • Communicates technical direction and tradeoffs clearly to product, design, delivery, and client stakeholders
  • Mentors junior and mid-level engineers through code review, pairing, design discussions, and direct coaching
  • Strengthens the team's engineering judgment alongside their own work — code review standards, design review rituals, on-call practice
  • Influences how the team approaches user focus, accessibility, and mission outcomes in technical decisions
Example outcomes
  • An architecture decision that improved system reliability, performance, or security posture for a capability
  • A platform service redesigned to support multiple consuming teams without rework
  • A security review process the team adopted that caught issues earlier and made ATO milestones smoother
  • An on-call and incident response practice that reduced mean time to recovery on a critical service
  • A modernization slice — a legacy component replaced or refactored — that unblocked further investment
  • A junior engineer who grew measurably under their mentorship into independent ownership

Staff

Improve engineering quality and velocity across multiple teams or programs through shared systems, standards, and direction.

Scope: what you decide and own
Sets technical direction across workstreams or teams; owns shared systems, standards, or initiatives that span teams (e.g., API standards, platform infrastructure, security review processes)
Relationships: working with stakeholders
Influences program-level technical strategy; resolves architectural and organizational blockers across teams and stakeholder groups
Reach: what changes because of you
Other engineering workstreams move faster or improve in quality because of the systems, standards, or direction they put in place
Calibration question
Would coordination, technical standards, or cross-team delivery slip if this person stepped away?
What success looks like
  • Sets technical direction across workstreams, teams, or contracts — not just within one
  • Identifies systemic technical issues that no single team would see and addresses them
  • Owns shared systems, standards, or initiatives — API standards, platform infrastructure, security review processes, observability conventions, network architecture patterns
  • Resolves cross-team architectural disagreements and unblocks delivery
  • Influences program-level technical strategy with client leadership
  • Mentors engineers across teams and helps Seniors grow into cross-team thinking
  • Establishes engineering practices that other workstreams adopt
Example outcomes
  • A shared API standard or platform service adopted by multiple delivery teams that reduced duplicate work
  • A CI/CD or infrastructure-as-code pattern rolled out across programs that cut deployment time or reduced incidents
  • A cross-team security review or compliance program that smoothed ATO across multiple systems
  • A modernization strategy across multiple workstreams that resolved architectural disagreements and set a shared direction
  • A network architecture standard that enabled consistent connectivity and segmentation across hybrid environments

Principal

Reshape how clients approach part of their mission through engineering, and help Skylight grow as an engineering organization.

Scope: what you decide and own
Reframes technical problems and influences mission-level direction for the client in their area; contributes meaningfully to Skylight's growth
Relationships: working with stakeholders
Trusted technical authority for client leadership; represents Skylight externally in their engineering domain through speaking, publishing, or community leadership
Reach: what changes because of you
The client adopts a different technical approach to part of its mission because of their work; new opportunities open for Skylight
Calibration question
Would the client's approach to its mission or Skylight's growth trajectory in engineering be different if they hadn't been here?
What success looks like
  • Reframes technical problems and influences how the client thinks about part of its mission — modernization strategy, security posture, platform direction, or service-delivery approach
  • Identifies major opportunities to improve government service delivery through engineering and brings clients along
  • Aligns client technical leadership around architectural or operational direction
  • Guides major tradeoffs across programs — build versus buy, modernization sequencing, security and compliance investment
  • Contributes to Skylight's Engineering practice area through hiring, leveling, craft standards, and developing Staff-level engineers
  • Contributes to Skylight's growth through proposals, expanded scope with existing clients, or opening new engineering opportunities
  • Represents Skylight externally through speaking, publishing, open source, or community leadership in their engineering domain
Example outcomes
  • A modernization approach the client adopted across multiple programs after a Principal-led technical assessment
  • A platform or shared-services strategy that changed how an agency invests in technology across its portfolio
  • A security or compliance framework adopted across a client's organization that meaningfully changed its risk posture
  • A successful proposal or contract expansion where the Principal's engineering credibility was a decisive factor
  • An engineering hiring bar, craft standard, or technical career framework adopted across Skylight

We’re hiring!

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