Full-Stack Developer 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

Full-Stack Developers deliver coherent features across the browser, service, and data layers. They can follow a user need through a React interface, an API, back-end logic, and a database change, then make sure those parts work together as one understandable system.

The role is defined by integration and end-to-end ownership, not by claiming equal depth in every specialty. You decide where logic belongs, keep contracts aligned, test the seams between layers, and work with deeper specialists when architecture, database operations, security, accessibility, or platform concerns exceed the feature team's scope.

You might spend one day improving a component and its state, another changing an API and schema migration, and another tracing a production failure across several services. Strong full-stack work reduces handoff gaps while preserving clear boundaries, review, and operational accountability.

What you'll build

· End-to-end features spanning React interfaces, back-end services, APIs, and relational data.

· Typed client and service contracts, validation rules, authentication flows, and authorization checks.

· Schema migrations, queries, service logic, component state, and accessible user interactions.

· Automated tests across unit, component, integration, contract, and browser layers.

· Delivery automation, diagnostic logging, metrics, traces, and runbooks for owned features.

Who you are

You are comfortable crossing layer boundaries while staying honest about risk and depth. You can diagnose whether a problem starts in the browser, the network contract, service logic, a query, or deployment configuration, and you bring in a specialist when the evidence points beyond your ownership.

You care about the complete user outcome. You keep interfaces and data contracts explicit, avoid hiding complexity in the wrong layer, and communicate changes so front-end, back-end, data, security, quality, and operations partners can review them effectively.

What you bring

• · Hands-on experience with React and TypeScript or JavaScript plus at least one modern back-end language and framework.
• · Ability to design and integrate HTTP APIs, application logic, relational schemas, SQL, and browser state.
• · Understanding of authentication, authorization, validation, transactions, accessibility, secure coding, and error handling.
• · Experience with automated tests, version control, code review, delivery pipelines, and production diagnostics.
• · Judgment about layer boundaries, service contracts, migration safety, maintainability, and when specialist review is required.
• Register for Full-Stack Developer Role
• Click Apply below to register for Full-Stack Developer Role.

Requirements

• An opening may specify React and Node.js, React and Python, a cloud platform, GraphQL, Representational State Transfer (REST), serverless services, containerized workloads, or a particular database and delivery stack. The exact balance among front-end, back-end, and data work should be stated in each opening.
• An AI-enabled product may require a full-stack developer to connect an approved model service to an accessible interface, retrieval or application data, feedback capture, and production observability. That work does not make the role the owner of model evaluation or AI governance; it makes the developer responsible for the feature's cross-layer implementation and user experience.