Principal Software Engineer (UI) - Delphix

📍 Job Overview

Job Title: Principal Software Engineer (UI)

Company: Perforce

Location: Pune, Maharashtra, India

Job Type: Full-Time

Category: Software Engineering (Frontend/UI)

Date Posted: February 13, 2026

Experience Level: 10+ Years

Remote Status: On-site

🚀 Role Summary

• This Principal Software Engineer role focuses on architecting, designing, and developing complex enterprise-grade frontend applications using Javascript and Angular.

• The position is integral to the Delphix product suite and its associated integrations, particularly with Atlassian products, requiring a strong understanding of SaaS principles.

• Key responsibilities include hands-on coding, technical design, performance and security analysis, code reviews, and mentoring junior engineers within an Agile development environment.

• Candidates will be expected to create proof-of-concept solutions for new technologies and features, contributing to the continuous improvement and innovation of Perforce's product offerings.

📝 Enhancement Note: While the job title is "Principal Software Engineer (UI)", the description heavily emphasizes frontend development with Javascript and Angular. The "Principal" level suggests a senior technical leadership role, requiring not just coding but also architectural design, mentorship, and strategic input on technology choices. The focus on "complex enterprise products" and "SaaS mindset" indicates a need for robust, scalable, and maintainable solutions.

📈 Primary Responsibilities

• Architect and design sophisticated, scalable frontend solutions for complex enterprise products, with a focus on user interface (UI) and user experience (UX).

• Write high-quality, maintainable, and efficient application code for the Delphix frontend and related Perforce products, adhering to best practices in Javascript and Angular development.

• Develop comprehensive technical documentation for all developed features, ensuring clarity and usability for team members and stakeholders.

• Conduct thorough analysis of component performance and security vulnerabilities, proactively identifying and implementing improvements to enhance product robustness and user trust.

• Perform meaningful code and design reviews for other engineers within the agile team, fostering a culture of technical excellence and knowledge sharing.

• Write comprehensive unit and integration tests to ensure code quality, stability, and reliability of frontend components and features.

• Collaborate effectively with the agile team to break down complex business requirements into actionable technical tasks and estimates.

• Lead refactoring efforts for legacy codebase sections, modernizing architecture and improving code quality and maintainability.

• Create and evaluate Proof of Concept (POC) solutions for emerging technologies and innovative features, assessing their viability and potential impact on the product roadmap.

• Mentor and provide technical guidance to other engineers on the team, sharing expertise in frontend development, architecture, and best practices.

📝 Enhancement Note: The responsibilities highlight a senior-level contribution, emphasizing architectural ownership, code quality, and technical leadership. The mention of "Atlassian integrations" suggests a need for understanding how frontend applications interact with broader development and collaboration platforms.

🎓 Skills & Qualifications

Education:

Experience:

• A minimum of 10 years of professional software engineering experience, with a significant portion focused on complex systems and enterprise-grade applications.

Required Skills:

• Mandatory hands-on coding proficiency in Javascript and Angular for frontend application development.

• Extensive experience in designing and consuming APIs, with a strong understanding of both consumer and provider perspectives.

• Proven experience with microservices architecture, including understanding how frontend applications integrate with distributed backend systems.

• Hands-on experience with data storage solutions, specifically Redis and at least one SQL-based database engine.

• In-depth knowledge of security mechanisms for user accounts, including OAUTH, JWT, and similar authentication/authorization protocols.

• Significant experience working within Agile development methodologies (e.g., Scrum, Kanban, Lean, XP).

Preferred Skills:

• Hands-on coding experience with Java is highly desirable.

• Experience with other prominent JavaScript-based frameworks such as React or Vue.js is beneficial.

• Familiarity with WebSockets for real-time communication.

• Experience with cloud platforms and containerization technologies such as AWS, Kubernetes, and Rancher.

• Understanding of DevOps principles and practices.

