Remote Docker + Engineer + Engineering + GraphQL + JavaScript Jobs

# About you\nWe’re hiring a Senior Backend Engineer to join our founding team. You will be working closely with our CTO, Charles, to shape both the team and platform while we get ready for scale.\n\nYou like to get things right, a **pragmatic perfectionist** who will continuously shape our application architecture and make it ready to scale. You understand the right balance between code readability, simplicity, development speed, performance, and maintainability.\n\nYou're well-acquainted with typed NodeJS codebases and preferably these technologies: GraphQL, Apollo, Postgres, Redis, ElasticSearch, Docker, AWS, websockets, microservices, event-driven architecture.\n\n# About TheyDo\nTheyDo is the first B2B SaaS platform that allows organizations to redefine cross-team collaboration around the customer journey. It is journey management, the product management way. We help teams make sense of a complex data graph and connect it with various data sources. Our users are design-savvy and we strive to make a highly polished and performant experience for them.\n\nWe're a passionate team from 🇳🇱🇵🇱🇺🇦🇸🇪. Founded in 2019, TheyDo has raised $2M+ from top investors to start a movement. We are about to double our team and get our product ready for scale while we are onboarding customers across all continents.\n\nWe're on a mission to help organisations scale Journey Management. Today, everyone is in the Experience business; here, we help our customers to make better and faster customer-centric decisions across the entire customer experience. Thanks to TheyDo, everyone agrees, including the customer.\n\nRead more on our [website](https://www.theydo.io).\n\n# Your assignment\nYour top priority is shaping the architecture of our product and getting it ready for scale. You'll work on the technically ambitious projects we have planned. Some examples currently on our roadmap:\n\n* 🔌 Realizing integrations with a wide ecosystem - Miro, Jira, Google Analytics, etc.\n* 📈 Implementing microservices and extend our event-driven architecture.\n* ⏱️ Enabling version control on all user data.\n* ⚡ Improving real-time collaborative functionality. Using fractional indexing, last-writer wins and other techniques to provide a superior user experience.\n\nAs a founding team member, you will get a chance to set the foundations of our engineering culture. You will help articulate our engineering principles and help set the long-term roadmap.\n\n# We're looking for\n* An ambitious engineer with several years of experience working on back-end architecture and design. Previous experience at a scaled product is a big plus.\n* An engineer who wants to be at the foundation of a fast-growing team.\n* A product-minded engineer that wants to understand how people use our product and why.\n* An asynchronous worker who organises and documents their work.\n* A clean coder who writes well-structured and maintainable code.\n\n# What we offer\n* Remote position, for 4-5 days per week, across flexible working hours.\n* Collaborate with zealous colleagues having 20+ years of experience working in the field.\n* A unique opportunity to shape a product and our growing team.\n* Regular off-sites/company outings with the TheyDo team.\n* Competitive compensation and equity package.\n* As many vacation days as you need, we expect you to take at least 25.\n* Professional development reimbursement.\n* Mental health and wellness reimbursement.\n* Paid parental leave.\n* Home office & technology reimbursement.\n\nTo summarise, we value work-life harmony backed by personal freedom under responsibility. Sounds like fun? We're looking forward to having you join our team. ✨🙏\n\n# Our engineering team\nThe engineering team consist of: a CTO, three full-stack engineers, one back-end engineer, and one QA tester. We aim for a relaxed environment within the ambitious goals we have for our product.\n\nOur server is fully typed and built using NodeJS, Apollo, Redis, Postgres, ElasticSearch and more modern technologies. Our web application is also typed and uses VueJS, Apollo, WebSockets, and more. Other tooling currently includes AWS, Storybook, Cypress, Jest, Stripe, and WorkOS.\n\nA typical day at the office for an engineer includes; flexibility to organise your own time, no set hours, ample time for deep work, as few mandatory meetings as possible, plenty of pair programming with team members to get your code just right, reviewing pull requests, and running around in our virtual office.\n\nView our team members [here](https://www.theydo.io/about-us).\n\n# Our culture\nTheyDo's culture is 'Do' rather than 'Talk'. Better ask for forgiveness instead of permission, no one will be accused of trying. We try to keep things simple because complexity slows us down.\n\nIt's not about the time spent, but the outcome achieved. It's up to everyone to map, plan and interact in the best way to get the most out of their day, week, and sprint. Always with an open mindset because we never know when and where the next great idea will surface.\n\nBeing remote we nourish and cherish connectivity, so no one feels alone or left out. We don't have long lines of communication or decisions because hierarchies and silos are part of the past and we love to shape the future. In our virtual office, you can just walk up to your team to have a quick chat, get work done or simply say hello. We motivate everyone to find their own work/life balance. Whether you choose to work asynchronously or synchronously it's up to you as long it fits you and your team.\n\nTheyDo is an equal employer treating everyone as equals. We value diversity and individuality. We think long term and strive to hire the best match for each role, no matter your background. \n\nPlease mention the words **SHIELD TOPIC SLIDE** when applying to show you read the job post completely (#RMjE2LjczLjIxNi4xOTg=). This is a feature to avoid spam applicants. Companies can search these words to find applicants that read this and see they're human.\n\n \n\n#Salary and compensation\n $80,000 — $130,000/year\n
\n\n#Benefits\n ⏰ Async\n\n
\n\n#Location\nEurope

