You can learn a lot in a limited amount of time, as you're usually joining a project halfway through. You need to pick up enough on the job as possible to make yourself useful. A good skill to learn!
On too many projects, a 60-80 hour work-week is entirely normal. This is systematic, and probably an industry-wide problem. I've seen the same happen at IBM.
Plenty of studies show that longer hours do not equal higher productivity. This hugely saps morale and has a lot to do with why you see so few people about 35 in the company...
Depends on the interviewer. Some are easy to discuss your solutions with; some have a very strict way of looking at things. Every company and every interview differs. I knew some nice people at interviews.
The interview process was very professional. It started off with a test, then an interview, then an assessment center, then a technical interview. The assessment center took about 4 hours with a number of tests and interviews.
Project: Can we implement multiple interfaces in a single Java class? What is run-time polymorphism and how is it achieved in Java? Explain project and self-introduction, and what are data types? And team management.
Depends on the interviewer. Some are easy to discuss your solutions with; some have a very strict way of looking at things. Every company and every interview differs. I knew some nice people at interviews.
The interview process was very professional. It started off with a test, then an interview, then an assessment center, then a technical interview. The assessment center took about 4 hours with a number of tests and interviews.
Project: Can we implement multiple interfaces in a single Java class? What is run-time polymorphism and how is it achieved in Java? Explain project and self-introduction, and what are data types? And team management.