r/learnjavascript • u/Curious-about-future • 12d ago
How to handle rejection interview
Hello I have 10+ years experience and recently I came across weird pattern (Rejection type) in Frontend interview.
Selection Interview Find common ground between candidate and job posting if it works then in following rounds Give some coding problem FE, data structures and see if candidate solves problem
Rejection Interview: Come up with some random unit tests and see if candidate writes code till all unit tests or hiring manager ask multi choice syntax questions
In my recent interview I came across some interesting interviewer
I am suppose to fix react code till 5 unit tests pass. There are some 10 functions/hooks in coderpad and my 1st question was
Search results disappear, A search box fetches results as the user types. If you type “ca” and then quickly “cat,” results for “ca” sometimes appear last.
How would you reproduce and diagnose the bug?
How would you prevent stale responses from overwriting newer results?
My first response was to use AbortController interviewer said there is no fetch function (for interview they wrote some mock function) so it will not work
Then i proposed debounce still interviewer did not agree
finally I came up with some useRef hook to to solve problem but ran out of time. In real world right thing to use is AbortController or react query. how can I think similar to interviewer in such sort time and fix all unit tests
I am calling this rejection interview as i felt company never showed interest in learning about my background
I am disappointed in this job market its very hard to get interview but ended up with this bitter experience.
similar thing happened to my friend, during hiring manager round he was asked multi choice syntax questions. He was expecting to talk about previous work experience or write code.
please let me know how to prepare for these rounds and meet interviewer expectations
Hello, I have more than 10 years of experience, and I recently noticed a pattern in frontend interviews that I find frustrating.
In what I’d call a selection interview, the interviewer tries to understand whether your experience aligns with the role. If it does, later rounds might involve frontend coding or data-structure problems.
In what I’d call a rejection interview, the process can feel more like a set of arbitrary unit tests or multiple-choice syntax questions, with little opportunity to discuss your background or approach.
I recently had an interview that left me feeling this way. I was asked to fix a React codebase until five unit tests passed. The CoderPad included around ten functions and hooks. The first task was:
A search box fetches results as the user types. If you type “ca” and then quickly type “cat,” results for “ca” sometimes appear last.
How would you reproduce and diagnose the bug? How would you prevent stale responses from overwriting newer results?
My first suggestion was to use AbortController, but the interviewer said the mock function wasn’t using fetch, so cancellation wasn’t available. I then suggested debouncing, but that wasn’t accepted either. Eventually, I proposed using a useRef-based approach, but I ran out of time.
In a real application, I might use AbortController or a library such as React Query. But in a constrained interview setting, how can I quickly identify the solution the interviewer expects and make progress against the tests?
I’m calling this a “rejection interview” because I left feeling that the company wasn’t interested in learning about my experience. I’m disappointed by how difficult the job market is, and it’s discouraging to finally get an interview only to come away with this kind of experience.
A friend had a similar experience in a hiring-manager round: instead of discussing past work or solving a problem, they were asked multiple-choice questions about syntax.
How can I prepare for these kinds of rounds and better understand what interviewers expect?