ARYIKA MEHROTRA
PORTFOLIO / 2026 DESIGN × ENGINEERING

I design the logic behind the interface.

I'm Aryika, a computer science graduate working across product design, front-end experiences, and data systems. I like making complex workflows feel clear, especially when design decisions meet real technical constraints.

Explore selected work

Built around the problem.

Explore the scheduler case study
02 WEB PRODUCT · SHIPPED

From brief to internal launch in four weeks.

Designed and developed Info Edge's IT intranet portal for 200+ users. The work required translating department needs into a usable information structure and shipping within a tight timeline.

Info Edge · 2023DESIGN / DEVELOPMENT
03 FRONT-END · SHIPPED

Making online learning easier to navigate.

Worked on AshokaX's site front end, including the India@75 program UI, live forms, bug fixes, and updates. The platform supported 200+ course registrations and 5+ live forms.

AshokaX · 2022UI / FRONT-END
04 DATA WORKFLOW · IN USE

Reporting designed to run again.

At Accenture, I built scheduled SQL and Python campaign reporting on Databricks for beauty clients. Automating recurring reports cut 8–20 hours of manual effort per report; the work also supports dashboard and audience decisions across 12 APAC markets.

Accenture · 2025–presentDATA SYSTEMS
05 PRODUCT ENGINEERING · SHIPPED

Pricing logic inside an existing journey.

On MakeMyTrip's TripMoney team, I integrated a new markup calculator into the Java Spring Boot forex pricing service and tested rate-cache updates across 14 currencies and two product types.

MakeMyTrip · 2024BACKEND / API
06 / INDEPENDENT PROTOTYPE

An itinerary that uses preferences, not just a destination.

I built a personal AI itinerary prototype using embeddings and tool calling: city and user preferences in, a suggested plan with links out. It was shared with MakeMyTrip as an exploration, separate from my internship work.

AI PRODUCT EXPLORATION · PERSONAL PROJECT

One component.
Different voices.

A small, working exploration of shared structure and publication-specific expression. This study was built for this portfolio; it is not a Condé Nast project or its Verso system.

SYSTEM QUESTION What should remain consistent when visual identity changes?
INTERACTIVE SPECIMEN / 001

Editorial card

Publication voice
IDEAS / DESIGN

How a visual language finds its shape

A sample story to test type, spacing, color, and interaction across three publication voices.

Read the system notes
ACTIONS
View specification

Search this small specimen inventory.

  • Editorial card
  • Button
  • Status badge
CONTENT STATUS
DraftPublished

Two example lifecycle states.

ACTIVE TOKENS
Display face
Editorial serif
Accent
Oxide
Density
Measured
Corner
4 px
SHARED CONTRACT

Semantic article structure, heading order, focus visibility, tap target, responsive behavior, and content slots remain stable.

BRAND LAYER

Typography, accent, surface, density, and corners change through a small token set. The component keeps its meaning across variants.

ENGINEERING NEXT STEP

In a production library, I would implement typed React props, token packages, visual regression coverage, Storybook documentation, and keyboard testing. Those are proposed extensions, not claims about this specimen.

Read the system rationale and implementation notes

How I work across the handoff.

FRONT-END

Structure, behavior, finish.

I work with HTML, CSS, JavaScript, TypeScript, and React, including CSS-in-JS approaches. I think in semantics, responsive layout, interaction states, and reusable components. This portfolio's live specimen uses browser-native HTML/CSS/JS; its case study includes an inspectable React/TypeScript reference component.

DESIGN TOOLS

From exploration to handoff.

Figma for flows and interface design; Photoshop, Illustrator, and Canva for visual work. I have also built with Wix and WordPress. The scheduler screens show my Figma product design; I do not claim a Figma plugin in this portfolio.

DECISIONS

Evidence before polish.

I use competitor patterns, platform constraints, and stakeholder feedback to frame product choices. At Accenture, I work with quantitative campaign data; for the scheduler, the strongest evidence so far is research and design work, with launch metrics still pending.

COLLABORATION

Make the work legible.

I have worked with founders and developers on feasible publishing flows, taught technical courses to classes of 60+, and led a 25-person student initiative. Those experiences inform how I explain decisions and review work; they are not presented as managing a design system engineering team.

Explore the component specification, documentation, QA, and review approach

Curiosity with a practical edge.

My B.Sc. and postgraduate diploma in Computer Science at Ashoka University gave me an engineering foundation. My work has moved between interface design, web delivery, backend integration, and data products.

At Accenture, I build recurring SQL and Python reporting and maintain dashboards for beauty brands across APAC. At MakeMyTrip, I integrated a pricing service in a Java Spring Boot flow. Those roles sharpened how I think about dependable systems and the people who use them.

I’m drawn to design systems because the best ones connect careful visual decisions to reusable code and clear team conventions.