Product UI and tools engineers have to live in
Frontend and tooling at Soliton Technologies — the interfaces and command-line utilities that other engineers open every morning and never think about again, if they are done right.
Company
Soliton Technologies
Role
Project Engineer (prev. Intern)
Period
Jul 2021 → Nov 2023
Surface
Product UI, tooling, services
01 · Context
IndexChapter 01
Context
My first production work. Engineering tools have a particular quality: their users are captive. Nobody churns from an internal scheduling interface — they simply suffer it. That makes UX quality a matter of professional courtesy rather than conversion rate, and it is a good place to learn craft.
Chapter 02
What I built
A responsive dark theme
Shipped across the product UI. Theming taught me that a colour system is a contract, not a palette — the same lesson this portfolio’s token system is built on.
Drag-and-drop scheduling
A scheduling interface where the primary interaction is direct manipulation. Getting drop targets, keyboard parity, and undo right is most of the work.
A CLI for device monitoring
Multi-device support, real-time data retrieval, and performance monitoring from the terminal — because sometimes the best interface is not a page.
Python services behind it
Backend services working with a document store and object storage, so the frontend I was building actually had something honest to display.
Chapter 03
The system pathway
How the pieces connected — a generic view of the UI, tooling, and services layer, from the interface an engineer touched down to the stores behind it.
Product UI
A responsive dark theme shipped across the product surface — a colour system built as a contract, not a palette.
States the frontend handles
- Light
- Dark
- Responsive
Chapter 04
Frontend challenges
- Direct manipulation is an accessibility trap. A drag-and-drop scheduler that only works with a mouse excludes people. That realisation is why the workbench on this site’s homepage never requires dragging.
- Modernising a codebase is a social act. Moving toward modular, maintainable component architecture meant convincing people, not just refactoring files.
- Mentoring exposes what you only half-know. Teaching HTML, CSS, JavaScript, and Node.js to other engineers rebuilt my own fundamentals.
Lessons
What it taught me
- Real users change how you build, immediately and permanently.
- Internal tools deserve the same care as customer-facing ones. The users just cannot complain publicly.
- Working across the stack — UI, CLI, services — made me a better frontend engineer, not a worse one.