
Aman K.
Project Manager
SUMMARY OF EXPERIENCE
β’ 4+ years in project and program management with a strong focus on client-facing delivery across B2B SaaS and consulting environments during the last few years. Currently leading multiple concurrent projects at DWAO with responsibility for end-to-end lifecycle management.
β’ Awarded Customer Kudos recognition in both 2023 and 2024 for delivery excellence, including managing complex GA4 migration programs for GA360 clients. Successfully managed programs with budgets exceeding USD 60,000 whilst maintaining strong client satisfaction and minimal escalations.
β’ At SupplyNote, drove cross-functional project execution across marketing, operations, product, and sales teams in a fast-growing B2B SaaS environment, establishing delivery workflows and reporting mechanisms that improved visibility into project progress and outcomes.
π What we loved about them
β’ Adaptable across PM tools: The fact that he manages different project management tools for different clients (Asana for some, Jira for others, Google Sheets for others) while maintaining an internal tool shows he's genuinely flexible and not precious about "his way" of doing things. He even uses Asana personally to track everything from water intake to gym sessions, which tells us he's naturally organised and doesn't need external pressure to stay on top of things.
β’ Emotional intelligence and stability: Aman remained measured and calm throughout both calls, even when being challenged or pushed on his answers. When we questioned his CEO communication approach or pushed back on his prioritisation logic, he didn't get defensive β instead he genuinely tried to understand the feedback and adjust his thinking. His communication in tricky situations is particularly strong because he always leads with "why" and tries to get to the root cause rather than making assumptions. He mentioned knowing exactly how to nudge different team members based on their working styles.
β’ People-centric project management: He's built genuine relationships with his team members and approaches project management through understanding people first. His solution for getting technical teams to update trackers is doing 15-minute stand-ups together rather than just demanding compliance. He explicitly said his strongest suit is understanding people and how each resource reacts to different situations, which helps him persuade rather than dictate. He even mentioned he doesn't shy away from "being the small person" when needed, which suggests he's willing to set ego aside to get results.
β’ Comfort with autonomy: Aman was honest that his approach depends on the situation β some problems need collaboration, others need him to just roll up his sleeves and dive in. He doesn't shy away from asking for help when needed but also doesn't wait around for permission when something's clearly his responsibility. He mentioned being available until 10pm most days and taking ownership of ensuring trackers stay clean and risk-free, suggesting he's genuinely self-driven rather than needing constant oversight. We genuinely appreciate that he doesn't make excuses or deflect, which makes him easier to manage and coach because he's genuinely open to feedback and owns his gaps.
βΉοΈ Things to be aware of
β’ He has a notice period of 30 days.
β’ Aman was refreshingly clear about wanting to work with more structured, organised teams in developed markets so he can learn and grow. He explicitly said money isn't his main motivation right now β it's about working with smarter people and evolving his skills. He's tired of the Indian market's lack of clear scoping and constant uncomfortable conversations about money, and genuinely wants to be in environments where project management fundamentals are respected.
πβοΈ 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
β’ Technical execution and tool proficiency [8.5/10]: Aman's technical abilities with Asana are genuinely strong β he approached the exercise with precision and care. He successfully created the project following all conventions, added team members correctly, and configured custom fields with proper attention to detail β even selecting the "notify collaborators" option without prompting, which shows he's thinking about downstream impact. His intuitive reordering of options and formatting of task descriptions demonstrates he's not just mechanically following instructions but actually considering how others will use what he's building. What we genuinely appreciated was that pragmatic moment when he asked about colour coding β it showed us he understands the difference between perfectionism and getting things done. He works efficiently, knows where features are located, and doesn't fumble with basic functionality. His only slip was forgetting how to convert a task to a milestone, but he proactively followed-up after the interview to confirm that he had figured it out and updated it in the workspace. Given he's worked across Jira, Microsoft tools, and Asana, his adaptability really comes through.
β’ Prioritisation and decision-making under pressure [8.5/10]: Aman demonstrates really sound judgement when faced with competing demands β we liked how he consistently applied clear reasoning rather than just going with gut feel. He correctly identified that seasonal PPC campaign as top priority because of its time sensitivity and business impact, which tells us he genuinely understands commercial implications beyond just ticking off tasks. His instinct to park the CEO meeting for client deliverables showed he's willing to make tough calls, and we appreciated that he asked sensible clarifying questions about campaign readiness rather than assuming information. His approach to the overdue report also felt measured and practical β he'd find coverage through the team or handle it himself, which shows both flexibility and genuine ownership. When the PPC specialist pushed back, he indicated that he'd investigate root causes first then manage client expectations if necessary. He structures thinking in clear tiers (P0, P1, P2) and estimates timeframes reasonably, though we did notice one gap β he positioned the CEO meeting as something to completely skip rather than thinking about joining for the last hour, which would have balanced both needs.
β’ Stakeholder communication and managing up [7.5/10]: Aman could have done better here; though we want to emphasise he demonstrates the underlying understanding when coached through it, which suggests this is definitely improvable with guidance. His initial CEO response felt templated and slightly mechanical β listing problems without conveying confidence or providing the reassurance senior stakeholders genuinely need in such situations. He also initially missed the critical out-of-scope landing page issue. That said, when we challenged him, he did grasp that the CEO needs to feel he has things under control, even if execution remained somewhat robotic. What we appreciated was that he understands client-first focus and explains his reasoning clearly when given time to think. He mentioned having a daily reporting habit in his current role (sending updates around 3-4pm), which tells us he knows proactive communication matters.
β’ Cross-functional coordination and relationship management [8.5]: This is where Aman really shines, and it's clear he has proper skill in navigating team dynamics and facilitating collaboration without creating friction. His approach to the cross-department conflict between SEO and web teams was exactly what we'd want β bring both parties together, find common ground, understand constraints, and only escalate when you genuinely can't reach consensus. What we really appreciated was that he consistently goes directly to the person doing the work rather than escalating to their manager, which shows he respects team structures and understands that accusatory approaches damage relationships you need long-term. His onboarding process for new team members felt thorough and thoughtful β setting communication preferences early, providing client context, being transparent about expectations, and making himself available as a resource. We also loved his practical solution for getting technical teams to update trackers through 15-minute stand-ups where you do it together, which demonstrates he works with human behaviour rather than fighting against it. Throughout scenarios, he maintained this calm, solution-focused demeanour when coordinating multiple people under pressure.
Areas of growth
β’ He needs to develop a more strategic lens when managing up, framing problems through business impact rather than just listing facts. Instead of bullet-pointed status updates, we feel he should lead with confidence, explaining what he's already doing before anyone has to ask. His tone needs to shift from checklist-reading to trusted advisor having a genuine conversation, which we believe will come with practice and conscious attention to how executives process information under time pressure.