Remote Engineering + Front End + GraphQL + Python Jobs

# About Us\nWe are [honu.ai](https://honu.ai), a venture backed startup building the next generation platform to give small business owners superhuman decision making capabilities. We are currently in stealth mode and are backed by Europe’s top investors (early backers of TransferWise, Tide, Coinbase, CityMapper, Cazoo, Nested, Habito, Cleo, King, Snyk, etc...) The technology we are building is novel and we will be pushing the boundaries of what has been done in this space.\n\nHonu is the name of the hawaiian green sea turtle, it is known to be an excellent navigator and symbolizes good luck, endurance and long life. Honu can also show up as a person’s guardian spirit, known as "Aumakua". We are the most loved, trusted and intelligent platform for small business owners that will help them navigate to success.\n\n# The Role\nWe are looking for an experienced **Front End Engineer** to join our growing team.\n\n- You will be part of the core team of 10 people building the first iteration of the product, you will contribute to both the front end and back end, but will be on of the go-to people for front end development.\n- You will collaborate with the team to define the strategy and vision for how we will build effectively and be successful\n- Improve engineering standards, tooling, and processes\n- Work with engineers across the company to build delightful features that span various parts of the system\n\n# Ideal Candidate\nThis is a unique opportunity to join a highly ambitious, venture backed company, on the ground floor. We’re taking a revolutionary approach and people who bring diversity of experience and a track record of creative solutions are particularly welcome.\n\n- 3+ years experience as a Front End Engineer.\n- 2+ years of commercial experience and demonstrable proficiency in React and TypeScript.\n- You can write semantic and easy to maintain CSS. Experience with Atomic Design, BEM, SASS and StyledComponents is a plus.\n- Nice to have experience:\n - TDD\n - Cypress.io\n - Framer Motion\n - React Hook Form\n - React Query\n - GraphQL\n - Functional programming\n - Python\n - Go\n- Data-oriented mindset: you want your work to be measurable and impactful\n- You will believe in clean coding, simple solutions, automated testing and continuous deployment.\n- Experience building Fintech or eCommerce products a plus.\n- You are considerate, humble, and a strong believer in teamwork.\n- You value honest feedback and creating an environment where it flourishes.\n- You're comfortably organised amongst chaos.\n- Essentials: You get things done, You take full ownership of your work, and you always strive for excellence and go the extra-mile.\n\n\n# Tech Stack\nOur initial stack is in Go and Python for the back-end, and React/Typescript on the front-end. We have a pragmatic, non dogmatic approach and will refine the tech stack and find the right tools for the job, as the product evolves. Scientific computing will be mostly implemented in Python, for now. \n\n# Our Values\n\n* Excellence : We constantly strive for excellence in what we do. We go above and beyond the call of duty. \n* Get Things Done : We acknowledge obstacles but orient towards solutions. We have a getting things done attitude, with laser focus on efficiency, as a team and individuals. \n* Open Communication : We communicate openly and respectfully about our opinions. Our conversations are constructive and all voices will be heard. However, when decisions are made, everyone commits to them. \n* Team Player : We are there for each other. As individuals we are reliable, responsible, collaborative and supportive. We respect each other’s time, we are punctual. We have got each others backs, and accept everyone’s authentic self. \n* High Integrity : We are honest with each other and with our partners, clients and collaborators.\n \n\nPlease mention the words **CHEST EXPRESS ERA** when applying to show you read the job post completely (#RMjE2LjczLjIxNi4yNTA=). 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 — $150,000/year\n \n\n#Location\nEurope

**Company Description**\n\nShopify’s mission is to make commerce better for everyone. From building a new product feature for our commerce platform, to helping a merchant troubleshoot an issue over the phone, we want to empower our ecosystem through our work.\n\nHaving a unified vision, a north star, is vitally important to ensure that we are all headed in the same direction. No matter the size or experience, we want to power every merchant’s experience. This is why we're all here.\n\nShopify is now permanently remote and we're working towards a future that is digital by default. That location you see above? Consider it merely an example of hundreds of potential locations across North America where Shopify is hiring. Learn more here: https://www.shopify.com/careers/work-anywhere\n\n**Job Description**\n\nAt Shopify, **Senior Lead Engineers** (also referred to as Senior Staff Engineers) use their expertise and passion to multiply the overall output of their development team. As a senior technical leader, you’ll help drive the product vision to its implementation. You and the team will design and build technically innovative solutions that empower all teams at Shopify to build powerful and resilient distributed cloud software. Merchants that depend on Shopify for a highly scalable, performant, and reliable platform benefit directly from the work you do. You will maintain a high bar for quality and lead and mentor other engineers. And of course, you’ll be hands-on in the code and contribute technically. Here are just some of the stories from the teams who build and scale Shopify.\n\nIntrigued? We’re recruiting Senior Lead Software Engineers to join teams in any one of these disciplines. Based on your experience and interests, let us know which one you identify with most in your application!

