|
 (my img hosting) Amazon Web Services is growing like crazy and we are hiring for Technical Account Managers and Cloud Support Engineers. I am currently a TAM in Seattle and the job is awesome. Imagine an IT world where you are treated like a grownup and a professional and every day are given opportunities to learn new cutting edge cloud technologies and work along side really, really smart people. Yeah, it's here. If you have a working knowledge of enterprise systems administration (UNIX/Linux and/or Windows Server), have a strong customer focus and like fast-moving environments and are excited about technology, send me your c.v. at agrikk@gmail.com and I'll send it to some friends in H.R. for review. Where are we? I am based out of the Seattle WA office, but we are hiring for any AWS location, so essentially globally. What are we looking for? Technical Account Manager (note that this link sends to you the UK position, but we are hiring everywhere) Cloud Support Engineer (this is for a Dublin position, but we are hiring worldwide) How do I apply? Send me a PM or email me at my user name at gmail dot com. You can also apply through the web links above, but make sure to let me know so I can call out your resume to HR. Agrikk fucked around with this message at 01:25 on Jul 22, 2014 |
#
¿
Jul 18, 2014 19:15
|
|
|
|
| # ¿ Apr 20, 2024 03:48 |
|
|
The AWS web site has a big list of open positions and which offices are hiring for them, so you should look there and find out of there's a gig for you open nearby. AWS has a pretty flexible telecommuting policy and a few TAMs work 100% remote. Basically if AWS decides they want you bad enough, they'll reach an accommodation. I myself could work 100% remotely, but I choose to go into the office three days a week because I like having a building full of experts ay my immediate disposal if I run into a problem. A list of AWS jobs by family is here and you can drill down into a role to see where there are positions available. edit: Hemick, I got your CV and will be forwarding it to my friend in HR. Good luck!
|
|
#
¿
Jul 22, 2014 01:22
|
|
|
Experto Crede posted:Hey Agrikk, could you give a bit more detail about what the TAM position entails day to day? Sounds cool, I'd like to hear more Sure. A TAM at AWS provides white glove service to a set of Enterprise customers paying for premium support. I have a set of customers who spend upwards of a quarter of a million dollars a month on AWS services and I work closely with them to make sure they're doing it correctly. I fast-track and baby sit any tickets they might open with tech support, I perform deep dives with them to help them understand an AWS service, best practice, or what a well architected web application looking like from an infrastructure standpoint. Having a problem with Elastic Beanstalk or EC2 or S3? Let me walk down the hall to the guys who coded the stack and talk to them directly. On any given day I can be on the phone or webex with a customer, dealing with a pain point of theirs or a question that involves one of the AWS services, or analyzing their AWS utilization and figuring out how they can save money (consolidating to a larger EC2 instance, or shutting idle instances off, for example), or attending an AWS-hosted training session on a new feature or service (put on by the guy who coded the new feature or service). The TAM isn't as technical as a Cloud Support Engineer or an engineer on a Service Team (all AWS offerings are called services), aren't as market-y or sales-y or business-y as those guys, but is involved in all of it. We are expected to be generalists with a scope of knowledge five miles wide and two inches deep. You tend to get better at the services that your customers use the most and the areas of AWS that you don't use every day get a little cobwebby in your head. The best part of the gig in my opinion is that you get all of AWS as your playground. For free. While support engineers are allowed to spin up things to test, they are expected to terminate them after the ticket is closed. TAMs on the other hand build complete environments in multiple data centers world wide that mimic in some way their customers' so that they can deep dive into whatever the customer is working on. (A current pet project of mine is building a Folding@Home stats tracker using PHP/IIS/SQL Server. It currently is hosted in two data centers (East Coast and West Coast) with two beefy SQL 2012 servers replicating data between the two sites, serving up data to two pools of IIS servers, using geo load balancing to split global traffic between the two sites based on utilization and latency. All of this is hosted for free in AWS.) I liken a TAM role like a trauma surgeon on Grey's Anatomy: We spend a ton of time researching, learning, collaborating and helping, and when the poo poo hits the customer fan, we jump all over it and call in all the specialists from all the other teams to bring a case to successful conclusion. Are you an IT generalist who loves learning new poo poo all the time? Can you thrive in ambiguity while drinking from a firehose? This gig is for you. You will never be bored and you are always always learning. You are doing this in an environment with some smart loving people who really want to see you succeed. In 18 years in IT, this is by far the best job I have ever had. Period. Agrikk fucked around with this message at 05:11 on Jul 28, 2014 |
|
#
¿
Jul 28, 2014 05:04
|
|
|
skipdogg posted:How's working there? Amazon has been getting trashed online lately regarding the work environment. Is there a semblance of W/L balance or is it 50-80 hour weeks? If you are referring to the glassdoor reviews, consider that it's sixty or so folks out of a hundred thousand... That said, I hear software developers are pretty hammered, but that's strictly hearsay. I work 40 hour weeks, but those forty hours land typically on six days of the week: some days are shorter, some are longer and sometimes I work on a weekend day, but there is definitely balance. My manager is all about making the customer happy, and if that's the state of my customers, he leaves me alone and doesn't sweat the clock. Again, I can only speak for TAMs. I have no idea how the other teams are.
|
|
#
¿
Jul 28, 2014 07:58
|
|
|
MJP posted:Agrikk, I shot you a PM but no response - is the cloud support engineer happening out of the NYC location at all? I didn't see a posting for it, but since you mentioned worldwide, figured I'd ask. Hey MJP and everyone else who pm-ed or emailed me: I've received your emails and PMs, but I was out on vacation all last week. I'll be contacting y'all in the next 24 hours with updates. To your question, MJP, The closest support office to NYC is in Herndon, Virginia. However lots of people telecommute and we have a few people who are 100% remote and come into the office once or twice a quarter. YMMV but I suggest applying and seeing what happens. If you are good enough and rock the interview they might hook you up.
|
|
#
¿
Jul 28, 2014 22:15
|
|
|
A few of you have contacted me about what you can do in your current job to prepare for a jump into AWS as a Cloud Support Engineer. Rather than respond individually, I thought I'd make the post public: A Cloud Support Engineer (CSE) is the front-line case-taker. To some they are considered the help desk for AWS, but I believe they are much more than that. Like Help Desk, the CSE needs to be really good at dealing with ambiguity and is constantly forced to expand their skill set as they received cases from customers that the CSE might not understand. The CSE is an extremely technical position and it is expected that you will soon have a deep understanding of one or more of the AWS services while being able to have an intelligent conversation on the rest of them. You will have a massive array of in-house developed tools at your disposal, and some say mastery of the tools at hand is harder than learning about the AWS services themselves. The right tool for the right job holds true here and knowing which tool to use is 60% of the task. Everything in AWS talks to everything else and therefore, a CSE must have a strong grasp of networking concepts and protocols (Subnets, routing, CIDR blocks, gateways, TCP/IP, the differences between TCP and UDP, DNS and DHCP operation) as well as exposure to virtualization (EC2 is basically the biggest virtual machine farm ever) and understand what goes on when you deploy a new linux/windows virtual machine from a deployment template. A deep knowledge in a subject that you are passionate about is important. While you are at your current gig, keep your eyes open for technology that you want to spend a lot of time in. Do you want to be a networking guru? A storage expert? A database god? a deployment manager? A security nazi? a deployment and scripting genius? Big Data developer? What blows your skirt up in tech? You should spend your free time at work and some more at home exploring new tech and developing a passion for something- because there will be times when that passion for tech is all that keeps you going. Play with MySQL or SQL Server Express, stand up some virtual machines on your laptop or home PC using Xen or Hyper-V and look into buying some cheap CCNA kits off of eBay and see if you like routing/networking. This passion will translate well during your interviews at AWS and the interviewer will immediately recognize it. AWS looks for a proven track record of being customer focused and displaying personal initiative to overcome technical obstacles in the face of ambiguity. I will keep linking this because I cannot stress this enough. Learn the Amazon Leadership Principles and map everything you do to them. Good Luck!
|
|
#
¿
Aug 1, 2014 18:10
|
|
|
hackedaccount posted:Is it true that Amazon is an "up or out" environment? I've heard from several sources that it is. I can't speak to the whole, but Amazon Web Services isn't like that at all. They are definitely geared towards retaining talent, to the point that during my orientation they told us to start thinking about the next position you want, so that if/when you get burnt out or bored you can move to another team and a new role within the organization. Talent is hard to come by and they really really want to keep it. They recognize that money only goes so far for retention: when a nerd gets bored he starts looking for new shiny things to play with.
|
|
#
¿
Aug 2, 2014 00:58
|
|
|
Paul MaudDib posted:My experience: MSc in CS, recent graduate. 2.5y of research work in computational biology in C/C++ with OpenMP and CUDA, resulting in 3 publications. Experience with C#, Python, some Java and SQL, Win/Unix environments, and the usual trappings of software development. I can pick up anything given a few weeks. Email sent.
|
|
#
¿
Sep 8, 2014 03:39
|
|
|
psydude posted:There's usually some good positions on here (and I got my first post-college job from this thread!) so here goes again! PM sent.
|
|
#
¿
Sep 8, 2014 03:44
|
|
|
Technical Account Manager - Enterprise Support Who are we? Amazon Web Services, an $8 billion subsidiary of Amazon.com. Enterprise Support is the top tier of customers within AWS and is the fifth largest business unit by revenue within AWS. Where are we? We have a global presence with a follow the sun support model. We have offices in the US East and West coasts, Ireland, Frankfurt, South Africa, Japan, China, Brazil, etc. and many TAMS telecommute 100% of the time. What are we looking for? We are looking for a personable individual with a body of tech knowledge five miles wide and four inches deep who also has the ability to [quickly learn enough about a subject to] go deep on any given subject on a moment's notice. Do you like to learn new things just because you are curious about it? This gig is for you. The TAM role requires technical acumen and an ability to talk shop with engineers amnd then shift gears to discuss business- and implementation strategies with executives. If you have ever built a company from scratch with corp/dev/prod environments running on virtualized environments we want to talk to you. If you are working for a company that is currently an AWS Customer, we want to talk to you. If you can speak code, storage, high-availability, disaster recover, databases and networking, sometimes all in the same sentence, we DEFINITELY want to talk to you. Why work for us? We have some of the smartest people in technology working here, and everyone has checked their egos at the door. TAMs seem to genuinely enjoy their work in a professional and grown-up environment where you are given all of the room you need to help your customers succeed, and where your feedback is heard and acted upon - even on the first day on the job. No time cards, no micromanagement, no bullshit. How do I apply? Shoot me your CV via PM or my forum name at gmail and I'll be happy to answer any of your questions. I have a friend in HR who reviews resumes I send her personally, so no waiting in a pile. Agrikk fucked around with this message at 18:49 on Jun 30, 2015 |
|
#
¿
Jun 30, 2015 01:17
|
|
|
kloa posted:wat Speaking as a Senior TAM, We are looking for an individual who has broad range of skills in the DevOps world or Infrastructure world and who isn't afraid to say, "I don't know that now, but give me a day or two and I'll get back to you." and then goes and learns. I may only have a vague sense of what all 50-ish services do, but if a customer expresses interest in something, it is my job to go and learn a ton about it so I am capable of teaching a 100-level or a 200-level seminar on the subject. If a technical issue comes up, it is my job to understand what the issue is so I can then represent the issue to the service teams and help them troubleshoot it. baquerd posted:They need a sales guy who doesn't suck rear end at talking about technical matters and who knows or can be taught about the AWS technologies appropriate to common problems. When talking to clients, your trump card is "Let me take that up with our senior engineers and get back to you". This is absolutely not a sales role, and if all I do is "take that up with our senior engineer" I'm failing at TAM.  The TAM exists as a liaison between the customer and AWS, representing AWS to the customer and representing the customer to AWS. As such, the TAM needs to be able to understand what the customer is trying to accomplish and be able to understand how to best use the various AWS services to help them succeed. When the customer has a problem, the TAM kicks in doors on their behalf. If AWS launches something or is looking for feedback from customers, the TAM takes that message to their customers. I have a portfolio of customers, and it is my job to provide customized support for them, understanding their environments as if I were one of their architects.
|
|
#
¿
Jun 30, 2015 18:31
|
|
|
baquerd posted:OK, sure, "not a sales role" but involves telling customers what technologies to use that just happen to cost the customer money. I work with an AWS TAM for my organization, and I regularly find them useless because we thoroughly understand the 100 and 200 level stuff, but need a graduate level technical dive into optimizing six nine's of uptime architecture. The TAM being entirely tapped out for knowledge or otherwise telling us they have no solution to our problems is a regular experience for me. We throw literal millions at AWS every year, so my experience may be significantly different than the usual TAM client, if the usual client is one who is just starting to use AWS. I will reiterate: the TAM role is absolutely not a sales role. If anything, call it Tier 4 support for Enterprise Customers. I work with a portfolio of customers (currently 4) with whom I build a lasting, ongoing relationship. I partner with them to help them accomplish their strategic IT initiatives while using what I know about their organization to recommend the best techniques and services I can to help them do their job. Since I do not carry a quota, I am free to make unbiased recommendations about our products, including "maybe we aren't a good fit for you" and let the Account Manager figure out how to make his revenue targets. Yes, our services cost money. By becoming an AWS customer, you are agreeing to spend some money on our services. But this is not a sales role, because I do not have a revenue target to meet or any other kind of quota, which gives me the freedom to give the unvarnished truth about what is or isn't needed by your deployment. I don't tell the customer to do anything. I make recommendations that include the pros and cons of every decision they might make and let them decide, because it's their company and they know best. Our front-line tech support roles are the Cloud Support Engineers and they are the ones primarily responsible for case handling and taking tickets. Instead, I work with the customer directly to influence their long term strategies and make sure their support experience remains top notch. If anything, I am more of a switch yard, brokering relationships between customers and our internal service teams, giving our enterprise customers in-depth and behind the scenes views of our abilities. But I sent you a PM. I'd like to know more about your company and your TAM. Everyone else: I've received your PMs and emails and will be responding after the weekend.
|
|
#
¿
Jul 3, 2015 23:08
|
|
|
 Who we are: Amazon Web Services Unless you have been living under a rock for the past five years, you have probably heard of us. AWS pretty much invented what is now known as "the cloud" and is on track to generate $13 billion in revenue in 2017. What we're looking for: Let me be perfectly clear: A Technical Account Manager is NOT a sales role and does not have a quota. If anything, TAMs can be considered Tier-4 post-sales support. Shamelessly copied from the Amazon Jobs page (the link is for a job posting in Chicago, but the description applies globally): Would you like join one of the fastest-growing organizations within Amazon Web Services (AWS) and help customers of all industries and sizes gain the best value and service from AWS? At AWS Enterprise Support we’re looking for a Technical Account Manager (TAM) to support our customers’ creative and transformative spirit of innovation across all technologies, including Compute, Storage, Database, Big Data, Application-level services, Networking, Serverless and more. This is not a sales role, but rather an opportunity to be the principal technical advisor and ‘voice of the customer’ to organizations ranging from start-ups to Fortune 500 enterprises. As a TAM, you will help craft and execute strategies to drive our customers’ adoption and use of AWS services, including EC2, S3, DynamoDB & RDS databases, Lamdba and many more. Your technical acumen and customer-facing skills will enable you to effectively represent AWS within a customer’s environment, and drive discussions with senior leadership regarding incidents, trade-offs and risk management. You will provide advocacy and strategic technical guidance to help plan and build solutions using best practices, and proactively keep your customers’ AWS environments operationally healthy. The close relationships developed with your customers will allow you to understand their business/operational needs and technical challenges, and help them achieve the greatest value from AWS. We are seeking individuals with strong backgrounds in I.T. operations and related areas such as Linux/Windows systems administration, DevOps, Big Data and more. The TAM is our centerpiece of value to our Enterprise Support customers, so if you wish to be at the forefront of innovation, come join us! What we're not looking for: Unmotivated folks who cannot cope with ambiguity. I cannot stress this enough. There is no time or willingness to hand-hold here. If you see something broken or dumb or just plain sucks, go fix it. As an AWS employee you have the agency to take up issues that bug you and hammer on them until they disappear. We live by the Amazon Leadership Principles and I refer to them daily. Location: Seattle, WA would be great, but we are hiring worldwide with the opportunity for telecommuting available. Approximate opening date: Now. We literally cannot get enough TAMs in chairs Benefits: Health, Dental, 4 weeks PTO, 1 week personal days, and hey, check out AMZN. A few shares of that can't hurt, right? Notes: I have been a TAM for over three years at AWS and I wouldn't dream of working anywhere else. I work with some ridiculously smart people (let me tell you about the time I interviewed a literal rocket scientist who was applying for a network engineer proposition) and there is always something new to learn or play with on my free AWS account. If you are bored, you aren't trying very hard. Also: AWS still remains the redheaded stepchild of Amazon. Yes, you've read the Atlantic and Times articles about people crying at their desks at Amazon, but these are people working on projects in close proximity to Jeff Bezos. We roll up to Andy Jassy who leaves us pretty much alone because AWS is awesome. Contact: email me at my username at gmail
