Find Platform Engineering Jobs

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

Mobile: React Native, Apollo.

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

CI: GitHub, Buildkite.

Infrastructure: AWS, Python.

We use whatever tools are appropriate to accomplish the task at hand. The backend stack currently consists of Node.js, Express, GraphQL, PostgreSQL, Docker and Lambda in AWS. We also have a strong bias towards 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.

AWS, Python, GoLang, Cloud9, GitHub, ELK, Cloudera

Web stack: Django, GraphQL, React, Postgres. Data pipeline: Spark, Kafka, Elastic Search, Scala. Infra: AWS.

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

Frontend: Typescript, React, Redux.

Data: BigQuery, BigTable, DataFlow, DataProc.

Javascript (React/Redux), Ruby on Rails, Scala, Postgres, LittleTable

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.

Across our product portfolio we leverage a variety of languages, frameworks and tooling. Much of our code is written in C#/.NET Core 2.x along with a handful of other languages such as Java, C++, PHP and Node.js. For frontend, Angular 7+ on the newer products, and a few mature products leveraging Javascript and JQuery. Many databases to store our 300TB+ of production data including MySQL, SQL Server, Snowflake, MongoDB & DynamoDB. We have some monolithic applications though new products & platforms are built using microservices running Docker containers on AWS ECS with some footprint in Azure. We leverage many AWS services – Lambda, CloudWatch, S3, EC2, Route53, EMR, IAM, SQS, SNS and more. We also use Terraform for configuring infrastructure, Jenkins for CI, and Git/GitLab for source code. These are flexible (they can and will change) and what a candidate knows for stack is not as important as their ability to think creatively – we can train languages, it’s much harder to train curiosity and intellectual drive.

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.

Ruby on Rails

Swift

Postgres

Redis

Memcache

RabbitMQ

AWS

Heroku

Ruby / Javascript / Python / Golang

Sinatra / Rails / React

MySQL / Mongo

Presto for data warehouse

Docker / Kubernetes for deployment

REST / JSON / gRPC for service communication

Frontend: React/Redux. Legacy JSP (although increasingly less!)

Monolith backend: Java on Tomcat.

Microservices backend: Java on Spring.

API: Java w/ Swagger.

TechOps: Hashicorp stack + Docker on EC2/AWS. Cloudflare, EBS, Redis. Git/GitHub for Source Control. Jenkins for CI. Ruby/Cucumber for testing.

Databases: MySQL

Search: SOLR

Data: Python (pandas, AirFlow, etc.). Redshift/Postgres.

OnForce Platform (subsidiary): PHP on baremetal LAMP (deprecating, moving to AWS).

Languages/Frameworks: Angular, Node, Serverless Lambda, Rails, Coldfusion

Databases: MSSQL, Aurora

Cloud Providers: AWS

We’re primarily a Python shop, using Django for our websites. We also have a few services written in Go and have started to build out our front ends using React. We use Github to host our code, Jenkins (for now) to automate our tests, and right now most of our applications and code live in VMs in a Colo just outside of Toronto. We’re in the process of transitioning to AWS. Other common technologies we use are Postgres (primary DBs), Redis (cache and key/value store), RabbitMQ (messaging broker) and Celery (task queue).