1

Overnight Government Software Engineering Jobs (NOW HIRING)

The government also imposes a level of bureaucracy that is typically not present in a company of ... Whether or not you have a CS or engineering degree (or any degree). * Whether or not you have ...

Company Description Nava partners with government to deliver mission-critical software that helps ... Whether or not you have a CS or engineering degree (or any degree). * Whether or not you have ...

The government also imposes a level of bureaucracy that is typically not present in a company of ... Whether or not you have a CS or engineering degree (or any degree). * Whether or not you have ...

Company Description Nava partners with government to deliver mission-critical software that helps ... Whether or not you have a CS or engineering degree (or any degree). * Whether or not you have ...

Our solutions support customers across corrections, government, critical infrastructure, and ... This role combines engineering leadership, software architecture governance, DevSecOps and release ...

Lead, develop, and scale the Software Engineering organization, focusing on meeting technical ... Saab is a federal government contractor and adheres to policies and programs necessary for ...

next page

Showing results 1-20

Overnight Government Software Engineering information

See salary details

$19

$49

$71

How much do overnight government software engineering jobs pay per hour?

As of Jul 16, 2026, the average hourly pay for overnight government software engineering in the United States is $49.58, according to ZipRecruiter salary data. Most workers in this role earn between $39.42 and $61.06 per hour, depending on experience, location, and employer.

What is the difference between Overnight Government Software Engineering vs Government Software Developer?

AspectOvernight Government Software EngineeringGovernment Software Developer
CredentialsBachelor's in Computer Science or related field; often requires security clearancesBachelor's in Computer Science or related field; security clearances may be preferred
Work EnvironmentNight shifts, often in secure government facilities or remoteDay shifts, in government offices or remote
Employer & Industry UsageGovernment agencies, federal or state, with project deadlines at nightGovernment agencies, involved in software development and maintenance
Common Search & Comparison IntentUnderstanding night shift roles in government softwareStandard government software development roles

Overnight Government Software Engineering typically involves working night shifts on government projects requiring security clearances, whereas Government Software Developers usually work during regular hours on similar projects. The main differences are work hours and shift requirements, with both roles sharing similar credentials and industry usage.

What cities are hiring for Overnight Government Software Engineering jobs? Cities with the most Overnight Government Software Engineering job openings:
What are the most commonly searched types of Government Software Engineering jobs? The most popular types of Government Software Engineering jobs are:
What states have the most Overnight Government Software Engineering jobs? States with the most job openings for Overnight Government Software Engineering jobs include:
Software Engineer

Software Engineer

Nava

Manhattan, NY • On-site

Full-time

Re-posted 26 days ago


Job description

