F5 technologies are at the heart of modern applications that are enabling digital transformation across the globe. We give the world’s largest businesses, service providers, governments, and consumer brands the ability to securely deliver every app, anywhere—with confidence. We do this by working collaboratively in an innovative environment, helping each other succeed. We take great pride in being trusted advisers to our customers, offering the best solutions for their interests. If our mission and culture excite you, we would love to talk to you!When applying for any of the roles in F5, please note, our ideal candidate is not necessarily someone who meets all the posted requirements. In fact, this is just a representative of how we know the job has been done in the past. We would love to talk to you even if you don’t check all the boxes here, but believe you bring your own unique capabilities that can be utilized to ensure the success of the role and the organization.The Enterprise Architect (EA)SolutionsArchitect (SA) job family. The SA’s primary function is to work collaboratively with sales teams identifying appropriate F5 solutions to address customers’ business needs. They provide technical expertise and business understanding across specific or multiple industries. Theychampion our customers’ requirements and ensure they are understoodacross other teams within F5 such asSales, Marketing, Product Management, and Product Development. role is part of the TheSA alsoshares knowledge and educates the solution engineering team internally and externally via whitepapers, trainings, demos, blogs, tech-tips, presentations etc.To be effective, an SA needs to blend strong business acumen with excellent technical skills and knowledge on both F5 products and the “eco-system” that we work in.He/she needs to be an authority in his/her field of expertise and act as a trusted advisor towards our customers. While the traditional Solution Architect is focused on going deep on a specific technology, the Enterprise Architect role is meant to be much broader and wider. The primary role of the traditional SA is to provide technical expertise in his specific domain while the EA is driving architectural discussions with our customers, helping