Actively recruiting / 3 applicants
We’re here to help you
Juliana Torrisi is in direct contact with the company and can answer any questions you may have. Email
Juliana Torrisi, RecruiterYour job is to own the solution design, challenge assumptions (including the founder’s), and make sure what we build actually works for users before engineers touch it.
If you like being told exactly what to design, this role is not for you.
- Problem → Solution ownership
- Translate problem statements, not feature requests, into usable solutions
- Propose multiple solution options with clear tradeoffs
- Decide flows, defaults, edge cases, and failure states
- Push back when a solution is weak—even if it comes from the founder
- User validation before build
- Run weekly usability tests
- Test with customers in across multiple regions
- Turn qualitative feedback into concrete design decisions
- Kill bad ideas early (success = fewer redesigns after build)
- Design that engineers can ship without guessing
- Deliver design-ready artifacts:
flows / prototypes
acceptance criteria
copy for key states
edge cases (empty, error, permission, loading)
- Work closely with engineers to ensure feasibility without dumbing down UX
- Product-level thinking (not just UI)
- Understand workflows, constraints, and real-world usage
- Optimize for clarity, speed, and correctness—not aesthetics alone
- Maintain and evolve a lightweight design system only where it adds leverage
What you will not do
- Take pixel-perfect instructions and execute them blindly
- Design in isolation without user contact
- Hand off pretty screens and disappear
- Optimize Dribbble shots over usability
What success looks like (first 90 days)
- Engineering reports fewer UX clarifications and rework
- Founder stops micromanaging UX decisions
- Features ship with minimal post-release redesign
- User testing becomes a default habit, not an exception