Many departments have this formalized. For example, in Field Engineering, there are "10x" and "Databricks Labs" venues for this that Solution Architects can work on their own projects.
Fast growth brings its own challenges. This is not applicable to all departments, though. Databricks mostly grows by adding more departments and adding verticalization, so a fast pace rarely is a bad thing here, except for the additional workload to help onboard new people.
Clear structure as far as stages are concerned. Although I have not had strict Databricks/Spark experience, I was approached by the Databricks recruiter. I was given the opportunity to go ahead with the interview and passed the technical stages. I wa
Rejected in the last round as they found a cheaper candidate. No concrete feedback has been shared yet. There were many rounds to prepare a candidate, but then there is no proper feedback which helps you get an offer.
The process consisted of six rounds over nearly two months, including: * A take-home technical coding assignment * Technical deep dive (Spark, cloud, architecture) * Project delivery discussion * Architecture & SME panel * Executive round
Clear structure as far as stages are concerned. Although I have not had strict Databricks/Spark experience, I was approached by the Databricks recruiter. I was given the opportunity to go ahead with the interview and passed the technical stages. I wa
Rejected in the last round as they found a cheaper candidate. No concrete feedback has been shared yet. There were many rounds to prepare a candidate, but then there is no proper feedback which helps you get an offer.
The process consisted of six rounds over nearly two months, including: * A take-home technical coding assignment * Technical deep dive (Spark, cloud, architecture) * Project delivery discussion * Architecture & SME panel * Executive round