# 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)](https://www.notion.so/splitgraph/Senior-Software-Engineer-Backend-2a2f9e278ba347069bf2566950857250)\n\n[Senior Software Engineer - Frontend (mainly TypeScript)](https://www.notion.so/splitgraph/Senior-Software-Engineer-Frontend-6342cd76b0df483a9fd2ab6818070456)\n\n→ [**Apply to Job**](https://4o99daw6ffu.typeform.com/to/ePkNQiDp) ← (same form for both positions)\n\n# What is Splitgraph?\n## **Open Source Toolkit**\n\n[Our open-source product, sgr,](https://www.github.com/splitgraph/splitgraph) 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](https://softwareengineeringdaily.com/2020/11/06/splitgraph-data-catalog-and-proxy-with-miles-richardson/)\n\n- Watch our co-founder Artjoms present [Splitgraph at the Bay Area ClickHouse meetup](https://www.youtube.com/watch?v=44CDs7hJTho)\n\n- Read our HN/Reddit posts ([one](https://news.ycombinator.com/item?id=24233948) [two](https://news.ycombinator.com/item?id=23769420) [three](https://news.ycombinator.com/item?id=23627066) [four](https://old.reddit.com/r/datasets/comments/icty0r/we_made_40k_open_government_datasets_queryable/))\n\n- [Read our blog](https://www.splitgraph.com/blog)\n\n- Read the slides from our early (2018) presentations: ["Docker for Data"](https://www.slideshare.net/splitgraph/splitgraph-docker-for-data-119112722), [AHL Meetup](https://www.slideshare.net/splitgraph/splitgraph-ahl-talk)\n\n- [Follow us on Twitter](https://ww.twitter.com/splitgraph)\n\n- [Find us on GitHub](https://www.github.com/splitgraph)\n\n- [Chat with us in our community Discord](https://discord.gg/eFEFRKm)\n\n- Explore the [public data catalog](https://www.splitgraph.com/explore) 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](https://www.python.org/) for the backend.** Our [core open source](https://www.github.com/splitgraph/splitgraph) tech is written in Python (with [a bit of C](https://github.com/splitgraph/Multicorn) 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](https://docs.pytest.org/en/stable/), [mypy](https://github.com/python/mypy) and [Poetry](https://python-poetry.org/) to help us write quality software.\n\n- **[TypeScript](https://www.typescriptlang.org/) for the web stack.** We use TypeScript throughout our web stack. On the frontend we use [React](https://reactjs.org/) with [next.js](https://nextjs.org/). For data fetching we use [apollo-client](https://www.apollographql.com/docs/react/) with fully-typed GraphQL queries auto-generated by [graphql-codegen](https://graphql-code-generator.com/) based on the schema that [Postgraphile](https://www.graphile.org/postgraphile) creates by introspecting the database.\n\n- [**PostgreSQL](https://www.postgresql.org/) 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](https://www.splitgraph.com/docs/publishing-data/push-data) so users can push Splitgraph images to it using [sgr](https://www.github.com/splitgraph/splitgraph), and `cloud-db` where we store the schemata that Postgraphile uses to autogenerate the GraphQL server.\n\n- [**PL/pgSQL](https://www.postgresql.org/docs/current/plpgsql.html) and [PL/Python](https://www.postgresql.org/docs/current/plpython.html) 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](https://www.graphile.org/postgraphile/functions/). 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](https://postgrest.org/en/v7.0.0/) for auto-generating a REST API for every repository.** We use this excellent library (written in [Haskell](https://www.haskell.org/)) to expose an [OpenAPI](https://github.com/OAI/OpenAPI-Specification)-compatible REST API for every repository on Splitgraph ([example](http://splitgraph.com/mildbyte/complex_dataset/latest/-/api-schema)).\n\n- **Lua ([luajit](https://luajit.org/luajit.html) 5.x), C, and [embedded Python](https://docs.python.org/3/extending/embedding.html) for scripting [PgBouncer](https://www.pgbouncer.org/).** 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](https://www.docker.com/) 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](https://www.gnu.org/software/make/manual/make.html) and** [docker-compose](https://docs.docker.com/compose/) **for development.** We use [a highly optimized Makefile](https://www.splitgraph.com/blog/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](https://www.nomadproject.io/) for deployment and [Terraform](https://www.terraform.io/) 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](https://airflow.apache.org/) for job orchestration.** We use it to run and monitor jobs that maintain our catalog of [40,000 public datasets](https://www.splitgraph.com/blog/40k-sql-datasets), or ingest other public data into Splitgraph.\n\n- **[Grafana](https://grafana.com/), [Prometheus](https://prometheus.io/), [ElasticSearch](https://www.elastic.co/), and [Kibana](https://www.elastic.co/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](https://mattermost.com/) 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](https://matomo.org/) 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](https://www.metabase.com/) and [Splitgraph](https://www.splitgraph.com) for BI and [dogfooding](https://en.wikipedia.org/wiki/Eating_your_own_dog_food)**. 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](https://www.zoom.us) for video calls, [Miro](https://miro.com/) for brainstorming, [Notion](https://www.notion.so) for documentation (you're on it!), [Airtable for workflow management](https://airtable.com/), [PivotalTracker](https://www.pivotaltracker.com/) for ticketing, and [GitLab for dev-ops and CI](https://about.gitlab.com/).\n\n- **Other fun technologies** including [HAProxy](http://www.haproxy.org/), [OpenResty](https://openresty.org/en/), [Varnish](https://varnish-cache.org/), 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](https://mattermost.com/) and have video calls on Zoom. We brainstorm with [Miro](https://miro.com/) and organize with [Notion](https://www.notion.so).\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**](https://4o99daw6ffu.typeform.com/to/ePkNQiDp)\n\nIf you have any questions or concerns, feel free to email us at [[email protected]](mailto:[email protected]) \n\nPlease mention the words **DESERT SPELL GOWN** when applying to show you read the job post completely (#RMjE2LjczLjIxNi4xOTg=). This is a feature to avoid spam applicants. Companies can search these words to find applicants that read this and see they're human.\n\n \n\n#Location\nWorldwide

