Capital One

• Friendly people and some brilliant engineers to work with. • Financially stable through these tough times. • Decent benefits and learning resources.

For any small piece of work, there's twice as much process. You want to refactor a screen? Speak to 10 different people, and you might be able to do it in 1-3 months' time. This means that, as an engineer, you stagnate the moment you join the company, especially for senior engineers.

Even when work gets done, it's usually very basic. No boundaries are pushed, and generally, it's difficult to be proud of anything you build.

The processes, despite costing a lot in terms of time, are simply ineffective. The tools used to support these processes are often buggy and completely block work for days and even weeks sometimes.

Mobile engineers rarely work on mobile. Their time is spent between service work in Java, infrastructure work on AWS, AMI refreshes, debugging buggy pipelines and services, creating change requests, attending community of practice meetings, and team/tribe ceremonies.

Lastly, managers' responsibilities are stretched, meaning they can't enact much change. Senior managers seem to be under-stressed and generally are a hindrance rather than helping with anything.

The only people who understand mobile are the mobile engineers. Most other people, from QEs and product to managers and above, have no experience with mobile. This leads to lots of confusion, unnecessary questions, and generally a lack of clear direction.

Change some of the senior managers and try to create a mobile-engineer-first culture within Mobile.