Build the data stack with us.
Four people building the tool we kept wishing existed. We write Python, YAML, and a fair amount of SQL. We have strong opinions about data contracts and dimensional modeling. Two open roles — both would have real ownership from day one.
Join the team
Two roles, both meaningfully leveled. We don't hire for headcount.
Senior Data Engineer
We need a senior engineer who can own the connector ecosystem, work on distributed transform scheduling, and help define our approach to Snowflake and BigQuery query pushdown optimization.
What you'll do
- Own and extend the connector library (Snowflake, BigQuery, Redshift, DuckDB)
- Improve the agentic routing engine: schema change detection, routing decisions, rollback
- Work closely with Wei on pipeline reliability and observability
- Help define API contracts between semantic layer and ETL components
You have
- 5+ years working with cloud data warehouses (Snowflake or BigQuery strongly preferred)
- Experience with dbt, Airflow, or similar modern data tooling
- Python proficiency — can write clean, testable data engineering code
- Strong opinions about schema design and data contracts
Developer Advocate
We need someone who can write clear technical content for data engineers, build community around the semantic layer concept, and help practitioners get productive with Loomkindle faster.
What you'll do
- Write practitioner-focused blog posts, tutorials, and documentation
- Build and manage our community (Discord, GitHub Discussions)
- Represent Loomkindle at data engineering conferences (dbt Coalesce, DataCouncil, etc.)
- Collect developer feedback and route it to the engineering team
You have
- Background as a data engineer or analytics engineer (you know what a DAG is)
- Strong technical writing — you can explain a YAML config without losing the reader
- Community-building experience (forums, Slack, Discord, GitHub)
- Comfortable on stage or in front of a camera
What it's like here
Small team, real ownership
Four people. No layers. You'll own actual product surface area from day one, not tickets in a backlog owned by someone else.
Write, deploy, learn
We ship weekly. Small PRs, fast iteration, postmortems when things break. No "sprint planning" theater.
Seattle HQ or fully remote
Our HQ is in South Lake Union. If you're in Seattle, great. If you're remote, we keep async-first communication that doesn't require you to move your timezone.
Don't see a fit? Say hi anyway.
We keep a short list of people we'd like to work with in the future. If you're a data engineer who shares our obsessions, reach out.