**Pros:** - Solid brand name on the resume for fintech/tech banking space. - The interview process is structured (if you like predictability). CodeSignal upfront weeds out some people early. - Benefits package is decent once you're in (though you have to get in first). - Some teams reportedly have good WLB compared to pure tech FAANG grind. **Cons:** - Inconsistent, borderline gaslighting feedback from recruiters. - Seems like they're running interviews for show or internal metrics rather than actual hiring intent. - Arbitrary bar movement and no transparency on calibration. **Interview Experience (Negative, Difficult)** Applied in May 2025 for Senior Lead Software Engineer. Process started with CodeSignal (4 LeetCode-style problems, easy to hard mix)—passed comfortably. Then "Power Day": System Design, Technical Coding (live), Case Study (business-oriented), Behavioral. Did solid overall but had one weaker moment in System Design. Recruiter called next day: passed everything except Sys Design (below bar), offered downgrade to regular Lead Software Engineer or wait 6 months to reapply for Senior Lead. Took the wait option since my current role was already Lead-level equivalent—no point in lateral move. Fast forward to Jan 15, 2026—reapplied and re-interviewed. Literally almost identical questions (Sys Design had a tiny tweak, but same core problem). I came hyper-prepared: refined my previous answers with better trade-offs, scalability examples, edge cases, and optimizations. Coding round: wrote clean, optimal, end-to-end working code (better than last time), discussed further improvements with interviewer, felt strong positive vibes—interviewer seemed genuinely engaged and impressed (10+ years of interviewing experience, I can usually read the room). Case, Behavioral, Sys Design all felt strong/pass. Recruiter called to reject: "Passed bar on Sys Design, Case, Behavioral—but below par on technical coding." That feedback felt completely fabricated. My solution was optimal, ran correctly, and we had good back-and-forth. No notes on bugs, efficiency, or style issues mentioned. They didn't even offer the downgrade this time—just straight reject. Feels like the outcome was predetermined. Either headcount froze, or they're doing mass interviews for some compliance/paperwork/calibration exercise without intent to hire. The flip-flopping feedback (Sys Design bad last time, coding bad this time—despite improvement) is ridiculous and disrespectful. Wasted two full cycles, prepped intensely both times, only to get nonsense reasons. If you're senior/staff+ level and they reach out, proceed with extreme caution. The process looks polished on paper (CodeSignal → Power Day), but the decision-making seems arbitrary and opaque. Plenty of other fintechs/companies respect candidate time better. Would not recommend interviewing here unless you're desperate or just want practice. 1 star purely because the structure exists—execution is poor.

My interview experience lined up with the other reports on here. After a recruiter screen to confirm a little bit about my background, I did a CodeSignal assessment. I did the first two questions pretty quickly. Then I looked at the third and fourth and decided that I was better prepared for the third one. So I did that and had a few minutes to spare. I tried to do the fourth one, but I ran out of time. The recruiter let me know I passed and then signed me up for a power day. I requested a couple weeks to prepare, since system design interviews especially were new to me. I used hellointerview and prepfully to prepare; those helped a ton. The day of the interviews was fine. The interviewers were friendly and engaging. The behavioral and coding rounds were straightforward. Both the CodeSignal assessment and coding round were familiar from my practice of Capital One questions on leetcode. For the system design, I made detailed non-functional requirements to go with the functional ones given to me. I didn't try to do any math about SLAs or anything like that though, and the interviewer didn't ask me to. I led the conversation since that is what expected at a senior lead level. The only one that seemed difficult was the case study interview, since it is unique to them and harder to prepare for. The question seemed bizarre, and a real-world case would need a lot more information. The instructions they give you ahead of time say not to worry too much about reality, though. The biggest advice I would give for this one is to type out your assumptions in the CodeSignal text field they give you. That will help you remember to do that and to be clear about what you are assuming about the data you are given. There may be some mental math involved -- there was for mine -- so practicing that wouldn't hurt, either. I would maybe ask an LLM to help you practice. There is a video on YouTube by Capital One about a retired case study for software engineers that they use as an example. I got feedback the day after my power day, saying that I passed and did very well. About a week later, I had a hiring manager call that went okay, but they weren't quite what I was looking for. Then it took about 2-3 weeks for another hiring manager to be interested. This one definitely wanted to hire me, specifically referencing how well I did in the power day interviews. That came up in the compensation discussion in the call with the recruiter as well, so I would definitely prepare as much as you can, since it's a massive ROI.