If you are hiring for senior product design, UX/UI, or design engineering, reach me directly. Send the role, what the team is building, and where you need senior-level product thinking.
Want to see the work first? View selected product, UX/UI, AI, and front-end case studies.Reach me directly
Email is usually best for a job description, product link, team context, or a little background. Call when the role or product is easier to explain out loud.
Send the job description, team context, product link, or a few notes about what you need from the role. A rough explanation is enough to start.
Phone
Call when the role, team, or product is easier to explain out loud, or when you would rather talk than type.
What helps
A useful first message makes the role and product concrete. It does not need to explain the entire company or predict every detail of the job.
I would rather understand what the team actually needs than read a polished description that hides the hard parts.
What are you hiring for, and why does the role exist now?
What are you building or improving, and who is it for?
What would this person own, and where do product, design, research, and engineering meet?
Where are you in the hiring process, and when are you hoping to have someone in the role?
Common reasons to reach out
These are the kinds of full-time opportunities that are especially relevant. Each one links directly to email with a useful subject line.
Full-time role
Share the team, product, level of ownership, and why the role exists now.
Talk about a role0→1 product
I am a strong fit for teams defining a new product, major workflow, or experience where research, UX/UI, systems, and build decisions need to stay connected.
Talk about the roleComplex product + AI
I am a strong fit for mature enterprise products, complex workflows, design systems, AI-assisted experiences, and teams that want design close to engineering.
Talk about the roleWhat happens next