Strong backend software engineering experience, with Go as your primary language, building and operating APIs, services, or ingestion systems that other teams depend on.
Experience designing well-defined APIs and integration contracts, including thinking about schemas, backwards compatibility, validation, and how other engineering teams will consume them.
Experience building production services in Go, from smaller utilities and scripts through to larger, long-running services or microservices.
Some experience with TypeScript or JavaScript and an ability to work comfortably in a codebase that spans backend and frontend technologies. This is primarily a backend role — you won't be responsible for UI development.
Familiarity with event-driven systems, data ingestion, or data pipeline tooling such as Segment, BigQuery, or similar.
Ability to work independently in a new area, make pragmatic technical decisions, and drive work forward with limited direction.
Comfortable writing RFCs and technical documentation, and working across teams to establish and drive adoption of a new integration point.
Clear, concise communication — a lot of this role involves defining contracts, documenting decisions, and helping other engineers integrate with what you build.
Nice to Have
Experience with observability, including tracing, logging, and metrics.
Experience integrating with GCP, AWS, or Azure.
Experience working with product analytics, event tracking, or telemetry systems.
What You'll Be Doing
Design, build, and operate the Analytics API and the underlying infrastructure, defining the schema and integration contract used by teams across Aura.
Make pragmatic architectural decisions around event ingestion, data contracts, reliability, and scalability as the platform grows.
Build a simple, well-defined integration layer that makes it easy for product teams to send analytics events without coupling them to the underlying data infrastructure.
Drive adoption across the Engineering organisation, working with teams to integrate with the API and providing the guidance and documentation they need.
Keep product analytics and billing concerns cleanly separated, even where the underlying data flows or infrastructure may be similar.
Evaluate build vs. buy across the existing analytics and data stack, including tools such as Segment and BigQuery, keeping the API focused on collection rather than reimplementing downstream capabilities.
Partner closely with the team building the downstream data pipeline to ensure raw events are reliable, well-structured, and usable for analytics.
Define and evolve the platform through RFCs, technical documentation, and close collaboration with Product Management and other engineering teams.
Perks and Benefits
Opportunity to shape the future of data and analytics
Joining a well-established and successful company in the graph intelligence platform industry
Part of a fast-scaling technology company with a strong customer base
Backed by world-class investors
84% of the Fortune 100 and 58% of the Fortune 500 use Neo4j