About The Position

Masabi is building a governed data lakehouse on AWS to replace its current Elasticsearch-based data store. Ticketing, validation and payment services publish events to Kafka, which the new platform will make queryable for transit agencies, internal teams and APIs. The role is part of a small Data team of software engineers who design and build the platform, evaluate performance and cost, and document technical decisions. The work applies software engineering practices to a data platform, including tested services, CI checks and infrastructure as code. This is a fully remote contract role for people based in Poland.

Requirements

  • Solid software engineering fundamentals, including production coding, appropriate testing, and comfortable use of Git and CI pipelines.
  • Daily use of AI coding tools and careful verification of their output, especially for SQL, schema changes and data correctness.
  • Good SQL skills and some experience building or running data pipelines, with comfort working with data from source to query.
  • A solid grasp of data modelling.
  • Clear, confident written and spoken English.

Nice To Haves

  • Experience running a lakehouse or data warehouse in production.
  • Production experience with Kafka and schemas, ideally Avro.
  • Experience handling personal data, including privacy, retention and access control.
  • Comfort making design decisions and explaining trade-offs in writing and conversation.
  • Enjoyment of working closely with the teams that produce data, as well as the teams that use it.
  • JVM experience (Kotlin or Java), Apache Iceberg, Terraform, AWS Lake Formation or DuckDB.

Responsibilities

  • Build and run services that ingest Kafka topics into Apache Iceberg tables on AWS, including partitioning, compaction, deduplication and historical-data backfills.
  • Write clean, well-tested and maintainable code; use AI tools with good judgement; and contribute to code reviews and shared engineering standards.
  • Work with data-producing teams on data contracts, including Avro schemas with field-level classification, schema evolution rules and enforcing CI checks.
  • Build privacy and access controls into the platform, including personal-data erasure, retention and per-agency access control.
  • Build the query layer behind the customer-facing data API and provide access through Athena.
  • Evaluate technical approaches, measure performance and cost, and document technical choices.
  • Migrate existing dashboards, reports and finance extracts to the new platform.
  • Later, build a curated layer of shared metrics and business-ready datasets for BI tools and an AI analytics assistant.
© 2026 Teal Labs, Inc
Privacy PolicyTerms of Service