Gitpod interview questions

Pro tip: If you're interviewing, there's an expectation that you have read all the company values and found something in your previous work experience that relates to near all of them. If you want the role there, be sure to have taken the time to have listened to the podcast shared along with having the values considered.

The interview process at Gitpod involved multiple stages; 1. Introductory discussion with their recruiter. 2. A brief conversation with the Head of Product Marketing 3. A more in-depth dialogue with the Head of Product Marketing 4. A meeting with the Head of People 5. A task based presentation, 6. An interview with the CEO. 7. An optional visit to London to meet the team 8. An optional one-on-one discussion with the current product marketing manager. The number of stages was quite extensive, surpassing that of even large enterprises I have interviewed for. Additionally, there were frequent rescheduling of meetings; on one occasion, I had two consecutive interviews that lasted a total of two hours. Regarding the individual stages of the interview, I found all participants to be friendly on the whole. However, the task presentation posed significant challenges. I was assigned the responsibility of selecting 5-10 assets to be given to a salesperson following a discovery call with one of the world's largest equity firms. These assets were meant to be sent over by the salesperson immediately after the discovery call. Furthermore, I was expected to choose one asset to design myself and role-play how to utilise it during the panel interview. Several aspects of the task made me uncomfortable. Firstly, it differed from prior assignments given to candidates; I later learned this was due their sales team being in active conversation with the world’s largest equity firm; this created the impression, that Gitpod was soliciting free labour. Additionally, the feedback I received was somewhat confusing. One panel member indicated they had anticipated a market and competitor analysis, despite this not being specified in the brief. Another panellist inquired about my perspective on the future of cloud development environments; I shared insights about the potential of blockchain to enhance safety and code quality, yet was subsequently informed that this was deemed irrelevant. My approach to a case study was criticised as 'cookie cutter,' despite feedback during the presentation highlighting its high degree of personalisation, customisation, and alignment with the specific compliance and integration needs of equity firms. I was also told that I failed to ask questions despite posing inquiries to the COO regarding win rates and to the Product Marketing Manager about cloud development environments and key personas for Gitpod. In summary, while the interview process involved many stages and the participants were generally amiable, I would recommend exercising caution regarding this company. The feedback was inconsistent, and the nature of the task gave the impression that candidates may be leveraged for free insights and consultations in the guise of an interview task.