Remote Backend + Front End + Health + Python + Senior Jobs

Steadily is a Series A insurtech startup for landlords.  We've grown from 5 to 30 people over the last year to match demand, and the technical/product challenges have gotten really interesting. We're hiring a senior engineer with experience building web apps and service oriented architecture to help us build the core of our stack.  \n\nAt Steadily, our purpose is to give landlords fast, affordable insurance and amazing customer service so they’re confident they’ll have the coverage they need on a rainy day. Because of our technology and service, our customers love being insured by us, even when they have a claim. \n\n**Why join us**\n\n* You'll be in good company. Not to toot our own horn too much, but the founders are solid engineers. Our VP of Engineering helped grow a company from 15 people to more than 2,000 software engineers. The President has gone through YC twice and has two previous exits.\n* We pay top of market with competitive base salaries and equity\n* You’ll be hands-on with everything, from coding in python to influencing product roadmaps\n* We're growing fast and are well-funded (Series A, $30M)\n\n**What you'll build**\n\n* Rating engines for calculating how much an insurance policy should cost\n* Combine property intelligence for external sources to estimate how likely a property is to flood, catch on fire, or get vandalized\n* A mobile experience for people to buy insurance that is so simple/intuitive that your least-tech savvy relative with a flip-phone could use it without help e.g. pass the Mom Test\n* Claim app that uses phone camera and sensors to document the damage smartly\n\n**Ideal background**\n\n* Experienced: This isn't your first rodeo. There's no specific minimum number of years requirement, but we expect you to be able to dive into a complex codebase without too much spin-up. Past experience as a team lead is definitely a plus.\n* Builder: You like the product-side of engineering and have thoughtful opinions on what the user experience should be. You're not the type of engineer who wants a fully-fleshed out spec thrown over the wall for you to code.\n* Pragmatic: Let's say you have a tradeoff to make: Option A is to ship something fast using an off-the-shelf API on AWS; you won't learn that much and it only solves 80% of the problem, but it'll only take a few days. Option B is to invest about two weeks building a new library and internally-hosted service that perfectly solves the problem; as a bonus you can share it on Github and give a presentation about it at PyCon. If you choose Option A 10/10 then you'll be at home here.\n* Specific languages: We don't really care if you've worked in our stack before as long as you're happy to learn it. If you're sharp enough to be on this team, you're sharp enough to learn any language or framework quickly.\n\n**Our stack**\n\n* Python 3\n* Django\n* Postgres\n* Heroku (with full CI pipeline)\n* Redis / Celery\n* Kafka\n\n**Compensation**\n\n* At least $150,000/year\n* We believe in paying top-of-market to attract the best person for each role.\n* However, the compensation package is usually the second reason people choose to join a startup. The primary reason is they want to experience the growth that comes from pouring your heart and soul into building something that people love. That’s what we do.\n\n**Things to consider**\n\nThis won't be easy. We work extremely hard to sustain our execution velocity and have sky-high expectations of each other. This fact is itself a huge reward: getting to work with other individuals as stellar as you.\n\n**Benefits**\n\n* Paid Time Off\n* Health Insurance\n* 401k / HSA / FSA\n\n**We’re excited to meet you!** \n\nPlease mention the words **CLARIFY MUTUAL SKATE** when applying to show you read the job post completely (#RMjE2LjczLjIxNi4xMzc=). 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 $150,000 — $250,000/year\n \n\n#Location\nWorldwide

Commit is building the remote-first community for software developers. We’re VC-backed, fully remote, and looking for [Entrepreneurial Startup Engineers](https://medium.com/commit-engineering/what-is-an-entrepreneurial-engineer-and-how-are-they-different-from-other-engineers-af4ebcf88047) to join Commit.\n\nIf you’re selected, we’ll pay you during our 3-month program to explore roles at startups you’re passionate about as a Commit Engineering Partner.\n\n**Join the most ambitious startups, without going through their normal technical interviews.** We take care of all the friction, so you can focus on finding the right fit. We hire you directly into Commit, pay you to find the right startup from a pool of vetted opportunities, let you **skip those startups' normal interviewing processes**, and then you get to test out startups for three months at a time until you find the perfect fit. \n\nMembers of our program have access to all of our Engineering Partners from past cohorts. Curious about what it's like to join a startup as the first engineer? Looking for the best course on Rust? Running into an issue with Terraform that you can't solve? Someone in the community has been in your shoes and can help. We’re run by engineers for engineers.\n\nIf you have 4+ years of experience in software engineering, and ambitions of excellence in your craft, [apply on our website](https://www.commit.dev) or by emailing [email protected]!\n\n**Read more about us:**\n* [Our guide](https://www.notion.so/commitdev/Commit-for-Software-Engineers-6608ecb933da4e449c16e67834ec0f4e) to what you can expect from our program\n* What it means to be a Commit Engineering Partner on [our blog](http://commit.dev/blog)\n* [Our website](http://www.commit.dev)\n\n**What we offer during the program:**\n* Full time paid employment as an Engineering Partner\n* Extended health and dental plan, for you and for your family\n* The right equipment to do your best work\n* Access to your own career coach and a mentor for your job search\n* We provide 15 vacation days, on top of statutory holidays while you're part of the Engineering Partner program. There is no limit on Sick Days or Personal Days\n* Invitation-only events with technical leaders. We’ve been lucky to have guests like Katie Wilde (VP Engineering @ Buffer), Armon Dadgar (CTO @ Hashicorp), Gokul Rajaram (board member at DoorDash, Coinbase, Pinterest and The Trade Desk) and many others join us for private learning sessions.\n\nWe are a fully distributed, remote-first community, launched in Vancouver, with posts in Toronto, San Francisco, Mexico City, and more. We raised $6M from Accomplice, Inovia Capital and Jason Warner (former CTO @ GitHub).\n\n**About you:**\n* 4+ years of experience in software engineering (non-internship)\n* Experience working on SaaS, marketplace, consumer or infrastructure\n* Entrepreneurial mindset\n* Growth-oriented attitude \n* Ambitions of excellence in your craft. Some of our past EPs have grown into CTOs, principal engineers, and/or joined companies as the first engineer\n\n**Our Preferred Tech Stack**\n* FE: One/some of: Vue.js, React, Redux\n* BE: One/some of: Golang, Node.js, Ruby/Rails, Python/Django (MVC!)\nWe believe that language is a tool. **It’s more important that you have experience with one or more modern coding languages, than that you have experience with any particular language itself.**\n\n**You might also have:**\n* Understanding of basic DevOps: AWS, GCP, Docker, Kubernetes/Terraform, CI/CD\n* Understanding of RESTful APIs and/or GraphQL\n* Understanding of cloud-native distributed systems and microservices\n\n**Our Commitment to Diversity & Inclusion:**\nAs an early-stage startup, we know it’s critical to build inclusive processes as a part of our foundation. We are committed to building and fostering an environment where our employees feel included, valued, and heard. We strongly encourage applications from Indigenous peoples, racialized people, people with disabilities, people from gender and sexually diverse communities and/or people with intersectional identities.\n\nSo what are you waiting for? Join Commit, unlock the next phase of your career. [Apply on our website](https://www.commit.dev) or by emailing [email protected]!\n\n\n\n \n\nPlease mention the words **SPOT FINISH COIL** when applying to show you read the job post completely (#RMjE2LjczLjIxNi4xMzc=). 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 $110,000 — $140,000/year\n \n\n#Location\nNorth America

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