Remote Analytics + API + Engineer + Front End + Video Jobs

# 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 (#RMjE2LjczLjIxNi4xMDA=). 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

Hi! 👋 We’re searching for a **Senior Frontend Engineer** to join our engineering team at vidIQ.\n\nWe’re a diverse team from around the world on a mission to empower video creators to share their stories with everyone. Help us shape new products and deliver simple, valuable features to our awesome customers.\n\nWe’re a remote company and our team works from wherever they want. That means you must be self-motivated to succeed. If that sounds great to you and you’re interested in empowering video creators, keep reading!\n\n**About you**\n\nYou’ll be a good fit for this role if the following are true:\n\n*  **You love building things.** Frontend development is full of helpful tools, libraries, and patterns, and you enjoy using these to build products people will love. You like new challenges and strive to ship new features to customers on a regular basis.\n*  **You love to learn.** You enjoy keeping up with the latest trends in frontend space. If a project uses a framework that’s new to you, you dive into the docs and tutorials to figure it out.\n*  **You act like an owner.** When bugs appear, you document and fix them. When projects are too complex, you work with others to refine the scope until it’s something you believe can be built in a reasonable amount of time and maintained in the long run.\n*  **You care about code quality.** You believe simple is better and strive to write code that is easy to read and maintain. You consider edge cases and write tests to handle them. When you come across legacy code that is difficult to understand, you add comments or refactor it to make it easier for the next person.\n*  **You understand balance.** Great products must balance performance, customer value, code quality, dependencies, and so on. You know how to consider all of these concerns while keeping your focus on shipping things.\n*  **You over-communicate by default.** If a project is off-track, you bring it up proactively and suggest ways to simplify and get things going. You proactively share status updates without being asked and strive to keep things as honest and transparent as possible.\n\nNote that we’re looking for someone with a minimum of 3 years of professional programming experience for this role.\n\n**Possible projects**\n\nAs part of our growing Frontend Team, you’ll work with team members at all levels to improve our existing products and develop new ones.\n\nThe tools we use most heavily right now are React and Redux, though we still have Backbone and Flux in some of our codebases as well. We use Asana for project management, GitHub for code reviews, and Slack for daily communication. We also have a Rails API and consider it a major bonus if you have experience working on Rails applications.\n\nSome projects you may work on include:\n\n* Research and implement architectural changes such as migrating our browser extension to Redux.\n* Help measure the effectiveness of certain features by building a reusable analytics module to use across our products.\n* Improve our brand and usability by reskinning components according to our new design system.\n* Make our products more reliable by writing integration tests to cover common user workflows.\n* Simplify our API interactions by building a GraphQL layer.\n* Level up the team by reviewing code and suggesting improvements.\n\nOver time, you’ll become an owner of some areas of our codebase and have the freedom to improve them as you see fit.\n\n**About vidIQ**\n\nWe believe everyone has something to share with the world and we’ve been empowering video creators to tell their stories for more than 6 years. We want to be the best platform for video creators. Everything we do is to build trust with our customers and help them improve at their craft.\n\nvidIQ is a small, remote team in many different time zones. We currently have team members stretching from California all the way to Kiev!\n\nA few of the perks of working here include:\n\n* A generous vacation policy. Take time away when you need it.\n* A flexible work schedule. You decide which hours to work and we expect an average commitment of 40 hours per week.\n* Support for professional development. If there’s a relevant course or conference you’re interested in, we’ll pay for it.\n* Annual retreats! You can expect to travel once per year for a company gathering. (We visited Portugal together last year!)\n\n**How to apply**\n\nTo save time and get to know you better, we ask a few questions as part of the application. Following that, our hiring process involves a phone conversation, a technical interview (no live coding, don’t worry!), and a short paid project.\n\nWhen you apply, you’ll hear back from us even if we don’t think there’s a good fit. We know you’re putting effort into your application and feel that deserves respect.\n\nPlease note that the preferred time zone for this role is between UTC-5 and UTC+2, but we're willing to be flexible for the right person.\n\nvidIQ does not work with recruiting agencies and strives to work with each candidate one-on-one through the hiring process. We will respect your time availability if you are currently employed.\n\nvidIQ provides equal employment opportunities to all employees and applicants, regardless of race, color, religion, age, sex, national origin, disability status, or sexual orientation.\n\nIf you think you would thrive in this environment, we would love to hear from you. Please apply! \n\nPlease mention the words **FRAME PUDDING SIREN** when applying to show you read the job post completely (#RMjE2LjczLjIxNi4xMDA=). 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, CSS, HTML, Senior, Engineer, Front End, Video, API and Travel jobs that are similar:\n\n $60,000 — $120,000/year\n \n\n#Location\nWorldwide

