Pipeline engineering
Build batch and real-time pipelines for claims, clinical, member, and transaction data across cloud platforms.
AWS Glue · Azure Data Factory · Airflow · Kafka · Kinesis
Senior Data Engineer
Birochan Mainali
I build secure cloud data platforms for healthcare and financial services. With 6 years of experience across The Cigna Group, Cardinal Health, and Visa, I bring together batch and real-time pipelines, lakehouse architecture, and AI-powered data applications.

Correctness. Reliability.
Clear ownership.
Open to senior data engineering opportunities
Explore my experience01 / Expertise
My focus spans the full data lifecycle: how data arrives, what it means, who can trust it, and how it behaves in production.
Build batch and real-time pipelines for claims, clinical, member, and transaction data across cloud platforms.
AWS Glue · Azure Data Factory · Airflow · Kafka · Kinesis
Turn business definitions into reusable transformations, dimensional models, and semantic layers for enterprise analytics.
dbt · Snowflake · Redshift · Synapse · Dimensional modeling
Modernize legacy platforms with distributed processing and lakehouses that support data sharing across domains.
PySpark · Databricks · Delta Lake · Fabric OneLake · Medallion architecture
Protect sensitive healthcare and financial data with access controls, lineage, cataloging, and automated quality checks.
Microsoft Purview · AWS Lake Formation · Great Expectations · PHI / PII
Improve workload performance, control cloud costs, and shorten incident recovery with production monitoring and automation.
Terraform · CI/CD · Datadog · OpenTelemetry · Query optimization
Connect trusted data to enterprise search, document retrieval, fraud detection, and machine learning workflows.
RAG · Azure OpenAI · AWS Bedrock · LangChain · Vector databases
Technical toolkit
A practical stack across ingestion, transformation, storage, and delivery. The choice starts with the requirements.
Express business logic clearly and move data across system boundaries.
Coordinate dependencies, version transformations, and make changes testable.
Transform large datasets with deliberate choices about layout and compute.
Process events and transaction streams for timely analytics and scoring.
Model and serve data for analytical and operational access patterns.
Match storage, processing, access, and cost to the workload.
Keep development reproducible and production changes reviewable.
Make data quality, access, lineage, and platform health visible and actionable.
Build retrieval, NLP, feature engineering, and model delivery workflows on trusted data.
Give business teams consistent definitions and timely access to useful insights.
02 / Architecture
Reference designA reference pattern for an analytics platform, from source capture to trusted consumption. Specific services depend on latency, volume, governance, and cost requirements.
Capture source records with stable keys, ingestion timestamps, and explicit schema expectations.
Python · SQL · Airflow
Retain raw data and load metadata so changes can be traced and failed runs can be replayed.
Cloud object storage · Raw tables
Deduplicate, reconcile, and transform into models with a defined grain and tested business rules.
Spark · dbt
Expose curated datasets with documented definitions, ownership, access, and freshness targets.
Snowflake or Databricks
Design scenarios
Three common data problems and how I approach their design.
01 / Design note
Payments, refunds, and late events can tell different stories about the same reporting period.
My approach
Define the reporting grain and timezone, preserve event history, deduplicate by business key, and reconcile totals to the source before publishing.
02 / Design note
Teams lose trust when dashboards calculate the same business metric differently.
My approach
Agree on definitions with stakeholders, centralize transformation logic, test the model grain, and document how changes affect downstream consumers.
03 / Design note
A partial load or upstream schema change can leave a pipeline green while its data is incomplete.
My approach
Track load progress, validate completeness, quarantine unexpected records, and replay bounded partitions with idempotent writes and reconciliation.
03 / How I work
Senior engineering means making sound decisions, communicating the reasoning, and leaving systems that others can confidently operate.
Clarify who needs the data, what it means, and when it must arrive. Let those requirements drive the model and architecture.
Design retries, backfills, and recovery alongside the happy path. A successful rerun should restore correctness without duplicating data.
Choose batch or streaming, warehouse or lakehouse, and managed or custom tooling based on latency, cost, complexity, and team capacity.
Use design reviews, mentoring, clear ownership, and practical runbooks to make the platform easier for the next engineer to operate.
04 / Experience
Six years of building data platforms for healthcare, financial analytics, and payments, from daily pipelines to cloud modernization.
Designed a unified healthcare data platform across AWS, Azure, and Microsoft Fabric for claims, clinical, and member analytics.
Built financial data pipelines, streaming analytics, and machine learning workflows while contributing to a migration from Redshift and Hadoop to ADLS, Delta Lake, and Snowflake.
Contributed to an AWS customer data platform and payment analytics workflows, supporting internal product, marketing, and fraud detection teams.
05 / Credentials
University of North Texas
SAA-C03
DP-203
06 / Contact
I'm exploring senior data engineering roles with teams that value reliable platforms, thoughtful architecture, and clear ownership. Tell me about your team and the data challenges ahead.