Use Case Developer (Junior)

Role summary You're the link between our internal product owners and our automation engine. Product owners bring you requirements; you understand them, translate them into use cases using our automation engine, and make sure the result is correct. When the AI gets the logic wrong, you fix it in code. Over time you also help develop the automation engine itself. The role has two sides. One is human: working closely with product owners, asking the right questions, and understanding what they actually need. The other is technical: driving an AI automation engine, reviewing its output critically, and fixing logic by hand. This is a junior role, and you won't be doing it alone. A team of senior developers stands behind you to support, teach, and review your work. We don't expect you to be excellent at any of this from day one — we expect you to learn, and we'll help you get there. What you'll do • Work closely with internal product owners — receive requirements, ask clarifying questions, and make sure you understand the intent before building anything. • Translate requirements into use cases using our automation engine. • Review the engine's output critically: is the logic correct, complete, and aligned with what the platform does? • Fix use case logic by hand when the AI gets it wrong — reading and writing code, not just editing text. • Feed structured feedback back into the system so its output improves over time. • Contribute to the automation engine itself: improvements, new capabilities, bug fixes. Must-have • Strong communication. You can talk to product owners, draw out real requirements, and turn vague asks into something precise. • Working knowledge of JavaScript and Python — you can read, write, and debug at a junior level. • Structured thinking: you break messy requirements into clear, testable use cases. • A critical eye for AI output — you don't take it at face value, and you're willing to dig into why something looks off. • Comfort using AI tools as a daily driver. Nice-to-have • Understanding of how LLM-based systems behave (prompting patterns, failure modes). • Interest in the maritime / operational-data domain. • Git and ticketing tool experience (Jira, Linear, or similar).