The job posting initially listed the role as remote (US).

The first phone screen with the hiring manager was essentially a full interview with extensive questions. At the end of the call, the hiring manager confirmed it was still a remote position.

Following this phone screen, a recruiter took over and rescheduled the next step three times. During this period, the position was changed to a hybrid role, requiring three in-person days per week. Amazon was willing to pay for relocation.

The recruiter seemed unaware of the position's specifics, asking only a few questions from a predetermined list. Despite their apparent lack of knowledge, they acted as if they were making a go/no-go decision and seemed to be on a power trip.

I proceeded to a third call, which was technically the "first interview" by their standards, again with the hiring manager. By this point, the position had changed again to fully onsite.

I opted not to move forward with further interviews because the role was advertised as remote when I applied. It appears Amazon is attempting to bring more employees back to the Seattle office, even though the hiring manager for this role did not work locally or in person.

The recruiter stated the salary for the role aligned with the job posting, but claimed that few candidates are paid at the higher end of the range, which was based on experience.

While the role itself was interesting, the "bait and switch" regarding the location was a significant deterrent. The interview process felt absurdly long, involving three meetings and dozens of emails, just to reach the official first interview.

Can you explain event-driven architectures?