Technical abilities

• Project management and organisational systems [8.5/10]: Harshitha's PM fundamentals are genuinely strong, and they've been tested in a demanding environment. Managing 5-7 concurrent programmes across software, hardware, mechanical, and certification teams, with government clients who hold you to strict compliance standards, requires exactly the kind of rigour this role needs. Her instinct to build a single source of truth, keep documentation accessible to all relevant parties, and maintain a weekly reporting cadence with clear visibility into risks and blockers are strong examples of her exposure to the key aspects of project manager. Her project setup answer was also thorough, i.e. understand requirements, check existing projects for alignment, communicate with internal team, identify blockers from comparable work, then document everything in a structured way with raw internal access and a filtered client-facing version. That's a considered approach, and the distinction between what the internal team sees versus what the client sees shows she understands the difference between operational transparency and client communication. The gap here is purely tool-specific as she's been working predominantly on Microsoft Project. That said, her thought process was spot on.

• Process thinking and quality assurance [8.5/10]: Her QA instincts are exceptionally strong, particularly around documentation and consistency checks. In her current role, she has to maintain audit-ready records that can withstand regulatory scrutiny, which is a higher bar than most marketing agencies require. The habit of double-checking numbers before they go to a client, verifying that status labels actually match what's been done, and building a "one source of truth" for approvals is all directly transferable. On the data task, she went beyond just flagging errors and explained what each inconsistency meant operationally. She also highlighted the one genuinely good row (planned one day, delivered one day, on time) as something worth surfacing positively, which shows she was reading the data as a communication tool rather than just a list of problems. Her Excel skills are also solid, particularly for someone who's largely self-taught on the analytical side – VLOOKUPs, database management, and visual reporting for clients are all things she uses regularly.

• Stakeholder and client management [9/10]: This is one of Harshitha's more seasoned areas, because her clients in aerospace have been government bodies that operate with strict, process-bound communication norms. She takes accountability first, works to understand the root cause before assigning blame, and frames requests to team members in terms of why it matters rather than just what they need to do. The Friday 5pm scenario answer was a good example, e.g. apologise to the client immediately, give a realistic new date without consulting the team first (because she doesn't have time), then go internally to understand what happened and hold it accountable without letting it spiral. The one unknown here is how she handles the pace and volume of a marketing agency's client relationships given that she's used to clients who move slowly and formally.

• Attention to detail and written communication [8.5/10]: The email task was very well-executed. She structured it clearly (completed, in progress, upcoming week, roadblocks), flagged the March 13th approval deadline with its impact on the March 28th launch, and handled the fifth blog post scope question professionally by noting it was pending a decision rather than just dropping it. The tone was professional without being stiff, and she avoided making it longer than it needed to be. As expected, her documentation instincts were also genuinely strong.

Areas of growth