Principal Engineer Software
Palo Alto Networks, Inc. (company site, opens in a new tab)8+ yrsPuneOn-siteDirect career pageEst. 40–70 LPA
Posted 3d ago
Reach people at Palo Alto Networks, Inc.
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 Palo Alto Networks, Inc. you could write to:
- Recruiters & HR
- People in this function
- Work addresses
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
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
- Own technical direction for major Identity Governance connector-framework programs, coordinating engineers and cross-functional teams.
- Design scalable, multi-tenant ingestion and secure customer access-data read/write capabilities; drive connector contracts and framework architecture aligned with the product roadmap.
- Improve connector delivery and production reliability through tooling, automation, testing, release practices, code reviews, and root-cause prevention.
Minimum Requirements
- Work Experience Required: Minimum 8 years in software engineering, focused on backend and distributed systems.
- Hands-on experience building enterprise services with Node.js, TypeScript, Express.js, and MongoDB, and architecting, deploying, and operating multi-tenant solutions on AWS.
- Experience with large-scale sync or ETL pipelines, REST, SCIM 2.0, GraphQL, SOAP, OAuth 2.0, and technical leadership of large projects, including design approval.
- Expertise in prompt engineering and AI-output review standards; visa sponsorship is not available for this position.
Ideal Candidate Profile
- Likely to succeed with substantial ownership of distributed, multi-tenant systems and complex data-sync reliability, including idempotency, consistency, and failure recovery.
- Strong shortlist fit for experience in IAM, PAM, IGA, or secrets management; these are preferred domain backgrounds, not stated as mandatory.
- Additional relevant signals include queues or workflow engines, integration platforms, secure cloud-connected agents, service extraction, infrastructure as code, or RAG-oriented architecture and documentation.