Distributed Systems Engineer - Platform
Distributed Systems Engineer (Platform) role at Inngest, where Systems Engineers build the core of the product: the durable execution layer, queueing system, state stores and the distributed systems that connect them. Inngest is solving long-standing developer problems in a novel way, creating first-of-their-kind solutions and tools that developers use in their everyday workflow, so UX and performance are primary. A Systems Engineer needs to be both generalist and specialist, responsible for the inner workings of the queueing system (e.g. debounce, concurrency over time), the state store (handling terabytes to petabytes of storage), the API layers in between, and sometimes the high-level SDKs users build with. The work directly impacts millions of developers. The role requires working-time overlap with US PST; ideally based in the SF Bay Area, but strong candidates may live anywhere in the United States, and the existing systems engineering team works in person in San Francisco several days a week.
Responsibilities
- ▹Architect and implement solutions in the queueing layer, state store and execution layer (e.g. concurrency over time, or function debounce)
- ▹Plan and implement improvements on throughput and latency at hundreds of thousands to millions of requests per second
- ▹Contribute to systems architecture and infrastructure changes as the company grows
- ▹Collaborate with team members to expose internal data across metrics stores, APIs and customer dashboards hosted in the cloud UI
- ▹Work with backend engineers to design APIs usable across the Inngest cloud dashboard, dev server and CLIs
- ▹Dogfood the Inngest product and develop ideas for improvements, features or integrations
- ▹Communicate with users through GitHub, email and Discord
- ▹Write technical specs for features and documentation for users
Requirements
- ▹Several years working on distributed systems
- ▹Two or more years of professional experience with Go or similar statically typed languages
- ▹Has architected, or been involved in designing, systems that handle scale
- ▹Understands engineering trade-offs and can make correct judgement calls on available approaches
- ▹Understands how to observe, monitor and maintain the systems you design
- ▹Appreciates simplicity, even when it is harder to design and build
Nice to have
- ▹Experience with compliance (SOC2, ISO27001, HIPAA, etc.) and making it serve security approaches
- ▹Experience with or solid understanding of networking
- ▹Experience managing and maintaining systems (e.g. SRE roles)