Software Engineer (Back End and Cloud) Role

About OPEN Data Jobs

OPEN Data Jobs (ODJ) is built to craft data careers. We connect high-potential data, AI, and software professionals with meaningful work on the cutting edge of the federal sector, and our aim reaches beyond any single opening: to help you understand your strengths, find the right role, and grow throughout your career.

ODJ is organized around Roles and Openings. A Role is a durable career type, such as Data Engineer or AI Engineer: it describes the work, the skills that count, and where the path can lead. An Opening is a specific position hiring right now, with a level, a location, and an application. Roles help you see where you fit; from there, there is more than one way to move.

Today, you can apply to any Opening that fits you through our secure application system. You can also register for a Role to express interest in that broader category of work. A Role registration is not an application to every future Opening.

The work

Software Engineers working on back-end and cloud systems build the services that enforce application behavior, connect systems, and move trusted work through production. They turn product and operational requirements into HTTP APIs, business logic, integrations, asynchronous workflows, and data-access components.

The work runs in containers, serverless functions, virtual machines, or managed cloud services. You design service boundaries and contracts, handle identity and authorization, validate inputs and dependencies, manage failure and retry behavior, and make the system observable through logs, metrics, and traces. You also test changes and automate delivery so the service can evolve without guesswork.

This role owns production service behavior, not just endpoint code. Back-end and cloud engineers work with front-end developers, data teams, security, quality engineering, and platform or DevSecOps teams to balance reliability, security, performance, maintainability, and cost.

What you'll build

· Secure HTTP APIs, service contracts, event handlers, and integration adapters.

· Back-end services in Python, Java, C#, JavaScript, TypeScript, Go, or comparable languages.

· Containerized, serverless, event-driven, and asynchronous cloud workloads.

· Authentication, authorization, validation, error handling, audit events, and dependency controls.

· Automated tests, delivery pipelines, operational dashboards, traces, alerts, and runbooks.

Who you are

You like making distributed behavior understandable. You can move quickly when learning or prototyping, then add the contracts, tests, controls, and operational evidence required for a production service.

You think beyond the happy path. You ask what happens when a dependency slows down, a message is delivered twice, an authorization check is missed, or a deployment needs to roll back. You communicate those tradeoffs clearly and share ownership across team boundaries.

What you bring

• · Strong software engineering experience in at least one back-end language and a modern web or service framework.
• · Experience designing, implementing, documenting, testing, and versioning HTTP APIs or event-driven interfaces.
• · Working knowledge of relational data, transactions, identity, authorization, secrets, validation, and secure dependency use.
• · Cloud experience with containers, serverless workloads, messaging, managed services, and automated delivery.
• · Ability to diagnose production behavior with logs, metrics, traces, tests, and clearly defined service expectations.
• Register for Software Engineer (Back End and Cloud) Role
• Click Apply below to register for Software Engineer (Back End and Cloud) Role.

Requirements

What openings may require

An opening may specify Python and FastAPI, Java and Spring, C# and.NET, Node.js, a cloud provider, container orchestration, infrastructure as code, or a particular identity and messaging stack. Some roles may emphasize Representational State Transfer (REST), OpenAPI descriptions, event processing, high-volume integrations, or systems with demanding audit and availability needs.

An AI-enabled opening may involve calling model APIs, serving retrieval-augmented generation workflows, exposing approved tools, recording citations or feedback, and adding latency, cost, safety, and quality signals to observability. The back-end engineer owns the secure and reliable application service around the model, while AI engineers own model behavior, evaluation, and AI-specific safeguards.