
Sripad J.
Account Manager
SUMMARY OF EXPERIENCE
β’ 3.5+ years in account management and B2B sales with strong focus on high-volume SaaS portfolios. Recently concluded a role managing Adobe's SMB customer success across North America.
β’ Whilst at MarketStar (LinkedIn Client), Sripad managed 1,800+ accounts across international markets, generating $2M in total revenue and achieving 120% quota attainment for two consecutive quarters with 53% growth in engaged accounts.
β’ Drove 11% QoQ increase in product adoption at MarketStar through strategic cross-selling and upselling, whilst supporting client onboarding, campaign optimization, and ROAS improvement through tailored media planning and ongoing relationship management across enterprise to SMB segments.
π What we loved about them
β’ Business over vanity metrics: His strongest quality is prioritising what actually matters to clients. When he immediately recognised that a 4:1 ROAS doesn't guarantee profitability, he demonstrated real commercial maturity. He understands that operations costs, product margins, and sales cycles all impact the bottom line, meaning he won't get distracted optimising campaigns that look impressive on dashboards but don't drive actual revenue.
β’ Good listener: His instinct is to listen first before problem-solving. He'd let frustrated clients explain their full reasoning before responding, understanding that people sometimes need to vent before they can hear solutions. His approach to the pricing objection scenario was diplomatic without being passive β he apologised for overstepping whilst still gently reaffirming that withholding relevant information would be doing clients a disservice.
β’ Consultative rather than transactional: His MarketStar experience shaped him into a proper consultant rather than just an account handler. He wasn't simply managing accounts β he created presentations, built quarterly strategies, and advised on creative direction when clients asked. The fact that clients from two years ago still congratulate him on LinkedIn suggests he built genuine relationships focused on their success rather than just hitting his targets.
β’ Has a proven upselling track record: He managed books worth Β£200k to Β£500k per quarter in expected revenue, demonstrating comfort with substantial account expansion conversations. He described product adoption as a key metric he was measured on β actively identifying opportunities to introduce new products and services rather than just maintaining existing spend. His cross-selling experience across both MarketStar and Adobe means consistent practice having "what else could help you" conversations.
βΉοΈ Things to be aware of
β’ He's looking to work somewhere he can see direct impact of his work rather than being a tiny cog in a massive machine, which aligns with a small agency environment where individual contributions actually move the needle.
β’ His two years at MarketStar gave him extensive hands-on experience with LinkedIn Ads, and he's demonstrated he can translate these principles to Google and Meta conceptually. The fundamentals of audience targeting, bid management, and conversion optimisation remain consistent across platforms. However, he'll need a short ramp-up period to get comfortable with the specific mechanics, interface nuances, and campaign structures of Google and Meta.
β’ He'd be particularly suited for accounts where strategic guidance and relationship management matter more than hands-on technical optimisation. With some structured onboarding around your specific tools and processes, he could become quite effective in this role.
πβοΈ 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
β’ Marketing fundamentals [7.5/10]: We think Sripad's strongest asset is his business acumen rather than technical depth. His standout moment was immediately recognising that a 4:1 ROAS doesn't guarantee profitability β he distinguished between marketing metrics and business outcomes, which shows commercial maturity. What we really appreciate is how he used accessible analogies like comparing metrics to "mustard and ketchup" to explain concepts, demonstrating he can translate technical problems into language clients actually understand. He also grasps channel differences well, understanding that PPC works better for restaurants because visual content drives impulse decisions. That said, we feel his technical knowledge stays at the strategic layer without getting into platform mechanics. For an account manager role where he'd guide strategy rather than execute campaigns directly, this is manageable, though he'd need support from specialists for hands-on optimisation.
β’ Client account management [7.5/10]: Sripad's interpersonal instincts are quite sound. He understands that difficult conversations require listening first rather than immediately defending, which came through when handling the pricing objection scenario. His approach to the "I'm not paying you for pricing advice" pushback was mature β he apologised for overstepping whilst gently reaffirming that withholding relevant information would be doing them a disservice. What we really liked was his political awareness in the franchise scenario, where he'd speak to regional managers individually before group meetings to build rapport and avoid public blindsides. However, we think his conflict resolution strategies feel a bit surface-level. His responses often focused on finding middle ground rather than using data to drive alignment, which works but isn't always the strongest path.
β’ Organisation and project management [7/10]: We think Sripad's prioritisation instincts are reasonable but not exceptional. In the Monday morning crisis scenario, he correctly identified that Client C (threatening to leave) needed urgent attention, though he missed that Client B's broken website represents the actual emergency with money being wasted in real-time. This suggests he's thinking about urgency in terms of client emotions rather than financial impact, which is a meaningful distinction. That said, his overall approach wouldn't cause disasters β he'd handle all three situations within the day. What concerns us slightly are his project management tool experience. When asked about PM tools, he talked about CRMs but didn't mention Asana, Monday, or ClickUp. His personal system involves writing tasks on paper, which feels makeshift for someone managing multiple clients with complex deliverables. This doesn't mean he'd drop the ball, but it suggests he'd need more structured systems in place to handle scale.
β’ Analytical thinking and problem-solving [7.5]: Sripad's problem-solving approach is methodical and grounded in business logic. For the gym chain scenario, he immediately spotted that equal budget distribution across unequally performing locations was inefficient, and his instinct to investigate root causes rather than just reallocating budget showed solid thinking. He wanted to know if underperforming locations had fixable marketing problems or structural issues like poor reviews, which demonstrates proper diagnostic instincts. His reasoning that visual motivation works better on social platforms for gyms also shows practical marketing understanding. The main limitation we see is depth of quantitative analysis. He didn't calculate unit economics β the cost per member acquisition or LTV:CAC ratio β which would have strengthened his recommendation significantly. Sripad stayed more conceptual, identifying problems correctly but not quantifying them as precisely as he could have.
Areas of growth
β’ His explanations sometimes meander before reaching the point, which could frustrate clients wanting quick answers. We think he'd benefit from structuring responses more tightly: state the conclusion first, then explain the reasoning.
β’ We genuinely believe he needs proper exposure to modern project management platforms and should develop more systematic approaches to tracking deliverables. His checklist system might work for individual focus but won't scale well.