\nButo is looking to add an enthusiastic engineer to its team of experts. We run an enterprise online video platform on AWS which is used by high-profile clients including Rugby Football Union, Mitsubishi, Deloitte and the Financial Conduct Authority. Our platform serves over 5 million API requests per day and processes over 2 million analytics metrics, on top of delivering terabytes of video content.\n\n\nYou’ll be joining the platform at an exciting time in its growth cycle, so we’re looking for someone with flexibility and a ‘can-do’ attitude who’s ready to learn more; somebody with a GitHub profile that shows they really love what they do.\n\n\nWe run an Agile ship with GitHub continuous integration and continuous deployment.\n\n\nWe love the AWS platform and use it heavily:\n\n\n\n* EC2, ECS, RDS, ElastiCache, DynamoDB, Lambda, S3, SQS…\n\n\n\n\n\nOur technology stack consists of:\n\n\n\n* React and Angular (Gulp + Grunt)\n\n* PHP (ZF, Cilex and Silex)\n\n* NodeJS\n\n* Docker (we love Docker) on AWS Linux\n\n* MySQL and MongoDB\n\n* Memcache and Redis\n\n* Slack, GitHub, CircleCI, NewRelic, Docker Hub, Zendesk…\n\n\n\n\n\nThis is your chance to work on a cutting-edge, high availability, high technology platform with a small, tight-knit team of awesome engineers.\n\n\nOh, did we mention we offer remote working? Although the role will require an initial period of working from our Birmingham office, all of our dev team work from home, and come into the office about once every two weeks. \n\n#Salary and compensation\n No salary data published by company so we estimated salary based on similar jobs related to Junior, Front End, Developer, Digital Nomad, Video, Angular, API and Engineer jobs that are similar:\n\n $65,000 — $120,000/year\n
\n\n#Benefits\n 💰 401(k)\n\n🌎 Distributed team\n\n⏰ Async\n\n🤓 Vision insurance\n\n🦷 Dental insurance\n\n🚑 Medical insurance\n\n🏖 Unlimited vacation\n\n🏖 Paid time off\n\n📆 4 day workweek\n\n💰 401k matching\n\n🏔 Company retreats\n\n🏬 Coworking budget\n\n📚 Learning budget\n\n💪 Free gym membership\n\n🧘 Mental wellness budget\n\n🖥 Home office budget\n\n🥧 Pay in crypto\n\n🥸 Pseudonymous\n\n💰 Profit sharing\n\n💰 Equity compensation\n\n⬜️ No whiteboard interview\n\n👀 No monitoring system\n\n🚫 No politics at work\n\n🎅 We hire old (and young)\n\n

\nButo is looking to add an enthusiastic engineer to its team of experts.  We run an enterprise online video platform on AWS which is used by high-profile clients including Rugby Football Union, Mitsubishi, Deloitte and the Financial Conduct Authority. Our platform serves over 5 million API requests per day and processes over 2 million analytics metrics, on top of delivering terabytes of video content.\n\nYou’ll be joining the platform at an exciting time in its growth cycle, so we’re looking for someone with flexibility and a ‘can-do’ attitude who’s ready to learn more; somebody with a GitHub profile that shows they really love what they do.\n\nWe run an Agile ship with GitHub continuous integration and continuous deployment.\n\nWe love the AWS platform and use it heavily:\n\n\n* EC2, ECS, RDS, ElastiCache, DynamoDB, Lambda, S3, SQS...\n\n\n\n\nOur technology stack consists of:\n\n\n* React and Angular (Gulp + Grunt)\n\n* PHP (ZF, Cilex and Silex)\n\n* Node.js\n\n* Docker (we love Docker) on AWS Linux\n\n* MySQL and MongoDB\n\n* Memcache and Redis\n\n* Slack, GitHub, CircleCI, NewRelic, Docker Hub, Zendesk...\n\n\n\n\nThis is your chance to work on a cutting-edge, high availability, high technology platform with a small, tight-knit team of awesome engineers.\n\n\nOh, did we mention we offer remote working?  All of our dev team work from home, and come into the Birmingham office about once every two weeks. \n\n#Salary and compensation\n No salary data published by company so we estimated salary based on similar jobs related to Front End, Developer, Digital Nomad, Video, Angular, API and Engineer jobs that are similar:\n\n $60,000 — $120,000/year\n
\n\n#Benefits\n 💰 401(k)\n\n🌎 Distributed team\n\n⏰ Async\n\n🤓 Vision insurance\n\n🦷 Dental insurance\n\n🚑 Medical insurance\n\n🏖 Unlimited vacation\n\n🏖 Paid time off\n\n📆 4 day workweek\n\n💰 401k matching\n\n🏔 Company retreats\n\n🏬 Coworking budget\n\n📚 Learning budget\n\n💪 Free gym membership\n\n🧘 Mental wellness budget\n\n🖥 Home office budget\n\n🥧 Pay in crypto\n\n🥸 Pseudonymous\n\n💰 Profit sharing\n\n💰 Equity compensation\n\n⬜️ No whiteboard interview\n\n👀 No monitoring system\n\n🚫 No politics at work\n\n🎅 We hire old (and young)\n\n