I recently finished an unusual interview process: 1 HM + 5 final rounds for an AWS Solutions Architect role, followed by 2 more rounds with a different team after the first didn’t work out. Eight interviews. No offer at the end.
This is the honest version of what happened, what I got wrong, and what I’d tell anyone considering the same path.
The Setup
I was a co-founder and Tech Partner at a cross-border payment startup for three years. We built a PCI DSS compliant platform from scratch, ran it with three years of zero downtime, and served real merchant customers. My background before that was at a large Chinese internet company doing infrastructure work — Kubernetes migrations, framework adoption across many teams. Before that, ten years of engineering work with a self-taught path from a linguistics undergraduate degree.
On paper, I had the technical chops for SA work. What I didn’t have was direct experience as a customer-facing Solutions Architect at a hyperscaler. That gap turned out to matter more than I expected.
The First Standard Loop: 1 + 5
The phone screen went well. The Online Assessment passed. Then came five back-to-back rounds across three days with sales people, a hiring manager, a peer SA (with a 30-minute architecture presentation), and a Bar Raiser.
I prepared obsessively. Twelve full STAR stories. Eight backup stories. A six-slide presentation on a real migration I’d led. Mock rounds. Recorded practice in Mandarin. A cheat sheet with one-line headlines I could glance at during the actual interviews.
Four of the five rounds went well. The hiring manager actively liked me. The Bar Raiser had what I felt was a strong conversation. The peer SA appreciated my deep technical examples. The second sales round landed.
The first round — with a sales manager early in the day — was the one that hurt. He probed my motivation hard. Why leave a startup? Why AWS? Don’t you think your experience doesn’t match an SA role? Do you have certifications? I gave him what I thought were reasonable answers, but I could tell he wasn’t convinced. He never asked me to share a story. He just kept testing my conviction.
After the loop, the recruiter called: Yes, you passed. But they’d selected another candidate with stronger industry-match experience. Several interviewers had liked me, but it wasn’t enough.
The Second Loop: 2 Rounds with a Different Team
The recruiter offered to forward me to another SA team — a different industry focus, just two rounds, fast-tracked. I’d already cleared the bar in the first loop, so they trusted that signal and only wanted to verify team fit.
I prepared again. Sharper motivation framing this time, because the recruiter had subtly hinted that motivation was the specific gap in my first loop debrief. New stories tuned to the new industry. Another two interviews were delivered as well as I could.
Same outcome. Different team, similar concern, no offer.
One month of work. Eight rounds. Zero offers.
What I Got Wrong
I underweighted the motivation question.
I treated it as something to address with a clever framing. “I want scale of impact.” It sounded reasonable to me. To an experienced sales person interviewing a co-founder for an IC role, it sounded like a textbook answer. He wanted conviction. I gave him reasoning.
Senior salespeople aren’t testing your logic. They’re testing whether you’ll still be excited in 18 months when the customer is being difficult, and the deal is slipping. Abstract reasons don’t survive that test. Specific, lived conviction does.
I learned later — too late — that the strongest motivation answer would have been: “I already stepped down from my company. I spent months reflecting on what I want next. I’m not exploring options anymore. I made the decision.” That kind of answer survives skepticism because the conviction is already in motion, not in the future tense.
I confused “cleared the bar” with “got the offer.”
Both times, multiple interviewers genuinely liked me. The hiring manager in the first loop actively advocated for me in the debrief. The Bar Raiser endorsed me. The recruiter forwarded me to a second team, which only happens for candidates rated above the bar.
But hiring decisions in competitive markets aren’t binary. When two candidates both clear the bar, industry-match becomes the tiebreaker. I lost both times to candidates with more direct experience in the specific customer industries those teams served.
This is the part that’s hard to accept emotionally but important to understand strategically: cleared the bar is necessary but not sufficient. If the role serves a specific vertical, you need to be either the best general candidate or the best vertical-match candidate. Being second on both axes loses to being first on one.
I optimized for breadth when I needed depth.
My story bank covered all sixteen Leadership Principles with two or three options each. I could pivot stories mid-round if I’d already used one. I was prepared for any LP question.
What I should have prepared more for was the industry context. When the peer SA in the final round mentioned PCI DSS hardware key management requirements, I defended my KMS-based approach by pointing to three years of clean audits. That was technically true, but not the answer he was probing for. A more senior answer would have engaged with the nuance: acknowledged the trade-off, explained the specific controls we implemented, and treated his expertise as input rather than a challenge.
I had architectural depth. I didn’t have enough domain-specific depth to navigate those moments with grace.
What I’d Tell Someone Going Through This
Prepare your motivation story like it’s a load-bearing wall.
It is. Sales people in particular will test it from multiple angles. Generic answers (“scale of impact,” “want to learn,” “love AWS”) fail with experienced interviewers. The strongest motivation answer is grounded in specific, recent action — what you’ve already done, not what you plan to do.
If you can honestly say, “I already left, I already reflected, I already chose” — that’s the strongest possible answer. If you can’t, find the most concrete equivalent.
Industry match is real and often decisive.
If you’re switching from one industry vertical to another, expect the bar to be higher. You’re competing against candidates whose entire backstory points to this specific role. Your transferable skills argument needs to be sharper than theirs. You also need to research the team’s customer base specifically — not just AWS broadly.
Insider information matters.
In my first loop, the hiring manager subtly disclosed which interviewer was the Bar Raiser and which were sales people. That changed my strategy in real time. In my second loop, the recruiter hinted at the specific motivation gap from my first debrief. Both pieces of intel materially helped my prep.
Build relationships during the process. Treat the recruiter as a coach, not just a coordinator. Ask thoughtful questions in each round. The information advantage isn’t unfair — it’s part of how senior candidates navigate hiring processes.
Have a parallel path.
I kept other opportunities active throughout the AWS process. After the second rejection, exhausted and disappointed, I had three rounds with a payment industry company — no prep, just showed up. They made me a verbal offer. The role isn’t my first choice, and the compensation ceiling is lower than the AWS opportunity would have been, but it’s a real offer with strategic value (direct integration with a major card network).
If I had bet everything on AWS, the emotional crash would have been much harder. The parallel path turned out to also be the smart path — building deeper payment industry depth is probably exactly what would close the gap that AWS flagged twice.
What I Don’t Regret
Didn’t get me an AWS offer, but it did sharpen skills I’ll use forever: distilling experiences into clear stories, navigating high-stakes conversations, presenting architecture trade-offs to non-technical audiences, and handling tough motivation questions without flinching.
The interviewers I met were thoughtful professionals. The process, while exhausting, was fair. The feedback — even the painful parts — was useful.
I’d do it again. Probably differently, but I’d do it again.
If you’re heading into an AWS SA loop, here’s the one thing I wish someone had told me earlier: the people interviewing you are trying to figure out if they want to spend three years working with you. They’re not just checking boxes. They’re imagining showing up at a customer site with you. Your job isn’t to prove you can do the work — they already think you can if you got the loop. Your job is to convince them that working with you would make their job better.
That’s a higher bar than I prepared for. Now I know.
But sometimes, you need some luck and a stroke of fate.