Front End Developer · 1 year-2 years years
3
Arun claims 6 years of experience and familiarity with React, Redux, React Query, JWT auth, Tailwind, and React performance hooks, but provided extremely thin, often incoherent answers across every probe. Responses were typically one or two fragmented words echoing the interviewer's terminology back, with no concrete project details, no architectural reasoning, and no operational specifics. Language fluency issues are evident, but even accounting for that, the technical substance is absent. Combined with very long pauses on basic questions, this interview does not demonstrate even junior-level front-end competence, let alone 6 years.
“User Management”
Two-word answer to a direct question about what data lived in Redux slices — no detail despite multiple follow-up probes.
“Interceptor”
One-word echo of the interviewer's term when asked to describe interceptor logic; subsequent attempt (320.6s) pivoted to an unrelated signup description.
Hello
Am I audible?
Yeah, coming through clearly! Good to go. So, Arun — thanks for making time today. I'm going to be chatting with you about some front-end stuff, mostly HTML, CSS, JavaScript. Pretty conversational, no tricks. Just want to get a sense of how you think and what you've built. To kick things off — what have you been working on lately? Like what's the last interesting front-end problem you had to solve?
During my project, I worked on internship recently.
Doing my project, I work on workings, front end part with React. I made some hooks and React, I use some React libraries.
Like Redux, React Query, U Form Validation, Gestalt.
And I also working.
on HTML, CSN and JavaScript.
Yeah, nice — sounds like a pretty full stack of front-end tooling. React with Redux and React Query together is interesting, those two can overlap a bit in terms of what they manage. So tell me — in that project, how did you decide what state went into Redux versus what you just let React Query handle? Like where did you draw that line?
Uh, in direct query, I In React Query, I worked on While React Query I worked.
cough
I worked on
Handling the routing with React Query and Use API.
Use API.
Books With post, put, and get APIs.
Got it, yeah — so React Query for the API calls, the server state side of things. That makes sense. What about Redux then — what were you actually storing in Redux in that project? Like what kind of data lived there?
Redux I use Redux toolkit.
Right,
In which it provides various functionalities, state management.
and server management.
Yeah, Redux Toolkit is pretty handy. But I'm curious about your specific project — what data were you actually keeping in the Redux store? Like was it user auth info, UI state, something else? What did your slices look like?
User Management
Ok, so user management — like the logged-in user's info, permissions, that kind of thing? What happened when the user's session expired — how did you handle that on the front end?
Through JWT Session expired JWT JSON web token.
It provides a token.
That way that user will not log in again and again.
Right, yeah, JWT is pretty standard for that. But I'm curious about the expiry handling specifically — like when the token actually expired mid-session, what did your app do? Did you have a refresh token flow, or did you just redirect the user to login?
No, it generate a token.
Through this token, user will log in again.
Read I am automatically Go with the lighter.
Sorry, I didn't quite catch that last part — can you say that again? Did you mean the token was automatically refreshed, or the user was redirected to login?
No, automatically refresh.
Got it, so you had an auto-refresh flow. How did you actually implement that — like was there an interceptor in Axios or something that caught the 401 and triggered the refresh?
Interceptor
Yeah, Axios interceptors are the go-to for that. Walk me through what that interceptor actually looked like — like what was the logic inside it when it caught a 401?
See, first time user will log in with ID sign up with ID and Email and create password and then sign in again. It sign in again. Then it will generate a token.
Session token.
And then it store Chrome will store it and then user will come.
On that website, it will log in automatically.
Right, so the token was stored — was that in localStorage, sessionStorage, or cookies?
Cookies.
Ok, cookies. And when the token expired, the interceptor would catch the 401 and then what — it'd call a refresh endpoint to get a new token?
Yes Yes Yes
Ok cool. And what did you do if the refresh also failed — like if the refresh token was expired too? Did you just boot the user to the login page?
Yeah, user will log in again.
Fair enough, yeah that's the standard fallback. Ok let me shift gears a bit — you mentioned you worked on HTML and CSS too. So let's talk CSS for a second. In that project, how did you handle the layout and responsiveness? Like were you using a grid system, flexbox, something else?
No.
In my project workings In my project.
I think I made like structure.
Structure stable table CSS in one file and I use a In every In every part of my project.
Like table, table CSS.
In dashboard, I use that CSS in other pages also, like in dashboards, dashboard support pages.
visitor pages like that.
Got it, so you had a shared CSS file that you reused across different pages. That makes sense for consistency. Were you doing any
Yeah.
Were you doing any responsive design in that project — like did it need to work on mobile too, or was it mostly a desktop app?
Yeah, that is responsive for tablet.
And tab, laptop, and phone.
Ok, so all three breakpoints. How did you handle that — were you writing media queries yourself, or using something like Bootstrap or Tailwind for the responsive grid?
Tell when, tell when, I use tell when.
Sorry, I didn't catch that — did you say Tailwind?
Yes Yes I use Talvent CSS.
Ah, Tailwind! Yeah that makes responsiveness a lot easier with those built-in breakpoint prefixes like `sm:`, `md:`, `lg:` and so on. So when you were using Tailwind
Yes, yes.
When you were using Tailwind, did you ever run into a situation where the utility classes weren't enough and you had to write custom CSS? Like did you extend the Tailwind config at all?
Sorry
Can you repeat again?
Yeah sure — with Tailwind, did you ever need to write your own custom CSS, or did the built-in utility classes cover everything you needed?
No, I didn't write custom tailwind CSS.
Ok, so the default utilities covered everything. Fair enough. Let me ask you about JavaScript for a bit. In that React project, did you run into any performance issues — like components re-rendering too much or anything like that?
No, in my project, rerendering handle React. I use React.
Right, but did you ever use anything like `useMemo` or `useCallback` or `React.memo` to prevent unnecessary re-renders? Or was the app small enough that it wasn't really an issue?
Use memo, use callback.
I used callback.
Yeah, where did you actually use `useCallback` in your project — like what was the specific situation where you needed it?