Capital One reviews

Interviewee TLDR: * Know what tech stack your team is working on. Ensure it's what they're actually using/maintaining, rather than roadmaps. Will you be happy if you're maintaining that? * (If you value in-office) Know *where* your peers are. --- I was hired for a "Backend Software Engineer" position, 100% of which just say you need experience in 'Java, Python, Go, or similar'. Despite making it very clear I have 0, 10, and 1 years experience in those languages (respectively), I was put onto a team that managed a Java application where they were maybe moving to Go. Instead of being able to work at a senior level, instead I'm just learning Java (the easy part), the Java ecosystem of packages/libraries/tooling (a bit harder), and trying to read and understand the application which was developed over years, some by contractors/interns (this is where experience in a language is actually useful). I was eventually driven out for, among other things, that I wasn't providing "PA-level contributions" to a language I just started using 5 months ago. The worst part for me was that I never worked with anyone in the physical space. COF has several floors in a Chicago Loop building, but none of my peers worked there. I started remote, but then they had a return-to-office initiative several months ago, which was a cruel joke for me as I would go in, and work alone, surrounded by people. Internal tooling has a bit of a learning curve. The documentation for it is 50-50 good or out-of-date and thus misleading. The internal GitHub is pretty open, plus Slack, so you can usually find examples. In the past few years there were many announcements of so and so VP coming in from Amazon, so I think they're buying-in whole heartedly to that, for better or worse.