Engineering Manager, 3D Platform

Dream Big. Build Fast

  • Glendale, Arizona
  • 18 days ago

    Highlights

    You will build and lead a team of engineers dedicated to the 3D platform, own its architecture, quality, and performance, and make it a platform other engineering teams love to build on. You will lead Moon's 3D platform: the real-time, in-home 3D design experience at the heart of how our customers' designers sell - built on React Three Fiber and Three.js.

    Numbers & Facts

    LocationGlendale, Arizona

    Description

    Role Overview

    You will lead Moon's 3D platform: the real-time, in-home 3D design experience at the heart of how our customers' designers sell - built on React Three Fiber and Three.js. You will build and lead a team of engineers dedicated to the 3D platform, own its architecture, quality, and performance, and make it a platform other engineering teams love to build on.

    About the role

    •   You will own a product area that is core to how our customers sell. The 3D experience runs on tablets, in customers' homes, in front of homeowners - and it must be fast, reliable, and beautiful everywhere it runs.

    What you'll do

    •   Build, hire, and lead a team of engineers dedicated to the 3D platform.

    •   Own the architecture and technical direction of the 3D application and its data.

    •   Own performance budgets for real-time 3D on tablets in the field - render performance is a sales metric here.

    •   Set the quality bar: versioned releases, documentation, and clean interfaces for the teams that build on your work.

    •   Work with product to own the platform's success metrics and deliver them through disciplined iteration.

    •   Stay hands-on: read code, review designs, ship when it matters.

    Qualifications

    •   8+ years of engineering including leadership of 3D/graphics or real-time rendering teams.

    •   Deep React Three Fiber and Three.js production experience; strong WebGL fundamentals.

    •   Has taken ownership of a substantial existing codebase and improved it without breaking delivery.

    •   Library/API boundary discipline - can describe an interface they refused to widen and why.

    •   Player-coach who still reads and ships code.