Product Designer (Tracking)

Huble | Time Tracking & Client Invoicing; Eu; Sur place; EUR 65 000 - 90 000; Plein temps

Résumé du poste

Huble | Time Tracking & Client Invoicing is seeking an experienced Product Designer to own end-to-end surfaces for timers, timesheets, and activity review. You will run weekly user interviews, pair with frontend engineers on the design-system surface, and shape the visual language for activity-state classification.

You will lead two cross-functional design reviews per quarter and document decisions clearly to align with privacy considerations and product goals.

Qualifications

• 6+ years in product design, including leading a surface end-to-end.
• Proficient in Figma and prototyping interactions, not just static mocks.
• Experience shipping privacy-sensitive surfaces and discussing trade-offs.
• Strong written communication; decisions documented in docs.
• Curious about engineering; able to read JSX and comment on PRs.

Responsabilités

• Design the timer, timesheet, and activity-review surfaces end-to-end.
• Run user interviews 1 day a week and translate findings into changes.
• Pair daily with two frontend engineers on the design-system surface.
• Own the visual language for activity-state classification (core, non-core, off).
• Lead 2 cross-functional design reviews per quarter.

Connaissances

Product design

Leadership

User interviews

Documentation

Cross-functional collaboration

Outils

Figma

Prototype interactions

Design systems

Description du poste

What you'll do

• Design the timer, timesheet, and activity-review surfaces end-to-end
• Run user interviews 1 day a week; turn findings into shippable changes
• Pair daily with two frontend engineers in the design-system surface
• Own the visual language for activity-state classification (core, non-core, off)
• Lead 2 cross-functional design reviews per quarter

What we're looking for

• 6+ years product design, with at least 2 leading a surface end-to-end
• Comfortable in Figma; can prototype interactions, not just static mocks
• Have shipped privacy-sensitive surfaces and can talk about the trade-offs
• Strong written communication — most decisions happen in docs
• Curious about engineering — you can read JSX and write a sensible PR comment