📝 Enhancement Note: The "Principal" title combined with 10+ years of experience and requirements for architecture, design, and mentoring strongly suggests this role is for a senior individual contributor or a technical lead who will shape frontend development direction. The mandatory Javascript and Angular skills are critical, with Java being a significant plus for understanding the full stack.

📊 Process & Systems Portfolio Requirements

Portfolio Essentials:

• Showcase complex frontend projects demonstrating architectural design patterns, robust UI implementation, and scalable Javascript/Angular code.

• Include examples of successful API integrations, illustrating experience in consuming and potentially providing APIs for enterprise applications.

• Present case studies demonstrating experience with microservices architecture and how frontend applications interact with these distributed systems.

• Provide evidence of data management experience, potentially including implementations involving Redis or SQL databases, and how these support frontend functionality.

Process Documentation:

• Documented examples of technical design documents for complex features or systems, outlining architecture, data flow, and component interaction.

• Evidence of creating clear and concise documentation for features developed, suitable for knowledge transfer and team understanding.

• Examples of performance and security analysis reports or contributions to improving these aspects of an application.

• Demonstrations of code review processes and contributions to team coding standards and best practices.

📝 Enhancement Note: For a Principal Engineer role, a portfolio should go beyond just code samples. It needs to demonstrate strategic thinking, architectural capabilities, and the ability to lead technical initiatives. Candidates should be prepared to discuss their design decisions, the trade-offs they made, and the impact of their work.

💵 Compensation & Benefits

Salary Range:

Benefits:

• Comprehensive health insurance coverage (medical, dental, vision) for employees and dependents.

• Generous paid time off (PTO), including vacation days, sick leave, and public holidays.

• Retirement savings plan contributions or provident fund matching.

• Opportunities for professional development, including training, certifications, and conference attendance.

• Employee assistance programs (EAP) for mental health and well-being support.

• Potential for performance-based bonuses and stock options/equity.

Working Hours:

• Standard full-time working hours, typically 40 hours per week, with flexibility available as needed to meet project deadlines and team collaboration requirements. Adherence to Indian Standard Time (IST) for core working hours is expected for collaboration with local teams.

📝 Enhancement Note: The salary range is an estimate based on typical compensation for Principal Software Engineers in Pune, India, factoring in the specified experience level and technical skills. Actual compensation will depend on the candidate's specific qualifications, interview performance, and Perforce's internal compensation structure.

🎯 Team & Company Context

🏢 Company Culture

Industry: Software Development, DevOps, Application Lifecycle Management (ALM), Version Control, Data Management. Perforce operates in a highly competitive technology sector, providing critical tools for development teams across various industries, including gaming, automotive, and software development.

Company Size: Perforce is a large company with a significant global presence, indicated by its "global footprint spanning more than 80 countries" and "over 75% of the Fortune 100" as clients. This suggests a stable, well-established organization with ample resources.

Founded: Perforce was founded in 1995, indicating a long history and deep experience in the software development tools market. This longevity suggests stability and a proven track record.

Team Structure:

• The role is within an Agile development team, likely composed of software engineers, quality assurance professionals, and potentially a product owner or scrum master.

• As a Principal Engineer, you will likely report to an Engineering Manager or Director of Engineering, with a dotted line to product management for feature direction.

Methodology:

• Emphasis on Agile methodologies (Scrum, Kanban, Lean, XP) for iterative development, rapid feedback, and continuous improvement.

• Data-driven decision-making, leveraging performance metrics, security analysis, and user feedback to guide development priorities.

• A strong focus on workflow planning and optimization, ensuring efficient development cycles and timely delivery of features.

• Adoption of automation and efficiency practices in testing, deployment, and development processes, aligning with DevOps principles.

Company Website: https://www.perforce.com/

📝 Enhancement Note: Perforce's emphasis on being a "community of collaborative experts" and a "problem solvers" suggests a culture that values technical expertise, teamwork, and innovation. The mention of "start-up feel with the security of an established company" indicates a dynamic environment that balances agility with stability.

