I was told I needed to polish up on some data structures and algorithms topics, which of course I knew already after the interview. More helpful was the feedback I got on the coding portion of the test. I was told I appeared to lack familiarity with Python since I shadowed a built-in function name with my own variable. I knew what I was doing. I didn't need the built-in function in that scope, naming things is hard, and under the pressure of coding under someone's watchful eye I made a quick decision. I won't do that anymore.
The email was actually pretty long, which is to Triplebyte's credit. Although who knows how much of it may have been algorithmically generated.
Here is an abridged version the sake of brevity:
Hey [Ravenstine]
Unfortunately, we're not going to move forward with your application right now.
You did well in the Kanban problem. You talked well about HTTP. You write really nice, idiomatic front-end code. You understand how to build the front-end of a web application, and explained it well on our used car API problem. And you were friendly and we enjoyed talking to you.
We didn't see the depth of knowledge that we look for in front end programmers: you didn't show very deep knowledge of security or data structures. On the used car problem, you didn't seem very knowledgeable about backend web systems.
You might benefit from studying some of the following topics: Classic algorithms and data structures. Basics of HTTP. Advanced Javascript things like the ES6 features, async/await.
We recommend you study algorithms more deeply.
We think you're really high potential, and we'd love to talk to you if you're still job searching in four months (we of course hope for your sake that you're happily employed by then), or next time you want a job.
Best,
Triplebyte Team
---
Again, the fact that they provided this kind of feedback is actually pretty good.
My problem is not only that I believe I was interviewed on the wrong things(over half my questions were CS and algorithms but I was applying as a web developer), but the feedback also isn't entirely accurate.
Could I shore up on algorithms? Sure.
But look at this:
> You talked well about HTTP. [...] You might benefit from studying some of the following topics: [...] Basics of HTTP.
What the hell? Not only is that feedback contradictory, but it's horseshit. I wasn't stumped on the HTTP questions, and all my answers about it were accurate. I've written HTTP servers and have done some interesting things cutting together audio and streaming mid-roll through HTTP, so don't tell me I don't know enough about HTTP. HTTP isn't complicated.
> Advanced Javascript things like the ES6 features, async/await.
I'm not sure whether this is related to the question about promises in JS that I was asked, but I don't see how because I explained their function accurately.
> you didn't seem very knowledgeable about backend web systems
This one blows my mind. I had way more experience doing backend than frontend at the time. I don't know what I could have told them that would have suggested that I effectively know nothing about how HTTP and backend programming works.
---
Maybe my diction was poor, idk. If it was, it didn't seem to stop me from getting jobs outside of Triplebyte.
Perhaps I wouldn't have been as miffed about this if they had included algorithm and CS questions in the initial multiple-choice quiz. I shouldn't have gotten to the point of the interview only to find out that I didn't have the knowledge required.