Principal Full Stack Software Engineer (P60) — Growth

As a Principal Full Stack Software Engineer (P60) on Starburst, you will serve as the lead technical anchor for multi-quarter onboarding and cross-flow initiatives across Atlassian's product suite. You will bridge complex frontend micro-frontends with robust backend integration services and experimentation infrastructure. Working at Atlassian Atlassians can choose where they work – whether in an office, from home, or a combination of the two. That way, Atlassians have more control over supporting their family, personal goals, and other priorities. We can hire people in any country where we have a legal entity. What You’ll Do Lead System Architecture: Define the technical vision and architectural patterns for multi-product Onboarding and CrossFlow experiences across Confluence, Loom, and TWC. Build End-to-End Solutions: Write production-grade code for high-complexity full stack features spanning React/TypeScript micro-frontends and scalable backend microservices. Champion Growth Engineering: Architect fast, robust experimentation frameworks and instrumentation (Statsig, telemetry) to power rapid hypothesis testing and conversion optimization. Bridge Multi-Product Teams: Partner across product boundaries (Loom, Confluence, Platform) to deliver seamless shared surfaces and cohesive API contracts. Drive Operational Excellence: Safeguard application performance, reliability, and observability while driving down operational toil and defect rates. Multiply the Team: Mentor senior engineers, author high-impact RFCs/tech specs, and elevate the technical craft across the Growth organization. 1. Technical Architecture & Cross-Product Systems Architect cross-product surfaces: Lead the technical strategy and architecture for end-to-end user journeys connecting Loom, Confluence, and Jira (e.g., embedding Loom async video capture/preview within Confluence or Jira workflows). Define clean integration patterns: Design robust API contracts (GraphQL, REST) and modular micro-frontend components that embed seamlessly into disparate host applications without causing performance or latency regressions. Author foundational Technical Specs & RFCs: Write comprehensive technical specifications, evaluate build-vs-buy decisions, and drive technical consensus across multiple engineering squads and platform teams. 2. Growth Experimentation & Telemetry Rigor Drive high-velocity experimentation: Partner with Product Managers and Data Scientists to design, instrument, and launch complex A/B and multivariate experiments (using Statsig/feature flags) to accelerate trial starts, activation, and conversion. Build clean experiment architectures: Structure frontend and backend code so experiments can be launched, modified, and cleaned up quickly without accumulating unmanaged tech debt. Own attribution & telemetry pipelines: Ensure accurate end-to-end event logging and funnel telemetry to maintain high data fidelity and minimize Time-to-Detect (MTTD) for funnel or attribution bugs. 3. Hands-on Execution & Foundational Prototyping Deliver complex/foundational code (60–70% hands-on): Build critical paths, shared libraries, and proof-of-concept prototypes that pave the way for other engineers. Lead platform consolidation & modernization: Decommission legacy flows, unify fragmented onboarding/activation mechanisms, and build reusable patterns for cross-flow journeys. 4. Cross-Functional Collaboration & Triad Leadership EPD Triad Partnership: Work closely with Product Management, Product Design, and Data Science from early ideation through execution and post-launch experiment analysis. Partner across org boundaries: Align with core product teams (e.g., Confluence Core, Loom Engineering, Platform/Identity, Commerce) to resolve shared dependencies and navigate host-app constraints. 5. Operational Health, Performance & Reliability Uphold performance & latency guardrails: Ensure onboarding modals, embedded video players, and cross-flow triggers do not degrade host-page load