> Markdown version of [/jobs/ext/4738470-ux-engineer](https://www.wearedevelopers.com/jobs/ext/4738470-ux-engineer). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md). --- # UX Engineer - **Company:** Tagetik Software srl - **Location:** Alphen aan den Rijn, Netherlands - **Experience:** Expert - **Contract:** Permanent contract - **Skills:** HTML, JavaScript (Programming Language), Artificial Intelligence, Cascading Style Sheets (CSS), Software Debugging, Github, Design of User Interfaces, Microsoft Visual Studio, Software Engineering, TypeScript, GitHub Copilot, Large Language Models, Claude Code, Front End Software Development - **Published:** November 16, 2026 - **Apply:** https://wk.wd3.myworkdayjobs.com/External/job/NLD---Alphen-Aan-Den-Rijn/UX-Engineer_R0060779 ## About the Role You can understand the real user problem (root cause), design a relevant solution, and make it real enough to test in working code. You are more technical than a typical UX designer, but this is not a software engineering role., * Roughly 3+ years of experience in UX, product design, design engineering, front-end prototyping, or a similar hybrid role. Strong evidence matters more than your past job title. * A portfolio showing how you moved from an unclear problem to a tested solution. * Experience working in a complex, highly regulated B2B/enterprise domain, such as legal, medical, finance, logistics, aerospace, etc., with complex workflows or data-heavy interfaces. * Solid interaction and UI design skills, including experience with design systems and prototyping. * Practical knowledge of HTML, CSS, and JavaScript/TypeScript. You should be able to build, inspect, and debug a functional prototype and identify issues at the interaction level. * Experience with Storybook, GitHub, Claude Code, and design tokens. * Enough discovery experience to ask useful questions, analyze workflows, test prototypes, and make design decisions based on the findings. * Ability to work with a design system and recognize when to reuse, adapt, or propose a change. * Comfort using AI tools for exploration and prototyping. * Clear written and spoken English. * Curiosity and good judgment when the brief is incomplete. ## Description As a mid-level UX Engineer, you will take semi-defined product problems and turn them into tested, workable solutions. Researchers, senior designers, or product managers will usually establish a broader opportunity. From there, you will analyze the available evidence, fill knowledge gaps, understand the user's context, define the specific problem worth solving, and build a functional prototype for testing and learning. This is not a strategic research role, but some tactical discovery is still an important part of the job. You need to know how to ask the right questions, connect with the right people, and use existing data to get to a concrete user problem. Much of the work happens in or close to the codebase, so you need enough technical skill to contribute on equal terms with other members of the team. You will organize the context and specifications, operate AI skills and agents, review outputs, and use classical UX artifacts (customer journeys, user flows, personas, jobs-to-be-done) in the formats relevant to LLM-assisted product development. Tasks and responsibilities Discovery * Partner with a senior designer or researcher and support discovery under their guidance, including stakeholder interviews, user interviews, workflow analysis, prototype testing, and synthesis of existing research. * Understand and contribute to UX artifacts such as customer journeys, user flows, personas, and jobs-to-be-done, and structure them in AI-readable formats. * Visually map user tasks and workflows to develop a deep understanding of what happens in the user's world and communicate that understanding to others. Our domain is complex, so visual thinking is a useful skill. If you enjoy diagramming and visual note-taking, this role will give you plenty of opportunities to do that. Delivery * Use product context, research, analytics, customer input, and domain knowledge to identify the actual user problem before jumping to a solution. * Design user flows, interaction patterns, layouts, and detailed UI states. * Explain design decisions clearly to Product, Engineering, QA, UX colleagues, and domain experts. * Build functional prototypes using approved AI-assisted development tools (GitHub Copilot, Visual Studio, Claude Code). * Use the Enablon and Wolters Kluwer design systems and access research through MCP to ensure solutions reflect both user needs and our internal standards. * Work with engineers to test interface behavior and propose evidence-based improvements. * Write clear, testable specifications covering behavior, rules, edge cases, and acceptance criteria. * Check usability and accessibility in both design and implementation. * Review implemented features with engineers and QA, identify UX defects, and help resolve them before release. Where appropriate, propose pull-request changes for straightforward UX improvements that are within your technical depth. What this role is not * Not a pure UI production role where requirements arrive fully formed. * Not a front-end engineer role focused on architecture, backend integration, or release ownership. * Not a senior strategy role responsible for setting the direction of an entire product area. The team You will work in a cross-functional team with Product Managers, Product Owners, Software Engineers, domain experts, and UX colleagues. A senior designer in your product domain will provide general UX direction and guidance, but you'll be autonomously responsible for a set of user problems (and resulting features). We value people who can make progress without waiting for every detail to be resolved. That does not mean working alone or guessing. It means making assumptions visible and connecting with others to get the missing information. Despite being a large company with mature processes, we rely on human relationships in the team a lot.