** At high level, im responsible for all technical aspects of bringing the new client onto Amazon’s cloud platform
instill confidence, build andmaintain trust to make transiton as graceful and seamless as possible so that their decision to invest in and adopt Amazon as their critical services provider never wavers.
** Specific role is to act in capacity of liaison with client and amazon’s intermal teams to customize a solution based on using a proper synthesis of amazon cloud services.
i effectively work to build a trust-based relationship with client foremost
client needs to have implicit trust of your confidence in Amazon’s offerings
and in my ability to bring ideas for relevant solutions to the discussion
my role broadens to that of a liaision between the client and Amazon teams
use available internal teams and partners collaboratively to determine most appropriate, effective, reliable, fault tolerant solution
segway to Amazon points of Leadership
im not necessarily tasked with doing the buildout. other teams and partners for that.
ill work with Amazon internal teams and partners. they’ll provide leverage in terms of deep, low-level knowledge of Amazon’s component products, their appropriate uses, nuances and potential complications or incompatibilities that may be problematic when used in integration with other products or within a particular architecture.
what are other, various types of teams?
enterprise teams
smb teams
project leads
business analysts
data specialists
security specialists, etc.
—
how does solutions architect allocate their time day-to-day?
1. 1/2 time spent engaging with customers.
do architectural review with client, at same time building trust)
while concurrently formulating solutions to help customers address their business pains, be it to improve on their own internal systems architecture or migrate to cloud (less reliance on internal staff by taking advantage of amazon’s large, skilled resource pool) and develop custom software solutions to meet their particular business challenges
build out proof of concepts
2. other 1/2
internal meetings (sales funnel, current customer progress, backlog funnel/burndown log, etc.),
self-education (product updates, new products)
presentations, writing articles, leading tech workshops, mentoring
scope creep – “the extent of what a project will produce and the resources needed to produce it.”
—
What’s It Like to Be a Solution Architect at AWS?
https://www.youtube.com/watch?v=IBqqYWr4t94
—
Related