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

We are looking for an experienced full-stack developer, focused on web front ends, to lead the development of our product UI/UX.\n\nWe are a cyber security company with many projects. Our web application is multi-lingual and has a base set of functionality, but we have an extensive list of features in our goal of a peerless product. Architecting, understanding our extensive backend, and implementing these features would be about 95% of your time. Additionally, our marketing websites are multi-lingual and updated about once per month, so this would be about 5% of your time.\n\n**Join PolySwarm.**\n\nWe're developing innovative solutions to age-old information security problems - and we need your help.\n\nPolySwarm is a marketplace that produces crowdsourced threat intelligence (malware detection today, more tomorrow).\n\nNo one has done this before. We'll get things wrong - that's okay! With your help, we'll get fewer things wrong, identify mistakes earlier, and improve processes to prevent future missteps.\n\nYou're in on the ground floor - you'll have a say in what we do and how we do it. By joining PolySwarm, you'll be joining a dynamic team on the bleeding edge of information (computer) security and blockchain - answering questions few have thought to ask.\n\n**If You Are:**\n\n* proficient with Docker, JavaScript, HTML, CSS/SASS, React, Redux, NodeJS, TypeScript, Jest, Storybook, and Gatsby\n* familiar with Python or Rust\n* experienced at creating clean/efficient UX\n* experienced building both the front-end and back-end for a web application\n* experienced with payment processing services like Stripe\n* experienced at developing/managing a multi-language web application\n* proficient in speaking/writing/reading English\n\n... then we are interested in you.\n\n\n**The Ideal Candidate Is**\n\nindependently motivated & self-directing\nintrospective: able to identify weak spots / problem areas in our existing processes or code and suggest / implement solutions\ninterested in creating a top quality user experience for both desktop and mobile users\ninterested in web application development\nhas an eye for design\n\n**We Offer**\n\n* Competitive salaries\n* Excellent health, dental, vision coverage\n* Paid vacation days\n* Flexible work hours - we have core hours on weekdays during US business hours, but outside of scheduled meetings, but if you want to start a little earlier or stay a little later, that's up to you..\n* Remote Ok - You can work remotely, or you can work from one of our offices when this Covid-19 stuff ends.\n* Powerful servers, laptops, desktops - whatever you need to be most productive!\n\n*In compliance with federal law, all persons hired will be required to verify identity and eligibility to work in the United States and to complete the required employment eligibility verification form upon hire.*\n\n**About PolySwarm**\n\nThe PolySwarm Team is made up of InfoSec veterans with decades of experience in government and industry. We’re driven to improve the threat intelligence landscape for ourselves, our clients and the industry at large. By providing robust incentives that align participants’ interest with continued innovation, PolySwarm will break the mold of today’s iterative threat intelligence offerings.\n\nAll PolySwarm (Co-)Founders are also members of Narf Industries, LLC, a boutique information security firm specializing in tailored solutions for government and large enterprises. Narf operates on the cutting-edge of InfoSec, blockchain and cryptographic research, having recently completed a blockchain-based identity management project for the Department of Homeland Security (DHS) as well as several cutting-edge partial homomorphic encryption projects on behalf of DARPA.\n\nFor more about the team and the team's advisers, head over to: https://polyswarm.io/team\n\nTo see our web application, head over to: https://polyswarm.network\n\n**What we use:**\n\n* Docker\n* JavaScript\n* HTML\n* CSS/SASS\n* React, Redux\n* NodeJS\n* TypeScript\n* Templating\n* Gatsby\n* Storybook\n* Jest\n\n**Bonus skills:**\n\n* Python\n* Rust\n* Elastic Search\n* Kibana\n* Kubernetes \n\nPlease mention the words **DEPUTY BURGER CENTURY** when applying to show you read the job post completely (#RMjE2LjczLjIxNi4xNDY=). 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 $100,000 — $150,000/year\n \n\n#Location\nWorldwide

[Screenly](https://www.screenly.io), the digital signage company, seeks a front-end developer to help create a great looking modern and responsive web UI. We're looking for people who are ambitious and deeply driven to make a difference. \n\nYour ability as a general pragmatic developer and fast learner is what truly matters to us. As you read the specifics below, keep in mind that the skill we are looking for is more in the lines of "awesome solver of challenges" than any one specific skill. \n\nYou would work on JavaScript, React, HTML, CSS and other techs to create a great looking modern and responsive web driven UI. You would also be ready to dive into the Django and Python underpinnings and add the bits necessary for a great user experience. Underneath it all you'll find Postgres, Redis and a good heaping of Docker and Kubernetes.\n\nWhile this ad is about the front-end, we're really into jacks-of-all trades. We think in a startup every team member needs to be nimble and flexible enough to do whatever it takes to deliver the product.\n\nYou can expect to work with a small full time team of crafty developers, in a quickly growing startup. We're a remote only shop so you'll never feel you're not in the loop due to not being in the main office -- there is no main office! You can learn more about how we work [here](https://www.screenly.io/blog/2016/11/23/how-we-work-at-screenly/).\n\nYou like:\n\n* Detail oriented front-end work.\n* Great UX.\n* Occasionally fun UI and UX.\n* Unit tests, integration tests, ui tests, test tests, every test.\n* Python.\n\nThis is a full-time position. We only hire individuals, not agencies. Please state the square root of twenty five in your cover letter. You will need to attend a daily meeting and a fortnightly video planning meeting (around 16:00 UTC) so please don’t apply if that doesn’t work for you or you can’t work a semi-regular 5-day week. Hours are very flexible, but you do have to be around often enough for the rest of the team to interact with you. \n\nPlease mention the words **MUCH THUMB HUMOR** when applying to show you read the job post completely (#RMjE2LjczLjIxNi4xNDY=). 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, CSS, Python, Front End, Docker, Developer, Digital Nomad and Video jobs that are similar:\n\n $60,000 — $125,000/year\n