We believe the way people interact with their finances will drastically improve in the next few years. We’re dedicated to empowering this transformation by building the tools and infrastructure developers need to create their own products. Plaid powers the tools millions of people rely on to live a healthier financial life. We work with thousands of companies like Venmo and SoFi, several of the Fortune 500, and many of the largest banks to make it easy for people to connect their financial accounts to the apps and services they want to use. Plaid’s network covers 11,000 financial institutions across the US, Canada, UK and Europe. Founded in 2013, the company is headquartered in San Francisco with offices in New York, Salt Lake City, Washington D.C., London and Amsterdam.
The Observability team provides a cohesive, well-curated set of products and tools for observing the behavior of our systems (services, applications, jobs, and more). We enable engineering to understand the state and behavior of their workloads with greater ease and efficiency.
The team is relatively new; We are currently in the process of consolidating the observability responsibility that was spread throughout the company. (For example, Prometheus and Sentry are owned by the Infrastructure team and ElasticSearch is owned by the Data Infra team). Our long term vision is to provide cohesive and unified approach towards observability for Plaid.
As an Engineering Manager, you'll help building and scaling these foundations and ensure that our systems continue to be highly performant and available. Plaid's systems are combination of AWS, open source, and vendor provided systems. ElasticSearch, Prometheus, Sentry, and Lightstep are few heavily used systems. Most of Plaid's applications are written in Node, Go, or Python. Observability team is responsible for the ergonomics and transport of telemetry events from the application.
Currently the team is focused on the operational excellence of the existing systems. However, we would like to have a cohesive narrative around Observability - How do these systems interact together? What systems are redundant? What systems should we introduce or replace? We love trying new technologies as individuals, but as a team we're pragmatic in our choices, favoring right tools over the flavor of the month. You'll lead a team of 4-8 engineers. You'll work closely with other engineering teams to bring our product and infrastructure services to life. Moreover, you’ll be collaborating closely with other functions on product and technical strategy.
