\nThe opportunity\n\n\nWe’re looking for a Full-Stack Engineer to elevate Chord as the leader in customer data platforms. You’ll join a growing team that is building a platform to empower modern and omnichannel brands with smart technology, unique customer experiences, and insightful data.\n\n\nIn this role, you will be responsible for building Chord’s storefront data SDK, which captures customer behavior on merchant’s ecommerce stores and feeds it into our data warehouse. You will also have an opportunity to expand our data reporting and administration portal, where merchants view key performance metrics necessary to grow their revenue. \n\n\nThis is a perfect opportunity for engineers who thrive on big data problems; using data to generate insights that lead to actions. As an early-stage technology startup, you will have an opportunity to influence the culture and practices of the Engineering team. You will have an instrumental role in the design and implementation of our flagship products. If you’re curious, willing to learn, humble, and a good team player, you’ll be at home here at Chord. \n\n\nAs a Full-Stack Engineer, you will be a key member of the Engineering team and will report to the Engineering Manager. You will work in a group with senior and principal engineers responsible for the end-to-end development of Chord’s software products. You will also regularly collaborate with members of our Product and Customer Success teams to contribute to product design and support customers.\n\n\nChord offers advanced technology for modern brands that want amazing customer experiences and unified data without a large engineering team. We like to think of our product as the tech engine for high-velocity e-commerce growth. Backed by top investors, Chord is a SaaS company led by industry veterans, and we’re seeking smart, focused, creative talent to help us realize our vision. \n\n\nOur company is proudly remote-first, distributed across North America. \n\n\n\nAs a Full-Stack Engineer, you will:\n* Design, build, and grow our proprietary storefront data capture SDK.\n* Design, build, and grow our analytics and data management platform.\n* Support projects to launch customers onto Chord’s platforms.\n* Analyze and resolve technical issues that arise during production operations.\n* Contribute to technical design discussions and proposals that improve our team's culture, processes, or architecture.\n* Collaborate within a cross-functional project and operations team to execute product plans and achieve company goals.\n* Learn and practice Chord’s engineering principles through pairing sessions with developers.\n* Support the growth of engineers around you.\n* Contribute to tutorials and documentation that our customers will love using.\n\n\n\nTo be successful in this role, you’ll need: \n* A reputation for being inclusive, curious, entrepreneurial, and thoughtful.\n* Proficiency in Javascript and Typescript.\n* Experience working with Node and React/Redux-based frameworks.\n* Skill in authoring and maintaining GraphQL or RESTful-based APIs. \n* Expertise in writing tests with tools such as Jest, Cypress, and React Testing Library.\n* Experience publishing and maintaining JS libraries. \n* Experience with CI/CD and DevOps tools like Github, Sentry, and CircleCI.\n\n\n\nBonus points for:\n* Proficiency in Ruby on Rails and common frameworks/integrations such as Solidus, RSpec, FactoryBot.\n* DevOps experience with Heroku, AWS (Lambda, API Gateway, RDS).\n* Experience creating metrics and monitors in Datadog.\n* Experience with static website libraries such as Gatsby and NextJS.\n* Skill in building integrations using middleware platforms such as Segment.\n* Background working with payment processors such as Stripe and Braintree.\n* Familiarity with modern CMS systems like Contentful or Sanity. \n* Hands-on experience with complex ecommerce experience is a big plus. \n\n\n\nWorking at Chord, you can expect: \n* An investment in your physical and mental well-being; we offer 100% employee Medical Benefits coverage, with 69% dependant coverage. \n* Flexible PTO; we encourage you to take the time you need to be your best self at work. \n* An onboarding package and annual work from home stipend to ensure you have everything you need to be successful while working remote. \n* Generous Parental Leave with customizable transition back to work program.\n* To make an impact! We’re an early-stage company, which means there is space to champion ideas, and create and lead initiatives at any level in the Organization. \n* The benefits of working from home, with opportunities to spend quality time with the team at Chord in-person events throughout the year.\n\n\n\n\n$145,000 - $170,500 a yearThis is the expected salary range for US-based employment. \nThis is a full-time, salaried position that includes Equity. We set standard ranges for all roles based on function, level, and geographic location, benchmarked against similar-stage growth companies in our market. This salary range represents the full salary range for the position. The starting base pay offered may vary depending on factors including experience, expertise, market demands, and internal parity. \n\nAbout your application and the interview process\n\n\nChord is an equal opportunity employer, and we value diversity. We do not discriminate on the basis of race, religion, color, national origin, gender, sexual orientation, age, marital status, veteran status, or disability status. If you’re unsure about your qualifications for this position, we still encourage you to apply. \n\n\nOur interview process for the role begins with an exploratory conversation with the Hiring Manager. After that, we’ll invite you to a Zoom session with a range of stakeholders from across our organization. We aim to get to know you and allow you to learn more about our team and product while being respectful of your time. \n\n#Salary and compensation\n No salary data published by company so we estimated salary based on similar jobs related to Design, SaaS, React, GraphQL, Testing, DevOps, JavaScript, Node, Ruby, API, Senior, Engineer and Ecommerce jobs that are similar:\n\n $60,000 — $110,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
\n\n#Location\nNew York, New York