\n\n**Back End Development**\n\nBack End Engineers with a passion for solving tough problems with performant code work on teams that ship on quality instead of on time. Our teams deploy new code many times a day, and our production scale is massive. We’re talking over 1 million online stores, and hundreds of millions of requests a day. Thousands of entrepreneurs will see your work within seconds – a difficult but incredibly rewarding responsibility. Shopify is the largest Ruby on Rails application in the world and we're a big part of the Rails community. We’re constantly improving our codebase to make it even better.\n\n**Mobile Development (React Native, Android & iOS)**\n\nOur Mobile Engineers work along with designers and product managers to build and launch new features for our apps. You’ll work on large-scale apps that are ever-changing, enabling entrepreneurship for hundreds of thousands of entrepreneurs. Our Android engineers use Kotlin and our iOS engineers use Swift. Our teams are increasingly working with React Native so openness to cross-platform mobile development is a plus! \n\n**Front End Development**\n\nOur Front End Engineers collaborate closely with software engineering teams, designers, product managers, and marketers to not only build incredible merchant-facing products and marketing campaigns, but also engineer-facing tools. You’ll use the latest web standards in HTML, CSS, and JavaScript, and modern technologies and frameworks like Typescript, React, GraphQL, Apollo and Ruby on Rails, to develop large front-end web applications and websites that scale and perform well on all devices. You’ll work across disciplines and are excited about building human-centered experiences. Front End Development exists across all of Shopify, from Product to Marketing, working closely with the teams that create performant experiences and communicate Shopify’s impact on commerce to a global audience. You may also collaborate with our Data and SEO teams, helping us make data informed decisions and driving additional new merchant acquisition. You might focus on creating thoughtful interfaces for our users, shaping our design language, and contributing to our shared component libraries in a maintainable and scalable way.\n\n**Qualifications\nWhat you’ll do as a Senior Lead Engineer at Shopify:**\n\n* Learn and grow constantly to feed your passion for self-improvement and make those around you better\n* Design and build highly available, resilient and scalable platform primitives & API\n* Work through problems with your team, roll up your sleeves, form an opinion and advocate for engineering-specific roadmap items\n* Collaborate with other Shopify leaders, executives and external partners to provide the best commerce experience for our merchants\n \n\n**Experience and skills that are important for success in this role:**\n\n* A proven track record of strong technical mentorship\n* Experience building large scale, high throughput distributed systems and scaling web services, particularly those using and analyzing large amounts of data\n* High level of fluency with and experience using technologies and frameworks like (but not limited to) some of our most-used languages - Ruby on Rails, GraphQL, Java/JEE, Node.js, PHP, Python, React or React Native, Golang, Kubernetes - or deep experience with any object-oriented language and relevant transferrable technologies\n* A passion for efficiency and collaboration, with a history of establishing great relationships with UX and Product Management teams across time zones\n* A commitment and drive for quality, technical excellence and results\n* Curiosity and passion to constantly learn new things; Shopify changes fast, and we need the people who work here to be able to change and learn fast too\n* Proficiency in systems thinking and systems design concepts like transactions, atomicity, idempotency, etc.\n* Raise the quality and speed (team efficiency) bar and move the platform into a position of maximum leverage\n* Use the right tool for the job, fix problems are the right level of abstraction and optimize to meet both functional and non-functional goals\n\n**Additional information**\n\nWe know that looking for a new role can be both exciting and time-consuming, and we truly appreciate your effort. Jane is an actual real live person (👋🏻) and is looking forward to learning more about you through your application. And remember, we want to know what you're really interested in building and why you want to build it at Shopify, so please give us as much detail on this as you'd like in the answers on the next page. 👍 📖\n\nAt Shopify, we are committed to building and fostering an environment where our employees feel included, valued, and heard. Our belief is that a strong commitment to diversity and inclusion enables us to truly make commerce better for everyone. 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. Please take a look at our 2019 Sustainability Report to learn more about Shopify's commitments.\n\n#LI-KO3 #LI-REMOTE #LI-AH1\n \n\nInterested, but not ready to apply? \n\nJoin the Shopify Talent Community to learn more about us, while you polish up your resume: https://www.shopify.com/careers/2021 \n\nPlease mention the words **SCENE MAID NOODLE** when applying to show you read the job post completely (#RMjE2LjczLjIxNi4yNTA=). 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\nunited states, canada

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