Company Description
We're a team of engineers, designers, and product builders that were brought in to help fix HealthCare.gov in the winter of 2013. Since then, we've been working with the government to improve the services HealthCare.gov provides and reimagining future government services.
Job Description
Opportunities and Challenges
You will be working within the government ecosystem, which means working, sometimes closely, with other government contractors and civil servants. Working with people outside of your company means you'll likely encounter different working styles and cultural norms. At the same time, working as part of a larger team allows us to deliver on projects of larger scale and complexity.
The government also imposes a level of bureaucracy that is typically not present in a company of our size in the private sector. We operate in a regulated environment, where checks and compliance is built into the process of building software. This can make the path to production slower and some decisions, such as tools and processes, lie outside of our control. However, beyond writing code, finding and recommending ways to improve the way government software is built is one of the highest-leverage ways we help fulfill our mission.
You will be working with legacy systems. While our work is to build new systems with up-to-date technology, we have to do that within an existing ecosystem. Our work is building functional, resilient software for production. We don't build flashy prototypes that don't work for real people. This usually means getting to know legacy systems, often with poor documentation and unreliable narrators, and trying to determine how to replicate the systems' behavior or how to integrate with these systems. This is a great opportunity for engineers who enjoy software archaeology. If you care deeply about how software systems work over time, and building systems for longevity and resilience, this work is for you.
Who we're looking for
You are a reliable, experienced engineer who cares deeply about building software that makes a real difference in people's lives, and is keen to grapple with the complexities and trade-offs involved in building government software. You prefer using proven technologies to build well-designed systems that are scalable, performant, and secure.
You enjoy working on cross-functional teams, and collaborating with others, and you are able to direct yourself and work independently. You have empathy for the people who rely on your work, and you care about how your behavior affects others. You are humble and you value critical feedback and personal growth. You are comfortable receiving and giving kind, candid feedback.
Beyond coding ability, communication and teamwork skills are paramount. You must be able to communicate clearly and professionally in writing, in person, and through online tools, especially because we work with government stakeholders and other contractors.
You exhibit good judgment and able to adapt to new situations well. You may encounter situations that no one on your team or at Nava has encountered before. You take responsibility and are able to persist through ambiguity to get to a solution.
You will be working within the government ecosystem, which means working, sometimes closely, with other government contractors and civil servants. Working with people outside of your company means you'll likely encounter different working styles and cultural norms. At the same time, working as part of a larger team allows us to deliver on projects of larger scale and complexity.
The government also imposes a level of bureaucracy that is typically not present in a company of our size in the private sector. We operate in a regulated environment, where checks and compliance is built into the process of building software. This can make the path to production slower and some decisions, such as tools and processes, lie outside of our control. However, beyond writing code, finding and recommending ways to improve the way government software is built is one of the highest-leverage ways we help fulfill our mission.
You will be working with legacy systems. While our work is to build new systems with up-to-date technology, we have to do that within an existing ecosystem. Our work is building functional, resilient software for production. We don't build flashy prototypes that don't work for real people. This usually means getting to know legacy systems, often with poor documentation and unreliable narrators, and trying to determine how to replicate the systems' behavior or how to integrate with these systems. This is a great opportunity for engineers who enjoy software archaeology. If you care deeply about how software systems work over time, and building systems for longevity and resilience, this work is for you.
Who we're looking for
You are a reliable, experienced engineer who cares deeply about building software that makes a real difference in people's lives, and is keen to grapple with the complexities and trade-offs involved in building government software. You prefer using proven technologies to build well-designed systems that are scalable, performant, and secure.
You enjoy working on cross-functional teams, and collaborating with others, and you are able to direct yourself and work independently. You have empathy for the people who rely on your work, and you care about how your behavior affects others. You are humble and you value critical feedback and personal growth. You are comfortable receiving and giving kind, candid feedback.
Beyond coding ability, communication and teamwork skills are paramount. You must be able to communicate clearly and professionally in writing, in person, and through online tools, especially because we work with government stakeholders and other contractors.
You exhibit good judgment and able to adapt to new situations well. You may encounter situations that no one on your team or at Nava has encountered before. You take responsibility and are able to persist through ambiguity to get to a solution.
Qualifications
Requirements
  • 2+ years experience developing software in a team environment, preferably building medium to large-scale systems.
  • Experience with modern web development frameworks.
  • Experience designing and implementing application architectures and code that is highly scalable, available, and performant.
  • Self-directed, requiring minimal supervision.

Responsibilities
  • Collaborate with the product team, government stakeholders, and other contractors to build new systems and make improvements to existing systems.
  • Design and spec out major functionality.
  • Participate in planning and breaking down requirements into tasks.
  • Maintain production systems, handle on-call duties, and systematically debug and resolve issues when they occur.
  • Review code and give feedback on technical specs.
  • Make improvements by proposing new tools and practices.

Things that are not important to us
  • Whether or not you have a CS or engineering degree (or any degree).
  • Whether or not you have Github contributions. (It's great if you do, but we don't expect it.)
  • Whether or not you have worked at a well-recognized company.

Additional Information
We're a small team working to radically improve our government, so everyone that joins us has a direct impact on the direction and success of Nava. We are stewards - we hold a deep responsibility towards the systems that we work with. We are a community - we value collaboration both within our teams and with the many hardworking people within government. We offer generous benefits and equity.
We care deeply about diversity and inclusion at Nava. We are an equal opportunity employer and do not discriminate on the basis of race, religion, color, national origin, gender, sexual orientation, age, marital status, veteran status, or disability status.
Note that we participate in E-Verify and upon hire, will provide the federal government with your Form I-9 information to confirm that you are authorized to work in the U.S.
https://jobs.lever.co/nava/7f427c2d-c29f-4598-a449-65d3f4d8b2ee/apply