Software conglomerate didn't work
Software conglomerate didn't work
Large company stability.
People leaving creates opportunities to grow.
Education opportunities for career growth.
Great on-site gym at Moffett Towers.
Nice peers lower in the food chain.
HPE's software conglomerate model didn't work. The strategy to acquire diverse and independent software assets created a big structure with little in common. The more layers of management that were added, the more insulated the decision-makers became from the businesses that drive revenue and their customers.
Add a consolidated, bureaucratic, antiquated sales and fulfillment infrastructure, too many SKUs in the sales quiver, and no sales specialization, and you've got declining revenues and declining market relevance across the board, leading to decreased investment in R&D and overall attrition and decline.
Appearances of the spin-merge with Micro Focus so far make it appear that the strategy going forward will be largely unchanged.
Re-diversify the software assets and re-specialize them in their respective markets. Hire leaders who understand the industry the individual software businesses cater to, so they can set business goals that are relevant in their given industry. Hire better, more inspiring leaders who can move the needle and generate real growth instead of filling out payroll rosters in low-cost regions just to save money from an ever-declining revenue pool.
Was this helpful?
Hewlett Packard Enterprise Interview Questions
Hewlett Packard Enterprise Interview Experiences
Engineering Manager
Very unorganized and a lack of planning in the interview process. Very poor process followed, at least for experienced professional interviews. In the pre-screening round, the Hiring Manager/Recruiting Team should talk with the candidate and give an
Software Engineer
The interview process was standard. First round was initial screening at the college career fair. Standard Java questions. Coding and concepts related questions. Then, two rounds of phone screen. Again, the questions were database schema design and
Perf Engineer
Was pretty straightforward shell knowledge and performance testing skills, and around that. LoadRunner knowledge, and the interview process pretty straightforward again, not much technical. Performance engineering background and things around it.
Engineering Manager
IndiaJune 21, 2019Very unorganized and a lack of planning in the interview process. Very poor process followed, at least for experienced professional interviews. In the pre-screening round, the Hiring Manager/Recruiting Team should talk with the candidate and give an
Software Engineer
Sunnyvale, California, United StatesApril 1, 2016The interview process was standard. First round was initial screening at the college career fair. Standard Java questions. Coding and concepts related questions. Then, two rounds of phone screen. Again, the questions were database schema design and
Perf Engineer
Sunnyvale, California, United StatesFebruary 1, 2016Was pretty straightforward shell knowledge and performance testing skills, and around that. LoadRunner knowledge, and the interview process pretty straightforward again, not much technical. Performance engineering background and things around it.
