Enterprise Cloud Architect Resume Storytelling Example

Without Storytelling

What was the problem and what were the challenges?

I work in Enterprise Architecture team for a mature global organization that doesn’t like change. I undertook the long process of getting my company to embrace off-premises Infrastructure-as-a-Service as a viable computing platform. Many different stakeholders both inside and outside of IT had to be convinced of the value and safety of running business applications at a third-party cloud service provider. Those stakeholders included the traditional infrastructure team, security, legal, contracts, finance, IT executive management and corporate executive management.

What work did you perform?

I created an IaaS Reference Architecture to provide a common model and language to frame discussions with the different technical and business teams. I conducted a cost/benefit analysis and then worked across the entire organization to drive discussions about the benefits of IaaS computing.  Whether it was one-on-one or meetings I was there with my list of benefits.

Once my conversations started to gain traction, I worked with stakeholders to create a pricing model that was acceptable to the cost-conscious finance manager.

I then defined the cloud vendor selection criteria for performing proof-of-concepts (PoC). I was part of the evaluation committee.

I established a cloud standards governing body (Cloud Security Alliance) and its cloud control framework across the organization to help IT evaluate its ability to manage the associated risks.

I held an introductory lecture about Amazon’s cloud service (AWS) that was broadcast to all of our global offices and arranged an executive briefing at AWS headquarters for our CIO and key members of the management team.

Our CIO then directed me to work with AWS to perform a TCO analysis and as a result the CIO acknowledged the strategic significance of off-premises IaaS Cloud and approved the formation of program to manage our Cloud adoption process.

The journey to the cloud has already yielded benefits:

Reduced the time for the spun off a business unit that was hosted in the cloud by 75%.

Utilized the agility of the cloud to allow for “just-in-time” infrastructure purchasing, eliminating a painfully slow provisioning cycle.

Normally it can take IT a year or more to transfer an application from our internal data centers to a new operating environment. In this case, the transfer (including moving to the cloud) took three months. Acquisitions take even less effort. Traditionally an acquisition team within our company will engage people throughout IT to onboard a company. If the acquisition target is hosted in the cloud, we leave them there and do minimal integration work.

Revised Version With Storytelling

I love this story. It is all about persistence and the drive to make extraordinary changes and enable business agility in a mature organization.  It is a rather long story, but we decided that this would be the only story to include for a five-year time period. It does such a good job of describing his strong leadership and very persuasive communication skills within both business and technical teams. These are trademark qualifications in an Enterprise Cloud Architect.

It is a good practice to write out the full story, and then decide what to include in your resume, your interview, your LinkedIn profile or your cover letter. This client’s story is long, so we used parts in his resume and parts in his LinkedIn profile.


Primary Challenge: Enable IT innovation, business agility, and cost controls for a global company that designs and sells telecom products/services, a market that is rapidly becoming saturated.

Transforming IT into a more agile and efficient organization through road mapping and adoption of cloud computing. Supporting corporate goals to build product faster and cheaper, as well as to seek new market opportunities.

  • Serve as a Cloud Architect and technology evangelist within the Cloud Steering team, driving the adoption of Infrastructure-as-a-Service (IaaS) as a viable computing platform.
    • Created an IaaS Reference Architecture for a common model and language to frame discussions across the organization, including the traditional infrastructure team, security, legal, contracts, finance, and IT and corporate executive management. Developed a cloud maturity roadmap.
    • Performed Cloud TCO analysis and worked with stakeholders to create a pricing model. Defined the cloud vendor selection criteria for performing proof of concept (PoC).
    • Socialized a cloud governing body (Cloud Security Alliance) and its cloud control framework for risk identification and management.
    • Worked at many levels to gain buy-in, including engaging the CTO and VP of Amazon, as a keynote speaker for the Enterprise Architectures Winter IT Tech Forum.
    • The journey to the cloud has already yielded the benefits of:
      • Reduction in the time to spin off a business unit by 75%.
      • “Just-in-time” infrastructure purchasing to eliminate a painfully slow and expensive provisioning cycle.