Technical abilities

• Project management and organisational systems [9/10]: This is where Aparna is most credible, and it comes through naturally. Seven years of managing a major client across multiple sub-projects, time zones, and teams gave her a level of systems thinking that most people at this stage simply haven't had the chance to develop. Her approach to setting up a new client project (kickoff with real objectives, Gantt or high-level tracker, clear owners, dependencies mapped, check-in cadences defined) is thorough without being over-engineered. What also came through was her instinct to centralise everything. The Bug Organizer example showed that she was able to fundamentally change how the team communicated so that nothing lived in someone's DM or inbox and everything was visible to whoever needed it. She applied the same logic to the ClickUp scenario in the discovery call, i.e. audit what's broken, understand what teams need, build the new structure, then migrate people across without disrupting live work.

• Process thinking and quality assurance [8/10]: Her QA instincts are sensible. Before handing off approved creatives, she goes back to the original objectives, checks that revisions are reflected, and does a quick pass to make sure everything is current. She also knows what to look for when something is wrong, e.g. if the paid team flags wrong dimensions, she checks where the breakdown happened first rather than assigning blame immediately. If it was communicated and she still missed it on her pass, she took ownership of it. On the data task, she correctly identified the most meaningful inconsistencies, i.e. rows where actual days far exceeded planned days and the work still wasn't delivered on time, and rows where the opposite was true (over-resourced and underutilised). Her framing of it as a resourcing and forecasting issue was also spot on.

• Stakeholder and client management [9/10]: Aparna is genuinely strong at this, and it's backed by real experience rather than just good interview answers. Seven years of being the primary point of contact for the Google account, managing expectations across New York, Argentina, and India, while also having to regularly go back to a founder and fight for her team's budget and resources, feels like a meaningful track record. Her approach to difficult conversations is also measured – she doesn't rush in without understanding the situation first, and she's clear about what belongs in a conversation with a team member versus what needs to escalate. The performance improvement plan answer was also considered: give the person specific goals, a clear timeline, and documented evidence before anything goes to HR. We appreciated her honesty about her own growth here – she mentioned that she used to call everyone in a panic when something went wrong and that she's now much more deliberate about not disturbing people outside working hours unless it's genuinely urgent.

• Attention to detail and written communication [7.5/10]: The email task showed she knows what information a client needs to see and how to prioritise what's urgent versus what's just an update. The content was well-structured in terms of logic: completed items, in-progress items, dependencies flagged, and impact of missing the approval deadline clearly stated. However, the issue was the formatting. She turned what should have been a clean client email into something that looked more like an internal project brief, with nested bullets, bold headers, and labels like "TL;DR" and "Action Item" littered throughout. She likely knows how to write a cleaner email and just got into the weeds on structure during the task. Verbally, she's extremely articulate and precise.

Areas of growth