# Aparna Balasubramanian — Product Designer > Plain-text version of https://aparnabee.com, for AI assistants and anyone reading without a browser. Every page's copy is here in reading order, with links to its images and videos. Generated 2026-11-13. Résumé (PDF): https://aparnabee.com/assets/aparna-balasubramanian-resume.pdf Contact: aparnnaa98@gmail.com · https://www.linkedin.com/in/aparnabla/ The live site is a hand-illustrated "virtual park": a signpost leads to case studies, my résumé, socials and my journey; the case studies sit in underground chambers. Everything was designed and illustrated by me. ## Résumé ### Aparna Balasubramanian Product Designer aparnnaa98@gmail.com · https://www.linkedin.com/in/aparnabla/ · aparnabee.com #### Summary Product designer with 3+ years of building 0 → 1 products at start-ups and agencies, shape shifting between health tech, compliance SaaS, restaurant tech and legal tech. Often the sole designer, I run research, set up visual styles and design systems, prototype, test and ship alongside PMs and engineers. Before this, I studied fashion and ran my own vintage clothing business, which is where I learnt to start with the customer. #### Skills & tools Skills: Product design, UX research, usability testing, interaction design, design systems, prototyping, visual design, illustration, 0 → 1 product development, B2B SaaS, AI-powered experiences, success metrics Tools: Figma, Adobe Photoshop, Illustrator, Hotjar, Claude #### Experience **Product Designer · Mave** Nov 2025 – Jul 2026 · Health tech, software for hardware · 0 → 1 - Sole designer on the companion app for Mave’s tDCS headset; designed the app from scratch and shipped it in 3 months with 1 PM and 1 engineer (including development). - Created Mave app’s new visual style and design system - Designed the manifesto and launch websites **Product Designer · Commenda** Sep 2024 – Nov 2025 · Compliance SaaS · 0 → 1 → 10 - Sole designer on the platform that moved Commenda’s entity formation and compliance services off email and into one workspace for customers and service delivery agents, collaborating with PMs, engineers and even users - Designed and maintained Commenda app’s component library - Built information architecture for Commenda’s multi-product dashboard **Product Designer · Parallel HQ** Jun 2023 – Sep 2024 · Design agency Urban Piper — restaurant tech - Researched pain points in menu configuration and aggregator publishing; designed a flexible menu structure for custom menus across multiple locations. - Ran discovery, rapid prototyping and user testing for Periscope, a real-time dashboard showing restaurants missing branches and menu items on delivery platforms. Dell — health tech, AI - Planned and ran an AI design sprint to prototype AI features for Chief Health Officers’ NCD app workflows, and created vision types for AI-driven solutions. Agami — legal tech - Worked with Agami, eGov and Samagra on fully functional e-courts that shorten a case’s lifespan through async submissions and court orders. **Founder · The Fine Finds** Jan 2020 – Jul 2023 · Vintage clothing business - Was one of the first few businesses to shape India’s online thrifting culture. - Curated and mended second-hand vintage clothing; sold 4,000+ pieces over 3 years and grew an Instagram following of 12.5k. - Managed 8+ vendor relationships, got featured in newspaper articles around sustainable fashion and thrifting, created marketing collateral and ran 6 pop-up events. #### Education B.Des. Fashion Design · NIFT Bengaluru · 2016 – 2020 Google UX Design Certificate · Coursera · 2022 #### Volunteering - Clothing QA Volunteer, The Shift (Apr 2024 – present): sorted and graded donated clothing for clothing swap events. - Research Fellow, Uninhibited (Oct 2022): interviewed women from marginalised communities to assess sexual health education programmes. - Research Fellow, Pollinate Group (Jun – Jul 2019): community outreach on clean drinking water and clean cookstoves; market research on locally sourced products; a leadership programme for women. ## Home page (https://aparnabee.com/) Hello! I’m Aparna I see the world in simple shapes I’m a product designer with 3+ years of experience making complex B2B and B2C products feel simple. I solve problems the way I built this park: One shape at a time. Signposts: My journey · Case studies · Resume · Socials Case study: Case study — Mave: Designing software for hardware (Health tech, 0 → 1) Case study: Case study — Commenda: Weaving email threads into a real product (SaaS, 0 → 1 → 10) Case study: Case study — Juggling domains at an agency: Health-tech, Legal-tech, Restaurant software Note: I think that the most impactful designs are ones inspired by our physical environment. Note: Click the purple “my journey” button right above my head if you’re curious about how I got here :) Mudlarking This is the activity of searching muddy areas (famously in the UK) for lost or discarded historical artifacts. I did this in London. A dream come true. I love that I can find pieces of history that I can keep. Fossils: Ammonite A coiled sea creature related to squid and octopus. Ammonites lived for over 300 million years, built their shells in perfect spirals, and went extinct with the dinosaurs 66 million years ago. Fossils: Scallop The fan-shaped shell. Scallops have been around for more than 200 million years and still live in the sea today, so this one has some living relatives on your dinner plate. The Fly Agaric Amanita muscaria A stunning but dangerous mushroom famous for its signature appearance. I love finding mushrooms and seeing this one out in the wild is on my bucket list! Here’s a little something just for you! I’m fishing for new work! If you’ve made it this far, I’d love to get in touch. Here’s where you can find me: aparnnaa98@gmail.com @aparnabla Case studies: Designing software for new age hardware Weaving email threads into a real product Agency work Browse: My journey Resume Case studies © 2026 Aparna Balasubramanian ## Case study 1: Designing software for new age hardware — Mave (https://aparnabee.com/mave.html) Mave app [Image: Mave app screen (UI design)](https://aparnabee.com/assets/mave/s129319.png) B2C Health tech Mave 0 → 1 Designing software for new age hardware This case highlights specifically how we built guidance into a hardware companion app while designing the entire app from scratch! The entire app was designed and built with 1 Manager, 1 Engineer and 1 Designer in 3 months (timelines include development) fuelled by hours of white boarding, sketching and debating tradeoffs. Mave headset Case study written and illustrated by me Skip to final screens My Role As the sole designer on this project, I did the following: Created Mave’s new visual style + design system Designed the entire app from scratch, utilising notes from 50+ demos (conducted using the previous version of the app) Collaborated with PMs, engineers and founders to build something that had Mave’s voice Polished UI inside the Mave app codebase Designer of things Aparna Bala Mave’s headset boosts the brain’s neuroplasticity through 20-min sessions conducted on its app Mave’s tDCS headset delivers mild electric current through the prefrontal cortex, clinically proven to help with depression, anxiety and ADHD. Apart from individuals experiencing the aforementioned conditions, the headset also attracted “biohacking” individuals who wanted to optimise their health to the max. To conduct sessions, there was a simple app built with the sole purpose of starting, pausing and ending tDCS sessions. This, along with one-on-one introductory demos for pilot users, was doing the job when there were only a small bunch of users. But users could not understand this technology without also having a one-on-one demo first With hundreds of orders pouring in, one-hour demos for each user was near impossible (especially considering that there was only one person for the job). ​ Pre-launch, the team had collected insights from the 50+ demos. From this, we understood the common sources of anxiety, what people found most confusing, and much more. ​ There was always going to be something a little freaky about voluntarily zapping yourself and even our bravest demos saw some hesitation and many questions. It’s raining Maves! We had to ask- Can the app give users the same feeling of safety and reassurance as our demos? We started by understanding what kind of guidance users needed Pre-launch, the team had collected insights from the 50+ demos. From these demos, we understood the common sources of anxiety, what people found most confusing, and much more. To find the right guidance users needed, we looked at the following: The questions users were asking before, during and after demos Places users got the most stuck Concepts and protocols unique to Mave and tDCS Here’s roughly what we ended up with: Post-session feeling sensation reassurance Concept: soundscapes When to remove device Concept: intensity Concept: ramp up Device care 5 day routine wearing instructions For this guidance to land, it had to be in the right part of the user journey We thought of 3 distinct phases considering that the goal was to have users fairly educated about Mave’s headset and tDCS by the end of their first session. Onboarding/ Pre-session There could be a little more material here as users would come in with a fresh mind and from a place of curiosity. Good for guidance on the device & tDCS. wearing instructions sensation reassurance When to remove device In session Concept: ramp up This is when the session’s tingling kicks in. It’s also when the user sees the session’s UI for the first time. Information had to be short, easy to consume and focused on the session’s main concepts. Concept: intensity sensation reassurance Concept: soundscapes Post-session This section should answer the common questions: What comes next? Is what I’m feeling right now normal? How often do I need to do this? Post-session feeling Device care 5 day routine After knowing what to say, we needed to figure out how it’ll look We then needed to find visuals that complemented Mave’s tech-meets-wellness position. I picked the home as a sample screen and tried just about everything that felt “Mave” based on my conversations with the team and the company mission. Existing app Exploration #1: Try everything that feels Mave [Image: Mave app screen (UI design)](https://aparnabee.com/assets/mave/s137668.png) [Image: Mave app screen (UI design)](https://aparnabee.com/assets/mave/s137979.png) [Image: Mave app screen (UI design)](https://aparnabee.com/assets/mave/s138160.png) [Image: Mave app screen (UI design)](https://aparnabee.com/assets/mave/s138352.png) [Image: Mave app screen (UI design)](https://aparnabee.com/assets/mave/s137783.png) Warm colors meets sharp fonts and sharp colors Artistic, calming and with a warm energy Grounded in real life, clean visuals Shapes that felt approachable, yet technical Exploration #2: Expand on one style [Image: Mave app screen (UI design)](https://aparnabee.com/assets/mave/s138665.png) [Image: Mave app screen (UI design)](https://aparnabee.com/assets/mave/s138857.png) [Image: Mave app screen (UI design)](https://aparnabee.com/assets/mave/s139057.png) [Image: Mave app screen (UI design)](https://aparnabee.com/assets/mave/s139256.png) colors, glows, grain try the dark version darker, more glowy more emphasis on info, with shape only as a supporting element Exploration #3: Different states using the one style [Image: Mave app screen (UI design)](https://aparnabee.com/assets/mave/s139410.png) [Image: Mave app screen (UI design)](https://aparnabee.com/assets/mave/s139545.png) [Image: Mave app screen (UI design)](https://aparnabee.com/assets/mave/s139681.png) [Image: Mave app screen (UI design)](https://aparnabee.com/assets/mave/s139820.png) The association between shapes and states is information the user would need to store in their heads. Can we make associations between shapes and states clearer? Final explorations: The pivot to dots Dots felt universal and could come together to form different shapes that carried different meanings. [Image: Mave app screen (UI design)](https://aparnabee.com/assets/mave/s141956.png) [Image: Mave app screen (UI design)](https://aparnabee.com/assets/mave/s141330.png) [Image: Mave app screen (UI design)](https://aparnabee.com/assets/mave/s139961.png) [Image: Mave app screen (UI design)](https://aparnabee.com/assets/mave/s142583.png) The result was information that took the right form and sat in the right places *and in the right hierarchy [Image: Mave app screen (UI design)](https://aparnabee.com/assets/mave/s173267.png) PRE-SESSION Wearing Instructions This piece needed users to think, check and readjust and can be considered one of the more “labour intensive” parts of the set-up process. To ease that load, I created a very simple step-by-step module that would explain each instruction with visual aid. Now [Video: prototype recording](https://aparnabee.com/assets/mave/wear1.mp4) [Video: prototype recording](https://aparnabee.com/assets/mave/wear2.mp4) [Video: prototype recording](https://aparnabee.com/assets/mave/wear4.mp4) Before Safety & Reassurance Since this would follow the heavy “wearing instructions” piece, the design and overall message needed to be concise yet clear. This information would also be mentioned again during and after the session and so, did not require an overstated design. IN SESSION [Image: Mave app screen (UI design)](https://aparnabee.com/assets/mave/s204393.png) Introducing “ramp up” When a session starts, the first 10-20 seconds are used to get the session up to the desired intensity. This gradual lifting of current is what we termed the “ramp up”. Now [Video: prototype recording](https://aparnabee.com/assets/mave/ramp-up.mp4) Before [Image: Mave app screen (UI design)](https://aparnabee.com/assets/mave/s204528.png) Sensation Reassurance through check-ins Shortly after the device reached its set intensity, we asked users how they felt. Feeling a sharp pain above an 8/10 was abnormal and an indicator of potential fit issues, skin issues or worst case, a sign that Mave may not work for the user. Pain below an 8 often faded out after a few minutes as the body adjusted to the sensation. Check-in: 1-4 pain rating Check-in: 5-7 pain rating Check-in: 8-10 pain rating Rating < 8 Rating 8-10 [Image: Mave app screen (UI design)](https://aparnabee.com/assets/mave/s144442.png) Introducing intensity & soundscapes The way this surfaces tries to emulate to moment when the user opens a part of the app, looks at the demo conductor and goes “oh what’s this?” Intensity [Video: prototype recording](https://aparnabee.com/assets/mave/intensity.mp4) Soundscapes POST-SESSION [Image: Mave app screen (UI design)](https://aparnabee.com/assets/mave/s144735.png) Device care Full session done Session stopped midway Every Mave session needs a fresh set of saline sponges that act as electrodes. While the wearing instructions mention that these sponges are single use, it is hammered down a second time after the session. [Image: Mave app screen (UI design)](https://aparnabee.com/assets/mave/s145857.png) Session aftermath Most people might be left feeling the same as before they started because tDCS takes weeks to see changes. Others report feeling sleepy or relaxed and some felt pain. It was all valid. ​ Having a blanket message that told users everything that was and was not normal had the potential to cause overwhelm and introduce bias. ​ So instead, we tried to understand how the user felt and made sense of their unique experience. 5-day routine [Video: prototype recording](https://aparnabee.com/assets/mave/routine.mp4) Given that the habit forming component is crucial to seeing results with Mave, it was important for us and for the user to emphasise it and even provide additional support to keep them on track. ​ We achieved this through an optional nudge to Lock in a routine. This routine would be saved in settings and editable at any time. Outcomes [Image: Mave app screen (UI design)](https://aparnabee.com/assets/mave/outcomes.webp) A note from my Product Manager 24% of users completed the 4-week protocol This metric was now something that could be worked upon and frankly, we were expecting much fewer individuals to be completing 20 sessions in 30 days. My design system could accommodate future needs Building a visual style and design system from scratch has to be one of my biggest challenges to date. ​ The foundations I set were not only used for future features on app, but also by the marketing team to create collateral for ads and video assets. Shipped right in time for 250+ preorders & ready to replace in-person demos With the app now giving the guidance, there was more: studying user behaviour on the app and finding improvement areas gearing up for Mave’s Gen 2 headset and all the new app requirements that come with networking, marketing, research and more We even got some love from a user in Korea! Read here. Take a trip down memory lane with me [Image: Aparna wearing the Mave headset at her desk](https://aparnabee.com/assets/mave/memory-1.webp) [Image: Paper sketches of app screens spread across a desk](https://aparnabee.com/assets/mave/memory-2.webp) During feature releases, I put myself in the user’s shoes by testing the app with the headset. Many a sketch was sketched. This was to scope out different page structures for the “analysis” portion of the app. Fun fact: This headset is in an unreleased color! [Image: A thumbs up in front of a laptop showing code](https://aparnabee.com/assets/mave/memory-3.webp) [Image: A whiteboard covered in app flow sketches](https://aparnabee.com/assets/mave/memory-4.webp) Towards the end, it was all hands on deck. I was making changes in the codebase for the first time! Some behind the scenes from all the whiteboarding that took place. I’m fishing for new work! Here’s a little something just for you! If you’ve made it this far, I’d love to get in touch. Here’s where you can find me: More case studies: Browse: Weaving email threads into a real product (https://aparnabee.com/commenda.html) My journey (https://aparnabee.com/journey.html) Resume Agency work (https://afinefolio.framer.website/) Case studies (https://aparnabee.com/index.html#case-studies) © 2026 Aparna Balasubramanian ## Case study 2: Weaving email threads into a real product — Commenda (https://aparnabee.com/commenda.html) Saas Commenda 0 → 1 → 10 Weaving email threads into a real product How I turned email-based services into a product that Commenda’s customers and the service delivery agents used daily. V1 in 2 weeks, V2 in a month with 1 Manager, 1 Engineer and 1 Designer (timelines include development) Case study written and illustrated by me Skip to final screens My Role As the sole designer on this project, I did the following: Gathered requirements to design V1 in 3 days In the next 4 months, collected Hotjar recordings, bug reports, and user feedback. For V2, looped in engineering to understand technical restrictions and used this to scope out features and improvements for V2. Designed V2 in 2 weeks Designer of things Aparna Bala For years, Commenda’s services operated over email Commenda helps businesses set up global entities and remain compliant. ​ In-house service delivery agents exchanged information and documents with customers and got just about anything done this way. ​ The user experience with email was functional, but suboptimal with the potential to seriously affect business. But convincing agents to switch out of their inboxes to a brand new tool wasn’t going to be easy. But email-first wasn’t going to scale “ I’m finally expanding to the US. I really hope this pays off.” For Customers: “ ~ the customer Lack of visibility over the entire process Important documents and information scattered across email threads Sensitive information shared across email I’m juggling emails and phone calls all day, but I always get the job done.” For Agents: ~ the Agent Frequent phone calls from customers to get updates No zoomed-out view of who was handling which client, or what stage each service was at Important documents and information scattered across email threads and hard to access for future services with the same customers Poor service delivery had the potential to hurt business The incorporation service was the start of Commenda’s “flywheel” business model. It wasn’t incorporations that made money for the business, but the direct and indirect tax package upsells that happened afterward, as these other services were recurring and high ticket in nature. So a speedy product experience (v1) was designed in just 3 days And it was fully built in 2 weeks on top of many assumptions. The idea was to pilot just one service and understand if this path could solve some problems. ​ We chose the service “Indian LLP Incorporation”; Commenda’s most popular. It was designed to be stupidly easy to understand and build. How worked: the pilot The customer starts the first task in the service Every service starts with the status “Not started” for both agent and customer. In this case, the customer is assigned the first step and will be the one to kick off things. The first step is completed The status of the service has now changed to “In progress” and the task inside the task group “Company formation details” is now marked complete. The next task opens up now, and it’s for the agent. On the agent’s side, a task now opens up In this case, the customer fills a form and the agent now needs to approve of all the details. This back and forth continues until the service is complete The service is divided into task groups containing tasks. And new steps unlock as the process goes on. Agent and customer go back and forth until all steps are completed. Note: In the interest of time, we attached the chat window from the previous design system. Services were delivered this way for 4 months. I worked on a bunch of other things during this period, but V2 was always hanging in the back of my mind. Watching people hit bumps because of something you designed is humbling. Agents came to me with problems. I also sat with agents and realised that the product was being used (and not used) in ways that could only happen when things didn’t work the way they were intended to. I watched customer HotJar recordings almost everyday. Some customers complained too. I noted it all down. V1 validated the concept, but there needed to be improvements What worked What kind of worked? The chat window The more it was used, the less customers called agents until eventually, agent’s personal numbers were not given out at all. ​ Revealing the process upfront There were much fewer questions of “what’s going on?” or “where are we stuck?” ​ A centralised system Documents and information could be found inside the Commenda platform. Goodbye email threads! The layout It got the job done, but it was hard for customer and agent to understand what tasks unlocked for them and when they were unlocked ​ Copy being the only way to understand task ownership Agents and customers needed to read out the copy each time in order to understand who the step was for. This was just subpar UX. What didn’t work Rigidity of the process We found that some agents were still doing things the manual way when they hit a snag. ​ The assumption that processes were step-by-step The interface assumed that every step in the process took place in a linear fashion when really, some steps could happen in parallel. ​ Understanding progress While it helped that the full service was laid out, one could not quickly infer how far along they were. And a few explorations later.. I designed the version our users needed The back and forth between agents remained, but I improved some key aspects of that experience. new & improved for EVERYONE How far along are we and who is the service currently stuck on? Earlier, tasks were nested inside task groups and it was tricky for one to tell when there was an open task assigned to them. We brought this information to the surface [Video: prototype recording](https://aparnabee.com/assets/commenda/c-tasks.mp4) Where do I find the NIC code? Users often needed documents and information from one service to help carry out others. Earlier, finding these was tricky- one had to go inside the service > Task group > task to find what they needed. ​ Now, I brought it all to the surface. [Video: prototype recording](https://aparnabee.com/assets/commenda/c-docs.mp4) Where can I have my random queries resolved? The all new chat now came with some much needed improvements such as AI rephrasing, individual message replies, pinning, search and more. [Video: prototype recording](https://aparnabee.com/assets/commenda/c-chat.mp4) a little something extra for AGENTS This task wasn’t done correctly. Can I reopen it? There were times when rules changed and steps had to be redone as a result. To enable this, agents could now reopen steps for themselves and the customer. [Video: prototype recording](https://aparnabee.com/assets/commenda/c-reopen.mp4) We don’t need to do this task anymore. Can I skip past it? Jira was originally used for this purpose, with agents and admins shuttling from app to app. Building this into the app cut costs for the business and also put these conversations inside the right context space. [Video: prototype recording](https://aparnabee.com/assets/commenda/c-skip.mp4) I’m having issues with this service/ customer. How do I escalate to admin? Agents could tag admins in the “internal chat” to escalate cases on time. This was previously done on Jira, and eliminating this tool reduced costs. [Video: prototype recording](https://aparnabee.com/assets/commenda/c-internal.mp4) Can I control when the service is formally closed? Earlier, services were auto closed when all tasks were marked complete. And with it, the chat window was also disabled. ​ Agents found that certain steps were added or needed to be redone within a service and this auto-closure didn’t allow for this flexibility. ​ To accommodate this, services were now manually closed by the agent. [Video: prototype recording](https://aparnabee.com/assets/commenda/c-close.mp4) Outcomes [Image: Commenda product screen (UI design)](https://aparnabee.com/assets/commenda/outcomes.webp) A departure from emails [Image: Messages about the project: a post on how the agent app changed work, and a note from the Services Lead](https://aparnabee.com/assets/commenda/quotes.webp) A personal outcome from this project Incorporations were now handled on the Commenda platform for the 50+ countries serviced at the time. No important information hidden in email threads! Reduced anxiety in customers Agents stopped being bombarded by phone calls from anxious customers. Agents no longer needed to provide their personal phone numbers to customers. 4 platforms merged into 1 Shuttling between Slack, Jira, ChatGPT and Commenda to carry out work was dizzying and this problem was finally solved. From the Services Lead working with Commenda’s agents Tighter communication Agents were averaging reply times of over 24 hours. Over the first few months of use, this dipped to just around 8 hours for many agents. Less waiting between steps Steps that don’t depend on each other can now run in parallel. This one change removed unnecessary blockers; reducing service delivery times. Take a trip down memory lane with me [Image: A pine tree through an office window](https://aparnabee.com/assets/commenda/memory-1.webp) [Image: Sticky notes on a glass window](https://aparnabee.com/assets/commenda/memory-2.webp) This is how we discussed page structures. There was no surface left un-doodled. More glass windows called for more ideating on windows. [Image: A video call with teammates across time zones](https://aparnabee.com/assets/commenda/memory-3.webp) [Image: An office at sunset](https://aparnabee.com/assets/commenda/memory-4.webp) We were a global team working across time zones. This made things extra challenging, but also extra rewarding A lot of work fuelled by a lot of pretty sunsets. This is one of the many things I miss! [Image: Commenda product screen (UI design)](https://aparnabee.com/assets/commenda/banner.webp) I’m fishing for new work! Here’s a little something just for you! If you’ve made it this far, I’d love to get in touch. Here’s where you can find me: More case studies: Browse: Designing software for new age hardware (https://aparnabee.com/mave.html) My journey (https://aparnabee.com/journey.html) Resume Agency work (https://afinefolio.framer.website/) Case studies (https://aparnabee.com/index.html#case-studies) © 2026 Aparna Balasubramanian ## Case study 3: Juggling domains at an agency Agency work (restaurant tech, health tech/AI, legal tech) is on my previous portfolio: https://afinefolio.framer.website/ ## My journey (https://aparnabee.com/journey.html) An animated short "movie" of how I came to product design. Aparna Balasubramanian Work Curiosities My story Why hello there! It’s a wonder wehaven’t met yet I’m glad that’s about to change Watch the movie Sometime in the late 90s Little bean Aparna was born in the sunny state of California I didn’t grow up dressinglike the other kids My immigrant parents did not believe a growing child needed to wear expensive American brands. And they were right. Go ahead!Grab a crayon. I’d wake up excited to draw outfits I dreamt about I learnt early on that drawing the things you want has a way of making you feel like you own them Fast forward to 2020 I got a degree infashion design! An almost-life long dream finally realised.This is the stuff you see in movies. I no longer wanted to make clothes.This industry wasn’t what I thought it would be. So.. what now? Career pivot #1 I’m an entrepreneur! I ran my clothing store curating vintage fashion. This was all kinds of rewarding. But suddenly... I realised I loved the part of my work that involved understanding customers Now where could I apply that? Career pivot #2 Enter Product design Some user empathy + skills from design school= a potentially new career? And 3 years in, I’ve covered some decent ground Agencies and start ups taught me agreat deal about building 0 → 1 at speed Health Compliance Restaurant Legal The kind of designer you’d get I approach work with curiosity, compassion and a strong intent to build the right solution. I enjoy environments where I get to geek out on the details, while also having the agency to help create systems built to last. I love my time in the outdoors and what I create often takes influence from what I find around me; from color palettes to layouts to the way things behave. One of the things I love most about my job is how it exposes me to information about how restaurant menus are built, how a cheque-bounce case is carried out, or even how tDCS aids in brain neuroplasticity. This mixed bag of learnings has broadened but my approach to problem solving. Growing up in both the US and in India has also given me varied perspectives about the world. I carry this context everywhere. I’m on the hunt for new team mates! My goal is to be part of a work culture that genuinely understands good design to be more than embellishment, and much closer to business outcomes. My work at startups has taught me to make friends with ambiguity. All I hope for in return in the openness to answer my questions. There will be plenty. I derive the most satisfaction in knowing the final outcome has been fully thought through by all involved. I appreciate open and honest communication and am genuinely open to criticism that takes us in the right direction. As long as we can be professional and treat each other with respect, we’re bound to do great things together! And that’s a wrap! Where to next? Back to home Replay