📈 Career & Growth Analysis

Operations Career Level: This is a "Principal Engineer" role, signifying a senior individual contributor position. It implies a high level of technical expertise, architectural responsibility, and the ability to influence technical direction. This level typically involves mentoring, leading complex projects, and contributing to strategic technical decisions.

Reporting Structure: The Principal Software Engineer will likely report to an Engineering Manager or Director, working closely with other senior engineers, product managers, and potentially architects. They will be expected to guide and mentor other engineers within their immediate team.

Operations Impact: The impact of this role is significant, directly influencing the development of core frontend components for enterprise products like Delphix. The quality, performance, and security of the UI directly affect customer adoption, satisfaction, and the overall success of Perforce's product offerings. Contributions to technical design and architecture will shape the future direction of the product.

Growth Opportunities:

• Technical Leadership: Opportunity to lead major architectural initiatives, define best practices, and influence the technology stack for frontend development.

• Specialization: Deepen expertise in specific areas such as complex UI architecture, performance optimization, security protocols, or cloud-native frontend development.

• Mentorship & Management: Develop leadership skills through mentoring junior engineers, potentially leading to team lead or management roles if desired.

• Cross-Functional Exposure: Gain broader understanding of the entire software development lifecycle and how frontend integrates with backend, DevOps, and product strategy.

• Industry Recognition: Contribute to Perforce's reputation as a leader in software development tools through innovative solutions and technical excellence.

📝 Enhancement Note: A Principal Engineer role is a significant career milestone. Growth here is often about increasing technical scope, influence, and leadership rather than just climbing a traditional management ladder. Candidates should be looking to make a substantial technical impact and mentor others.

🌐 Work Environment

Office Type: The role is listed as on-site in Pune, Maharashtra. This suggests a traditional office environment designed for collaboration, with dedicated workspaces and meeting rooms.

Office Location(s): Pune, Maharashtra, India. This location is a major IT and business hub in India, offering access to a strong talent pool and a vibrant professional ecosystem.

Workspace Context:

• The workspace will likely be a collaborative office environment where engineers can interact directly with team members, product managers, and other stakeholders.

• Access to modern development tools, robust IT infrastructure, and high-speed internet is expected to support complex frontend development tasks.

• Opportunities for informal and formal collaboration will be abundant, fostering knowledge sharing and problem-solving sessions.

Work Schedule: The standard work schedule will be full-time, likely aligned with business hours in India (Asia/Kolkata timezone). Flexibility might be offered, but core hours will be important for team synchronization and collaboration with geographically distributed teams or stakeholders.

📝 Enhancement Note: An on-site role in a major tech hub like Pune implies a professional office setting conducive to team collaboration and focused work. The company's global presence might also mean occasional interactions with international teams, requiring some flexibility in working hours.

📄 Application & Portfolio Review Process

Interview Process:

• Initial Screening: HR or recruiter call to assess initial fit, understanding of the role, and basic qualifications.

• Technical Phone Screen: An engineer or hiring manager will conduct a technical interview, likely focusing on core Javascript,

Angular concepts, API design, and problem-solving.

• On-site/Virtual On-site Interviews: This stage typically involves multiple rounds:

  • Coding Challenges: Live coding exercises in Javascript/Angular to assess practical skills and problem-solving abilities.
  • System Design/Architecture: A session dedicated to discussing architectural approaches for complex enterprise frontend applications, microservices, and API integrations.
  • Behavioral/Situational: Questions assessing leadership, mentorship, teamwork, and how candidates handle challenging situations.
  • Manager/Director Interview: A final discussion to assess overall fit, career aspirations, and alignment with Perforce's culture.

• Portfolio Review: Be prepared to walk through specific projects from your portfolio, explaining your role, design decisions, technical challenges, and outcomes.

Portfolio Review Tips:

