Data Engineer

FlyLo Airlines, Inc.; San Francisco (CA); On-site; USD 120,000 - 170,000; Full time

Job summary

FlyLo Airlines, Inc. seeks a data engineer to turn flight, crew, bag, and guest events into a single trustworthy data warehouse. You’ll build scalable pipelines and ensure they’re tested, documented, and observable to operations.

You’ll define on-time metrics, protect personal data, and coordinate with morning briefs for Pacific hours, while using SQL, TypeScript, and Python to integrate a cloud warehouse and an orchestrator.

Qualifications

• Four or more years building data pipelines in production.
• Strong SQL and a typed language; we use TypeScript and Python.
• Experience with a cloud data warehouse and an orchestrator.
• A written point of view on privacy.
• Overlap with Pacific hours for the morning operations brief.

Responsibilities

• 01 Model flight, crew, bag, and guest events into one shared warehouse.
• 02 Keep pipelines tested, documented, and observable.
• 03 Agree definitions of on-time and satisfaction with operations and guest care.
• 04 Review any change that touches personal data before it ships.
• 05 Leave the platform smaller than you found it.

Skills

Data pipelines

SQL

Privacy viewpoint

On-time definitions

Operations collaboration

Tools

TypeScript

Python

Cloud warehouse

Orchestrator

Job description

You turn departures, bags, crew, and guest records into tables the airline can trust. The standard is a number someone can query at 06:00 without asking where it came from.

Responsibilities

• 01 Model flight, crew, bag, and guest events into one shared warehouse.

• 02 Keep pipelines tested, documented, and observable.

• 03 Agree definitions of on-time and satisfaction with operations and guest care.

• 04 Review any change that touches personal data before it ships.

• 05 Leave the platform smaller than you found it.

Requirements

• 01 Four or more years building data pipelines in production.

• 02 Strong SQL and a typed language. We use TypeScript and Python.

• 03 Experience with a cloud warehouse and an orchestrator.

• 04 A written point of view on privacy. We do not copy a field because we can.

• 05 Overlap with Pacific hours for the morning operations brief.