Skip to main content
Loading
loadingbar
Loading, Please wait..!!

Principal Engineer – Data & Microservices Architecture

  • Principal Engineer – Data & Microservices Architecture job type Posted on: Nov 18, 2026
  • Principal Engineer – Data & Microservices Architecture experience level GTN Technical Staffing
  • Principal Engineer – Data & Microservices Architecture employment type Dallas, Texas
  • Principal Engineer – Data & Microservices Architecture employment type Onsite
  • Principal Engineer – Data & Microservices Architecture salary Full-time

Point Apply Here APPLY LATER

Curious about compensation?

Explore the historical salary trends, average pay, and estimated compensation for Principal Engineer – Data & Microservices Architecture roles in Texas.

View Salary Guide →

Job Title :

Principal Engineer – Data & Microservices Architecture

Job Type :

Full-Time

Job Location :

Dallas Texas United States

Remote :

No

Jobcon Logo Job Description :

Principal Engineer – Data & Microservices Architecture
Location: Dallas, TX (Hybrid – 2 days onsite / 3 days remote)

Overview

Lead production data architecture, microservices design and algorithmic engineering for complex cloud applications. Own reliable data ingestion, quality, lineage, distributed service contracts and scalable scoring/ranking capabilities. This is a hands-on software engineering role, not a data science research position.

Key Responsibilities

  • The data architecture across the platform — how data is modelled, stored, moved and made available
  • Ingestion pipelines for domain, clinical, behavioral and third-party reference data
  • Data modelling for both transactional access and analytical workloads
  • Data quality: validation, reconciliation, anomaly detection, and the processes that catch bad values before they reach a user
  • Provenance and versioning — knowing which data produced which output, and reproducing it later
  • The foundation for advanced analytics: health, behavioural and domain data combined into a longitudinal view
  • Data retention, lineage and access patterns that respect the regulated boundary
  • Service and data boundaries — which service owns which data, and what the contract looks like
  • Event design and schema evolution across independently deployed services
  • Patterns for consistency, idempotency and reconciliation in a distributed estate
  • Performance of cross-service data access, including caching and precomputation
  • The scoring and ranking engine matching catalog items to individual individualized targets
  • Translating clinical and healthal logic into deterministic, testable computation
  • Performance engineering — scoring a live catalogue within interactive latency budgets
  • Explainability: scores are shown to users and reviewed by clinical staff, and must be defensible
  • Correctness infrastructure — test harnesses, regression suites, validation against expert review

Required Experience

  • Built and operated production data architecture at a platform level, not only individual pipelines
  • Strong data modelling across transactional and analytical workloads
  • Production experience with ingestion, transformation and validation pipelines
  • Practical experience with data quality problems and the tooling to catch them
  • Comfortable across relational and non-relational stores and clear on when each applies
  • Microservices architecture experience in production — decomposition, data ownership, contracts, versioning
  • The failure modes that appear when data moves across many independently deployed services
  • Event-driven architecture and message-broker experience
  • Azure cloud depth
  • 8+ years engineering experience including substantial algorithmic work
  • Strong computer science fundamentals — complexity analysis, data structures, optimization
  • Production experience taking algorithmic work from specification to running system
  • Performance profiling of computation-heavy code paths
  • Expert-level C# / .NET, or comparable depth with clear ability to transfer
  • Fluent with AI-assisted development, including using it to explore approaches and generate test cases

Preferred Experience

  • Health, biomarker or longitudinal patient data experience
  • Behavioural or engagement analytics
  • Recommendation systems, search or ranking infrastructure
  • Feature stores or ML data infrastructure
  • health, biology or health-science exposure

Role distinction: This position focuses on production data, distributed architecture and algorithms; the Health Platform Principal focuses on regulated healthcare integration and compliance architecture.

Jobcon Logo Position Details

Posted:

Nov 18, 2026

Reference Number:

2567612

Employment:

Full-time

City:

Dallas

Job Origin:

RECRUITCRM_ORGANIC_FEED

Share this job:

  • linkedin

Jobcon Logo
A job sourcing event
In Dallas Fort Worth
Aug 19, 2017 9am-6pm
All job seekers welcome!

Principal Engineer – Data & Microservices Architecture    Apply

Click on the below icons to share this job to Linkedin, Twitter!

Principal Engineer – Data & Microservices Architecture
Location: Dallas, TX (Hybrid – 2 days onsite / 3 days remote)

Overview

Lead production data architecture, microservices design and algorithmic engineering for complex cloud applications. Own reliable data ingestion, quality, lineage, distributed service contracts and scalable scoring/ranking capabilities. This is a hands-on software engineering role, not a data science research position.

Key Responsibilities

  • The data architecture across the platform — how data is modelled, stored, moved and made available
  • Ingestion pipelines for domain, clinical, behavioral and third-party reference data
  • Data modelling for both transactional access and analytical workloads
  • Data quality: validation, reconciliation, anomaly detection, and the processes that catch bad values before they reach a user
  • Provenance and versioning — knowing which data produced which output, and reproducing it later
  • The foundation for advanced analytics: health, behavioural and domain data combined into a longitudinal view
  • Data retention, lineage and access patterns that respect the regulated boundary
  • Service and data boundaries — which service owns which data, and what the contract looks like
  • Event design and schema evolution across independently deployed services
  • Patterns for consistency, idempotency and reconciliation in a distributed estate
  • Performance of cross-service data access, including caching and precomputation
  • The scoring and ranking engine matching catalog items to individual individualized targets
  • Translating clinical and healthal logic into deterministic, testable computation
  • Performance engineering — scoring a live catalogue within interactive latency budgets
  • Explainability: scores are shown to users and reviewed by clinical staff, and must be defensible
  • Correctness infrastructure — test harnesses, regression suites, validation against expert review

Required Experience

  • Built and operated production data architecture at a platform level, not only individual pipelines
  • Strong data modelling across transactional and analytical workloads
  • Production experience with ingestion, transformation and validation pipelines
  • Practical experience with data quality problems and the tooling to catch them
  • Comfortable across relational and non-relational stores and clear on when each applies
  • Microservices architecture experience in production — decomposition, data ownership, contracts, versioning
  • The failure modes that appear when data moves across many independently deployed services
  • Event-driven architecture and message-broker experience
  • Azure cloud depth
  • 8+ years engineering experience including substantial algorithmic work
  • Strong computer science fundamentals — complexity analysis, data structures, optimization
  • Production experience taking algorithmic work from specification to running system
  • Performance profiling of computation-heavy code paths
  • Expert-level C# / .NET, or comparable depth with clear ability to transfer
  • Fluent with AI-assisted development, including using it to explore approaches and generate test cases

Preferred Experience

  • Health, biomarker or longitudinal patient data experience
  • Behavioural or engagement analytics
  • Recommendation systems, search or ranking infrastructure
  • Feature stores or ML data infrastructure
  • health, biology or health-science exposure

Role distinction: This position focuses on production data, distributed architecture and algorithms; the Health Platform Principal focuses on regulated healthcare integration and compliance architecture.

Loading
Please wait..!!