Technical Enterprise Account Manager, PaymentsCustomer ServiceRejectedDifficulty 3/5
Fast, well-run process: about two weeks from application to decision, with a reply after every round. A recruiter screen was followed by a 45-minute screen with the hiring manager from Solutions Engineering. The second round went deep on payments: what makes a card-not-present web payment succeed, how to test a payments API, and how to troubleshoot with a customer whose payments are failing. The rest was customer partnership and situational questions about customer use cases. The rejection came with a real reason, which I appreciated: they wanted more depth in payments knowledge and customer partnerships.
Asked: What makes a cardless (web / card-not-present) payment successful, from authorization through settlement?
Sr Solutions ArchitectEngineeringOfferDifficulty 3/5
The path here wasn't a straight line. I originally interviewed for a Principal Solutions Engineer role, and I put a lot into the process: a technical case study, a presentation to leadership, and more mock interviews than I can count. In the end, the team felt that role was scoped a bit more senior than where I was, but they also saw where my background could make a real impact and opened a different role for me.
Specialist, SeasonalCustomer ServiceOfferDifficulty 4/5
First interview was a group interview at an apple store. We were broken up into teams of 4 and answered 4 questions by two different apple employees. Straight forward questions (ex. Tell me about a time....). Made it to the second round did another group interview virtually with one other candidate and 2 Apple representatives. Similar questions but more in depth ( ex. What made you choose apple/ why apple).
