Remote Cloud + Docker + Front End + JavaScript Jobs

### A bit about Newfront\nFrom the Mayflower to the moon landing, every venture relies on insurance. The $1 trillion insurance industry is fundamental to our economy and society, but remains stuck in the stone age. Incumbents rely on antiquated pen-and-paper process and there's a huge opportunity to transform it through technology. At Newfront, we're building software to supercharge insurance brokers and help them deliver a delightful experience to clients.\n\nWhile we’re a technology-driven company, we believe that people and trusted relationships matter. Newfront believes in empowering people rather than "disrupting" them. Our singular mission is to create the future of work for this massive industry.\n\nWe believe breakout growth creates breakout opportunities and diversity drives innovation.\n\nAs an Engineering Lead at Newfront, you will work with a team building features across the platform to help clients manage their risk and supercharge our brokers. There are tons of challenging technical problems to solve that directly impact the lives of your teammates and Newfront clients.\n\nNewfront scales by hiring brokers who join with their book of business. Through automation and artificial intelligence, we eliminate paperwork and pay brokers a higher split of their commission revenue. We represent a paradigm shift in the industry and career path for tens of thousands of brokers.\n\nThis position is open to remote candidates with Pacific Time Zone preferred. ***#LI-Remote***\n\n\n* 🎥 To learn more about the technology we're building, watch our video [Engineering at Newfront](https://www.linkedin.com/feed/update/urn:li:activity:6513862682058330112/)\n* 🚀 To learn more about our mission and values, check out our [Careers Page](https://www.newfront.com/careers) or [Key Values](https://www.keyvalues.com/newfront)\n* 💰 To learn more about our funding, check out this [Forbes article](https://www.forbes.com/sites/igorbosilkovski/2020/10/20/exclusive-meet-the-entrepreneurs-who-have-raised-over-100-million-to-digitize-insurance/?sh=727e74a03206)\n\n### What you'll work on\n\n* ***Lead the development of product features:*** You'll be involved during product discovery and you'll contribute to the technical design process. You are product-minded and able to collaborate with a Product Manager to define the product roadmap and vision. You'll be responsible for speccing and guiding your team in building out features and infrastructure.\n* ***Shape business processes:*** As Newfront is a technology-enabled brokerage, we are looking for new ways to improve business processes by using technology. You will become the expert on how an area of the business functions and work directly with stakeholders to build optimizations.\n* ***Define technical direction:*** You will help shape the technical vision and roadmap for a large area of the product. You will also influence best practices and introduce new technologies when appropriate. You'll need to clearly communicate your vision with the team to gain support and a shared understanding of the technologies.\n* ***Mentor other engineers:*** You will working with more junior engineers on your team to help them grow and develop their skills.\n\n### Requirements\n\n* ***5+ years of engineering experience.*** You have previous success developing and shipping a large-scale application with a user-empathetic mindset\n* ***2+ years of experience leading an engineering team.*** You have proven abilities in providing technical direction for a small to medium team of engineers.\n* ***You're product-minded.*** You take initiative to understand production intention, team goals, business context, and user problems to propose improvements, eliminate gaps, and reduce risk in the project. You contribute to and drive the teams roadmap with product and design. You meet with stakeholders across the company when needed to eliminate gaps in your knowledge. You work closely with design to make sure that a design is able to be built and that it has a logical system behind it.\n* ***Security-minded,*** You have a detailed understanding of security protocols like OAuth2/OIDC/JWT. You understand client-side cookie authentication and JWT. You should have an understanding of front-end security risks and how to mitigate them.\n* ***You're highly skilled with web technologies including JavaScript (React/Node), HTML, and CSS.*** These are important foundational skills for a front-end engineer and impact everything from performance, to maintainability, to accessibility. You understand which features can be used across the various browsers, you understand how to make a website accessible, and you know how to implement responsive design.\n* ***You have experience architecting complex front-end web applications. We use React/Next.js,*** but you might have experience with Ember or Angular. You understand the concepts of services, stores, state management, build tools, routing, testing, serverless functions, and API design. You might have experience working with micro front-end applications and you are able to discuss trade-offs when slicing up a front-end app. You have created frameworks and libraries to abstract away complexity in your application to amplify your impact across the team.\n* ***You have some experience with micro-service/cloud and enterprise architecture patterns.***  You have an understanding of cloud architecture patterns, like pub-sub and BFF APIs, and are able to work with other engineers to discuss the trade-offs and benefits. While you might not be setting up these systems, you understand how they work, why they're used, and how they can impact front-end app performance, product requirements, and front-end code architecture.\n* ***You have a strong understanding of design:*** You understand that as a front-end engineer it is your job to help uphold the quality of the product. You're aware that loss of quality is often death by a thousand cuts and you care when elements are a few pixels off. You're able to understand why particular interactions should be used and when and you're able to recommend particular UI patterns to solve user problems. You'll have contributed to or have built design systems in the past.\n\n### Some of the technologies we use\n* Node\n* Typescript/JavaScript\n* React/Nextjs\n* styled-components\n* Vercel\n* Docker\n* NestJS\n* Redis\n\n### Nice To Haves\n* Proficiency with Typescript, React, Jest, and Next.js.\n* Experience with styled-components or similar CSS-in-JS libraries.\n* Understanding of containerization technologies such as Docker.\n* Experience using Vercel to deploy applications.\n* Experience with Node.js and/or serverless functions.\n\n### Compensation + Benefits\n* $50k-$100k USD (based on experience)\n* All employees receive equity (based on experience)\n* $500 work from home stipend\n* Unlimited vacation\n\n---\n\nNewfront is an equal opportunity employer. We celebrate diversity and are committed to creating an inclusive environment for all employees. [Learn more about our commitment to diversity and inclusion.](https://www.newfront.com/diversity-and-inclusion)\n\nNewfront provides reasonable accommodations for qualified individuals with disabilities in our job application procedures. If you need assistance or an accommodation due to a disability, you may contact us at [email protected]. \n\nPlease mention the word **SUCCESSFULLY** when applying to show you read the job post completely (#RMTguOTcuMTQuODI=). 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 $50,000 — $100,000/year\n
\n\n#Benefits\n 🏖 Unlimited vacation\n\n
\n\n#Location\nLatin 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 (#RMTguOTcuMTQuODI=). 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 building some really exciting sh*t at x.ai\nAt x.ai, we're building artificial intelligence super-powered productivity software. The software schedules meetings for our customers automatically. It avoids the typical back and forth over emails and negotiates when and where the meeting is to happen. The software uses state-of-the-art machine learning in our production environment. We're looking for a self-motivated and experienced individual to join us on the journey in building this new frontier. You’ll get to work side by side with a group of focused and passionate individuals in a fully distributed setting.\n\n# Responsibilities:\n* Build, maintain and continue to simplify the infrastructure and services that support all components of the system and customer facing products \n* Design, deploy and implement internal tools to multiply the developer team\n* Identify and measure key infrastructure performance metrics, improve and maintain monitoring and ensure robust alerting and logging systems\n* Lead our on-call process and actively troubleshoot and resolve issues, collaborate closely with customer support\n* Own system health - ensure uptime, preemptively take action to improve our systems and tooling, identify risks and interdependencies to minimize impact on customers\n* Be a main driver and contributor in building, testing, and deploying user-centric features\n* Own and drive the full cycle of building features, API and system integrations from system design to deployment\n\n# Qualifications:\n* 5+ years of experience\n* Experience with Docker and managing AWS cloud infrastructure deployments\n* Experience setting up network and troubleshooting network issues, and strong knowledge of VPN, AWS VPC, DNS, network interfaces\n* Experience in Scala\n* Experience in Javascript, Node.js, Angular a plus\n* +/- 8 hours from EST\n* Thrives in a fully remote setting\n* Intellectually curious, collaborative, self-motivated, fast learner that is comfortable with uncertainties – evolve as needed, flexibility is key!\n* Customer obsessed\n\n \n\nPlease mention the words **PROJECT INSIDE PUMPKIN** when applying to show you read the job post completely (#RMTguOTcuMTQuODI=). 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