I recently completed a Karat interview that I found to be professional and a valuable opportunity to showcase my skills. The technical aspect was handled well, and I appreciated the thoughtful questions and supportive environment.
However, the experience took a downturn after my conversation with HR.
During our discussion, I transparently shared my current CTC and the base pay of the offer I am holding. I also communicated that I was seeking a 30% increase over my current offer. Despite this openness, HR quickly assumed that my primary motivation was financial gain, without considering other important factors I value in a role, such as company culture and long-term growth opportunities.
This quick judgment felt unfair and did not account for the broader picture of what I am looking for in my next career move. It was disappointing to have the process end based on this assumption rather than a comprehensive evaluation of my skills and interests.
I hope the company reconsiders its approach to candidate evaluations in the future. While salary is a significant factor, it's essential to recognize that candidates also weigh various other aspects of a role. A more in-depth evaluation process could lead to a better understanding of candidates' true motivations and potential contributions.
Some k8s and AWS-related stuff, and two coding questions.
The following metrics were computed from 1 interview experience for the Splunk Software Engineer, Backend role in India.
Splunk's interview process for their Software Engineer, Backend roles in India is extremely selective, failing the vast majority of engineers.
Candidates reported having very negative feelings for Splunk's Software Engineer, Backend interview process in India.