Comp, remote first, and meeting to heads down time were great.
Volatile roadmap, lack of consistent product direction, lack of continued ownership amongst engineers made the once a month on-call rotations brutal. For a startup that wanted to act small, leadership’s ears still felt miles away.
The work-life balance was not great. Big bet new logos continuously outweighed the overwhelming customer needs for better UX.
Recruiter call, then a C++-specific interview where I was asked about class constructors and move semantics, then a coding interview. I was told by the recruiter that all interviews would be in C++ so that was fine... except the coding interview req
I started interviewing for a senior role which got filled after 2 interview rounds - 1 with HM and 1 C++ round. Then I was asked if I'd be interested to interview for a software engineer role. Then I had another C++ round, HM round and a take home as
Started with an initial HR interview, then with the hiring manager who went over the job and asked basic questions. Then two technical interviews on C++. Not LeetCode related, mostly basic things about C++ and if I could make an LRU. There was a c
Recruiter call, then a C++-specific interview where I was asked about class constructors and move semantics, then a coding interview. I was told by the recruiter that all interviews would be in C++ so that was fine... except the coding interview req
I started interviewing for a senior role which got filled after 2 interview rounds - 1 with HM and 1 C++ round. Then I was asked if I'd be interested to interview for a software engineer role. Then I had another C++ round, HM round and a take home as
Started with an initial HR interview, then with the hiring manager who went over the job and asked basic questions. Then two technical interviews on C++. Not LeetCode related, mostly basic things about C++ and if I could make an LRU. There was a c