Got noticed by a recruiter on LinkedIn, had a chat, and a phone call to understand more. Scheduled a follow-up virtual interview.
Virtual Interview:
Behavioral Question: Give an example of something you did beyond your job responsibilities.
Algorithm Question: Given a table that records requests made by various URLs in a site. Write a function to check if two URLs (a_url, b_url) can be connected from a_url to b_url. Used BFS algorithm.
During discussions, found out the VO did not include system design, and it’s for an L4 position. Asked if it’s possible to interview for L5, or if performing well, can be considered for system design, but received no response, so proceeded directly.
VO:
- Interviewer was a guy.
Behavioral Question: - Dealing with conflicts with teammates.
- When assigned a task realizing there’s a lot to learn, needing more knowledge.
Algorithm Question: Design a component to render the time passed since a post date in real-time updates (e.g., just now, xx seconds ago, xx minutes ago, xx months ago, xx years ago). Also, discussed handling multiple components on a page efficiently.
A manager:
Behavioral Question:
- Needing more knowledge to complete a project (similar to the second BQ in the first round).
- Dealing with a serious mistake that may lead to missing a deadline.
Algorithm Question: Managing multiple 2D tables, tracking the sum of each row and column. Changing an element in one table should update the corresponding row and column sums. Discussed optimization for large tables using multiple hosts.
A serious girl with few words:
Behavioral Question: Related to deadline issues (details forgotten).
Algorithm Question: Develop a complete page with an API to request a set of photos from the backend with sorting methods and pagination. UI design includes a dropdown menu for sorting, grouping photos with titles based on location or time, and navigation buttons.
A guy always smiling:
Behavioral Question:
- Balancing completing a task quickly with quality when facing tight deadlines.
- Taking initiative to prevent a negative event from happening.
Algorithm Question: Faced the original interview question, designed a frontend calculator component without changing the algorithm much, considering corner cases like unequal parentheses and consecutive operators. Discussed frontend OOD and ended with vanilla JS for UI.
Received a verbal offer.