Technical abilities

• Project management and organisational systems [8/10]: Jagrati's answer on setting up a new client project was extremely thorough – she walked through the whole structure without being prompted, e.g. folders per product, sections per service line, tasks with owners and due dates, sub-tasks for internal review, and notification settings so the team doesn't have to keep manually checking in. What also came through was her instinct for keeping things clean over time, not just at the start. She mentioned not letting people create duplicate folders for the same service, and flagging when colleagues weren't marking tasks complete (and why it matters downstream). The Chrome profile idea was a nice detail too (i.e. one profile per client so the right tools open automatically), because it shows she thinks about reducing friction in small, practical ways.

• Process thinking and quality assurance [7/10]: This came through most clearly in how she talked about the Meta Ads go-live process. She had a clear sequence in her head: internal approval, client approval, copy writing, publishing, client notification, and then a midnight check to make sure nothing got half-published by mistake. Her answer on the wrong-dimensions scenario was also sensible – she held both the designer and the paid team accountable, which is the right call, because QA is a shared responsibility (she didn't just point the finger at one person. On reporting, there's room for improvement. She knows what metrics matter and why, and she can structure a client-facing report clearly, but she ran short on time during the data task and didn't finish.

• Stakeholder and client management [8.5/10]: This was probably Jagrati's strongest area across the whole interview. Whether it was handling a senior colleague ignoring Asana updates, pushing back on unrealistic deadlines, or dealing with a client chasing a campaign that hadn't gone live, her approach was consistent, i.e. stay calm, make it about impact rather than blame, and get to the root cause before saying anything definitive. The missed campaign scenario was also a good test of this – rather than panicking or improvising an excuse, she said she'd acknowledge it to the client immediately, buy time, and then come back with an honest answer once she actually knew what had happened. A lot of people skip the first step (i.e. the immediate acknowledgement) because they're scared, and that's usually what makes the situation worse. Her approach to the senior colleague and the deadline pressure was also worth noting, as she framed it as a quality conversation ("do you want me to deliver fast or deliver well?"), which typically is the tone and style of language that tends to land with people who are more senior.

• Attention to detail and written communication [7.5/10]: The status update email was a good piece of work overall. She separated completed tasks, in-progress items, and urgent approvals clearly, and she flagged the risk to the March 28th launch date if the client didn't respond by the 13th. Formatting-wise, it could've been tightened (the layout felt slightly uneven and the sign-off was a bit abrupt), but the structure and logic were sound. In general, when you're sending a weekly update to a client, content and clarity matter more than perfect formatting, and on that front she delivered. Verbally, her answers can meander a little when she's working through a complex scenario – she always lands in the right place, but sometimes takes a few extra sentences to get there. That's more of a communication style note than a red flag, and it tends to show up less in written work where she has a moment to think first.

Areas of growth