Working at scale, so you get a lot of exposure to distributed microservices architecture.
Generally a young company, so people are energetic.
Some good technical people are there, and working with them is fun (a lot of learning, conversation, and questions, with no pressure even while delivering).
Managers put a lot of pressure in the name of "ownership". This creates unnecessary pressure and stress, which affects personal lives.
A lot of how you are treated depends on your designation.
Generally a young company, so most of the people without any real responsibilities otherwise, hence give very long hours to office work. It's difficult for experienced people to cope, unless you directly get into a senior role.
Managers and most other people are interested in getting things done as per the current requirement. Hence, solutions and design are non-futuristic and not platform-oriented.
Instead of a pushy culture, create a culture of inclusiveness of employees. Most of your employees work towards a given target only.
Incentivizing only the delivery is a dangerous trend, as people hardly care about the proper platform inclusion of the solution, which usually takes time.
Your managers are technical only in talking big. They care only about the end result. And why wouldn't they, if at the end they are promoted?
There is very little appreciation for the actual ground workers as compared to the effort the people put in.
I was interviewed for a Senior QA position (Manual Testing). There were two technical rounds, both scheduled through a consultancy. Both rounds were not overly difficult and mainly revolved around coming up with test cases and discussing tools used
The aptitude test was conducted using InterviewStreet.com. It contained 10 MCQs and a programming problem. The programming question was a variation of the coin exchange problem (Dynamic Programming). The interview lasted 3 rounds. Each round had que
A phone interview, typically for 15-20 minutes. Afterwards, 4 interviews on-site: * Two problem-solving and coding rounds * One design round * One managerial round
I was interviewed for a Senior QA position (Manual Testing). There were two technical rounds, both scheduled through a consultancy. Both rounds were not overly difficult and mainly revolved around coming up with test cases and discussing tools used
The aptitude test was conducted using InterviewStreet.com. It contained 10 MCQs and a programming problem. The programming question was a variation of the coin exchange problem (Dynamic Programming). The interview lasted 3 rounds. Each round had que
A phone interview, typically for 15-20 minutes. Afterwards, 4 interviews on-site: * Two problem-solving and coding rounds * One design round * One managerial round