Java Software Engineer

We're building an AI system to accelerate teamwork for software teams. Most AI tools accelerate individuals; we want to accelerate teams. Starting by building systems that understand what teams are talking about, what needs to get done & bringing in contextual agents to move the work forward with minimal human effort.

The work you'll do: This role is about building the backbone that powers the intelligence systems that need to be fast, reliable, and ready to scale.

Platform Services: Build and extend our core orchestration layer that coordinates between integrations, AI services, and the product surface.

Integration Infrastructure: Own the systems that connect to Slack, Jira, Linear, GitHub, and calendarshandling OAuth, rate limits, webhooks, and data sync at scale

Real-time Messaging: Design and maintain the infrastructure for real-time communication between our backend and clients, with sub-100ms P99 latency targets.

Data Pipeline & Storage: Build efficient ingestion and storage patterns for high-volume workplace data while keeping query performance tight.

API Design: Design clean, well-documented APIs that power both our product and future platform extensibility.

Reliability & Observability: Instrument services for deep observability, build alerting, and own incident response for your systems.

Security & Compliance: Ensure our infrastructure meets SOC 2 and enterprise security requirements from day one.

You'll work on problems that combine: High-throughput event processing from workplace tools Multi-tenant architecture with strong isolation Coordination between synchronous APIs and async AI workloads Infrastructure that needs to earn enterprise trust Cost-conscious scaling decisions

You'll be building the foundation the product runs on, not just features on top. Who will thrive: You've built backend systems in production for 7 +years, ideally with Java, Kotlin or Go. You've worked with message queues, caching layers, and relational databases at a meaningful scale. You think about failure modes, retry strategies, and graceful degradation instinctively. You've dealt with third-party API integrations and know the pain of rate limits and webhook reliability. You prefer owning outcomes over just shipping features. You want to be an early engineer at a company where your work shapes the product's foundation.

Sahiba