|
|
#
¿
Aug 12, 2017 00:14
|
|
|
Tab8715 posted:That doesn't sound like a TAM? You can call it whatever you want, but that is what AWS calls it and the description is what we do. We have no goals for revenue generation. That and relationship management are the Account Manager's responsibility. But we do work to build and foster trust with the customer and advocate for them to internal AWS staff.
|
|
#
¿
Aug 13, 2017 01:43
|
|
|
mayodreams posted:I pinged you about this in email. I got it. Thank you! I'll reply on Monday.
|
|
#
¿
Aug 13, 2017 02:30
|
|
|
Tab8715 posted:Is this one of those roles where need knowledgeable that's "an inch deep and a mile long?". Pretty much. But most TAMs find an area of interest and concentrate there. So it's an inch deep and a mile wide and a mile deep in that one place. Phuzun posted:Sent you an email. Got it. I should be all caught up in emails now, so if you haven't heard from me via email I didn't get it. Some additional details about the TAM role: When I was hired to AWS I literally knew nothing about the cloud. What sold them was that I demonstrated an ability to rapidly pick up new technologies on demand and I can also talk about architecture until I am blue in the face. Prior AWS knowledge isn't as important as a demonstrated willingness and ability to learn and master new technologies quickly. Also, this is a fairly senior level position. We are looking for a track record of ever-increasing responsibilities and projects of increasing complexity. Stood up a single DC running DNS and DHCP? Well, okay I guess. Built out a datacenter with corporate/dev/test/prod environments with multiple load-balanced tiers and VPN links to remote offices and road-warriors? Every automated yourself out of a job? YES! Agrikk fucked around with this message at 21:19 on Aug 14, 2017 |
|
#
¿
Aug 14, 2017 19:58
|
|
|
AWS is always hiring, and there is no specific position to be filled. If we find one candidate or one hundred, we'll take 'em! (And I get a referral bonus every time!)
|
|
#
¿
Aug 14, 2017 23:42
|
|
|
Thanks for all the resumes, everyone. I'm currently on the road, and will be home tonight, so my plan is to review and forward resumes to my friend in HR tomorrow. And to everyone else, there is no specific position to be filled, nor does this opportunity expire so if you are considering applying please do so! (If we find one person, we'll hire one person. If we find 100 people, we'll hire a hundred people.)
|
|
#
¿
Aug 16, 2017 16:25
|
|
|
Hey everyone, I'm now back from vacation and be able to finally get to all of your emails and resumes and will be contacting y'all this week. My apologies for the delay. I know this is people's careers on the line here...
|
|
#
¿
Aug 28, 2017 20:29
|
|
|
Alzabo posted:Please confirm thread, I am doing the correct thing by not giving them any numbers before the on-site interview? The first numbers really discussed should be their initial offer after deciding they can't live without me? One the one hand, Amazon asks for numbers to see if you fit the role and uses the expected range as a sanity check. But no, don't give the range. Nail the interview, make Amazon want you, then make them offer what you are worth.
|
|
#
¿
Sep 4, 2017 05:35
|
|
|
|
| # ¿ Apr 20, 2024 03:48 |
|
|
Thanks everyone for the CV submissions! At this point I'm pretty sure I've responded to everyone who reached out to me. If you have contacted me and not heard back, please reach out to me again and I promise that I won't delay (school has started so no vacations in my future...)
|
|
#
¿
Sep 6, 2017 03:52
|
|