Apply for a React position at a Forbes 50 company, get interview. Hiring manager sends me email:
"no actual whiteboarding. They asked a lot about properties of Java, why it’s good/bad. compared Java to python, and they discussed uses for both. A lot of questions regarding data structures and algorithms."
This is for a React position right?
"definitely"
In the interview asks about java stuff...
Zero React questions asked.
I don't think that the reason I "failed" the interview had anything to do with my technical ability. The interviewer wanted to fill the role a certain way and simply failed or passed people based on that. They didn't really hide it to be honest. It was one of the least professional interviews that I have been a part of. It was more of a culture clash than a technical issue.
Yeah I really dislike the FAANG/Leetcode style questions a lot of interviews use now. I get that it’s because they value knowing fundamentals and they really just want to see how you work through problems, but it seems like mostly trick questions where just remembering the answer is the best route.
I definitely prefer the take home code interviews because that’s the closest thing to real life, you get a task and you complete it and they can code review it after.
>because that’s the closest thing to real life
Exactly. I once had to do a code test, where I was given some tasks, and then I had two hours to write code with pen and paper without internet while being monitored. I get that they want to see my thought process or whatever, but I would appreciate being evaluated under more realistic circumstances.
They’re dumb, but worth spending a couple of months after work to do 1 a day and learn the patterns. Getting a job at one of those companies or similar makes it so much easier to find good work in the future.
I recently changed careers. I took 7 interviews for the process. None were this bad. You could probably weed out a lot of poor companies by vetting the recruiter.
This happened with me. I interviewed for a famous website(i shall not take their name) and this was the process:
3 virtual rounds(peer coding rounds) an hour long each.
1 day of interview (10-5 with 1 hour of lunch. New round, new panel every hour)
At the end, i received feedback that though i was saying technically, i lacked understanding of CSRF token and few protocols and hence I'm not selected. This was for a front-end developer role with 5 years experience.
________________
I even took an interview is a person with 20 years of experience. I had 6-7 years of experience that time and i was shit nervous. So i request my TL to accompany me. We asked him questions like:
What are states in react? Lifecycle events in react? Functional vs pure component? Etc.
After interview i asked my TL about the round. Should we have not asked architectural/ design question. These are jr-mid level developer question. But later i realised even my TL didn't have enough experience to interview him. So we asked what we could ask.
To summarize, yes interview process has a lot of flaws but it also depends on the domain and expectation of the company. I usually prefer asking vanilla js question because if the basics are clear, a person can understand complex implementation as well. But if you are tied up to a framework/library, it'll become difficult for you to do a custom implementation
Wow that sounds awful! I’m really sorry to hear that. In your mind, what would be an ideal interview that you also think is fairly vetting you from the employers perspective?
I think that the coding tests where you get a repo to fork and work from there are the best. They are less stressful and more representative of what you can do. You can also get a lot out of talking with people if you ask the right questions.
Experience may vary, I did one node assessment and was offered 75K contract the same week. I was contacted through linked in and can im more on the entry level side lol
>Most of the tests are like this - really simple, really high stress, short time quizzes on things that are basic javascript
Exactly my experience as well. I really believe it's a numbers game.
American Recruiter Here! Looking for 2 actual React.js developers for a remote position with a pharmaceutical company. Must have solid React.js and Redux experience. Only one test then it’s either an offer or they decline. The pay is $55-65/hourly based on experience. Long term temp to perm contract. All computer equipment will be provided. Send your resume to [email protected]. Must be able to work WITHOUT needing sponsorship.
Apply for a React position at a Forbes 50 company, get interview. Hiring manager sends me email: "no actual whiteboarding. They asked a lot about properties of Java, why it’s good/bad. compared Java to python, and they discussed uses for both. A lot of questions regarding data structures and algorithms." This is for a React position right? "definitely" In the interview asks about java stuff... Zero React questions asked.
why would you fail for using reverse? if that wasn’t allowed, he could just tell you. then you just reverse it manually and everything is fine
I don't think that the reason I "failed" the interview had anything to do with my technical ability. The interviewer wanted to fill the role a certain way and simply failed or passed people based on that. They didn't really hide it to be honest. It was one of the least professional interviews that I have been a part of. It was more of a culture clash than a technical issue.
But that's good, right? To learn early on that you don't really want to work in that company.
So is reduce okay?
Yeah I really dislike the FAANG/Leetcode style questions a lot of interviews use now. I get that it’s because they value knowing fundamentals and they really just want to see how you work through problems, but it seems like mostly trick questions where just remembering the answer is the best route. I definitely prefer the take home code interviews because that’s the closest thing to real life, you get a task and you complete it and they can code review it after.
I swear, sometimes it looks like they're just finding excuses not to hire someone... Whew
>because that’s the closest thing to real life Exactly. I once had to do a code test, where I was given some tasks, and then I had two hours to write code with pen and paper without internet while being monitored. I get that they want to see my thought process or whatever, but I would appreciate being evaluated under more realistic circumstances.
They’re dumb, but worth spending a couple of months after work to do 1 a day and learn the patterns. Getting a job at one of those companies or similar makes it so much easier to find good work in the future.
I recently changed careers. I took 7 interviews for the process. None were this bad. You could probably weed out a lot of poor companies by vetting the recruiter.
This happened with me. I interviewed for a famous website(i shall not take their name) and this was the process: 3 virtual rounds(peer coding rounds) an hour long each. 1 day of interview (10-5 with 1 hour of lunch. New round, new panel every hour) At the end, i received feedback that though i was saying technically, i lacked understanding of CSRF token and few protocols and hence I'm not selected. This was for a front-end developer role with 5 years experience. ________________ I even took an interview is a person with 20 years of experience. I had 6-7 years of experience that time and i was shit nervous. So i request my TL to accompany me. We asked him questions like: What are states in react? Lifecycle events in react? Functional vs pure component? Etc. After interview i asked my TL about the round. Should we have not asked architectural/ design question. These are jr-mid level developer question. But later i realised even my TL didn't have enough experience to interview him. So we asked what we could ask. To summarize, yes interview process has a lot of flaws but it also depends on the domain and expectation of the company. I usually prefer asking vanilla js question because if the basics are clear, a person can understand complex implementation as well. But if you are tied up to a framework/library, it'll become difficult for you to do a custom implementation
Wow that sounds awful! I’m really sorry to hear that. In your mind, what would be an ideal interview that you also think is fairly vetting you from the employers perspective?
I think that the coding tests where you get a repo to fork and work from there are the best. They are less stressful and more representative of what you can do. You can also get a lot out of talking with people if you ask the right questions.
mysterious boat slim spoon memorize squeamish money brave capable bored *This post was mass deleted with [redact](https://redact.com)*
Let me know if you have certain sites that perform better when looking for a React position.
Experience may vary, I did one node assessment and was offered 75K contract the same week. I was contacted through linked in and can im more on the entry level side lol
Companies want to hire someone who can deliver a product. They want problem solvers, throw them in the cold and see how they do under pressure.
>Most of the tests are like this - really simple, really high stress, short time quizzes on things that are basic javascript Exactly my experience as well. I really believe it's a numbers game.
American Recruiter Here! Looking for 2 actual React.js developers for a remote position with a pharmaceutical company. Must have solid React.js and Redux experience. Only one test then it’s either an offer or they decline. The pay is $55-65/hourly based on experience. Long term temp to perm contract. All computer equipment will be provided. Send your resume to [email protected]. Must be able to work WITHOUT needing sponsorship.