The interview process was CTO screening call, followed by take home technical, then take-home review over call, and then lastly on-site interview with CEO and other engineers. Fairly straight-forward and everyone seemed reasonably nice, with a few yellow/red flags.
A. Had no opportunity to ask questions during CTO screening call even though the interview went 30 minutes over. This is my main gripe, as I would have withdrawn from the process had I been able to learn more earlier on.
They use salesforce as a database/backend with no plans to move, which I think is important information to share with candidates early on. Salesforce dev is not the same as a typical software engineer. Maybe could even put that in job title and have recruiters screen for that.
B. Take-home was fun and interesting, but when I asked the engineers more about it, they informed the take-home had nothing to do with actual work that would be done day to day on the job. Again, seems important to share that early on // they should probably change the take home to be relevant to the role.
The on-site itself went an hour over time. Rejection email was a generic message saying the role was competitive. Very few companies give actual honest feedback so that was not surprising.
Biggest takeaway is they should probably change the role title from Software Engineer to Salesforce Developer for clarity.
Interview questions [1]
Question 1
- screening call: how do you approach mentorship?
- take home: write a CLI application that does some data analysis based on api results
- on-site: walk me through your experience. why did you leave each company you have worked at.