Data Integration Engineer (Open Source / SQL)

About the Role

Picture this: a data engineer opens their dashboarding tool, picks your database from the dropdown, wires up a view, and everything just works. No weird errors, no half-broken queries, no "ah, we only support Postgres 9.6". Or a developer installs a Python package, points their SQLAlchemy models at your cluster, and immediately starts crunching time‑series data with pandas and Dask. You're the person who makes those experiences feel effortless.

The product is a distributed time‑series database with a strong SQL and Postgres‑compatible surface area. The ecosystem team sits at the boundary between that and... basically everything else. One day you're deep in a JDBC driver, figuring out the right behaviour over the wire protocol. The next day you're tweaking a Fivetran or Kafka-based pipeline, or adding database‑specific logic into a BI tool, stream processor, or orchestration framework like Airflow or Flink.

You'll work closely with founding-level engineers on projects that live in public Git repositories, not behind closed doors. That means real code ownership, real discussions with maintainers, and real users depending on what you build. Sometimes you'll be the person quietly keeping critical drivers healthy across versions. Sometimes you'll be the one scouting a new project in the AI/data tooling explosion, deciding if it makes sense to integrate, and then building that bridge.

If you enjoy variety, context-switching between languages, tools, and communities, and you like the idea of being "T-shaped" with one or two strong languages but enough breadth to pick up whatever's needed, this is your playground.

You probably:

• Write solid code in Python and/or Java and can get productive in new languages with documentation and a bit of stubbornness.
• Understand HTTP, JDBC, DB-API, and database wire protocols enough to debug at the edges when things get weird.
• Are comfortable with SQL, schemas, indexes, and performance basics.
• Have shipped integrations, connectors, or SDKs, not just greenfield web apps.
• Can read someone else's code, reverse-engineer what's going on, and then improve it.

Bonus points for:

• Experience with Kafka, MQTT, AMQP, or similar systems, and their brokers.
• Having maintained software in containers (Docker, Kubernetes) in real environments.
• Any evidence that you enjoy public collaboration (blog posts, talks, OSS, even thoughtful issue threads).

What you get:

• A fully remote role with flexible hours, anchored around European time zones.
• A welcoming, international team that values autonomy, craftsmanship, and honest communication.
• Competitive salary, equity, and perks like flexible holidays and learning budgets.
• The chance to watch a VC-backed company grow from early-stage into whatever comes next -- and help steer its ecosystem along the way.

How to Apply:

If this sounds like the kind of work that would keep you interested for the next few years, email me at anika@seekr.inc with the subject "I Speak Fluent Glue Code" and include one link to a public repo, PR, or issue you're proud of.