4 ms·
While I am no stranger to interacting with developers who seem to only be in the industry because of how well it pays, I find your advice frustrating. My experi
by gymbeaux 4y ago
While I am no stranger to interacting with developers who seem to only be in the industry because of how well it pays, I find your advice frustrating. My experience with startups is that they demand a lot of A) interest from the candidate immediately, before the candidate has even talked to a human, and B) attention from the candidate- but that same interest and attention is not returned to the candidate. Thinking about the startups I interviewed with in the last couple of years (all via TripleByte fwiw), I have noticed the following patterns:
- The founders/cofounders think they have come up with the best idea ever, when objectively the idea is novel but garbage (usually a solution looking for a problem), and only want to hire people eager to smell their farts all day long (and probably on some nights and weekends, too).
- The interview process is unnecessarily complicated, despite the supposed ahead-of-time vetting done by TripleByte (which used to tout "skip to the final interview", but in reality is "skip the computer-graded, timed Leetcode Easy brain teaser"). In the worst-case, a company had me interview with 4 different people throughout the week, give a 15-minute presentation on a coding project I worked on, and then they expected me to work nights and weekends for an entire week to "test drive" me (the irony here is that while they get an idea of what it's like to have me as an employee, I don't really get to see what it's like to work for them as a company - it's not like I am in their Slack channels or participating in meetings.
- The pay isn't that great. Again, the founders are delusional, think it would be a real privilege for anyone to work for them, and seem to believe that they cannot be too selective. "Give me a candidate who has familiarity with NodeJS on the backend and [Scala/Ruby/Go/Rust] (because why not), is willing and able to work nights and weekends (but it's okay because we offer uNliMiTeD PTO), all for the generous, generous salary of $130k/year.
If you don't draw parallels between these and Wundergraph, kudos, but with each of the startups I interviewed with, I could feel myself becoming more and more jaded until I just gave up. A year later I'm still at my current job, and I'm glad I stayed, but I put a lot of energy into those interviews, hours spent even before I had my first interview, just researching the company, looking at their code (if any of it was public) and coming up with thoughtful questions. Why did these four companies not want to give me a job offer? I'm not sure. It could certainly be cultural more than technical. Despite my cynical attitude now, I promise you I came into each interview with enthusiasm, respect, and genuine interest in the role.
I was also sure they all knew where to find my LinkedIn, Medium, StackOverflow and Github profiles, which all give insight into my abilities and (I think) prove I enjoy writing code and building stuff, and most importantly, that I could probably handle whatever frontend-for-a-database app they were building. Let's be real, most apps aren't that complicated.
- precompute 4y agoWere these interviews via triplebyte in the last year or two or before that? I've heard that the platform isn't what it used to be.
- gymbeaux 4y agoI hear it isn’t what it used to be as well. They used to do in-person interviews, then they moved to un-proctored quizzes to prove skill, which I find to be a unique and mostly-accurate gauge of skill in a particular area. That said, I don’t know how common cheating would be. If it’s high, that certainly explains why companies don’t seem to put much merit on them. Also, there’s the irony that TripleByte went from a language-agnostic in-person (virtual) interview to very specific quizzes. So instead of saying “this dev knows how to dev”, they now say “this dev knows C#, Python, SQL, and JavaScript”