• 4/24: Automated email rejection after applying for Staff Full Stack Engineer (Frontend).

• 8/24: Applied again and received an automated email rejection after applying for Staff Full Stack Engineer (Frontend).

• 6/25: A recruiter reached out via email with the subject line "Staff SWE, Company Onboarding Team @ Rippling (SF & NYC)". I responded to the recruiter but received no response. I followed up a few days later with no response. I was ghosted.

• 7/25: A different recruiter reached out on LinkedIn with the subject line "Staff Engineering Opportunities at Rippling". I responded. Strangely, there was no calendar link, platform, or scheduling assistant. Instead, we exchanged messages on LinkedIn to agree on a call time. I proceeded with the call. The recruiter was pleasant and happy to provide information. She then coordinated the scheduling of a technical interview.

• 7/25: Technical Interview. This involved a Zoom call with an interviewer who was an engineering manager from a different team than the role would fall under. Out of the gate, I don't think that's good at all. Ideally, the interviewer would represent the team's interest for a fit.

This interview involved live coding a challenge using React. The first oddity was how a Staff level role would be expected to utilize JavaScript, when in this era (and for a while now), TypeScript is the standard and provides a better understanding of real-world programming. The interviewer did not understand what a schema is. At the beginning of the live coding test, as I read through the code that needed to be populated, I was admittedly very thrown off by the incorrect terminology usage (for example, "schema" was actually intended to be a value in the challenge).

The interviewer was rude and exhibited a lack of experience in React, fundamental JavaScript, and people skills. I don't think the interviewer's level is that crucial, however, the rudeness is simply unacceptable and reflects poorly on Rippling as an organization.