Software Engineer, Neo4j

• 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
• Research shows that members of underrepresented communities are less likely to apply for jobs when they don’t meet all the qualifications. If this is part of the reason you hesitate to apply, we’d encourage you to reconsider and give us the opportunity to review your application. At Neo4j, we are committed to building awareness and helping to improve these issues

Desirable

• In this role you’ll be one of the founding members of the Product Analytics Platform team
• You’ll help define the technical foundations for how product analytics data is captured across Aura, building the Analytics API and underlying infrastructure that provides a consistent integration point for engineering teams across Neo4j
• You’ll have significant ownership over the design of the API, balancing the needs of multiple product teams with the long-term maintainability of the platform
• You’ll work closely with Product Management and other engineering teams to shape the solution, drive adoption, and evolve it as the platform grows
• 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