Developer experience: surprisingly good for a buttoned-up company. I didn't get stuck awaiting Windows admin for VS Code, Windows Subsystem for Linux, Docker, Python, Node.js, Git, or GitHub Enterprise.
Good pay.
Learning opportunities (infra/systems at scale).
Every meeting is a production (like a TV show), and you are expected to look good on camera.
Every project and team is a stylized codename that doesn't actually explain the thing.
There are a lot of vague, disparate docs on Confluence, and view permissions were strict.
If your boss says, "Automate yourself out of a job" and "Don't work too hard," don't share your solutions, or you will indeed automate yourself out.
I landed on a weird team that was suspiciously young and diverse, so your mileage may vary...
Foster an open culture, not a guild culture. Else, impact is driven by a social game and not engineering.
Completely practical and friendly team. Scenario-based questions on AWS and DevOps. Based on CloudFront, S3, Kubernetes, Docker, and various AWS services; static web hosting; Virtual Private Cloud; and scripting, etc.
First, there was an initial recruiter screening. Then, there was an in-person logical interview focused on Java to see if you understood the concepts of Java and OOP. Next, there was a technical interview with LeetCode-style questions.
Mostly behavioral, with less of a technical focus. The interviewer was interested in hearing about my prior experiences. I prepared Leetcode questions but wasn't asked anything like that. This role was specifically Golang microservices, so they asked
Completely practical and friendly team. Scenario-based questions on AWS and DevOps. Based on CloudFront, S3, Kubernetes, Docker, and various AWS services; static web hosting; Virtual Private Cloud; and scripting, etc.
First, there was an initial recruiter screening. Then, there was an in-person logical interview focused on Java to see if you understood the concepts of Java and OOP. Next, there was a technical interview with LeetCode-style questions.
Mostly behavioral, with less of a technical focus. The interviewer was interested in hearing about my prior experiences. I prepared Leetcode questions but wasn't asked anything like that. This role was specifically Golang microservices, so they asked