Taro Logo

Fullstack Engineer Interview Experience - United States

July 12, 2023
Neutral ExperienceNo Offer

Process

Firstly the positive. Everyone I met with seemed friendly and like someone I wouldn't mind working with. Went through hiring manager, technical interview then a panel interview. While I found the overall interview fair the panel interview was probably one of the most poorly executed interviews I've seen. To start I was sent documentation on what to expect. That I should have a local environment I could work in. Appropriate Node version, an editor and an application to interface with an SQL database. So I sent an email to clarify some of this, didn't receive a response for almost 5 days and it didn't answer my question. On the day of the interview I again asked for clarification and was just told I wouldn't need anything.

System design - fair and typical not much to add Front end / back end - Unlike the preparation email stated this was a fully hosted in cloud development environment called Gitpod. Would have been nice to be made aware, like why not just say so lol? Also it only allows SSO so ya better be ready to sign in with a personal GitHub or similar, again why not tell the candidate this? It took around 5 minutes to get an account created another 5 or so to learn how to use the environment. The interviewer didn't exactly know how to log output for the FE portion so another 5 debugging how to do this. After 15 minutes I then realized we needed to implement some external library which took around 10 minutes to go through its documentation.

So with around 25 minutes - the typical 5 for questions you are left with a maximum of 15 minutes to do anything. For the BE at least the environment was now setup. But the question was totally ambiguous it was just a prompt of some use case and no data examples. Admittedly I overthought this, though based off the expectations set I figured this to be primarily about SQL or specific BE features. I repeatedly tried to clarify if this solution was expected to be DB specific or was a pure JS solution fine. Couldn't get an answer and was also not even told where to write code in a codebase that had dozens of files. Though eventually I figured it was probably best to not use SQL and got to a solution.

Really kind of weird TBH because you don't need a BE to solve the question and I would argue an optimal solution would not be done on the BE at all. The last interview was an algorithms challenge. I was asked the exact same question from my first interview. I told the interviewer and then was asked to implement some ML algorithm instead which I did in maybe 15 minutes and discussed optimizations. Walked away feeling like I wasn't really put in a position to succeed and more like a test run for an untested interview process. In theory I get what Substack is doing and appreciate a different take on the interview process but in practice I don't think it works as is.

Was this helpful?

Interview Statistics

The following metrics were computed from 1 interview experience for the Substack Fullstack Engineer role in United States.

Success Rate

0%
Pass Rate

Substack's interview process for their Fullstack Engineer roles in the United States is extremely selective, failing the vast majority of engineers.

Experience Rating

Positive0%
Neutral100%
Negative0%

Candidates reported having mixed feelings for Substack's Fullstack Engineer interview process in United States.

Substack Work Experiences