I design the parts of software people never have to think about — turning ambiguous problems into interfaces that feel obvious in hindsight. B.E. Computer Science graduate blending design craft with the ability to actually ship it.
I'm Praveenraja, a final-year B.E. Computer Science Engineering student at V.S.B. Engineering College with a foot firmly in both design and code. Most of my design work starts from a technical question — "can this actually be built the way I'm drawing it?" — which keeps my UI decisions grounded in what's shippable.
My path into UI/UX started the practical way: building interfaces in HTML, CSS and React and noticing how much of a product's success came down to decisions that had nothing to do with the code — hierarchy, spacing, the wording on a button, where a user's eye lands first. That gap is what pulled me toward design systems, wireframing and prototyping in Figma.
I'm currently looking for a UI/UX Design Internship where I can work on real products end-to-end — research, wireframes, high-fidelity screens, and the handoff conversations with engineers that make a design survive contact with production.
A blend of design craft and frontend fluency — I can take a problem from a blank canvas to a component a developer can implement without guesswork.
Each project moves through the same rigor — research, flows, wireframes, high-fidelity UI — applied to a different domain: food, retail, banking, healthcare and education.
Food delivery apps overload the home screen with promotions before a user has even decided what they want to eat. Decision fatigue, not lack of restaurants, is the real drop-off point — users abandon the app mid-browse more often than they abandon a cart.
A short survey and 6 informal interviews with peers who order food weekly showed the average session involved re-opening the app 2–3 times before ordering — mostly to re-compare places they'd already seen. The friction wasn't choice, it was re-finding choice.
Low-fidelity flows were sketched to validate the shortlist concept before any visual design — shown below as the underlying structure, now rendered at high fidelity.
An interactive Figma prototype connects Home → Shortlist → Restaurant → Cart → Checkout with realistic transitions, tested with 8 peers in moderated sessions.
Persisting a "shortlist" without adding a whole new save/favorite system users would have to learn.
Reused the existing search history model — restaurants a user views for 3+ seconds are auto-added to the shortlist, no explicit action required.
Shoppers add items to cart confidently but abandon at checkout once shipping fees and delivery dates appear late in the flow — the surprise, not the cost itself, is what erodes trust.
Competitive audits of 5 shopping apps showed shipping cost was disclosed after address entry in 4 of 5 cases — directly contradicting what users said they wanted most: "tell me the real price before I commit."
Showing full pricing upfront without cluttering the product card on smaller screens.
Collapsed shipping + delivery estimate into a single trust strip directly under the price, using a fixed height so layout never shifts as data loads.
Most banking dashboards present every account and every number with equal visual weight, forcing users to do the prioritization the interface should be doing for them.
Card-sorting with 5 participants showed users mentally group their finances into just three questions: "What can I spend today, what's due soon, and is anything unusual?" — the dashboard was redesigned around those three questions.
| Merchant | Category | Amount | Status |
|---|---|---|---|
| Amazon | Shopping | −₹1,240 | Cleared |
| Unknown POS | — | −₹4,999 | Review |
| Electricity Board | Utilities | −₹890 | Cleared |
Surfacing a flagged transaction without triggering unnecessary alarm for routine account activity.
Used a calm amber "Review" pill instead of red, paired with plain-language copy ("Doesn't match your usual pattern") rather than alarmist warning icons.
Appointment booking flows are often designed for calm, confident users — but people booking hospital visits are frequently anxious, in pain, or booking on someone else's behalf. Complexity here has a higher cost than in almost any other app category.
Interviews with 4 older relatives and peers revealed that "which doctor do I even need" was a bigger blocker than the booking mechanics themselves — symptom-based navigation was needed before specialty-based navigation.
Minimum 16px body text, 4.5:1 contrast ratio throughout, and symptom icons paired with text labels — never icon-only navigation.
Designing for a user who may not know medical vocabulary, without dumbing down the app for users who do.
Symptom-first entry point with specialty names shown as a secondary line beneath — both audiences get what they need in one screen.
Students juggling multiple courses lose track of what's actually due versus what's just available — most platforms list content, not priority, leaving planning entirely up to the student.
A survey of 15 classmates found "I forgot an assignment existed" was the most common reason for late submissions — not difficulty, but visibility.
Surfacing urgency without making the dashboard feel stressful to open every day.
Capped visible urgency badges to genuinely time-sensitive items only, and used a single calm gradient card as the entry point rather than a wall of red flags.
Posters, social creative and campaign banners — the same type and color discipline applied to marketing surfaces.
A consistent process is what makes five very different products feel like they came from the same design head.
A look inside the working file, not just the polished export — frame structure, components, auto layout, and the tokens holding it all together.
The engineering half of the profile — problem-solving, project delivery, and hands-on experience.
Placeholder figures — replace with your actual internship, LeetCode and project counts before sending this portfolio out.
Open to UI/UX design internships and junior product design roles. I reply fast — reach out any of the ways below.