Haneef S.M.
Founder's Associate
SUMMARY OF EXPERIENCE
• 1.5 years of post-MBA work experience, with his most recent role as Deputy Manager at JSW MG Motors India where he managed East Zone sales operations across a monthly cash flow of ~80 crores.
• At MG Motors, he ran dealer-wise demand forecasting and stock planning across 13 states and 18 outlets, reducing slow-moving inventory by 60%, cutting average stock days from 56 to 35, and improving customer satisfaction scores by 28% across pre and post-sales parameters.
• Prior to MG Motors, he completed internships at Samsung R&D (research on Google Privacy Sandbox's impact on digital advertising), Ultratech Cements (dealer activation across Bengaluru, Chennai, Vijayawada and Kochi, meeting 70+ dealers in person).
👍 What we loved about them
• His level of preparedness: Haneef had a few days to research an industry he'd never worked in, and he came in with a genuinely decent grasp of the steel value chain – covering production types, buyer segments, cost structures, and even the supplier power dynamics in the scrap market. He clearly went beyond a quick Google search, which showed us how he prepares when something matters to him.
• Cares about the facts: Across multiple scenarios in the technical interview, his first move was always to ask: how do I actually know this is true? Whether it was the unplanned shutdowns discrepancy or the cost-per-tonne problem, he consistently went to the data validation step before jumping to a solution. He talked about cross-referencing ERP records, stockyard logs, and attendance data, and he flagged that a plant visit would be needed for things the data alone couldn't explain.
• Transparency and self-awareness: At a couple of points in the technical interview, Haneef openly acknowledged he wasn't certain how something worked in a steel plant specifically. Rather than bluffing through it, he said so clearly and then continued with what he did know. When we asked him what he needs from a founder, he was specific and honest – clear deadlines, process autonomy, and openness to feedback.
ℹ️ Things to be aware of
• He's available to join immediately.
• His experience, while real, is entirely within automobile sales. He's never worked in an operations-first or manufacturing environment, and he's never been in a role that's formally about supporting a founder. His instincts are decent, but there's a meaningful learning curve ahead of him, particularly around how plants operate, how to read operational data in an industrial context, and how to run the kind of structured review cycles this role demands. He also works best with clear direction and defined timelines – something worth keeping in mind when thinking about how much structure you're able to provide, especially early on.
💁♀️ 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]: When Haneef was walked through the unplanned shutdowns scenario, his instinct was solid – he immediately started thinking about how to verify it, suggesting cross-referencing attendance logs, ERP records, and stockyard movement data to build a clearer picture. He also correctly flagged that 90% utilisation and unplanned shutdowns aren't necessarily contradictory depending on how utilisation is being measured, which is a nuanced point that not everyone would catch. On the cost-per-tonne question, he worked through the problem in a logical sequence (raw materials, energy, labour, wastage) and, importantly, noted that a plant visit would be needed to validate what the numbers can't explain on their own. Where he loses a few marks is in not always pushing through to the "so what" layer. He'd identify the right buckets to investigate but would sometimes stop before connecting it back to a clear hypothesis or next action.
• Operational systems and process design [7.5/10]: Haneef correctly diagnosed why the current approach wasn't working (i.e. it was putting the burden on the founder rather than distributing accountability) and then offered a few realistic alternatives (e.g. a dedicated note-taker, AI transcription tools, or department-wise MOM distribution), depending on the company's resources and culture. He also thought about verification, suggesting that for the first few meetings, recordings could be used to cross-check whether the new system was actually capturing everything. His data scenario response also showed a reasonable understanding of how manufacturing data flows work (i.e. ERP systems, inward delivery logs, production records). We felt he knew enough to ask the right questions about where data lives and how to reconcile it. That said, his systems thinking stayed at a fairly high level. He described what a good system would look like rather than getting into the specifics of how he'd actually build it.
• Stakeholder management and communication [7/10]: Haneef communicates clearly and thinks out loud in a way that's easy to follow. His point about drawing parallels between dealership sales teams and blue-collar workers was a genuinely good insight – he's clearly had to work across different types of people in his MG Motors role, and he's comfortable with that. He also gave a thoughtful answer about what he needs from a founder (clear deadlines, process autonomy, and openness to feedback), and when we challenged him on the apparent contradiction between autonomy and needing timelines, he handled it well by clarifying that he wants ownership of the how, not to be left without a by-when. Where it gets a bit softer is in how he handles authority and resistance. His response to senior stakeholders reverting to old habits (i.e. redirecting them to email or forwarding the message again) was passive rather than direct.
• Founder's associate readiness [7/10]: His answer on helping the founder move from reactive to proactive was interesting – he drew directly from MG Motors, talked about setting 3–5 focus areas, delegating everything else, and reviewing progress through clearly defined KPIs. He also showed self-awareness about what makes the founder-FA relationship work (clear communication, mutual trust, openness to feedback), which suggests he's thought about this more than just at a surface level. However, we felt his thinking stayed at the strategic level without grounding it in specific execution. He spoke about delegation and goal-setting in broad terms, but the "here's exactly how I'd implement that in week one" detail was largely missing. He also has no direct experience working with a founder, so there'll be a learning curve on things like managing a founder's time, running review cycles, and owning cross-functional accountability, all of which are learnable, but worth factoring in.
Areas of growth
• In the authority question, his instinct when faced with difficult stakeholders is to adapt and work around them, which is a good trait, but he'll also need to develop the confidence to have harder conversations when the situation demands it.
• When talking about systems or processes, he tends to stay at the "what" level rather than the "here's specifically how I'd build it" level. We feel that'll need to grow quickly in this role.