Database 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

Database Developers build the database-resident layer that makes application and analytical data correct, usable, and efficient. They write SQL, create views, functions, and procedures, evolve schemas, and design database objects that express rules close to the data.

The work is grounded in query behavior and transactional correctness. You read execution plans, select or revise indexes, remove avoidable work from a query, manage migrations, validate constraints, and test changes against realistic data volumes. You also consider permissions and the security consequences of views, functions, and other database objects.

Database Developers partner with software engineers, data engineers, data architects, analysts, and database administrators. The role is distinct from broad data-pipeline engineering and from operating the database service: its center of gravity is the code, structures, and access patterns inside the database.

What you'll build

· SQL queries, views, materialized views, functions, procedures, and database packages.

· Schema migrations, tables, constraints, indexes, partitions, and reference data.

· Tested data-access layers for applications, reports, integrations, and analytical workloads.

· Query-performance improvements based on execution plans, workload evidence, and data distribution.

· Version-controlled database changes, automated tests, deployment checks, and rollback plans.

Who you are

You enjoy making data behavior explicit. You can move from a business rule to a reliable database implementation, reason about edge cases and concurrency, and tell the difference between a query that merely runs and one that will remain safe and understandable.

You treat production data carefully. You review plans and evidence before tuning, test migrations before release, document assumptions, and collaborate across application and operations teams when a change crosses ownership boundaries.

What you bring

• · Strong SQL and relational database experience, including joins, set operations, transactions, constraints, and window functions.
• · Hands-on work with views, functions, procedures, schema migrations, and database version control.
• · Ability to interpret execution plans and improve queries, indexes, and data-access patterns.
• · Understanding of permissions, secure database coding, transactional integrity, and safe change practices.
• · Experience testing database changes and working with application, data, architecture, and operations teams.
• Register for Database Developer Role
• Click Apply below to register for Database Developer Role.

Requirements

What openings may require

An opening may center on PostgreSQL, Microsoft SQL Server, Oracle Database, a cloud warehouse, or another specific platform. It may require procedural SQL, partitioning, replication-aware development, change-data-capture integration, reporting workloads, or a particular migration and deployment toolchain.

Some AI-enabled applications use semi-structured data, vector-capable indexes, retrieval metadata, or feedback records in a database. Those needs may appear in an opening, but they do not redefine the role: the Database Developer remains accountable for database-resident logic, data integrity, query behavior, and safe schema change.