Product Engineer

About the role

WHO WE ARE

Percepta’s mission is to transform critical institutions with applied AI. We care that industries that power the world (e.g. healthcare, manufacturing, energy) benefit from frontier technology.

To make that happen, we embed with industry-leading customers to drive AI transformation. We bring together: https://challenge.percepta.ai

- Forward-deployed expertise in engineering, product, and research

- Mosaic, our in-house toolkit for rapidly deploying agentic workflows

- Strategic partnerships with Anthropic, McKinsey, AWS, companies within the General Catalyst portfolio, and more

Our team is a quickly growing group of Applied AI Engineers, Embedded Product Managers and Researchers motivated by diffusing the promise of AI into improvements we can feel in our day to day lives.

Percepta is a direct partnership with General Catalyst, a global transformation and investment company.

ABOUT THE ROLE

We're hiring Product Engineers to build cross-cutting products that become the foundation for multi-engagement tools that enable Perceptrons to more easily deliver their best work, and help to continue to show our differentiation.

Most of Percepta's engineering is forward-deployed, and we believe it’s essential for you to get exposure to the field. Our operating model is: Someone embeds with a customer, learns their systems, and ships. That work is real and it's why customers trust us. The products that will generalize across customers don't get built well from a distance, and we are excited to invest in our product team to make sure we have deep focus on getting this right.

In your first several months, you'll work alongside a customer team doing real delivery work in the field: shipping into their environment, sitting with their constraints, finding where the duct tape is. You understand that context is earned, and this is a mission to feel the pain of our engineers and clients in the field, and build a deep sense of empathy and understanding for what you’ll build next.

Once you’ve had ample time to get a deep sense for the places we should invest, you'll have time that isn't attached to a customer contract to get a first working version of something in front of engineering leadership, and you should expect to make the case for it: Who it's for, why it matters past this one account, how it's built, what it does today. If it holds up, you own what comes next. Roadmap, rollout, adoption, all of it.

A meaningful share of your time will be dedicated to exploring and creating product wherever you think the gap is; the rest goes at things we already believe need to exist. The bar for the former is that you can say who buys it, why now, and what it replaces.

Two shapes of product come out of this, and you don't have to pick before you've seen an account up close:

Vertical. Something deep in one industry. Operationalizing a hospital system, for example, where the product is inseparable from how that industry actually runs and the commercial story is specific.