Regular/Senior UX Designer

UX design for complex design tooling, at the intersection of design and engineering. This is a UX design role inside Qt's Design Tools Unit (DTU). The tools serve designers and developers building production Qt applications - people with deep domain knowledge who form opinions about tools quickly and expect them to be well-considered at every level.

We are hiring at two levels: Regular and Senior. Both work the same products alongside the same engineering teams; what differs is scope of ownership and the level at which each contributes to product direction.

DTU works deeply with engineering. Design that can't be built costs everyone time. UX designers here - at either level - understand implementation constraints, propose solutions that work within them, and stay close to the build. This is genuine collaboration with engineers, not handoff.

Requirements

Regular UX Designer

• Two or more years of UX design experience, with a portfolio showing solid work across flows, wireframes, and interaction design.
• Comfortable in Figma.
• Able to collaborate with engineers through implementation and communicate design decisions clearly to people who weren't in the room when they were made.
• Some exposure to design or development tooling is a genuine advantage - DTU's product users are design professionals themselves, so the UX is always under scrutiny.

Senior UX Designer

• Five or more years of UX design, with a portfolio demonstrating ownership of complex product surfaces, not just individual features.
• Able to hold a design problem from research through delivery and articulate the reasoning behind decisions at every stage.
• Figma to professional standard.
• Real understanding of the designer-developer workflow.
• DTU's products live at that boundary and the person in this role needs to understand both sides.
• Comfortable designing for technically sophisticated users.
• Experience in design tooling, developer tools, or B2B software is a strong advantage.
• A background on larger product teams - where decisions in one area created real dependencies in others - is directly relevant.

Main responsibilities

• Interaction and flow design.

User flows, wireframes, and interaction patterns for product surfaces. Both the core feature design and the detailed interaction states between them. The goal is designed behaviour that is obvious to the people using it, even when the problem it solves is not.

• Prototyping and validation.

Prototyping flows to test assumptions before committing them to engineering. Bringing user feedback in early enough that it can still change direction, not after the build is already done.

• Engineer collaboration.

Working alongside engineering through the full development cycle. Communicating design intent clearly, answering questions that come up during build, and staying close enough to delivery that the design doesn't drift in ways that matter.

• Design system.

Using DTU's shared design system correctly. Raising gaps to the system maintainer rather than solving them in isolation.

• UX and visual design boundary.

DTU has distinct UX and visual design roles working the same product surfaces. Being clear on what UX owns and where visual design takes over - and collaborating across that boundary cleanly - is part of what makes the work here function well.

What the senior track adds

• Product surface ownership

End-to-end UX responsibility for a product surface or major feature area - from problem definition through shipped product. Not treating delivery as the finish line, but staying close enough to see how it lands with real users.

• Product strategy contribution.

A point of view on product direction: which are the right problems, what trade-offs are worth making, where the team might be undervaluing something. Senior designers here are expected to push back on scope and shape what gets prioritised.

• Research as design input.

Planning and running user research to validate direction early. Synthesising findings into decisions, not just reports. At Senior level, research is a design input, not a separate workstream - it informs what gets designed and why.

• Design system contribution.

Not just applying the system, but contributing to it: flagging where interaction patterns need library support, and working with the system maintainer to address gaps through process rather than workarounds.

• Systemic thinking.

Spotting dependencies between product areas early, before they create problems. Bringing the right people into conversations before decisions lock. Experience from larger product teams, where cross-area collaboration was unavoidable, maps directly to what this level of the role requires.