Little more background for all. The position we hired for will be given a project right off the bat and expected to do 95% of the work solo as itās a new project from scratch for the most part. They will work with me to provide them access to an existing API and to expand on that API as they need. Also, in the future, we are going to post links to our job postings here.
vipatron
On 8, yes nested ie other objects and arrays. The key here was to understand if you do a shallow clone that object a { sub1: { name: ātestā } } where b = a, b.sub1.name = āchangedā that a.sub1.name === āchangedā. Additionally, if they mentioned b = JSON.parse(JSON.stringify(a)) I wanted to make sure they could explain when they might not want to use that, ie in a server-side function that is called frequently as itās blocking and slow. Normally, the speed would not matter but in a REST endpoint, it can kill performance.
Question 2 was not a pass or fail. It was just getting to know them/we use it but not hard to learn. Also, 7 is not as hard as you think. I read an article on Medium a while back that I think was written by an FCCāer to get up to speed. While async/await is not perfect, once you go async/await you never want to go back, lol. We converted away from cb hell/promise treeās this last year and want to make sure whoever we bring on will be up to speed.
As to FCC, thanks! I actually got my CS degree before I found FCC. The FCC material was FAR more valuable than what I learned in College.
psychometry
Why Material? Because we use it. Not a show stopper. I try not to go in with hard questions right off the bat. If you didnāt know it, which most didnāt, I didnāt really care. It was more of a nice plus.
The biggest thing to understand about Arrow, which you pointed out is that it binds this to the scope its defined in. This can cause major headaches when the calling code that the arrow has been passed to expects this to belong to a specific scope. Mochajs is a good example of where things can go wrong. https://mochajs.org/#arrow-functions Another, major spot is when you do something like onclick=(event)=>aObjInstance.someFunction(event). I donāt remember the specific details but someFunction was broken by the arrow.
cndragn
I donāt know if you are going after junior positions or something higher up, but if you could answer most of these questions as a jr. dev then I would hire you. I do throw some coding problems at jr. devs. Right now, I would make sure to have a coding problem using fetch / node-fetch. One of the APIās would return a JSON body normally, but on errors, it would return a string body. Dumb, I know, but that was a recent error we ran into. Another item would be to download a file from one location and upload it to another using node-fetch.
Dohn_Joe
I donāt know React well. All of our apps up to this point were internal facing only, so my level of React was fine, and the speed of getting it built was not an issue. We are going to launch a new external product in the next 6 months. So we decided to bring on an experienced React Dev. We mostly looked at their prior work and I asked them the basics of React just to make sure they did the work. Most failed these basic react questions to the point of not even having a clue.
vaidotasp
Yeap, as I wrote to Dohn_Joe my react skills are weak/jr level. On the other hand, my JS/Node skills are considerably stronger. Iāve been doing JS/Node/React for 4+ years, but the workload is 50% ops, 40% Node/Mirth Connect, 10% React/Frontend.