# 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

# Lead Product Engineer - Core Experience\nSegment is building the future of how companies manage their constantly increasing volume of customer data. We help our customers collect data from a variety of sources, combine and understand that data, and ultimately act on it to give their users a better experience.\nImagine you want to answer a question that is core to your business — maybe you changed the pricing on your product and you want to understand if that’s driving revenue or creating churn and customer confusion. In order to properly answer that question, you would need data from your payment processor, your CRM, and telemetry data from your application. In the past, business teams have had to wait for developers to build ETL pipelines to move data from one place to another. This is painful, time-consuming, and doesn’t keep up with the pace of the customer needs. Segment allows you to get all of this data in one place, automatically, and start using it immediately rather than spending time building data pipelines.\n## Who we are:\nWe're a small distributed team of full-stack engineers based in San Francisco, Vancouver and the world 🌎 who love to ship high-quality code.\nFrom collecting data through [analytics.js](https://github.com/segmentio/analytics.js), to building powerful tools for data governance, to implementing algorithms that can handle complex billing scenarios at scale, to optimizing Sign Up conversion, the Product Engineering team is focused on creating fantastic user experiences.\nWe're looking for talented engineers that are passionate about building world-class experiences that delight our customers.\n## How we work:\n- 💅 We enjoy building UIs in React so much that we created our own internal components library.\n- 🛠️ We believe in using the best tool for the job. We write customer facing features using React, NodeJS and GraphQL. Our write-heavy traffic services are written with Go and leverage multiple data storage solutions.\n- 🚢 We deploy our code multiple times per day. We "semver" everything :)\n- 🎤 We love conferences. (An engineer spoke in 4 different countries last year!)\n- 👯 We love open source: https://open.segment.com\n- 📈 We’re proud of the code we write, but we’re not dogmatic about methodologies or techniques. We believe building the "right thing" is more important than building things "right".\n\n## Who we're looking for:\nYou can turn complex business requirements into working software that our customers love to use.\n- You're proud of the code you write, but you're also pragmatic.\n- You know when it is time to refactor, and when it's time to ship.\n- You're focused, driven and can get challenging projects across the finish line.\n- You're empathetic, patient and love to help your teammates grow.\n- You have experience running apps in production and take software engineering practices seriously. You write meaningful tests and understand the value of great logging, proper monitoring and error tracking.\n\n## A few projects you could be working on:\n- We collaborated closely with our BizOps and Design team to rebuild all parts of our billing experience, from the customer’s first visit, to building a pricing simulator tool, to implementing algorithms that can handle complex billing scenarios at our scale.\n- We’re building an [open-source version](https://github.com/segmentio/evergreen) of our UI library that saves our engineers multiple hours of work every week. Think pixel-perfect implementations by default 😱 🎨.\n- We used a [HLL](http://antirez.com/news/75) to scale an analytics tool that handles thousands of requests / sec.\n- We're building powerful tools that help our customers protect the integrity of their data, and the decisions they make with it.\n\n## Requirements:\n- You can write both client side and server side JavaScript using the latest APIs and language features.\n- You have some familiarity with Golang or are excited to learn it.\n- Minimum of 3 years of industry experience in engineering or some cool projects on GitHub you think we'll love to check out.\n- You provide a deep understanding of the complexities involved in writing large single-page applications.\n- You show evidence of exposure to architectural patterns of high-scale web application (e.g., well-designed APIs, high volume data pipelines, efficient algorithms.)\nWe are an equal opportunity employer and value diversity at our company. We do not discriminate on the basis of race, religion, color, national origin, gender, sexual orientation, age, marital status, veteran status, or disability status. \n\nPlease mention the words **SWITCH TURTLE AUTO** 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, React, Node, Golang, Engineer, GraphQL, Docker and Executive jobs that are similar:\n\n $65,000 — $120,000/year\n
\n\n#Benefits\n 🌎 Distributed team\n\n