# Lead Product Engineer - Core Experience\nSegment is building the future of how companies manage their constantly increasing volume of customer data. We help our customers collect data from a variety of sources, combine and understand that data, and ultimately act on it to give their users a better experience.\nImagine you want to answer a question that is core to your business — maybe you changed the pricing on your product and you want to understand if that’s driving revenue or creating churn and customer confusion. In order to properly answer that question, you would need data from your payment processor, your CRM, and telemetry data from your application. In the past, business teams have had to wait for developers to build ETL pipelines to move data from one place to another. This is painful, time-consuming, and doesn’t keep up with the pace of the customer needs. Segment allows you to get all of this data in one place, automatically, and start using it immediately rather than spending time building data pipelines.\n## Who we are:\nWe're a small distributed team of full-stack engineers based in San Francisco, Vancouver and the world 🌎 who love to ship high-quality code.\nFrom collecting data through [analytics.js](https://github.com/segmentio/analytics.js), to building powerful tools for data governance, to implementing algorithms that can handle complex billing scenarios at scale, to optimizing Sign Up conversion, the Product Engineering team is focused on creating fantastic user experiences.\nWe're looking for talented engineers that are passionate about building world-class experiences that delight our customers.\n## How we work:\n- 💅 We enjoy building UIs in React so much that we created our own internal components library.\n- 🛠️ We believe in using the best tool for the job. We write customer facing features using React, NodeJS and GraphQL. Our write-heavy traffic services are written with Go and leverage multiple data storage solutions.\n- 🚢 We deploy our code multiple times per day. We "semver" everything :)\n- 🎤 We love conferences. (An engineer spoke in 4 different countries last year!)\n- 👯 We love open source: https://open.segment.com\n- 📈 We’re proud of the code we write, but we’re not dogmatic about methodologies or techniques. We believe building the "right thing" is more important than building things "right".\n\n## Who we're looking for:\nYou can turn complex business requirements into working software that our customers love to use.\n- You're proud of the code you write, but you're also pragmatic.\n- You know when it is time to refactor, and when it's time to ship.\n- You're focused, driven and can get challenging projects across the finish line.\n- You're empathetic, patient and love to help your teammates grow.\n- You have experience running apps in production and take software engineering practices seriously. You write meaningful tests and understand the value of great logging, proper monitoring and error tracking.\n\n## A few projects you could be working on:\n- We collaborated closely with our BizOps and Design team to rebuild all parts of our billing experience, from the customer’s first visit, to building a pricing simulator tool, to implementing algorithms that can handle complex billing scenarios at our scale.\n- We’re building an [open-source version](https://github.com/segmentio/evergreen) of our UI library that saves our engineers multiple hours of work every week. Think pixel-perfect implementations by default 😱 🎨.\n- We used a [HLL](http://antirez.com/news/75) to scale an analytics tool that handles thousands of requests / sec.\n- We're building powerful tools that help our customers protect the integrity of their data, and the decisions they make with it.\n\n## Requirements:\n- You can write both client side and server side JavaScript using the latest APIs and language features.\n- You have some familiarity with Golang or are excited to learn it.\n- Minimum of 3 years of industry experience in engineering or some cool projects on GitHub you think we'll love to check out.\n- You provide a deep understanding of the complexities involved in writing large single-page applications.\n- You show evidence of exposure to architectural patterns of high-scale web application (e.g., well-designed APIs, high volume data pipelines, efficient algorithms.)\nWe are an equal opportunity employer and value diversity at our company. We do not discriminate on the basis of race, religion, color, national origin, gender, sexual orientation, age, marital status, veteran status, or disability status. \n\nPlease mention the words **SWITCH TURTLE AUTO** when applying to show you read the job post completely (#RMjE2LjczLjIxNi4xOTg=). This is a feature to avoid spam applicants. Companies can search these words to find applicants that read this and see they're human.\n\n \n\n#Salary and compensation\n No salary data published by company so we estimated salary based on similar jobs related to JavaScript, React, Node, Golang, Engineer, GraphQL, Docker and Executive jobs that are similar:\n\n $65,000 — $120,000/year\n
\n\n#Benefits\n 🌎 Distributed team\n\n