Principal Platform Engineer
Hewlett Packard Enterprise (HPE) (company site, opens in a new tab)10+ yrsBengaluruOn-siteDirect career pageEst. 45–70 LPA
Posted 26d ago
Your match
Against your primary resume
Log in to see your match score
Create a free account or log in to unlock your CV match score across:
- Role fit
- Experience
- Industry relevance
Reach people at Hewlett Packard Enterprise (HPE)
People at this company you can reach
Log in to see who works here
Create a free account or log in to see the people at Hewlett Packard Enterprise (HPE) you could write to:
- Recruiters & HR
- People in this function
- Work addresses
Protocol Intelligence
How competitive this role is
Competition
Background fit
Strictness
Log in to see why each signal reads the way it does.
Job description
Structured overview of role & requirements
About This Role
- Develop and define software systems architectures and methodologies across multiple platforms and global teams within the business unit.
- Identify, evaluate, and integrate new technologies and partner relationships aligned with technology roadmaps and business value.
- Provide technical guidance, mentorship, and influence executive leadership and external partners on software design and development standards.
Minimum Requirements
- Bachelor's or Master's degree in Computer Science, Information Systems, or equivalent.
- Typically 10+ years of relevant experience in software system design and architecture.
- Experience designing and developing software systems design tools and languages, including multi-platform software system integration.
- Work Location: Hybrid model requiring approximately 2 days per week working onsite at HPE office.
Ideal Candidate Profile
- Experienced in high-performance computing, AI, or related complex, data-intensive workload environments.
- Demonstrates ability to influence at the executive and business unit leadership level and with external partner organizations.
- Proven innovator with history of patents or deployed solutions in software design, skilled in communicating complex architectures effectively.