Distributed Systems Engineer- Platform

Details

• Architect and implement solutions in our queueing layer, state store, and execution layer (eg. 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 we grow
• Collaborate with team members to expose internal data across metrics stores, APIs, and customer dashboards we host in our cloud UI
• Work with backend engineers to design APIs that can be used across the Inngest cloud dashboard, dev server and CLIs
• Dogfood the Inngest product and develop ideas for improvements, features, or integrations
• Communicate with our users through Github, email and Discord
• Write technical specs for features and documentation for our users
• You've been working on distributed systems for several years
• You've used Go or similar statically typed languages professionally for two years or more
• You've architected, or been involved in designing, systems that handle scale
• You understand engineering trade-offs and can make correct judgement calls on approaches available
• You understand how to observe, monitor, and maintain the systems you design
• You appreciate simplicity, even if it's harder to design and build
• Work with compliance (SOC2, ISO27001, HIPAA, etc.) and know how to make it serve security approaches and not the other way around
• Experienced or have a solid understanding of networking
• Understand and have experience managing and maintaining systems, eg. SRE roles
• First week: you’ll learn how we work as a team and our approach to growth. You’ll also start to learn our system architecture and hopefully make a couple of small contributions to the dev server UI or our cloud dashboard.
• By day 30, you’ll be proficient with our weekly cadence of work and have contributed a new feature to our executor, state, queue, metrics, or some other component. You’ll fully understand our company, product, and growth strategy and start to build up context for your product mindset.
• By day 90, you'll have shipped significant changes to our open source project and cloud platform. You also helped define the specs. You'll have learned where you can contribute outside of the engineering domain (growth, UX design, DevRel, etc.) and contributed ideas around product and growth. We're all aligned and mutually excited about how we work together now and in the future!
• Backend: Go, Postgres, Redis, Clickhouse, PubSub/Kafka, k8s
• APIs: gRPC internally, GraphQL and REST APIs for UI
• Hosted on AWS, GCP and Bare Metal
• Github, Linear, Slack, Notion, Figma