FeedbackIf you find a bug, or have feedback, put it here. Please no job applications in here, click Apply on the job instead.Thanks for the message! We will get back to you soon.

[Spam check] What is the name of Elon Musk's company going to Mars?

Send feedback
Open Startup
Health InsurancePost a job

find a remote job
work from anywhere

Get a  email of all new Remote Kibana + Python Jobs


πŸ‘‰ Hiring for a Remote Kibana + Python position?

Post a job
on the πŸ† #1 Remote Jobs board

Remote Health by SafetyWing

Global health insurance for freelancers & remote workers

This job post is closed and the position is probably filled. Please do not apply.
# We're building the Data Platform of the Future\nJoin us if you want to rethink the way organizations interact with data. We are a **developer-first company**, committed to building around open protocols and delivering the best experience possible for data consumers and publishers.\n\nSplitgraph is a **seed-stage, venture-funded startup hiring its initial team**. The two co-founders are looking to grow the team to five or six people. This is an opportunity to make a big impact on an agile team while working closely with the\nfounders.\n\nSplitgraph is a **remote-first organization**. The founders are based in the UK, and the company is incorporated in both USA and UK. Candidates are welcome to apply from any geography. We want to work with the most talented, thoughtful and productive engineers in the world.\n# Open Positions\n**Data Engineers welcome!** The job titles have "Software Engineer" in them, but at Splitgraph there's a lot of overlap \nbetween data and software engineering. We welcome candidates from all engineering backgrounds.\n\n[Senior Software Engineer - Backend (mainly Python)](\n\n[Senior Software Engineer - Frontend (mainly TypeScript)](\n\nβ†’ [**Apply to Job**]( ← (same form for both positions)\n\n# What is Splitgraph?\n## **Open Source Toolkit**\n\n[Our open-source product, sgr,]( is a tool for building, versioning and querying reproducible datasets. It's inspired by Docker and Git, so it feels familiar. And it's powered by PostgreSQL, so it works seamlessly with existing tools in the Postgres ecosystem. Use Splitgraph to package your data into self-contained\ndata images that you can share with other Splitgraph instances.\n\n## **Splitgraph Cloud**\n\nSplitgraph Cloud is a platform for data cataloging, integration and governance. The user can upload data, connect live databases, or "push" versioned snapshots to it. We give them a unified SQL interface to query that data, a catalog to discover and share it, and tools to build/push/pull it.\n\n# Learn More About Us\n\n- Listen to our interview on the [Software Engineering Daily podcast](\n\n- Watch our co-founder Artjoms present [Splitgraph at the Bay Area ClickHouse meetup](\n\n- Read our HN/Reddit posts ([one]( [two]( [three]( [four](\n\n- [Read our blog](\n\n- Read the slides from our early (2018) presentations: ["Docker for Data"](, [AHL Meetup](\n\n- [Follow us on Twitter](\n\n- [Find us on GitHub](\n\n- [Chat with us in our community Discord](\n\n- Explore the [public data catalog]( where we index 40k+ datasets\n\n# How We Work: What's our stack look like?\n\nWe prioritize developer experience and productivity. We resent repetition and inefficiency, and we never hesitate to automate the things that cause us friction. Here's a sampling of the languages and tools we work with:\n\n- **[Python]( for the backend.** Our [core open source]( tech is written in Python (with [a bit of C]( to make it more interesting), as well as most of our backend code. The Python code powers everything from authentication routines to database migrations. We use the latest version and tools like [pytest](, [mypy]( and [Poetry]( to help us write quality software.\n\n- **[TypeScript]( for the web stack.** We use TypeScript throughout our web stack. On the frontend we use [React]( with [next.js]( For data fetching we use [apollo-client]( with fully-typed GraphQL queries auto-generated by [graphql-codegen]( based on the schema that [Postgraphile]( creates by introspecting the database.\n\n- [**PostgreSQL]( for the database, because of course.** Splitgraph is a company built around Postgres, so of course we are going to use it for our own database. In fact, we actually have three databases. We have `auth-db` for storing sensitive data, `registry-db` which acts as a [Splitgraph peer]( so users can push Splitgraph images to it using [sgr](, and `cloud-db` where we store the schemata that Postgraphile uses to autogenerate the GraphQL server.\n\n- [**PL/pgSQL]( and [PL/Python]( for stored procedures.** We define a lot of core business logic directly in the database as stored procedures, which are ultimately [exposed by Postgraphile as GraphQL endpoints]( We find this to be a surprisingly productive way of developing, as it eliminates the need for manually maintaining an API layer between data and code. It presents challenges for testing and maintainability, but we've built tools to help with database migrations and rollbacks, and an end-to-end testing framework that exercises the database routines.\n\n- [**PostgREST]( for auto-generating a REST API for every repository.** We use this excellent library (written in [Haskell]( to expose an [OpenAPI]( REST API for every repository on Splitgraph ([example](\n\n- **Lua ([luajit]( 5.x), C, and [embedded Python]( for scripting [PgBouncer](** Our main product, the "data delivery network", is a single SQL endpoint where users can query any data on Splitgraph. Really it's a layer of PgBouncer instances orchestrating temporary Postgres databases and proxying queries to them, where we load and cache the data necessary to respond to a query. We've added scripting capabilities to enable things like query rewriting, column masking, authentication, ACL, orchestration, firewalling, etc.\n\n- **[Docker]( for packaging services.** Our CI pipeline builds every commit into about a dozen different Docker images, one for each of our services. A production instance of Splitgraph can be running over 60 different containers (including replicas).\n\n- **[Makefile]( and** [docker-compose]( **for development.** We use [a highly optimized Makefile]( and `docker-compose` so that developers can easily spin-up a stack that mimics production in every way, while keeping it easy to hot reload, run tests, or add new services or configuration.\n\n- **[Nomad]( for deployment and [Terraform]( for provisioning.** We use Nomad to manage deployments and background tasks. Along with Terraform, we're able to spin up a Splitgraph cluster on AWS, GCP, Scaleway or Azure in just a few minutes.\n\n- **[Airflow]( for job orchestration.** We use it to run and monitor jobs that maintain our catalog of [40,000 public datasets](, or ingest other public data into Splitgraph.\n\n- **[Grafana](, [Prometheus](, [ElasticSearch](, and [Kibana]( for monitoring and metrics.** We believe it's important to self-host fundamental infrastructure like our monitoring stack. We use this to keep tabs on important metrics and the health of all Splitgraph deployments.\n\n- **[Mattermost]( for company chat.** We think it's absolutely bonkers to pay a company like Slack to hold your company communication hostage. That's why we self-host an instance of Mattermost for our internal chat. And of course, we can deploy it and update it with Terraform.\n\n- **[Matomo]( for web analytics.** We take privacy seriously, and we try to avoid including any third party scripts on our web pages (currently we include zero). We self-host our analytics because we don't want to share our user data with third parties.\n\n- **[Metabase]( and [Splitgraph]( for BI and [dogfooding](**. We use Metabase as a frontend to a Splitgraph instance that connects to Postgres (our internal databases), MySQL (Matomo's database), and ElasticSearch (where we store logs and DDN analytics). We use this as a chance to dogfood our software and produce fancy charts.\n\n- **The occasional best-of-breed SaaS services** **for organization.** As a privacy-conscious, independent-minded company, we try to avoid SaaS services as much as we can. But we still find ourselves unable to resist some of the better products out there. For organization we use tools like [Zoom]( for video calls, [Miro]( for brainstorming, [Notion]( for documentation (you're on it!), [Airtable for workflow management](, [PivotalTracker]( for ticketing, and [GitLab for dev-ops and CI](\n\n- **Other fun technologies** including [HAProxy](, [OpenResty](, [Varnish](, and bash. We don't touch them much because they do their job well and rarely break.\n\n# Life at Splitgraph\n**We are a young company building the initial team.** As an early contributor, you'll have a chance to shape our initial mission, growth and company values.\n\n**We think that remote work is the future**, and that's why we're building a remote-first organization. We chat on [Mattermost]( and have video calls on Zoom. We brainstorm with [Miro]( and organize with [Notion](\n\n**We try not to take ourselves too seriously**, but we are goal-oriented with an ambitious mission.\n\n**We believe that as a small company, we can out-compete incumbents** by thinking from first principles about how organizations interact with data. We are very competitive.\n\n# Benefits\n- Fully remote\n\n- Flexible working hours\n\n- Generous compensation and equity package\n\n- Opportunity to make high-impact contributions to an agile team\n\n# How to Apply? Questions?\n[**Complete the job application**](\n\nIf you have any questions or concerns, feel free to email us at [[email protected]](mailto:[email protected])\n\n#Location\n🌏 Worldwide

See more jobs at Splitgraph

# How do you apply?\n\nThis job post is older than 30 days and the position is probably filled. Try applying to jobs posted recently instead.