Ga naar de inhoudGa naar de voettekst
  • Vacatures
  • Bedrijven
  • Salarissen
  • Voor werkgevers

      Geef je carrière een boost

      Ontdek hoeveel je kunt verdienen, vind droombanen en deel anoniem inzichten over werk en privé.

      employer cover photo
      employer logo
      employer logo

      Amazon

      Actieve werkgever

      Over
      Reviews
      Salaris en arbeidsvoorwaarden
      Vacatures
      Sollicitatiegesprekken
      Sollicitatiegesprekken
      Gerelateerde zoekopdrachten: Reviews voor Amazon | Vacatures bij Amazon | Salarissen bij Amazon | Arbeidsvoorwaarden bij Amazon
      Sollicitatiegesprekken van AmazonSollicitatiegesprekken voor Cloud Application Architect bij AmazonSollicitatiegesprek bij Amazon


      Glassdoor

      • Over
      • Blog
      • Contact met ons opnemen

      Werkgevers

      • Gratis werkgeversaccount
      • Werkgeverscentrum
      • Werkgeversblog

      Informatie

      • Help
      • Gedragscode
      • Gebruiksvoorwaarden
      • Privacy en advertentiekeuzes
      • Verkoop of deel mijn persoonlijke gegevens niet
      • Hulpmiddel voor instemming met cookies

      Partnerships

      • Adverteerders
      De app downloaden

      • Bladeren op:
      • Bedrijven
      • Vacatures
      • Locaties

      Copyright © 2008-2026. Glassdoor LLC. "Glassdoor", "Worklife Pro", "Bowls" en logo zijn gedeponeerde handelsmerken van Glassdoor LLC.

      Gevolgde bedrijven

      Volg de bedrijven van je dromen om als eerste op de hoogte te zijn van vacatures en te profiteren van tips van insiders.

      Vacatures

      Zoek naar vacatures om gepersonaliseerde vacature-aanbevelingen en -updates te krijgen.

      Topbedrijven voor 'vergoeding en arbeidsvoorwaarden' bij jou in de buurt

      avatar
      Google
      4.5★Vergoeding en arbeids­voorwaarden
      avatar
      eBay
      4.0★Vergoeding en arbeids­voorwaarden
      avatar
      Booking.com
      4.2★Vergoeding en arbeids­voorwaarden
      avatar
      Meta
      4.6★Vergoeding en arbeids­voorwaarden

      Sollicitatiegesprek voor de functie Cloud Application Architect

      4 mrt 2021
      Anonieme werknemer
      München, Bavaria

      Overige sollicitatiereviews voor Cloud Application Architect bij Amazon

      Sollicitatiegesprek voor de functie Cloud Application Architect

      12 dec 2025
      Kandidaat voor anonieme sollicitatie
      Dublin, Dublin
      Aanbod geaccepteerd
      Positieve ervaring
      Moeilijk sollicitatiegesprek

      Sollicitatie

      Ik heb via een werknemersdoorverwijzing gesolliciteerd. De procedure duurde 4 weken. Ik heb gesolliciteerd bij Amazon (München, Bavaria) in jan 2021

      Sollicitatiegesprek

      The interview process was really exciting. I was referred by my friend who works for Amazon. After 1 week or 10 days of referral, I got an invite for the Phone screen interview which was done on Amazon Chime, Audio call. After I passed the Phone screening I moved to the next phase -the Amazon loop interview where there were 5 interviews in one day. All the people who took my interview were really nice and made me feel comfortable. 5 interviews in a day with around 7 people (including people who just observe) can be really hectic and difficult but everyone made sure that I am relaxed and calm. 4 interviews were purely behavioural questions and everyone dug deep into my experiences. Don't try to make up stories that you will not be able to explain in detail. 1 Round was technical where I was tested on my technical basics. Everything was done over Amazon Chime because of COVID.

      Sollicitatievragen [1]

      Vraag 1

      Phone screening: NoSQL vs SQL Interface vs abstract classes - pure OOP Why serverless? Microservices communication patterns / designs Design example for securing webapps How can application be scaled? Database scaling - sharding How to debug microservices? When would you use NoSQL How to improve indexes? When was the last time you apologiesed to someone? How did you force a change by asking questions
      Vraag beantwoorden
      7
      Geen aanbod
      Negatieve ervaring
      Eenvoudig sollicitatiegesprek

      Sollicitatie

      Ik heb online gesolliciteerd. De procedure duurde 7 weken. Ik heb gesolliciteerd bij Amazon (Dublin, Dublin) in nov 2025

      Sollicitatiegesprek

      The process took around over two months. First I had an HR email round, yes an email round, the HR at Amazon are the worst I have ever seen in my life. Then there was a technical screen call, a video call on their Amazon Chime software that crashes every few seconds. lolx. Then there was this SUPER day (They still believe in Ancient ways) 5 interviews all in one day, but i requested to split in two different days. As I have a life too BRO. After that an HR call to informe the final verdict, they insited on having a call rather than sharing the outcomes in an email. They requested to arrange a call for an update on my application on FRIDAY evening, and then had a 2 minutes call and kept me in worst situation you could ever be on Friday night. I have overall the WORST epxerience with AWS/Amazon.

      Sollicitatievragen [2]

      Vraag 1

      ****** A bad interviewer can RUIN your potential careera at a tech Giant. ***** - First Assessmet for System Design recomendations evaluations: - Then a second interview (tech screening interview. ) started with Role overview. My background. Coding test (find out the second smallest and second largest number in the given very large array). Discussion around the Software design approach where a transaction processing system is being built. How would you handle the load during events like christmas. What is event-driven-architecture ? How it could help in the scenario with the online shop software? How would you make sure that the catalog having only one item left to be ordered is ordered by one person, and at the same time not accept the same item's order from a differnt person (or same person again). Bascially updating and managing the state of the items in an ecomerece website. How would you avoid having a single point of failure? Then, discussion went into the adding Queuing capability into one of the services. What is high cohession? Why is low coupling helpful and how is that achieved? We further discussed the Microservices and containerised approach for architectural discussions. How the low cohesion helps in the microservices architecture ? What are the pros and cons of using Microservices architecture? How many ways the microservices may communicate with each other? Why would you choose a Micrososervices, vs VM deployment, vs the serverless? Why and when would you use the lambda functions? Authentication vs Authorisation? How can you make sure the least previlage principle? What is RBAC ? How it could be implemented? Have you heard of the SOLID principles? What dependecy inversion is ? What is inversion of control ? Should a class have only one responsibility as per SOLID principles, so what about the functions in a class ? What is TDD ? What SOLID principle adheres to unit testing? What is mocking ? What SOLID principle are advocating for mocking during unit testing ? Then interviewer asked me about the Databses that I worked, then he went onto asking question about documents based database, how the retrieval happens. then what if the hashing mechanism have duplicates (keys) ? Interviewed changed the gears and then moved on to the scenario based questions where they epxect you to answer a STAR based answers. Tell me a difficult situation during a project work ? Tell me a situation where you were unable to deliver ? Then interviewer gave me a chance to ask any question. I asked how does the team works and responsibilities of individual team members. Moreover, whats the next process? Any more techncial rounds ?
      Vraag beantwoorden

      Vraag 2

      Super day interviews: - System Design: Went through my resume, asked a couple of queries there, talked about RAG, what AI you worked on ? how did you use AI to carry out a project in your resume? Why did you not used AI if you didn't ? API management, what Clouds you worked on? chance to ask. REST API vs GraphQL ? API version management ? What are CDNs and how many do you know ? Followed by some leadership principles, and chance to ask. - Hiring Manager Interview: Best three leadership principles, worst leadership principle in your opinion. Why AWS ? What is your high and low moments of your carrier? Leadership principles: Speed vs Quality? chance to ask. - Tech Fit Interview: held with Tamara+Sara: tamara kept hereself behind curtain all the times and appeared in the last two minutes on the CHIME software. While Tamara was senior she let a Junior take the interview. The Interviewer Ms. Sara was Not the best communicator. The network lag was there in Amazn CHIME, the audio was distorted, I tried to connect using dial in via phone, over ther the audio was even worse. Had to skip a couple of questions due to the audio issues with Amazon chime software. This could have been improved over the years. Technical start, Cloud architecture, asked for examples on cloud native apps, give examples for microservices you worked with. WHat tech stack you choose, and why ? what visualisation did you choose, how did you decide among many options for the visualisation. Give a project example which is not Data pipeline specific, no ETL etc? Interviewer asked some other vague questions that needed to clarified, do clarify the context of the question. Followed by a coding test. again same second smallest and second largest number coding exercise. Last question whether I have worked on moderenisation? Give an example of system you built/designed without data pieplines? - Fourth Interview with Chiragh: Adoption to a current software you are working on, onbaording, Anything you did exceptional (going out of the way) that helped a client and your own employer? Example of a problem you faced and you step up to resolve it without being asked by management? tell me a time when you worked to resolve an issue? - Fifth interview with Mr. Olu: (he was the only coolest interviewer at Amazon TBH) Behavioural questions with minor level details. Focused on leadership principles including Bias for Action. Tell me about a time you had to dive deep into data to solve a problem. Give me an example where you have to take a risky action without consulting others ? Give me an example of time when you went out of the way and did something that helped your team? Example where you went above and beyound for customer?
      Vraag beantwoorden

      Sollicitatiegesprek voor de functie Cloud Applications Architect

      11 jul 2022
      Kandidaat voor anonieme sollicitatie
      Singapore
      Geen aanbod
      Negatieve ervaring
      Gemiddeld sollicitatiegesprek

      Sollicitatie

      Ik heb via een recruiter gesolliciteerd. De procedure duurde 3 weken. Ik heb gesolliciteerd bij Amazon (Singapore) in mei 2022

      Sollicitatiegesprek

      1. Phone screen call with TA. 2. Phone Call with another Recuriter 3. At home assignment, architect cloud solution for a problem statemnt 3. Video call with an architect to walk through your solution

      Sollicitatievragen [1]

      Vraag 1

      Walk through your architecture solution and choices
      Vraag beantwoorden

      Sollicitatiegesprek voor de functie Cloud Applications Architect

      3 jul 2021
      Anonieme werknemer
      Aanbod geaccepteerd
      Positieve ervaring
      Moeilijk sollicitatiegesprek

      Sollicitatie

      Ik heb via een werknemersdoorverwijzing gesolliciteerd. De procedure duurde 4 weken. Ik heb gesolliciteerd bij Amazon

      Sollicitatiegesprek

      Phone screening followed by rigorous day long interviews, comprising 5 hour-long interviews with one break in between. One of the 5 interviews was technical. The remaining focused on some Leadership Principle or another, but the interviewer would not reveal which Leadership Principle they have been assigned,

      Sollicitatievragen [1]

      Vraag 1

      Leadership Principles as indicated by the recruiter during the preparation phase
      1 Antwoord
      1