Engineering at Scope3
Our engineering team values a high-level understanding of our comprehensive technical ecosystem. We prioritize this technical familiarity in order to facilitate effective collaboration, cooperation, and productivity in a cross-functional environment.
About The Role
We are excited to add a lead engineer to our platform team, based in the US or Canada working from the EST time zone, the UK, France, or Germany. This individual contributor role will be responsible for overseeing + shaping the technical vision for our core emissions measurement API and all real time systems. In this role, you will not only guide the technology underpinning Scope3’s core api, but also help setting high performance standards across the engineering organization - with a focus on maintainable and performant Golang code.
Tech Stack + Architecture
Emissions Measurement API (documentation here)
This API is utilized directly by our customers (typically via batch pipelines, so we get huge request spikes every hour) and is the backbone for many of the products that we have built and have made available at scope3.com. For instance, all of the core emissions numbers powering our property report (example here) are powered by this core API.
The current tech stack focuses on running high throughput + low latency golang services deployed to a kubernetes engine running in Google Cloud Platform. Since low latency is a priority for our API - we utilize a large in-memory database to reduce the need for external network calls. This role would be instrumental in establishing the future architecture of this API as the breadth of data modeled and their use-cases continue to expand.
Real Time Systems
We recently added a real time data provider (documentation here) to our stack. This system has to have capacity to handle 1M+ QPS globally as well as reliably sub 5ms latencies. This network latency requirement also set us up to deploy our own servers next to our clients (we are using Equinix to get bare metals). The core application is built in Go and currently we are relying on in-memory cache systems (such as this one). The overall architecture and caching strategies used for this system are actively being iterated on and would be a key project undertaken by this individual.
What We’re Looking For:
Preference may be given to candidates with the following:
Our Culture & Values
A Note To Applicants
We believe that all people are capable of great things. We encourage you to apply even if you do not meet all of the requirements that are listed within this job description.