Like many employees, I joined Substack because I loved the product and wanted to work on making it better for the next generation of writers on the platform. I didn't know what to expect of the engineering quality and company culture.
Half a year in, I've been blown away by the caliber of engineer working here, and the kindness and curiosity demonstrated by everyone I work with. From no-holds-barred all-hands discussions to fun offsites and deep discussions with coworkers, every day working here has brought new surprises and challenges, and I can't recommend it enough for any engineers who care about building a platform for the future of writing on the internet.
Substack is still a small company, and as such is subject to the same growing pains as many other startups. Internal processes are often better suited to an engineering team half the size, and documentation is a work-in-progress.
Some information gets siloed or lost in the depths of internal tools. But, these problems are well understood and agreed upon, and I have no doubt that in a year they won't be issues any more.
First coding interview: Calculate the document frequency and inverse document frequency for a body of strings. Optimization is to precompute the frequency for all words in the corpus. For the multi transform, store previously computed transforms in a
The process felt disorganized and slow. I applied for a more frontend role and was redirected to a systems role. After the initial phone screen there were 8 days of silence, then a manager call, then another week before a technical screen that was 45
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 probabl
First coding interview: Calculate the document frequency and inverse document frequency for a body of strings. Optimization is to precompute the frequency for all words in the corpus. For the multi transform, store previously computed transforms in a
The process felt disorganized and slow. I applied for a more frontend role and was redirected to a systems role. After the initial phone screen there were 8 days of silence, then a manager call, then another week before a technical screen that was 45
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 probabl