Prerna D.
Founder's Associate
SUMMARY OF EXPERIENCE
• 2+ years of experience at Tata Steel, starting as a Management Trainee across technical and operational rotations before moving into a Mining Manager role where she currently oversees 100+ employees and 30+ machines to deliver iron ore to Tata's customer plants in Jamshedpur and Kalinganagar.
• As Mining Manager, she drove a digitisation initiative that improved data management efficiency by 20% and led a research project on blasting risk mitigation that produced recommended best practices for community safety around the mine.
• Prior to Tata Steel, she completed a 5-month product internship at Bharatsure, an early-stage B2B insurtech, where she owned feature development end-to-end and delivered a 25% improvement in CTA on key product features through UX research and iterative testing.
👍 What we loved about them
• Genuine domain expertise: Givern her experience of working at a mine, she was able to explain the procurement process from an insider's perspective. Her walkthrough of the steel value chain in the technical interview covered the full picture, from iron ore grading at the mine level, through sintering, blast furnace operations, crude steel production, and into hot and cold rolling. What was great was that she was able to connect each stage to the actual cost or quality implication, not just the process.
• Proactive and thorough: Twice across both interviews she identified a broken system and proposed a fix without being asked. In the data scenario, she flagged that data not being ready the night before a review is a symptom of a deeper problem with how data is being captured continuously, and offered to go and inspect that. In the WhatsApp notes problem, she immediately saw that the founder doing his own note-taking in meetings was the root issue, not just the notes themselves. All-in-all, we consistently felt that she goes one level deeper than the surface problem.
• Curious and deep-thinker: In the supplier scenario during the discovery call, before giving any recommendation, she stopped and asked two specific questions: is the business currently profitable, and what's the actual differentiator of the new supplier beyond price? It was good to see that Prerana wanted sufficient context to give a more useful response rather than come across as someone who has all the answers. When we gave her the trust context on the existing supplier, she immediately updated her view and gave a clear recommendation. We feel she has the right instincts, especially when working in a data-heavy and ambiguous environment.
ℹ️ Things to be aware of
• She has a 3-month notice period, which can potentially be reduced if her employer is compensated for the early release.
• Her strongest suit is operational thinking with genuine domain depth. She understands how steel plants actually work, not just at a conceptual level but from the ground up, having spent two years at a working mine managing real teams and real output. When problems come up in a plant context, she doesn't need to be brought up to speed on the basics; she can go straight to the source, ask the right questions, and identify what's actually broken.
• Her operational background is strong, but across both interviews there wasn't much evidence of her having to think about financial trade-offs at the business level. She touched on cost drivers correctly, but when the conversation moved toward things like margin structure or business profitability, her framing stayed at the operational layer rather than connecting to the financial outcome. She'll pick this up quickly given the environment, but it's worth knowing going in.
• She's going from a large, structured corporate role managing 100+ people and a fleet of machines to a lean, high-proximity operator role working directly with a founder. The nature of the work, the pace, the ambiguity, and the expectations will all feel quite different. She seems genuinely motivated by the shift and has thought about why she wants it, but it's worth having a candid conversation with her about what the adjustment will actually feel like in the first few months.
💁♀️ Where he may need support
-
Although he lacks extensive experience with LinkedIn and Bing ads, his proficiency in Google ads suggests a high adaptability to new platforms.
👩💻 Technical interview performance
Objective
This candidate was invited to a 60-minute follow-up interview to assess their technical capabilities in more detail. During this interview, we assessed their critical-thinking skills, technical expertise, and overall conversational skills.
Technical abilities
• Structured problem-solving and analytical thinking [7/10]: 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.
Where she's slightly less strong is in landing on a clear recommendation. She tends to lay out options well but sometimes stops short of saying "here's what I think is most likely" or "here's the one thing I'd investigate first."
• Operational systems and process design [7.5/10]: 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.
Separately, she flagged that data not being ready shouldn't be a routine problem and pointed to the need for continuous data capture systems rather than month-end scrambles.
• Stakeholder management and communication [8/10]: 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.
• Founder's associate readiness [7.5/10]: 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.
Areas of growth
• In some answers, she was a little too exploratory out loud. In front of a founder or a senior stakeholder, it's probably better to do that thinking internally and present a cleaner output. We felt this was a small calibration rather than a meaningful gap.
• Her analysis occasionally went broad without narrowing to a clear recommendation. In the cost-per-ton scenario, she surfaced the right questions but didn't land on a specific hypothesis or a concrete next step.