> Markdown version of [/jobs/ext/2635858-llm-data-engineer-citizen-only](https://www.wearedevelopers.com/jobs/ext/2635858-llm-data-engineer-citizen-only). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md). --- # LLM Data Engineer- Citizen Only - **Company:** Lightning Minds Inc. - **Location:** United States (Remote available) - **Contract:** Permanent contract - **Skills:** Application Programming Interfaces (APIs), Artificial Intelligence, Amazon Web Services, Amazon S3, Audit Trail, Clinical Data Repository, Continuous Integration, Data as a Services, Information Engineering, Data Files, Dicom, Identity and Access Management, SQL Databases, Fast Healthcare Interoperability Resources, Large Language Models, Apache Spark, Amazon Virtual Private Cloud (VPC), Containerization, AWS Glue, Health Level Seven International, AWS Data Analytics, Terraform, Docker - **Published:** August 6, 2026 - **Apply:** https://www.dice.com/job-detail/44c5795a-95d9-49fd-9427-4777627241a7 ## About the Role * AWS, Data Sets, data sources, data services with in AWS * Strong AI & LLM * Recent healthcare industry exp (HIPAA, hl7, etc) * LinkedIn Page * Strong communication * US Natural Citizen considered first and among all candidates., * Data engineering: Production-grade pipeline code, not notebooks. Strong testing discipline with developing deterministic, idempotent, re-runnable jobs. * AWS data stack: Deep hands-on experience with S3 (layout design, lifecycle policies, storage class economics at image scale), AWS Glue and/or Spark on EMR, Athena, Step Functions, Lambda, and AWS Batch. * SQL and data modeling: Complex temporal joins, point-in-time correctness, and the discipline to avoid label leakage in time-series clinical data. * Data quality and lineage: Validation frameworks, schema enforcement, and versioned datasets. * AWS security and governance: IAM policy design, KMS, VPC endpoints and PrivateLink, and working inside a HIPAA-eligible architecture with a BAA in place. Desirable Skills * Healthcare data formats and standards: DICOM, FHIR, HL7v2, OMOP CDM, and the practical realities of clinical coding (ICD, LOINC, RxNorm, SNOMED). * Medical imaging handling: pydicom, OpenSlide, and the basics of WSI pyramid structure and tiling. * Infrastructure as code (Terraform) development. * Containerization and CI/CD: Docker, ECR, and a mainstream CI system. * Enough familiarity with LLM APIs and multimodal payload construction. Nice to Have * Prior work on clinical prediction models or healthcare ML datasets (MIMIC, eICU, or equivalent institutional data). * Experience with AWS HealthImaging or HealthLake. * Familiarity with de-identification tooling and re-identification risk assessment. ## Description * Build ingestion and normalization pipelines for three distinct modality families: DICOM radiology studies, whole-slide pathology images, and tabular EHR extracts (labs, vitals, encounters, medication administration records). * Design the canonical benchmark record format, which is the intermediate representation that every task configuration and every model adapter reads from, so that full EHR record and image only variants of the same task are provably drawing from the same underlying case. * Solve the modality packaging problem: gigapixel pathology slides and multiseries radiology studies must be reduced to payloads that fit inside third-party API limits (48 images, 20 MB) without silently destroying diagnostic signal. You will build the tiling, region selection, downsampling, and compression strategies, and the provenance metadata that records exactly what was sent so results remain reproducible and defensible. * Construct the cohort and label pipelines behind the prediction tasks: timewindowed feature assembly for sepsis onset, survival horizon calculation for days-to-death, and longitudinal series construction for lab value trends. * Build the results store and analysis layer per-run, per-model, per-task scored outputs. * Enforce PHI handling discipline end to end: encryption at rest and in transit, least-privilege access, audit logging, deidentification where required, and clear boundaries around what leaves the VPC when a payload goes to a third-party API. ## Related Videos - [How we built an AI-powered code reviewer in 80 hours](https://www.wearedevelopers.com/videos/1511-how-we-built-an-ai-powered-code-reviewer-in-80-hours) - [Docker Compose: Rediscovered](https://www.wearedevelopers.com/videos/1978-docker-compose-rediscovered) - [ZEISS & Microsoft - Building the Next Generation Medical Ecosystem in the Cloud](https://www.wearedevelopers.com/videos/424-zeiss-microsoft-building-the-next-generation-medical-ecosystem-in-the-cloud) - [Coffee with Developers - Maria Apazoglou](https://www.wearedevelopers.com/videos/1209-coffee-with-developers-maria-apazoglou) - [Tips, Techniques, and Common Pitfalls Debugging Kafka](https://www.wearedevelopers.com/videos/838-tips-techniques-and-common-pitfalls-debugging-kafka) - [Docker build without Docker](https://www.wearedevelopers.com/videos/100114-docker-build-without-docker) ## Related Articles - [What Are Large Language Models?](https://www.wearedevelopers.com/magazine/304-what-are-large-language-models) - [Dev Digest 196: AI Killed DevOps, LLM Political Bias & AI Security](https://www.wearedevelopers.com/magazine/659-dev-digest-196-ai-killed-devops-llm-political-bias-ai-security) - [How to Become an AI Engineer](https://www.wearedevelopers.com/magazine/331-how-to-become-an-ai-engineer) - [How We Built a Worry-Free System That Runs for 10+ Years – And What We’d Do Again](https://www.wearedevelopers.com/magazine/751-how-we-built-a-worry-free-system-that-runs-for-10-years-and-what-we-d-do-again) - [Dev Digest 121 - AI goes offline](https://www.wearedevelopers.com/magazine/456-dev-digest-121-ai-goes-offline) - [Dev Digest 132 - Binging WADFlix?](https://www.wearedevelopers.com/magazine/473-dev-digest-132-binging-wadflix)