Related Posts
I am a Principal Solutions Architect with 13 YOE of which 5 years exp is with Biotech focusing on Public Cloud (AWS) & overall AWS exp. 9 years. I need suggestions /opinions if applying for a Senior Solutions Architect (Level6) at AWS makes sense or if I should aim for a Principal SA (level 7) role at AWS with Healthcare & Lifesciences industry experience. If it makes any difference, I worked for AWS ProServe as an external SA in the past. Any insights / feedback appreciated.
Amazon Web Services
At what stage is the hiring manager interview?
More Posts
Please DM if interested asap
Additional Posts in Consulting
New to Fishbowl?
unlock all discussions on Fishbowl.
Depends on what they ask you. If they say “tell me about a time [blah blah]” and you did [blah blah] go into as much detail as necessary to answer their question. Don’t necessarily give the whole story, look at it like checking a box. They are assessing your skills/experience, and a slew of other things, and your answer hypothetically checks the box. How you deliver, your energy, personality, body language, dress, word choice, all kinds of things matter. But answering the question with the most relevant detail is what I’m usually expecting. I don’t have much compunction cutting people off after a minute or two if they are rambling...but maybe that’s just me.
G1 is right. Hit the three key items from your resume why you would be a fit/move the business forward and then create a personal connection in the remaining 28 minutes and 30 seconds.
I would *not* recommend spending valuable interview time on explaining granular resume details. Consider the resume a “pre-read” that the interviewer has done (but may in fact not have read), and instead use the interview time to “win the job” and be the top candidate he/she recommends for next steps. Unfortunately, the prize for 2nd place is a rejection email from the recruiter, so do everything you can to win.
6 grains deep