Netherlands · Trimble

Private brief: not for distribution Six case studies, shipped mobile apps and one personal build, selected for this review: including client work not shown publicly. The case studies are password-protected; you'll find the password in my CV.

Nitesh Reddy

Product designer at Trimble, Netherlands. Across regulated, technical, multi-stakeholder domains — research, design and engineering fluency in one pair of hands.

Teaching what the work taught me.

Presenting, mentoring and documenting, so the methods outlast the project.

Internal · Trimble · March 2026

AI workflows for product managers and designers

A session on integrating AI tooling into the design and product workflow — where it accelerates, where it misleads, and what changes in how a team operates when the tooling is good enough to use daily.

External · ADPList · 2025 — now

Design mentoring

Portfolio reviews, career direction and craft conversations with designers at different stages, from first portfolio to senior transition.

Six practices, each one load-bearing.

Each one carries at least one project in this brief.

01

End-to-end product design

Scoping → research → IA → interaction → UI → handoff. Comfortable owning the whole arc or slotting into any part of it, on teams that already have their own rituals.

02

Design systems at scale

Created, scaled and governed systems for banks, railways and industry — tokens, patterns, Storybook and Figma parity, plus the governance that keeps them alive after launch.

03

UX research

Heuristic evaluation, usability and A/B testing, interviews, surveys, and customer discovery in complex B2B segments where users are specialists, not consumers.

04

Code-driven prototyping

Beyond Figma — local code prototypes that make design decisions engineering-informed: desktop shells, browser builds, and native iOS and Android where the platform's own conventions are part of the problem.

05

Complex, regulated domains

Banking, insurance, rail, health, energy, construction — anywhere being wrong costs money, time or safety, and the constraint is the brief. The sector changes; the discipline of understanding it before drawing doesn't.

06

Technical and engineering fluency

An engineering degree and years shipping into real product repositories — I read the codebase, work with the people who build it, and design to the actual constraint. It transfers to any technical domain, from a bank's data flows to a health platform.

Eight years, three countries.

In-house, agency and studio-of-one, comfortable as the only designer or one voice in a multi-team programme.

2024 — now

Product Designer · Trimble

Netherlands
2023 — 2024

UX Designer · Peter Schmidt Group

Berlin
2022 — 2023

UX/UI Designer · Neural Jam

Berlin
2017 — 2023 · own studio

Contract Designer & Owner · nnrdesign

Milan
2025 — now · alongside

Mentor · ADPList

Remote

Engineer by training, designer by craft.

Nitesh Reddy

Eight years, almost entirely where the domain is the hard part.

  • Started in sketching; sharpened at Titan, watchmakers, where design met a manufacturing standard, not a visual one.
  • Engineering degree, then an MSc in Integrated Product Design, Politecnico di Milano. Most of the rest, self-taught.
  • Product, UX and UI across fintech, telecom, translation, e-commerce, HR, ed-tech, transport and health.
  • The engineering half is why I read the codebase before I open Figma.
  • Off-screen: mountains, drone photography and film, audiobooks, and non-profits.

What people I've worked with say

"Nitesh demonstrated exceptional organizational skills and was deeply involved in the research, leading to a seamless onboarding process."
Simone Perone Simone Perone VP, Translated
"Nitesh enriched the Star team with his positive nature, motivation, and passion, making our collaboration successful."
Tobias Skuhra Tobias Skuhra Design Director, Star
"I worked with Nitesh and he designed our whole app from scratch."
Laurin Hahn Laurin Hahn CEO, Jobticket+ Ticket+ on the App Store ↗

AI is in every part of how I work.

What changes is the speed, not the quality trail. I own the judgement, the tooling handles the repetition, and everything it produces is checked against the source before it ships.

In the method

An AI-integrated design workflow

Research, synthesis, spec and handoff run through an AI-assisted process I've built and refined, and one I've run as an internal session for product managers and designers.

In the product

Automation as a feature

AI-driven recommendations designed with explicit consent, and a plugin that replaced a manual icon pipeline, about 93% less time to produce one icon.

In the build

Built AI-assisted, end to end

My personal builds are engineered with AI in the loop and guarded by a full automated test suite, so the workflow is pressure-tested on real systems, not slideware.

Where the line is

AI removes the repetition, not the accountability. I own the judgement, the direction and the final call on what ships. Sensitive material is handled to whatever a team's security setup requires, local-only included.

How I approach the interesting ones.

01What do you do when the brief is wrong?

At Translated the brief was "ask for less" at sign-up; the research said the opposite. A shorter form starves the matching engine, whose signal comes mostly from onboarding. I made the case for adding steps against a completion target and A/B-tested it into production (the numbers are on the Translated case). The senior part isn't the screens; it's changing the question before answering it.

02When you're the most senior designer in the room, how do you make the call?

At Trimble there's no design authority above me. Sign-off is collective, run in-session with the PMs and QA, but the product decision and its trade-offs are mine. Across eight products the domain experts hold the domain and I hold the call — the same seat I held in banking, rail and insurance; on VDC it meant fusing two products' heritages into one command architecture and defending what it cost.

03What happens to the work after you hand it over?

It keeps shipping without me. That's the test. Ticket+ was designed end-to-end and handed off; Gorilla Fitness runs on a foundation I set, now iterated by Kabata's in-house designer (both in Selected work above, with the numbers). A handoff works when it's designed so the next person's decisions are easy, not just your own.

04What do you change about how a team works?

Two things, beyond my own output: handoff stops being a static Figma spec and becomes something engineers can read and run, and an AI-integrated workflow takes the repetition out of research, spec and QA while judgement stays with a person. Both have been adopted by other designers and a dev team. The return on a senior hire is partly what the people around them start doing better.

( Get in touch )

Questions on any of these?

Happy to walk through any case study live, or answer over email. The password for the protected cases is in my CV.

Netherlands · CET · usually replies within a day