Find Back-End Developer Jobs

TypeScript, JavaScript, and React

Scala (high performance backend)

Python (infrastructure management and data analysis)

Android and iOS

Luna1 (legacy in-house functional reactive framework, similar to Meteor)

Our backend is written in Kotlin using the SparkJava framework on top of a Postgres database. We use the React framework written in Typescript on the frontend, Jenkins for CI/CD, and our infrastructure is fully deployed on AWS, dockerized and managed by Terraform.

We use whatever tools are appropriate to accomplish the task at hand.

The backend stack currently consists of Node.js, Apollo server (GraphQL), PostgreSQL, Docker and Lambda in AWS. We also have a strong bias toward a micro-service architecture.

The frontend stack currently consists of React Native, TypeScript, Expo, Apollo client (GraphQL), and Jest testing framework. We have a mobile app with cross-platform support.

Backend: Python3, Deployed on AWS Lambda + ApiGateway, GraphQL endpoint.

Frontend: React written in Typescript.

Airtable’s core stack is written using JavaScript, augmented with static type checking and other tools. We use Node.js on the backend, and mostly-React on the frontend, but our application requirements drive a substantial amount of custom software architecture; that is, Airtable is pretty far from a boilerplate “React + Express” application. We also periodically evaluate adding other languages into our codebase for ecosystem or performance reasons. Mobile apps are currently written in the standard platform language, mixed with JavaScript in webviews where appropriate. Our production infrastructure runs on a variety of AWS services, principally using Terraform for deployment; for data collection, aggregation, monitoring, and alerting, we use a mixture of ELK and some carefully selected third-party services.

React Native, React, Ruby on Rails, Go

Frontend is React Native for mobile, and we’re experimenting with React Native Web on the web side.

Backend is currently Java deployed using Kubernetes, but we have a polyglot approach to problem solving, and we will likely end up with a backend that reflects that.

Backend: Ruby on Rails. Frontend: ReactJS + Typescript.

Ruby on Rails, AngularJS, Python, SQL, Postgres, Docker, AWS

d3.js/React/Redux single page webapp, Go backend, multi-language support for client libraries

JavaScript, Python, Node.js, React + React Native, AWS Lambda, Spark, Kinesis, MongoDB, Redshift

Node.js, React.js, Redis / Mongo, AWS, Kubernetes / Terraform / Docker

Clojure, React, Postgres, AWS, Git

Backend: Node.js, Express, MongoDB/Mongoose, Testing (Jest, Supertest, Nock), Cloudflare. Frontend: Angular 1, React. Hosting/Infrastructure: Heroku, MongoDB Atlas, GitHub, Codeclimate, CircleCI.

React, Node.js, Python, Java

We’re on service-oriented architecture. Our backend is composed of a collection of Java services that communicate via RPC. Our frontend web stack is a React/Redux application. We use Objective-C and Swift in the iOS app and Kotlin in the Android app. Our data infrastructure is cloud native in AWS and includes S3, EMR, Redshift/RDS, Lambda, and ECS.

React, React Native, Node.js, Elasticsearch, Redis, Heroku, AWS

Frontend: React, Relay, Flow, Jest, Enzyme.

Mobile: React Native, Apollo.

Backend: Ruby on Rails, Postgres, GraphQL, Python, RSpec, Java.

CI: GitHub, Buildkite.

Infrastructure: AWS, Python.

On the frontend, we use TypeScript, React, Redux, GraphQL, Apollo. On the backend, we use Node.js, Go, TypeScript, MySQL, Elasticsearch, Redis. Everything is containerized in Docker and running on Kubernetes.

Web: PHP, JavaScript, TypeScript, React/Redux, MySQL, Docker, and Elixir.

Mobile: Kotlin, Swift, Java, Objective-C, React Native, and Electron.

Systems: Docker, Nginx, PHP, C, Lua, MySQL, MongoDB, Node.js, Statsd, Graphite, Prometheus, Elasticsearch, Logstash, Hadoop, MogileFS, HDFS, and BGP.

Data: Hive, Impala, HBase, Spark, HDFS, Python, Java, Scala, Kafka, Elasticsearch, MySQL, Solr, and Lucene.

Dark’s backend is written in a combination of OCaml, Rust, and Dark (that’s right, Dark is partially built in Dark!). We use Kubernetes and Postgres, running on top of Google Cloud.

Our frontend is also in OCaml – we don’t expect you to know OCaml before you join, and you typically learn it in the first few weeks. We compile the OCaml to JS using Bucklescript/ReasonML, and use a framework similar to Redux or Elm for managing state.

Backend: Ruby on Rails, Postgres, Elasticsearch, Google Cloud Platform, Kubernetes.

Frontend: Typescript, React, Redux.

Data: BigQuery, BigTable, DataFlow, DataProc.

AWS (ECS, ECR, EC2, S3, Cloudwatch…), Docker, Ruby (Sinatra), Python, Postgresql, Mysql, Swift, Kotlin, Sentry, Jenkins, React.js

Ruby on Rails, Elixir, React.js, GraphQL, Node.js, AWS, Redis, Spark & Scala (Data team)

Our clients (Android, iOS, and web) and backend are all built in JavaScript using technologies like React, React Native, Nodejs, and GraphQL.

Frontend: express, react, redux, bootstrap. Middleware: express. Backend: everything but dominantly GoLang running on AWS.

Backend: Node + Express, Typescript, Go Microservices. Frontend: Next.js, React + Hooks, Storybook. Infrastructure: Heroku + AWS, CircleCI, DataDog.

Blog Post on our Tech Stack

Lever uses our own open source MVC framework called Derby that syncs all data via Operational Transformation (the algorithm behind Google Docs). OT is the way we handle concurrency conflicts for any piece of data that is edited at the same time. In addition to real-time sync, OT allows us to provide a smoother UI since we can render updates on the client instantly without waiting for our backend to respond, while still guaranteeing consistency.

Lever makes extensive use of AWS, Docker, Node, Mongo, ElasticSearch, and Redis within our infrastructure. We use tools like Hubot to streamline deployments and Grafana to see what’s going on under the hood. In addition to automating all the things, we love to version them too! Our systems are all created using Terraform and Chef, working together to ensure consistency at all costs.

We have a service oriented stack deployed on AWS using containers. Most of our backend services are written in Go, with the exception of an NLP/ML service written in Python. Services talk to each other using gRPC.

Our web application is served statically from Cloudfront/S3 and is written using React. Is is a Progressive Web App, with a service worker to speed up delivery.

We integrate with third party software such as Google Drive, Calendar, Jira, GitHub, Asana, Slack. These areas are some of the most complex parts of our systems. They’re also some of the most important: integrations enable the “magic” of a user coming to Range in the morning and seeing all of their work from the previous day already gathered in one place.

Back: Node, Golang

SRE: Terraform, Kubernetes, Rancher, AWS, MongoDB, Postgres, RabbitMq, ElasticSearch, Docker

Front: React-like frameworks, Webpack, Javascript, AngularJS (only until we kill the old product)

React

Ruby on Rails

Java

AWS

LAMP / LEMP, Laravel / Zend, Node.js, AWS, Redis / Memcache, Ubuntu / CentOS, MySQL / Mongo, VanillaJS, VueJS, HTML5 / CSS3, Angular / Backbone / Ember / Ionic