Backend Engineer, LaunchDarkly

• Experience with at least one server-side programming language and interest in working with Go
• Ability to build and maintain basic RESTful APIs using existing patterns
• Understanding of core computer science concepts such as data structures, concurrency, and distributed systems basics
• Familiarity with databases or event stores like Postgres, ClickHouse, ElasticSearch, Snowflake, or similar
• Exposure to data or event-processing tools such as Kinesis, Airflow, Spark, Lambda, Flink, or equivalents
• Basic experience with infrastructure-as-code tools like Terraform, or willingness to learn
• Familiarity with observability tools like Datadog. Able to read dashboards and debug with guidance
• Willing to commute to Oakland twice a week

Desirable

• As a P2 on Metrics, you’re building the part of the platform that turns raw events into meaningful LD units that can be turned into measurements
• Your work will support safer releases, clearer experimentation, and faster learning across both traditional software and emerging AI workloads
• This is a chance to grow as an engineer while contributing to infrastructure that modern teams depend on every day
• Build and maintain backend features within the Metrics services, following established patterns and designs
• Help develop internal APIs that connect customer events to experimentation and release-safety workflows, with guidance from senior engineers
• Work with data pipeline teams to understand how events flow through ingestion, storage, and querying, and make targeted contributions where needed
• Assist in integrating event-driven capabilities into areas like AI Configs, Observability, and Experimentation
• Support service reliability work by adding tests, improving logs, tuning alerts, and helping investigate issues during development
• Participate in code reviews, design discussions, and planning sessions, asking clear questions and contributing thoughtfully
• Learn the operational side of running distributed systems, including debugging, monitoring, and safe rollout practices