Python Engineer; Drivers & Connectors

You like being the person who makes everything talk to everything else. Databases, frameworks, dashboards, message buses – you see them as pieces of one big puzzle, and you actually enjoy figuring out how they all fit together.

In this role, that puzzle is a distributed, SQL-first time-series database used to power serious, real-world workloads. Your job is to make it feel like a first-class citizen in the tools engineers already love: SQL Alchemy, pandas, Dask, Kafka, Flink, Airflow, Superset, Grafana, Fivetran, Tableau – and the next thing that hits Hacker News tomorrow.

Sometimes that means building or extending a driver (JDBC, Python / SQL Alchemy, PG wire, DB-API). Sometimes it’s adding the missing dialect, fixing the weird edge case, or nudging a project to treat this database properly instead of “just Postgres-ish”.

You won’t be handed a neat backlog of tickets and a product owner telling you exactly what to do. You’ll be handed a problem like “make this database work beautifully with X” and expected to go figure out the SDK, the APIs, the rough edges, and ship something robust, documented, and maintainable. Half the time you’ll be inside our own drivers and internal tools (CLI, Admin UI, migration tools), the other half you’ll have your head in someone else’s codebase, negotiating with their community on issues and PRs.

If you like the idea of spending your days in public repos, working directly with very experienced engineers, and being that jack‑of‑all‑trades who quietly makes the ecosystem “just work”, you’ll probably enjoy this.

You’ll be good at this if:

• You’re comfortable in Python and Java, and curious enough to dive into Rust, Go, C++, or whatever a new tool happens to use.
• You’ve built integrations, SDKs, drivers, or data pipelines that glue multiple systems together.
• You’re happy in SQL and relational databases and understand what “Postgre
  
  SQL compatible” really means in practice.
• You can debug gnarly issues across network boundaries, protocols, and versions without losing your cool.
• You’re not scared of open source – opening issues, sending PRs, reviewing feedback in public.

Nice signals:

• Contributions to open source (even small ones).
• Experience with Kafka, MQTT, AMQP, or similar message systems.
• Comfort with Docker/Kubernetes and how software actually runs in production.

Things you should know:

• This is a remote-first, European-timezone-friendly, VC-backed startup environment. Expect ownership, ambiguity, and impact rather than hand-holding.
• About half of your time will be on “existing stuff” – maintaining and improving current drivers and integrations – and half on new integrations and projects.
• Maintenance isn’t just bug-fixing; sometimes a new upstream version lands and suddenly you have a multi-week, genuinely interesting upgrade puzzle to solve.

If you’ve read this far and you’re thinking “this is literally how my brain works”, email me at anika with the subject line “Open Source My Ecosystem” and tell me your favourite integration you’ve ever built and why.