I had the opportunity to work here after I graduated college and learned a lot working with cloud-based infrastructure.
New management came in and changed up a lot of things. Turnovers were often. They came in and changed the organization of my team. They started to assign work that I had never worked with before because I work on cloud. After a number of layoffs, I finally got kicked.
They were moving away from public cloud and were in the process of building out their private cloud. They invested so heavily in a specific public cloud provider, but it just seems like they want out now. Tons of applications were still hosted in the cloud environment around the time I got let go. It seemed like my role became irrelevant (along with a few others, old-heads who knew Geico infrastructure inside out).
Stop changing out CTOs every week and have some sort of plan to support employees on new technologies if you want it to be pushed so bad.
Initial contact was with a recruiter. This led to a one-hour meet and greet. After the meet and greet is a four-hour "Power Day," which consists of four rounds of interviews.
Contacted by recruiter after about 1 month. Scheduled the same day I had a call with the recruiter to talk to the manager and another Sr. engineer. (Flag 1: recruiter hated life and mentioned recent RTO directive; flag 2: desperate to have the inter
Questionnaire, followed by OA (1 easy LC), followed by a 1.5-hour interview (1 hour coding, 30 minutes behavioral). Aced all the coding well ahead of time and efficiently, but the behavioral interviewer asked extremely specific questions about techno
Initial contact was with a recruiter. This led to a one-hour meet and greet. After the meet and greet is a four-hour "Power Day," which consists of four rounds of interviews.
Contacted by recruiter after about 1 month. Scheduled the same day I had a call with the recruiter to talk to the manager and another Sr. engineer. (Flag 1: recruiter hated life and mentioned recent RTO directive; flag 2: desperate to have the inter
Questionnaire, followed by OA (1 easy LC), followed by a 1.5-hour interview (1 hour coding, 30 minutes behavioral). Aced all the coding well ahead of time and efficiently, but the behavioral interviewer asked extremely specific questions about techno