Back to jobs

Senior Data Architect, Scientific Data Platform

Pay
Pay not listed
Work setting
Not stated
Employment
Full-time — employment source
Employment type in the employer’s posting: Full time
From the employer’s posting

What you’ll work on

Full posting
  • Define target state, service boundaries, and contracts for catalog and access paths

  • Own schemas and contracts for catalog records, subgraph boundaries, and data service views

  • Design access paths AI agents use to read data, with controls and provenance

  • Design pipelines keeping catalog, search index, and access views current, including backfill and recovery

  • Design modernization paths for legacy sources, including on-premises to hybrid or cloud moves

From the employer’s posting
the target state for discovery and access, and the path to it, are yours to define.
Own the schemas and contracts your areas depend on: catalog records, subgraph boundaries, data service views, and versioned event schemas.
Design the access paths AI agents use to read what they can, under what controls, and with what provenance.
Design the pipelines that keep the catalog, the search index, and the access views current as data arrives, from extractor output through backfill and recovery.
Design modernization paths for legacy sources that keep customers running through the transition, including moves from on-premises to hybrid or cloud.
Apply at Agilent Technologies

Posting record

Report an error
Status in our records
Live
First seen by us
Sep 25, 202658 days ago
Recorded sightings
139
Last seen by us
Nov 16, 2026

These dates show when we found the posting. Check the employer’s website to confirm it is still accepting applications.

How this job compares

Time since we first saw it

Day 58

Up longer than most. Similar jobs usually come down between day 8 and day 57.

At Agilent Technologies, jobs usually come down by about day 44.

From 9,995 similar postings that came down, and 26 of Agilent Technologies’s. Coming down is not always a hire.

Agilent Technologies is hiring

11 open jobs

Open jobs by the week we first saw them, last 12 weeks.

  • Hiring has slowed
  • Takes jobs down at a usual pace
  • 9% of open jobs were reposted
Hiring record

See how this role fits your experience

Add your resume and we’ll mark which of these tools you already use, and point out anything in the posting that could rule you out.

  • C#
  • Java
  • SQL
  • TypeScript
  • Elasticsearch
  • Kubernetes
  • Oracle
  • PostgreSQL
  • S3
  • SQL Server
