Principal Services Architect I

As a Principal Services Architect I at Axway, your daily responsibilities include overseeing the application solutions for enterprise cloud clients, ensuring all service level agreements are met. You’ll collaborate with technical teams to implement changes, manage incidents, and administer applications. Additionally, you'll engage in troubleshooting network issues within AWS and provide solution design based on client needs.

To apply for the Principal Services Architect I position at Axway, you should have a Bachelor's degree in Computer Science or a related field, along with at least 3 years of experience in relevant areas. This experience should encompass work with B2B products, Unix/Linux/Windows platforms, and understanding various communication protocols like AS2, FTP/S, and SFTP.

Yes! The Principal Services Architect I role at Axway offers flexibility with partial remote work options, allowing you to balance your professional responsibilities with comfort, as long as you reside within a reasonable commuting distance to our Scottsdale office.

Essential technical skills for the Principal Services Architect I at Axway include a strong background in B2B and serialization products, cloud platforms such as AWS and Azure, and working knowledge of databases like MySQL, PostgreSQL, and Oracle. Familiarity with incident management, disaster recovery, and web applications is also crucial for success in this role.

As a Principal Services Architect I at Axway, you will work with a variety of software and tools, including B2B and EDI products, incident tracking systems, and cloud management tools for AWS and Azure environments. Your role will also involve utilizing protocols such as AS2 and FTP/S, as well as managing databases like MySQL and Oracle.

In answering this question, highlight specific projects where you utilized B2B and serialization technologies, including any challenges you faced and how you overcame them. Use relevant metrics or outcomes to demonstrate the impact of your work.

Address this by discussing your methods for tracking performance metrics, regular communication with clients, and proactive risk management strategies. Provide examples of how you have successfully maintained SLAs in past roles.

Share your troubleshooting framework, emphasizing a systematic approach to identify root causes and implement solutions. Discuss any specific tools or methodologies you use, such as logging systems or monitoring tools, to support your problem-solving process.

Select a specific example that showcases your technical expertise and problem-solving skills. Describe the situation, your approach to resolving the issue, and the eventual outcome. Highlight what you learned and how it enhanced your skills.

Demonstrate your commitment to continuous learning by mentioning relevant courses, certifications, webinars, or industry publications you follow. This shows your proactive approach to professional growth in the rapidly-evolving tech landscape.

Provide examples of how you have collaborated with different teams, such as sales, customer success, or project management. Emphasize your communication skills and ability to foster teamwork to achieve common goals.

Discuss the strategic role of the Principal Services Architect in aligning technology solutions with client goals, ensuring their needs are met throughout the project lifecycle, and acting as a trusted advisor to foster long-term relationships.

Share your techniques for prioritization and time management, such as using project management tools or methodologies. Provide an example demonstrating how you successfully managed competing tasks to meet deadlines.

Discuss your systematic approach to product installations and upgrades. Include steps like pre-installation planning, testing, and post-deployment checks to ensure the upgrade maintains functionality and addresses existing issues.

Highlight the critical nature of disaster recovery by discussing your strategies for ensuring data integrity and availability. Include examples of plans you've created or executed during your previous roles to maintain business continuity.