Prerana's approach to the missing data scenario was clean and straightforward – she identified the core issue (vague timelines, missing key metrics), broke it into four clear steps, and pushed for a reschedule only after verifying data quality rather than just punting the meeting. Her cost-per-tonne analysis also showed good instincts; she triangulated between demand-side misalignment, internal supply chain inefficiencies, and raw material procurement as possible explanations, which is the right place to start.

This is probably where Prerana is the strongest. When asked about fixing the WhatsApp notes problem, she named specific tools (Fathom for transcription, Jira for task tracking), described a 30-60-90 action framework for post-meeting follow-through, and proposed a short debrief to align on immediate priorities. Her 90-day plan showed she understands what operational leverage actually looks like in practice. She also prioritised fixing data systems and communication infrastructure in the first 30 days (the things that directly feed the founder's decision-making) rather than jumping to bigger, slower projects.

Her answer on working in male-dominated environments was one of the more genuine moments in the interview. She described a real, specific approach – build rapport before asserting authority, use her youth as a reason people are more candid with her, and adapt her style person to person. She even acknowledged that she sometimes had to route feedback through a male colleague to get shop floor workers to act on it (we appreciated her transparency here). Her communication during both interviews was generally well structured without being too stiff. In particular, she self-corrected when she went off track, asked clarifying questions where appropriate, and kept her answers anchored to the question rather than drifting.

She understands the underlying rational behind this this role and had good answers to questions around how she might settle into the role/company. Her framing of the 90-day plan showed she's thought about what a founder's time is worth and what kinds of problems shouldn't be landing on his desk. She talked about taking on data system fixes, manpower grievances, and communication infrastructure so the founder can stay focused on the 60 to 90-day horizon. She was also honest about her own ramp-up, acknowledging she'd need time to understand the business before taking on more strategic work and proposing to start with problems she could control and fix quickly.