Omana Dutta

Why this persona fits the audience

She works in Bengaluru for a 9-person cricket analytics startup building dashboards for clubs and sponsors. She bridges design and code in Tailwind CSS, keeps reusable chart and card components in a private repo, and still uses spreadsheets for stat inputs from the operations team.

• Age: 26
• Location: Bengaluru, India
• Occupation: UX Engineer
• Income: ₹24 LPA
• Education: Bachelor's in Computer Engineering
• Company size: 9
• Years in role: 2.5

“I tell people my job is like umpiring—everyone thinks it's about the big calls, but actually 80% of the game is just making sure the boundaries are consistently measured.”

Omana Dutta grew up in Kochi watching cricket matches with her father, who tracked players with spreadsheets when she was a teenager—planting the seeds for her career. She did her engineering at Rajagiri School of Engineering & Technology, where she developed a reputation for building projects that bridged beauty and function. After a brief stint at a Bangalore-based fintech company, she joined her current startup when they were still a 4-person team building basic analytics tools. Her breakthrough moment came when she convinced the team to adopt Tailwind CSS, which drastically reduced their prototyping time even as the team grew to 9 people. Now, as the only UX engineer, she's become the de facto design system architect, constantly juggling the tension between rapid iteration and long-term consistency. Her personal design library—a private Figma file and GitHub repo—has become the team's secret weapon, though she's frustrated by how much time she spends maintaining it when she'd rather be creating new systems. This year, she's determined to finish migrating older components to Tailwind, a project that's both thrilling (she can finally implement that gradient system she's been dreaming about) and terrifying (she knows the team will resist the temporary slowdown). She measures her professional success by how much time she saves others—whether it's through reusable components or teaching her colleagues how to structure data properly. Outside work, her two passions areAnalytics and indoor cycling, both of which she treats with the same relentless focus on improvement. She's currently saving for a trip to the Wankhede Stadium to watch a Test match, where she plans to take notes on player behavior that she can later analyze in her personal data projects. Despite her meticulous nature, she's deeply collaborative, often staying late to help junior team members understand design principles in a way that resonates with their coding backgrounds. Her biggest professional fear is that the team will grow too quickly without solid design foundations, forcing her to constantly play catch-up. Her biggest personal fear is that she'll look back in 10 years and realize she spent all her time helping others build things and none building something uniquely hers.

Background & daily life

A day in their life

Her weekday starts at 7:30am with indoor cycling to a Tamil hip-hop playlist while watching IPL highlights on mute. By 9am, she's at her standing desk reviewing the operations team's morning spreadsheet dump, mentally translating their chaotic data inputs into structured queries. The first 2 hours are spent refactoring components from the previous day, where she gets visibly frustrated when she finds uncommented code changes. Lunch is either dal khichdi from the office canteen or a quick Indian-Chinese delivery if she's deep in a design sprint. Afternoon meetings alternate between client calls (where she mentally translates technical jargon for laypeople) and internal syncs where she advocates for better documentation habits. Evenings are spent prototyping new dashboard interactions in Figma, occasionally pausing to debug a colleague's CSS that 'just needs to look customer-ready.' She ends the day by drafting a 5-minute standup memo for her distributed team, then cycles home to make a quick dinner while listening to a cricket analytics podcast. The last hour before bed is her personal time—either working on her side project (a open-source cricket analytics tool) or watching match replays, where she takes notes on player movements that might inform her work the next day.

Lifestyle

Omana splits her apartment with a wall-mounted stationary bike and a growing collection of cricket memorabilia—mostly autographed bats from lesser-known players she met at analytics conferences. Her routine revolves around avoiding Bengaluru's traffic by working late mornings and early evenings, with a daily 10am coffee run to Cafe Coffee Day where she reviews Figma files. She's gradually replacing her sneakers because she cycles to work 3 days a week but still keeps a mash-up playlist of Tamil and English hip-hop for those commutes. Money goes mostly to rent (₹20k), TakeoutPay orders, and a standing international subscription to Tableau conference recordings. Weekends are either spent hitting the gym or at local cricket grounds where she takes notes on player movement patterns for her personal analytics experiments. Her social life is small but intentional—weekly dinner with her cousin who works in fintech, and a rotating group chat with 3 other women in tech who argue about whether cricket analytics is art or science.

Work life

At the 9-person startup, Omama's days are a tightrope between 'ship fast' and 'make it exact.' Her biggest project this quarter is building an interactive player-performance dashboard for a local club sponsor, where she's struggling to balance the operations team's spreadsheet inputs with the sponsor's demands for 'cinematic' data storytelling. She'd ideally want to standardize all visual components in a shared repo, but the team keeps improvising quick fixes that create inconsistencies. Her manager trusts her to bridge design and code but gets nervous when she insists on refactoring components before deadline. The office has the chaotic energy of a team that's still figuring out its rhythm—some days she spends more time explaining why a design system matters to the junior devs than she does actually building. Her recent decision to switch from React to Tailwind CSS for new components was met with resistance, but she's quietly proving its worth by showing how much faster they can prototype. The pressure comes from having to explain technical debt to stakeholders who only care about 'seamless UX.'

Relationships

Her close-knit family lives in Kerala, and she video-calls her parents weekly to report on her health, work, and diet in that order. Her older brother in Dubai sends her cricket memorabilia from every trip, which she displays on a rotating wall in her apartment. In Bengaluru, she's close with 3 other women in tech—two from her previous job and one from her cycling club—who form her core support group for venting about misogyny in tech. Her immediate circle includes two coworkers she's convinced are the only ones who truly understand the importance of design systems. She's particularly influenced by women data scientists she follows online, especially those who talk about balancing technical rigor with storytelling.

How they decide

She's research-heavy and data-informed, but once she commits to a decision, she acts with conviction. She'll collect every possible data point (like comparing 3 different chart.js libraries before choosing one) but ultimately judges tools by how they solve specific problems for her team—not by hype. She prefers to consult 1-2 trusted peers before making work-related decisions, especially when it involves changing established workflows. Personal purchases often come after extensive online comparisons but with a tendency toward pragmatic middle-ground choices (like buying a mid-range stationary bike that can handle apartment living rather than splurging on a full smart bike).

How they sound

Speaks in measured, analytical sentences that build upon each other—often using analogies from cricket to explain technical concepts. Avoids technical jargon in mixed company but will happily explain why 'the design system is like field placements—you can improvise but only within certain boundaries.' Her humor is dry and self-deprecating, particularly about her own perfectionism ('I spend half my time trying to name things perfectly and the other half fixing other people's naming decisions'). She has a sharp eye for details but describes them calmly, without histrionics. When frustrated, she'll make cricket metaphors about 'bowling too many wides' or 'playing out of position.'