i'm scheduled to go through HP's process in late July for a BizOps/strategy role in their PC division. can people drop recent data points here? specifically looking for: what was the round structure for non-engineering roles? did they do a case study or work sample? how heavy was the behavioral vs. strategic thinking balance? anything surprising that you wish you'd known going in?
any function is helpful, even if it's not ops. just trying to build a picture of how the loop is run. thanks in advance
3 replies
apm_aisha
i interviewed for an APM-adjacent role at HP about 4 months ago. for non-eng roles they did: recruiter call, HM call, then a 2-hour virtual panel with 3 people covering: 1 behavioral, 1 strategy/case (informal, not a full McKinsey case, more like a mini product/market sizing), 1 with a cross-functional stakeholder who asked mostly about how you work with eng teams. no take-home for my loop.
jordan_pm
HP ops/strategy roles tend to ask about data-informed decisions and working across siloed teams. they have a LOT of business units that don't talk to each other. if you can show you've navigated that kind of mess before, you'll score well.
director_dee
from a hiring side: for BizOps at large legacy tech cos like HP, we're basically looking for two things. can you structure ambiguous problems? and have you worked with executives who have very different agendas? the strategy/case piece is usually not hard, it's more of a screen for logical thinking. the behavioral depth is where people actually differentiate.