6 ms·
ProServe and SAs have little-to-no on-call responsibilities, but the general workload issues and mindsets affect those teams as well. Just as an example, resour
by awsthro00945 5y ago
ProServe and SAs have little-to-no on-call responsibilities, but the general workload issues and mindsets affect those teams as well. Just as an example, resource management (aka staffing) and project scoping are things that AWS Sales is absolutely fucking awful at, and are things in particular that other consulting companies have figured out decades ago, but AWS does nothing to improve the shitty staffing processes because they have essentially just thrown up their hands and think the inefficient, inaccurate, and incredibly stress-inducing process is normal.
- vr46 5y agoOf course, I guess there's no perfect isolation. A friend at Amazon set me up a video call last year with an SA at AWS (Seattle/NW) so I could inquire about working there. It sounded pretty cool but I wasn't sure. I didn't think that AWS consulting was much of a thing, since my experience client-side has been that AWS will advise but not build. Anyway, irrelevant to this thread. Not sure consulting is much better away from AWS as in my world, it's 90% dependent on the client you're with and boy have I had some awful projects.
- awsthro00945 5y agoBased on my experience working on different teams and interfacing with the SA teams (but not actually working as an SA, mind you), being an SA at AWS seems to be one of the better positions in terms of workload, limited on-call responsibilities, etc, but you do need to be very comfortable with constant customer-facing responsibilities (which can sometimes be better than on-call, and sometimes can be worse than on-call) and the team is still dragged down by the general Amazon/AWS culture.