Runpoint needs interaction designers who can work directly in the medium of software.
The old loop was understand the user, design the flow in Figma, hand it to someone else, then wait to see what survived implementation. That made sense when building was expensive. With AI-native tools, the faster loop is often to build the first working version, put designer judgment on the live interaction, and keep tightening until the software matches what the client actually needs.
The Interaction Designer-Operator uses product taste, workflow empathy, and agentic tools to translate fuzzy client intent into useful product behavior. The job is to understand what the client is really trying to accomplish, shape the interaction, and help implement the better version in software.
What you will do
- Listen to client notes, Looms, screenshots, Slack threads, and live workflow feedback, then preserve the real user intent instead of flattening it into generic requirements.
- Turn ambiguous workflow needs into concrete product behavior: states, defaults, copy, affordances, handoffs, edge cases, and the small interaction details that make software feel obvious.
- Use Codex, Agentation, browser automation, and local product environments to build or direct the first working version of an interaction.
- Work in short design-build-refine loops, comparing the running software against the client's actual job rather than against a static mockup.
- Create lightweight artifacts that builders and agents can act on immediately: intent summaries, interaction notes, annotated screenshots, acceptance criteria, and refinement prompts.
What we need
- You have interaction design judgment and can explain why a workflow feels natural, confusing, overbuilt, or incomplete.
- You are comfortable working with live software instead of treating Figma as the only place design happens.
- You can use AI tools to explore, change, and refine product behavior without outsourcing your taste.
- You can sit with messy client context, infer the real job behind the request, and turn it into a sharper interaction.
- You move quickly in short asynchronous passes and know when a working prototype teaches more than another diagram.
Strong signals
If any of these describe you, the conversation will move quickly.
- You have designed internal tools, product workflows, support surfaces, implementation flows, or operational software where the user's job mattered more than visual polish.
- You can turn a messy client request into a working interaction, then explain what changed and why.
- You have strong opinions about defaults, empty states, progressive disclosure, copy, permissions, and handoffs because you have watched real users get stuck.
- You can record a short walkthrough showing how you used AI tools to move from client intent to a better software interaction.