• Curate Select Projects: Choose 2-3 of your most impactful projects that best showcase your Principal Engineer capabilities, focusing on complex enterprise applications, SaaS, and UI/frontend architecture.

• Detail Your Contributions: Clearly articulate your specific role, responsibilities, and the technical decisions you made. Quantify achievements where possible (e.g., "improved performance by X%", "reduced load times by Y seconds").

• Showcase Architecture and Design: For each project, explain the architectural choices, the frameworks used (especially Angular), API integrations, and how you handled scalability, performance, and security.

• Highlight Mentorship/Leadership: If applicable, provide examples of how you mentored junior engineers or led technical initiatives within your projects.

• Prepare for Technical Deep-Dives: Be ready to answer detailed questions about your code, design patterns, and the technologies you employed.

Challenge Preparation:

• Master Javascript & Angular Fundamentals: Thoroughly review core concepts, ES6+ features, component lifecycle, state management, routing, and performance optimization techniques in Angular.

• Practice System Design: Prepare to discuss designing scalable, maintainable, and secure frontend architectures for enterprise SaaS products. Consider topics like micro-frontends, API gateways, state management strategies, and security best practices.

• Refactor and Optimize: Be ready to discuss how you would refactor legacy code to improve performance, maintainability, or security.

• API Integration Scenarios: Practice designing and discussing API interactions, including RESTful principles, error handling, and data transformation.

• Agile & Collaboration Scenarios: Prepare to discuss your experience working in Agile teams and how you collaborate with cross-functional stakeholders.

📝 Enhancement Note: The interview process for a Principal role is rigorous. Emphasize not just coding ability but also strategic thinking, architectural vision, and the ability to lead and mentor. A strong portfolio that demonstrates these qualities will be crucial.

🛠 Tools & Technology Stack

Primary Tools:

• Frontend Frameworks: Javascript, Angular (mandatory), React, Vue.js (preferred).

• Version Control: Git (highly likely).

• Build Tools: Webpack, Angular CLI, or similar.

• Package Managers: npm, Yarn.

Analytics & Reporting:

• Performance Monitoring Tools: Browser developer tools, Lighthouse, potentially APM tools integrated with the backend.

• Error Tracking: Sentry, Rollbar, or similar.

• Analytics Platforms: Google Analytics, Adobe Analytics, or internal tracking solutions.

CRM & Automation:

• API Development/Testing Tools: Postman, Insomnia.

• CI/CD Tools: Jenkins, GitLab CI, GitHub Actions (likely used for automated testing and deployment pipelines).

• Containerization & Orchestration: Kubernetes, Docker, Rancher (preferred for cloud deployments).

• Databases & Caching: Redis, SQL databases (e.g., PostgreSQL, MySQL).

• Security Protocols: OAUTH, JWT.

📝 Enhancement Note: While the job description explicitly mentions Angular and Javascript, the "nice to have" skills and general enterprise context suggest familiarity with a broader modern web development stack, including cloud technologies, CI/CD, and various data stores.

👥 Team Culture & Values

Operations Values:

• Collaboration: Fostering an environment where team members work together, share knowledge, and support each other’s growth.

• Excellence: A commitment to high-quality code, robust design, and continuous improvement in all aspects of development.

• Innovation: Encouraging the exploration of new technologies and creative problem-solving to deliver cutting-edge solutions.

• Ownership: Taking responsibility for features and projects from conception through deployment and maintenance, ensuring successful outcomes.

• Customer Focus: Understanding customer needs and delivering solutions that provide significant value and positive user experiences.

Collaboration Style:

• Agile and Iterative: Working in short sprints, with regular feedback loops and adaptability to changing requirements.

• Cross-Functional: Close collaboration with product management, backend engineering, QA, and potentially UX/UI designers to ensure alignment and cohesive product development.

• Open Communication: Encouraging transparent communication, constructive feedback, and knowledge sharing through code reviews, team meetings, and documentation.

