Ideas for change and improvement often come from individual contributors as opposed to management.
Switching teams is relatively easy.
C-levels are very approachable.
The hiring bar is really high, and other engineers come from successful backgrounds.
We just hired a VP of Engineering that's going to change/fix a lot of the organizational issues and restructure the org.
Career advancement and review cycles are still being fully ironed out. The product has a ton of area as it's really wide, and it gets progressively harder to understand everything.
LeetCode questions typical for an SWE1 interview level. Study from NeetCode to help. Questions are on a case-by-case basis. Hope this helps you in your interview process. These are very reasonable questions.
I went through the standard "apply through LinkedIn" route and had a phone call with the recruiter. Ten minutes after a seemingly good interview (I solved the problem and believe I did a good job), I received a rejection letter. I emailed the recruit
The interview process began with a chat with HR, followed by a first-round interview that included a coding challenge. The final round was a virtual onsite composed of four interviews. * The first interview was a deep dive into one of my projects,
LeetCode questions typical for an SWE1 interview level. Study from NeetCode to help. Questions are on a case-by-case basis. Hope this helps you in your interview process. These are very reasonable questions.
I went through the standard "apply through LinkedIn" route and had a phone call with the recruiter. Ten minutes after a seemingly good interview (I solved the problem and believe I did a good job), I received a rejection letter. I emailed the recruit
The interview process began with a chat with HR, followed by a first-round interview that included a coding challenge. The final round was a virtual onsite composed of four interviews. * The first interview was a deep dive into one of my projects,