I applied online. The process took 1 week. I interviewed at ReadMe in Mar 2025
Interview
1. One on one discussion w/ hiring manager.
This was a general discussion to get to know me and my experience. We discussed current and past issues I've faced and how I would go about resolving them.
2. Discussion w/ two engineers
The recruiter asked me to bring along a project I've worked on with some general topics the engineers would discuss around that project. This was probably one of the best interview tactics I've seen: it allowed me to present something I was well-versed in and tailored the questions around that project: how did I handle deployment, migration, scaling, monitoring/metrics, and any ongoing problems and how I would resolve them.
3. My experience ended here, but based on the job description, there would be a several hour interview with the team.
Despite not getting to the 3rd step or an offer, the team here is incredibly enthusiastic about what they are working on, but are also blatantly honest about the problems they face and the reasons they were looking for an Infrastructure Engineer. I got the impression that the team would be easy to work with and they were very open to new ideas ways of doing things.
Interview questions [1]
Question 1
Present past project you have worked on and be ready to explain how it works and some problems you solved or still need to solve.
I applied online. The process took 4 weeks. I interviewed at ReadMe in Feb 2024
Interview
Sorely disappointed. I applied online via their REST API. From there, I had calls with company leadership and engineering leaders. I thought each of the 3 conversations went exceptionally well. I had to frequently contact the recruiter for status of my process and to move on to the next phase. I loved the culture and values that they seemed to embody, especially since the space was so exciting for me. In the end, I don't think I was given a fair shake to really to let others get to know me based on the feedback provided. Interviews are hard and I feel let down that their "Always Do What's Human" value came through in their process and evaluation of me.
Interview questions [1]
Question 1
What if another technical leader from another organization presented challenges with the way the Readme open source code worked?
I applied online. I interviewed at ReadMe in Nov 2022
Interview
Applied online and received an email from the recruiter asking me to schedule directly with the CEO - I took this as a good sign because most current tech interview loops are painfully and needlessly long. Chat with the CEO was pretty informal - this was going to be their first product hire. I walked away with the impression that he didn't entirely understand the discipline of product management or what they should be expecting their first product hire to do. I leaned into my expertise regarding product growth, pricing, and revenue, given that a product head would rightfully be expected to contribute (if not outright own) to discussions and strategy re: pricing and MRR. The CEO bluntly replied "I don't care about money", which seemed like a bizarre opinion for a CEO to both have and to admit outloud. Left a bizarre taste in my mouth.
Interview questions [1]
Question 1
Very little in the way of formal questions - mostly "tell me about this thing I see on your resume" sort of stuff. Again, it felt like the CEO didn't really understand product as a discipline or how to ask questions about it.
