Engineering Manager - Frontend Interview Experience - United States
Process
Recruiter screen.
HM interview with behavioral questions.
Manager interview with two managers.
Technical interview with two engineers, which was mostly FE fundamentals questions.
Take-home exercise: coding a table with a few rows of downloadable files and their details from a screenshot they provide.
Follow-up interview with two engineers where they ask what you would change about your design and how you'd implement filtering and sorting.
Culture interview with someone not in engineering.
Questions
What’s the difference between var, let, and const?
What’s bubbling and event delegation?
What are Promises? - How do you handle deeply nested promises?
What’s the diff between old and new functions?
What do bind, call, and apply do?
What is CSS specificity?
How do you manage z-index?
What is separation of concerns?
Do you prefer single file components or division by language (HTML, CSS, JS)?
What are the pros and cons of your favorite frontend framework?
What are some accessibility concerns?
What is XSS?
For the homework follow-up:
Do we want this component to be a generalized one?
When should we get the status of a file (available for download or not)?
How would you manage thousands of entries?
What if a user wanted to select all?
What if someone selected all then went to a page and just deselected a few?
Interview Statistics
The following metrics were computed from 1 interview experience for the CrowdStrike Engineering Manager - Frontend role in United States.
Success Rate
CrowdStrike's interview process for their Engineering Manager - Frontend roles in the United States is incredibly easy as the vast majority of engineers get an offer after going through it.
Experience Rating
Candidates reported having mixed feelings for CrowdStrike's Engineering Manager - Frontend interview process in United States.
CrowdStrike Interview Questions