Where the posting names them
What we work with: - .NET (C#) services, Angular front ends, and a federated GraphQL gateway - PostgreSQL by default, with Oracle and SQL Server across the installed base
- Has built and run data pipelines, including recovery and backfill. - Reads production code in a typed language (C#, Java, TypeScript, or similar) and can build a proof of concept. - Uses AI tools in daily architecture and data work (profiling and cleaning data, reading and generating code, drafting decision records) and can show the process: what you delegate, what you verify, and how.
- .NET (C#) services, Angular front ends, and a federated GraphQL gateway - PostgreSQL by default, with Oracle and SQL Server across the installed base - RabbitMQ for messaging and event-driven change discovery
- Has owned the architecture of a production system in at least one of these areas: data catalogs and metadata management (DataHub, OpenMetadata, or similar); search and indexing (Elasticsearch, OpenSearch, or similar); API or federated-query data access layers (Apollo Federation, or similar); or the data layer of a scientific, laboratory, or regulated application. - Writes SQL and reads execution plans in PostgreSQL or SQL Server. - Has built and run data pipelines, including recovery and backfill.
- Has defined architecture ahead of finalized standards and governance and can show which decisions held up and which had to change. - Has owned the architecture of a production system in at least one of these areas: data catalogs and metadata management (DataHub, OpenMetadata, or similar); search and indexing (Elasticsearch, OpenSearch, or similar); API or federated-query data access layers (Apollo Federation, or similar); or the data layer of a scientific, laboratory, or regulated application. - Writes SQL and reads execution plans in PostgreSQL or SQL Server.
- RabbitMQ for messaging and event-driven change discovery - Kubernetes and Helm alongside Windows installers for on-premises and hybrid customers, with S3-compatible object storage - Scientific data in proprietary instrument formats as well as vendor-neutral formats like Allotrope

Your next step

Complete your application on agilent.wd5.myworkdayjobs.com. The employer’s form will show what is required.

Applying through Workday

  • You create an account with each employer before you can upload anything. Every Workday employer has its own account, so one sign-up doesn’t carry over.
  • “Autofill with Resume” comes right after sign-in, before the My Information and My Experience steps. Check every field it fills in those steps, since that’s what recruiters see.
  • Your application status lives in that employer’s Candidate Home, under the same sign-in.

Already applied? Track this application

Job description

View original posting ↗

Job Description


Agilent instruments produce the measurements behind pharmaceutical quality control, food and environmental testing, and research labs worldwide. That data sits in dozens of software products, and we are building a platform that lets our products, our customers' workflows, and AI agents find and use it wherever it lives.
 

We are hiring a data architect to own the discovery and access side of that platform: how scientific data is registered and found, and how it is composed and served. The platform architecture is established; the target state for discovery and access, and the path to it, are yours to define.
 

You work under the Lead Data Architect, who owns cross-service standards and governance. Within your areas, the architecture decisions are yours; cross-service decisions go to the Lead with evidence, options, and a recommendation.
 

This is an architecture role with hands-on evidence: you decide the architecture for your areas, stay with engineering through implementation, and read the code, run the queries, and build the proof of concept when an argument needs one.
 

Your areas:

  • Data access. Your part of the federated GraphQL gateway, which the platform team owns how connected systems are represented on it, directly or through data services; the read layer that composes results across systems; and the application data services that expose access-controlled views of scientific data to products, workflows, and AI consumers.
  • Catalog and search. The catalog record model, how connected systems register their data and how that metadata is represented, search over it, and the path to richer indexes like vector and graph.
     

Access is the first-year priority; catalog work runs alongside as the first connectors land. File management, metadata extraction, and semantic standards are owned by other architects on the team. The data is scientific data created by software products: results, methods, samples, files. ERP, CRM, and other enterprise business systems are out of scope.


What you will do:

  • Establish how the catalog and access paths behave today and define the target state: service boundaries, contracts, integration patterns, and the path between the two.
  • Own the schemas and contracts your areas depend on: catalog records, subgraph boundaries, data service views, and versioned event schemas. Design them and make explicit which system is authoritative for each piece of information under the program's data governance rules, and version them so existing consumers keep working.
  • Design the access paths AI agents use to read what they can, under what controls, and with what provenance.
  • Review proposed integrations against your contracts and the program's participation requirements. Change your contracts when the evidence warrants and propose changes to the requirements.
  • Design modernization paths for legacy sources that keep customers running through the transition, including moves from on-premises to hybrid or cloud.
  • Set query and index performance targets for catalog and access paths.
  • Design the pipelines that keep the catalog, the search index, and the access views current as data arrives, from extractor output through backfill and recovery.
  • Work directly with engineering: clarify designs, evaluate implementation plans, review delivered work against the decisions.
  • Write the decision records and diagrams for your areas, and explain the tradeoffs to engineers, product managers, and business stakeholders.

What we work with:

  • .NET (C#) services, Angular front ends, and a federated GraphQL gateway
  • PostgreSQL by default, with Oracle and SQL Server across the installed base
  • RabbitMQ for messaging and event-driven change discovery
  • Kubernetes and Helm alongside Windows installers for on-premises and hybrid customers, with S3-compatible object storage
  • Scientific data in proprietary instrument formats as well as vendor-neutral formats like Allotrope
  • AI assistants in daily use

Qualifications


Required qualifications:

  • Has 8+ years in software engineering, data engineering, or architecture with distributed systems: service boundaries, APIs, and event-driven integration.
  • Has defined architecture ahead of finalized standards and governance and can show which decisions held up and which had to change.
  • Has owned the architecture of a production system in at least one of these areas: data catalogs and metadata management (DataHub, OpenMetadata, or similar); search and indexing (Elasticsearch, OpenSearch, or similar); API or federated-query data access layers (Apollo Federation, or similar); or the data layer of a scientific, laboratory, or regulated application.
  • Writes SQL and reads execution plans in PostgreSQL or SQL Server.
  • Has built and run data pipelines, including recovery and backfill.
  • Reads production code in a typed language (C#, Java, TypeScript, or similar) and can build a proof of concept.
  • Uses AI tools in daily architecture and data work (profiling and cleaning data, reading and generating code, drafting decision records) and can show the process: what you delegate, what you verify, and how.
  • Works across product, engineering, and business teams without direct authority.

Preferred qualifications:

  • Has delivered data products consumed by applications: APIs, views, or datasets that other software depends on.
  • Working knowledge of catalog, search, and data access beyond the area you have owned.
  • Laboratory informatics or regulated life sciences, including data integrity and audit trail expectations.
  • Architecture decision records, C4 or similar diagrams, and interface contracts.
  • Cloud integration patterns (identity, storage, messaging, managed data services) alongside on-premises deployment.

Additional Details

This job has a full time weekly schedule. It includes the option to work remotely.

Our pay ranges are determined by role, level, and location. Within the range, individual pay is determined by work location and additional factors, including job-related skills, experience, and relevant education or training. During the hiring process, a recruiter can share more about the specific pay range for a preferred location. Pay and benefit information by country are available at: https://careers.agilent.com/locations

Agilent Technologies Inc. is an equal opportunity employer. Qualified applicants will receive consideration for employment without regard to race, color, religion, sex, sexual orientation, gender identity, national origin, protected veteran status, disability or any other protected categories under all applicable laws.

Travel Required:

25% of the Time

Shift:

Day

Duration:

No End Date

Job Function:

R&D

About Agilent Technologies

People
About 18,100 in 2025, up 1% from the year before.Annual report (SEC Form 10-K)
Company
Listed as A.
H-1B visas
12 approved for new hires in fiscal 2025.US Citizenship and Immigration Services

Demand for Data Leadership roles

New Data Leadership postings at the employers we follow are up 8% over the last 6 weeks compared with the 6 before.

Weekly new Data Leadership postings at the same employers, from the week of August 17 to the week of November 9. The fewest in a week was 751, the most 1,165, and the latest week had 775.
August 17Last week

Each bar is one week of new postings. The darkest bars are the last 6 weeks.

Counted from the hiring pages we’ve followed for at least five weeks, so employers we add don’t look like growth. Updated weekly.

About the role

We file this job under Data Leadership, by the work the posting describes.

Data leaders run data teams or design how a company's data fits together. Managers hire, set priorities and answer for whether the data work pays off; architects choose the systems and the shape of the data.

Expect years of hands-on data work, experience leading people or projects, and the ability to explain tradeoffs to executives.

Unlike a senior engineer or analyst, most of a data leader's week goes to people, planning and decisions rather than building.

US government figures for computer and information systems managers

Median yearly pay, May 2025
$175,140
Expected change, 2025 to 2035
15.8% more jobsagainst 3.5% for all jobs

The government has no code for data leaders, so these figures are for the closest group, computer and information systems managers, which includes data processing and data operations managers.

Source: US Bureau of Labor Statistics, Occupational Employment and Wage Statistics (May 2025) and Employment Projections (2025 to 2035). Occupation code 11-3021.

Source details

View original posting ↗

Source notes

Source excerpts

Selected passages from the saved posting. Check the full description for conditions and exceptions.

Pay

No pay amount identified in the saved description.

Location & working pattern

Spain-Barcelona

- Review proposed integrations against your contracts and the program's participation requirements. Change your contracts when the evidence warrants and propose changes to the requirements. - Design modernization paths for legacy sources that keep customers running through the transition, including moves from on-premises to hybrid or cloud. - Set query and index performance targets for catalog and access paths.
More source context
- RabbitMQ for messaging and event-driven change discovery - Kubernetes and Helm alongside Windows installers for on-premises and hybrid customers, with S3-compatible object storage - Scientific data in proprietary instrument formats as well as vendor-neutral formats like Allotrope
Work authorization

No clear work-authorization passage found. Eligibility is unconfirmed.

Find answers in the posting

AI
How answers work

AI selects complete passages from this posting. Check them for conditions and exceptions.

Uses this posting and your question. No profile needed.