Oracle Tag!!!
It's better to join other product development teams at Oracle.
Never-ending list of cons:
Official timings: 9:00 AM to 5:30 PM and holiday on Saturday. Never ever expect this to happen in this team.
Developer duty: You are expected to stick to your desk 24/7 and never expect anything in return.
Saturdays: All Saturdays are working days without prior notice or information. Sometimes, working on Sundays is also expected. Don't expect any salary or comp-offs for working on Saturdays/Sundays.
Work-life balance: You have to sacrifice your life for the work and never expect anything in return.
Team Leads' job: The boss/team lead is expected to be arrogant and abusive (using fowl language) and should always pressure the developer until they leave the company.
Team Leads' imagination: Leads imagine that developers waste time on lunch, snacks, washroom breaks, and chit-chat. They track the time spent at desks and create a scene of "Resource is not working up to full potential," taking this as an issue to higher management.
Deadlines: Complete the work quickly to get more work. Also, every five days of work is expected in one day.
Appraisal: It's a biggest joke. Hard-working resources get the highest hike percentage, which is 10%. Management delays announcing hikes year by year, so you end up getting a 5-6% hike annually on average, only if you are very hard-working. Management will not hesitate to give a 0% hike for average, hard-working freshers.
HR management: Micromanagement and support for managers. If a resource files a harassment complaint against any manager, no action will be taken.
Talent: It's foolishness to have talent here. Good talent will never be appreciated. Eventually, most talented people have already left or are leaving soon.
You can join if you are willing to:
If you are a fool, this is the place for you to join and enjoy bad quality work without expecting money or growth.
Just shut down the project so that people can search for real jobs in the market.
The interview process consists of two technical rounds, followed by a manager round and an HR round. Technical rounds focus on Java, SQL, algorithms, and puzzles. The manager round includes some puzzles and communication exercises. They want to see
I was contacted by the recruiter, who explained the interview process to me in a meeting. This started with a code challenge on HackerRank that wasn't very complicated to do. After this challenge, I was supposed to have contact with someone from Ora
They were very down-to-earth and didn't try to stump me too badly with big problems to solve. They were as interested in how I would work with the team as they were in whether I could write a palindrome.
The interview process consists of two technical rounds, followed by a manager round and an HR round. Technical rounds focus on Java, SQL, algorithms, and puzzles. The manager round includes some puzzles and communication exercises. They want to see
I was contacted by the recruiter, who explained the interview process to me in a meeting. This started with a code challenge on HackerRank that wasn't very complicated to do. After this challenge, I was supposed to have contact with someone from Ora
They were very down-to-earth and didn't try to stump me too badly with big problems to solve. They were as interested in how I would work with the team as they were in whether I could write a palindrome.