Product UI
Data-heavy screens, forms, loading states, and the small interface details that make software easier to trust.
Manvendra Singh / Melbourne, Australia
Frontend engineer building product interfaces and the API contracts behind them.
I like practical software: clear screens, predictable data flow, and write-ups that keep the next build from starting at zero.
01 / Work areas
Areas I work in
API boundaries
The shape of requests, validation, auth checks, and server behavior that decide how simple the frontend can be.
Systems notes
Cloud, security, and infrastructure labs, usually written up with the parts that failed and the checks that helped.
02 / Work
Selected work
All projectsA small archive of labs and case studies. The useful part is usually the setup, the failure mode, or what I changed after the first pass.
03 / Notes
Writing
Short notes from work, labs, and the bits I do not want to relearn from scratch.
What I've Been Learning During My Internship at Diagno Energy
What changes when your code has real users? A few lessons from my internship made that pretty obvious, pretty fast.
04 / Practice
A few rules I keep coming back to
- Ship in small pieces that can be reviewed and rolled back.
- Treat empty, loading, failed, and partial states as product work.
- Write down the fix while the weird details are still fresh.
05 / Site
Content index
06 / Contact
Send a note
Roles, product work, systems questions, freelance projects, or a useful technical conversation. A short message is enough.