The current state of our HR policy is far from ideal. The absence of a clear definition for the number of leaves we are entitled to has resulted in many of us taking fewer leaves than we should.
In the past, our policy offered flexibility in terms of office hours and the option to work from home. However, recent pressure from the CTO to mandate 3 days of in-office work is causing concern.
This request is particularly challenging for those of us who regularly extend our working hours late into the night to connect with colleagues in the US. The combination of inflexible office hours and an undefined leave policy is making our work environment less employee-friendly with each passing day.
Furthermore, there has been a delay in the appraisal cycle. It is disheartening that the management has not addressed the issue of compensation for this delayed period.
This situation is eroding the trust and morale of the employees.
It's crucial that we prioritize the well-being and needs of our employees before making any decisions.
Established organizations often provide more structured and employee-friendly policies that can serve as valuable benchmarks for us to consider.
By doing so, we can create a work environment that not only attracts top talent but also ensures the satisfaction and productivity of our existing staff.
The interview process at Fanatics was incredibly streamlined and well thought out from beginning to end. The first round is a call with a recruiter to go over things like role fit and background. The second round is a technical with a senior engine
Had one round of interview with a person on the West Coast. There was a coding question regarding separating and segregating logs based on their type through code. Add test cases for the coding scenario. Technical questions on how to debug a login
Drive: 3 rounds, 1 coding and 2 technical rounds. Kafka internal logic and project architecture. 3-round technical interview focused on coding, microservices, Kafka, Kubernetes, cloud services, authentication, caching, design patterns, databases, m
The interview process at Fanatics was incredibly streamlined and well thought out from beginning to end. The first round is a call with a recruiter to go over things like role fit and background. The second round is a technical with a senior engine
Had one round of interview with a person on the West Coast. There was a coding question regarding separating and segregating logs based on their type through code. Add test cases for the coding scenario. Technical questions on how to debug a login
Drive: 3 rounds, 1 coding and 2 technical rounds. Kafka internal logic and project architecture. 3-round technical interview focused on coding, microservices, Kafka, Kubernetes, cloud services, authentication, caching, design patterns, databases, m