Frontend
Calm interfaces for messy flows
I like turning dense states, awkward workflows, and unclear UX into something people can trust.
Manvendra SinghFrontend engineerBackend aware
Melbourne, Australia / building calm software for messy problems
I design interfaces people can trust and build the systems underneath them well enough to hold up.
Most of my work starts at the product edge: dense UI, awkward workflows, unclear data, and the hidden complexity that appears after launch. I like turning that into something clear, fast, and sturdy.
Backend
Enough depth to shape the product well
I care about APIs, validation, auth boundaries, and data structures because they decide how clean the UI can be.
Systems
Labs that sharpen engineering judgment
Cloud, security, and infrastructure experiments help me understand what breaks once software leaves the happy path.
$profile --summary
Frontend engineer with a product lens, enough backend depth to shape better experiences, and a habit of turning labs into learning.
Setting Up Active Directory for Beginners
What I've Been Learning During My Internship at Diagno Energy
$stack --core
Next.jsTypeScriptReactTailwindNodeAPIsAuthMDX
Live site signal
Published content, served from a small route handler.
What I can own
Frontend polish matters more when the data contracts, loading states, and failure paths are solid too.
Frontend systems
Interfaces that stay readable under pressure.
- Design systems and reusable UI patterns
- Data-heavy views, progressive disclosure, and careful empty states
- Performance-aware rendering and interaction design
Backend surfaces
The server-side work that makes UI feel better.
- API shaping for real screens and product flows
- Forms, validation, auth, and sensible failure states
- Server rendering, content pipelines, and boring reliability
Labs and learning
Hands-on systems work that turns into case studies.
- Cloud and security experiments
- Infrastructure notes and setup guides
- Explaining what broke, why, and how I fixed it
Selected work
Case studies, labs, and shipped experiments that show how I work when the details matter.
I like projects that leave behind something useful: a clearer system, a better interface, a stronger mental model, or a write-up worth revisiting later.
Featured case studyAugust 13, 2025
Setting Up Active Directory for Beginners
I set up a small AD DS lab on Windows Server and wrote down the parts that actually mattered: DNS, time sync, group policy, and the bits that broke first.
Windows ServerAD DSGPOSecurityPowerShell
Open case study
Why this section exists
I want the portfolio to show thinking, not just screenshots.
The goal is to make the work legible: what I built, what I was trying to understand, what broke, and what I would improve next.
Read the full write-upLatest writing
Fresh note
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.
Read the articleBuild with me
Looking for someone who can shape the interface and think beyond the happy path?
Roles, freelance work, product ideas, or just swapping notes all fit here. A short message is enough.