It all depends on project to project. In my case, I worked in both scenarios: where I had a lot of work, 10-14 hours a day or more, and where there was a team driven by an agile coach, where I spent 6-8 hours working.
So I found some common pros in both cases:
They should give good hike if I compare it with lateral hires.
Management should look at the work before going for any bid. At the end, developers and other folks have to bear that pain.
Three rounds of interview: 2 technical interviews and 1 HR interview. Project activity questions: * Core Java basic questions * Spring Boot and basic microservices questions * Some database GROUP BY and ORDER BY questions * Project build-related to
The recruiter contacted me through my Naukri profile. After postponing the interview for three to four times from their end, the interview finally happened. That day, the interviewer also delayed it by 30 minutes without informing me prior. The int
It was smooth. First, they started with general questions, followed by resume-based questions. They also asked a few real-time questions, as I was interviewed on ETL Informatica. Majorly, transformations and real-time based questions were the highlig
Three rounds of interview: 2 technical interviews and 1 HR interview. Project activity questions: * Core Java basic questions * Spring Boot and basic microservices questions * Some database GROUP BY and ORDER BY questions * Project build-related to
The recruiter contacted me through my Naukri profile. After postponing the interview for three to four times from their end, the interview finally happened. That day, the interviewer also delayed it by 30 minutes without informing me prior. The int
It was smooth. First, they started with general questions, followed by resume-based questions. They also asked a few real-time questions, as I was interviewed on ETL Informatica. Majorly, transformations and real-time based questions were the highlig