📝 Enhancement Note: Perforce's stated values ("collaborative experts, problem solvers, and possibility seekers") align with a culture that values technical prowess, teamwork, and a forward-thinking approach to development.

⚡ Challenges & Growth Opportunities

Challenges:

• Technical Complexity: Working with intricate enterprise product architectures and ensuring scalability, performance, and security across a broad feature set.

• Legacy Code Refactoring: Modernizing and improving existing codebase sections while minimizing disruption to ongoing development and existing functionality.

• Cross-Team Dependencies: Managing dependencies and ensuring seamless integration with backend services, APIs, and potentially third-party integrations (e.g., Atlassian).

• Staying Current: Keeping pace with the rapidly evolving landscape of frontend technologies, frameworks, and best practices in a Principal Engineer capacity.

Learning & Development Opportunities:

• Advanced Frontend Architecture: Deepen expertise in areas like micro-frontends, state management patterns, and advanced UI performance optimization.

• Cloud & DevOps Integration: Gain hands-on experience with cloud platforms (AWS), containerization (Kubernetes), and CI/CD pipelines, understanding how frontend fits into the broader DevOps ecosystem.

• Technical Leadership & Mentorship: Hone leadership skills by guiding junior engineers, leading design discussions, and contributing to technical strategy.

• Industry Conferences & Training: Opportunities to attend relevant conferences, workshops, and pursue certifications to stay at the forefront of technology.

📝 Enhancement Note: The challenges presented are typical for a senior role in a complex product environment. The growth opportunities are geared towards deepening technical expertise and leadership capabilities, essential for a Principal Engineer.

💡 Interview Preparation

Strategy Questions:

• "Describe a time you architected a complex enterprise frontend application. What were the key design decisions, and what were the trade-offs?"

• "How would you approach refactoring a large, legacy Angular codebase to improve performance and maintainability? What steps would you take?"

• "Walk me through your process for analyzing and improving the security posture of a frontend application."

• "Explain your experience with microservices architecture from a frontend perspective. How do you manage communication and state across micro-frontends?"

Company & Culture Questions:

• "What interests you about Perforce and the Delphix product specifically?"

• "How do you see your skills and experience contributing to our Agile development process and company culture?"

Portfolio Presentation Strategy:

• Structure: For each project, use the STAR method (Situation, Task, Action, Result). Clearly define the problem, your role, the specific actions you took, and the quantifiable results.

• Technical Depth: Be prepared to discuss the technical details of your code, architecture, testing strategies, and the reasoning behind your technology choices.

• Focus on Impact: Emphasize how your work contributed to business goals, improved user experience, enhanced performance, or strengthened security.

• Visual Aids: When possible, use diagrams or screenshots to illustrate your architecture and UI designs.

• Conciseness: Be clear and concise, focusing on the most relevant aspects of your projects for this Principal Engineer role.

📝 Enhancement Note: Interview preparation should focus on demonstrating not just technical proficiency but also strategic thinking, leadership potential, and alignment with Perforce's culture and values. A well-prepared portfolio presentation is critical.

📌 Application Steps

To apply for this Principal Software Engineer (UI) position:

• Submit your application through the provided link on jobs.lever.co/perforce.

• Tailor your resume: Highlight your extensive experience with Javascript, Angular, enterprise SaaS development, API integrations, and microservices architecture. Quantify your achievements wherever possible.

• Prepare your portfolio: Select 2-3 key projects that best demonstrate your architectural capabilities, complex UI development, and leadership experience. Be ready to discuss these in detail.

• Practice technical and system design questions: Review core Javascript/Angular concepts, API design, microservices patterns, and common refactoring/performance optimization scenarios.

• Research Perforce: Understand their product suite, company mission, and values to articulate your interest and cultural fit during interviews.

⚠️ Important Notice: This enhanced job description includes AI-generated insights and operations industry-standard assumptions. All details should be verified directly with the hiring organization before making application decisions.

---