I saw the posting on LinkedIn and applied.
The recruiter called me a couple of days back and took notes of my experience and followed up by setting up the first interview with the hiring manager.
The hiring manager was good and even brought a deck representing high-level architecture.
This was followed by a panel interview with 5 people at the management level.
Almost all of them were technical, some little in-depth and others not so.
I work for a big tech professional services division and am quite hands-on when it comes to big data technology and have public blogs on how to build and use transactional data lakes.
After the panel interview, I was informed that I did not go in-depth into technology, which was a surprise to me.
If they wanted to do an in-depth technology calibration, they either should have asked low-level coding questions or should have done the internals of how Apache Hudi or Iceberg works.
I feel that some of the panelists were simply looking for a big tech candidate to validate what they were intending to do.
On the whole, the process was fair, and evaluating candidates is always tough.
The recruiter was kind enough to have a follow-up call to provide me the feedback, which I really appreciated.
Expect people to ask you about using Iceberg for time travel and schema evolution, as well as the data versioning and data virtualization, such as views versus materialized views.
The following metrics were computed from 2 interview experiences for the Komodo Health Staff Data Architect role in United States.
Komodo Health's interview process for their Staff Data Architect roles in the United States is fairly selective, failing a large portion of engineers who go through it.
Candidates reported having very good feelings for Komodo Health's Staff Data Architect interview process in United States.