Member of Technical Staff, Product Engineering
Role and Responsibilities
Own the customer-facing product surfaces at PSI end-to-end. Design and build the web applications, dashboards, and workflow interfaces that physicists, researchers, and engineering teams use to run physics discovery on our platform.
Every screen ships with intent: clear information hierarchy, fast interactions, real-time feedback on long-running scientific workflows.
Translate raw platform capability into product experience. Our AI agents run multi-hour physics simulations, search experiment spaces, and produce results that users need to monitor, compare, and act on. Build the interfaces that make agentic physics legible, not opaque, to a working scientist.
Build for scale from day one. Component architecture, performance, accessibility, and observability are first-order concerns, not afterthoughts.
Drive product decisions, not just implementation. You partner with other engineers, platform engineers, physicists, and product managers to decide what to ship and how it should feel.
Strong product and design instincts. You can read a specification, identify what is missing, propose what should be there, and partner with designers and product peers when the role exists.
When the role does not exist yet, you can carry the product weight yourself with taste the team trusts.
Comfort working across the stack into APIs, data layers, and platform integration. The product is not a static site; it is a live interface to long-running scientific compute.
You have built systems that handle real-time updates, streaming results, and partial failures gracefully.
What We're Looking For
Five or more years building production user-facing products at companies known for engineering and product rigor.
You have shipped polished product surfaces that real users depend on, not internal tools or one-off prototypes.
Deep fluency with the modern frontend stack: TypeScript, React or comparable, the build and bundling layer, state management, and performance characteristics.
You have an opinion on component architecture and can defend it against simpler-looking alternatives that do not scale.
Strong product and design instincts. You can read a specification, identify what is missing, propose what should be there, and partner with designers and product peers when the role exists.
When the role does not exist yet, you can carry the product weight yourself with taste the team trusts.
Comfort working across the stack into APIs, data layers, and platform integration. The product is not a static site; it is a live interface to long-running scientific compute.
You have built systems that handle real-time updates, streaming results, and partial failures gracefully.
Nice to Have
Background in scientific computing, technical product surfaces (developer tools, data platforms, research interfaces), or other domains where the user is technical and the underlying capability is non-trivial.
Experience as the first or near-first product engineering hire at a fast-growing company, with a track record of standing up the function as the company scales.
Design tooling fluency (Figma, prototyping, design system construction) at the level where you can produce mockups and design tokens yourself when needed, even if a designer eventually owns them.
Open-source contributions to frontend frameworks, component libraries, or design systems that the broader community has adopted.