“Architect” – It’s one of the most overly used, abused and least understood of software engineering roles. Every senior developer thinks they are one. Many aspire to become one. The rest can’t stand them. The word takes on a totally different meaning if prefixed with development, solution or enterprise. It gets even more divided when referring to architects for technologies (i.e., UI architect, Java architect, etc.). The topic is hardly covered in formal education and every new meetup/conference will give you their perspective.
Well, Mike and Rajesh have their views on it, too. Attend this Tech Talk to learn more about what being an architect really means, their role in the organization, their responsibilities and the blind spots that budding architects can fall into.
About the speakers
Michael Walker is the Chief Architect for CA Technologies Application Performance Management product line. In this role, he leads the architecture definition across 14 scrum teams and 4 geographies. Prior to joining CA Technologies, Michael worked as an architect at Cassat Corporation where he led the virtualization effort for their platform. Michael has also held senior engineering positions at Sun Microsystems where he worked in their System Software group and contributed to their Solaris Operating System.
Rajesh Raheja is vice president for architecture and technology initiatives in the Applications Delivery BU and an enterprise software veteran of 24 years. He recently came to CA after 18 years at Oracle in various leadership roles in Communications, CRM, ERP, SaaS and SOA groups. In his most recent role, he architected, designed and led DevOps engineering for an Integration Cloud iPaaS offering; the success of which saw him assume leadership of a central cloud delivery team to on-board all integration cloud services in the PaaS division. Rajesh holds a Bachelor of Engineering degree in computer engineering from University of Bombay, one US patent on enterprise app deployment strategy and SCPM, CSM and PMC-11 certifications.