Product & engineering
Product Engineer
Work directly with operators, build what solves their problems, and turn repeated patterns into product.
The mandate
Collapse the distance between understanding a customer’s operation and shipping the system that improves it.
The exact shape will evolve. We care more about the outcome you can own than preserving the boundaries of a job description.
The work
What day to day actually looks like.
The mix changes with the company’s bottleneck, but these are the recurring loops you should expect to own.
- 01
Talk with operators, watch how work actually happens, and map the costly gaps in their current process.
- 02
Prototype the smallest useful solution across interface, data, and backend behavior.
- 03
Ship quickly, instrument adoption, and return to customers to learn what changed in practice.
- 04
Polish the interaction and turn a successful bespoke fix into a reusable Trellis capability.
The outcomes
What success starts to look like.
- Take one painful customer workflow from discovery to repeated weekly use.
- Show clear adoption or time-saved evidence, not just shipped output.
- Convert what worked into a simple product pattern the team can reuse.
The person
Signals we look for.
You do not need to match every line. Show us evidence of slope, ownership, and the quality of judgment you bring to unfamiliar problems.
Could you own this at Trellis?
Apply with evidence of what you have built, changed, or learned unusually fast.