
Purvi A.
Project Manager
SUMMARY OF EXPERIENCE
β’ 6+ years of operations and programme management experience, currently serving as Senior Program Manager at CodeCube.io, where she manages 6-8 high-priority programmes simultaneously as strategic partner to the CEO.
β’ Whilst at CodeCube.io, Purvi architected workflow automation solutions using API integrations that reduced operational overhead by 120+ hours monthly, whilst establishing analytics dashboards tracking expansion metrics that drove strategic decisions across the organisation.
β’ Previously managed 10+ strategic consulting engagements at Emphatic Technologies across technology, fintech, and healthcare sectors, implementing data-backed solutions that reduced turnaround time by 30% whilst supporting C-suite decision-making.
π What we loved about them
β’ Comprehensive experience: Purvi has designed workflows, automated approvals, set up incident management protocols, and built employee onboarding from scratch across multiple companies. She talks naturally about identifying inefficiencies like excessive back-and-forth and fixing them through better processes. The fact that she's done this across consultancy work with different clients means she can adapt her approach to various contexts rather than just following a single playbook.
β’ Strong prioritisation instincts: In both interviews, she correctly identified the most urgent items based on business impact rather than what was loudest. She understood that Client B's PPC campaign mattered because of the external deadline and revenue implications, and in the discovery call scenario, she immediately flagged the out-of-stock product issue as top priority. Her logic for why certain things take precedence over others is fundamentally sound.
β’ Root cause thinking: Purvi consistently asks "why" before jumping to solutions. When the PPC specialist needed another day, she wanted to understand if it was a skill issue, workload issue, or mindset problem. When discussing the overdue task scenario, she thought through whether someone wasn't updating because they were overwhelmed or didn't see the value. Her diagnostic approach means she's more likely to solve actual problems rather than just treating symptoms.
βΉοΈ Things to be aware of
β’ She's available to join in 2 weeks.
β’ Purvi was explicit about wanting to grow into a senior operations or a chief of staff role. She sees this PM position as a meaningful stepping stone and specifically mentioned she wants to be the person the leadership team can blindly trust to get things done.
β’ She's joined companies at 15-50 people and watched them grow to 100-250 people, twice. During that growth, she actively built the infrastructure β set up SOPs, onboarding processes, performance management systems, and hired people based on client needs. She's worked directly with CEOs in early-stage environments and understands what it takes to create structure whilst maintaining agility during rapid growth phases.
β’ Purvi has solid PM fundamentals and good collaborative instincts, but hasn't previously worked in a marketing agency; we feel that she will require clear onboarding on typical marketing workflows, agency roles, and information flows.
πβοΈ 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 [9/10]: We're genuinely impressed with Purvi's Asana proficiency β it's clearly her strongest area and stands out throughout the interview. She moved through the project setup exercise with real confidence, completing everything correctly without hunting for features or second-guessing herself. What we really appreciate is that she's not just mechanically following instructions; she's opinionated about how to use Asana effectively based on real experience. When she talked about minimising subtasks to maintain dashboard visibility and using dependency mapping intelligently, we could tell these aren't theoretical ideas but lessons she's learned from actually managing complex projects. She works efficiently with keyboard shortcuts, flips between multiple views depending on what she needs, and has clearly built reporting and portfolios before, which shows she understands the balance between automation and simplicity.
β’ Prioritisation and decision-making under pressure [7.5/10]: Purvi demonstrates solid prioritisation logic and genuinely understands impact-based decision-making. When we threw the Monday morning chaos scenario at her, she correctly identified that Client B's PPC campaign should be top priority because of the external deadline and direct business impact. However, we do feel her execution isn't quite as sharp as her thinking. She didn't naturally think to communicate with the CEO within the first few minutes, instead suggesting she'd spend 30-60 minutes investigating the PPC issue before even notifying him about missing the strategy meeting. That shows decent thoroughness but lacks the urgency and stakeholder awareness you'd want when keeping people informed is just as important as solving the problem. She also tends to be less concise in her responses, going around in circles rather than getting straight to the point.
β’ Stakeholder communication and managing up [7.5/10]: Purvi understands the right principles around stakeholder communication β she mentioned wanting to be transparent and keep people informed, and when drafting the CEO message about Peak Performance Gym, she identified most of the key issues that mattered. That said, her initial message was a bit surface-level and didn't convey the urgency of a situation that's been deteriorating for a month. She used slightly casual phrasing and didn't frontload the most critical information clearly. When we pressed her on it, she acknowledged she should have provided a more comprehensive overview.
β’ Cross-functional coordination and relationship management [8/10]: Purvi shows genuine strength in her collaborative instincts and relationship-building approach. When we asked about the cross-department dependency scenario, she immediately suggested getting all three people on a call to prioritise together based on business needs rather than team-level concerns, which is exactly the right approach. Her emphasis on understanding whether issues stem from workload, planning, or processes shows she's thinking systemically. Her approach to building rapport with a new team member was genuinely thoughtful β setting up informal coffee chats, listening more than talking, and making herself available as a resource. However, when we asked about getting blocked information for a PPC client setup, her instinct was to schedule a formal 15-30 minute meeting with finance or sales, which felt a bit unnecessarily heavyweight for what could be a quick Slack message to the account manager.
Areas of growth
β’ Purvi needs to recalibrate her instincts around when to use synchronous versus asynchronous communication. She'd also benefit from understanding typical agency roles and information flows β like knowing that account managers usually have client budget details. With proper onboarding about your team structure and some shadowing of how information typically gets shared, she'd adapt reasonably quickly because her collaborative instincts are fundamentally sound.