interviewing at Amex in about 3 weeks for a senior software engineering role. the job req is on the enterprise payments platform side. trying to build a real picture of the current loop structure before i go in.
if you've been through an Amex interview loop in the last 6-12 months, would appreciate: role type and level number of rounds any technical format specifics (was there a take-home? live coding? system design?) behavioral themes that came up repeatedly
even 'i declined / didn't get it' reports are useful. i want the actual signal not the polished version.
4 replies
backend_bekah
went through the SWE loop about 5 months ago, senior level. 4 rounds after the recruiter screen: (1) hiring manager behavioral, (2) system design with two engineers, (3) coding round, (4) 'values and leadership' with a director. no take-home. coding round was on coderpad, they gave me two problems, medium difficulty. the system design was pretty open-ended, they gave me a payments scenario and let me drive. i didn't get the offer but the feedback was that my behavioral answers were too 'team we' and not enough first-person action. useful feedback at least.
contractor_kai
that first-person thing is a note i see consistently for amex. their interviewers are trained to probe for individual contribution. i'll be more deliberate about that. thanks.
staff_steph
staff-level loop two months ago, different team (internal developer platform). it was heavier on the leadership and influence questions than i expected even for a senior IC. 'tell me about a time you changed direction on something major and how you brought people along' came up in two separate rounds. i think they're really trying to assess whether you can operate in a matrix without authority. which is basically half the job at a company that size.
sec_sasha
applied for an AppSec role, got to the panel stage then withdrew. the loop for security was: recruiter, HM, two technical rounds, and a values round. technical rounds had both a threat-modeling exercise and a 'how would you secure this API' design question. nothing too surprising for AppSec. withdrew because the comp was lower than i wanted and they weren't willing to move much.