Design across the Guardian product surface: Guardian Releases, Guardian Monitoring, and the Software Factory, including the PR experience, auto-flagging flows, release health views, regression detection, rollback UX, and flag cleanup.
Work close to engineering: contribute to implementation decisions, understand technical constraints, and stay engaged through the build, not just at handoff.
Map and clarify complex workflows to identify UX debt and opportunities for improvement across Guardian's surfaces.
Ship production-quality work through multiple shipped states, iterate based on real usage, and maintain quality under delivery pressure.
Contribute to the UX strategy for your product surfaces alongside your fellow Guardian designer: understand current state, define future state, and articulate the tradeoffs in each path.
Partner with your PM and EM on scope, sequencing, and tradeoffs. Come with a point of view and advocate for strong user experiences.
Ground design decisions in evidence: engineering constraints, customer feedback, analytics, and design partner signals from the Factory Alpha and Beta programs.
Contribute to LaunchDarkly's design system: extend patterns for Guardian's specific interface types (monitoring views, pipeline states, health indicators) and build alignment across the UX team.
Participate in UX critique. Give and expect direct, specific feedback.
Requirements
6-8+ years designing complex, shipped digital products, ideally in developer tools, observability, CI/CD, incident management, or configuration-heavy B2B SaaS.
A portfolio that shows production-quality work across multiple shipped states: not just polished concepts, but shipped interfaces you iterated on and improved over time.
Real experience working alongside engineers: contributing to implementation and trade-off decisions, understanding what is hard to build, and staying engaged past the handoff.
Comfort with data-dense, stateful interfaces: monitoring dashboards, pipeline views, health indicators, or any surface where users need to understand the current state of a system and take action.
Developer user empathy: enough context to design for users whose daily tools include terminals, CI dashboards, observability systems, and pull requests.
History of operating as a genuine partner to PM and Eng, shaping work direction rather than waiting for requirements.
A portfolio that demonstrates production-quality execution at speed, engineering proximity, and at least one example of a data-dense or technically complex interface shipped to real users.
Must be authorized to work in the US or Canada (no visa sponsorship or relocation offered at this time).
Ability to collaborate during core hours overlapping Pacific Time.
Occasional travel (up to 10%) for team onsites, planning sessions, or customer visits.
Portfolio required, showing production-quality execution on technically complex products.