Fast paced however middle management sucks.
Fast paced however middle management sucks.
-
Building things fast leads to good learning.
-
There are good business problems to solve.
-
The company is investing in AI.
- the company has devalued themselves by 40% in terms of market cap - check recent news articles. - Culture has started going into a downward spirals. Used to be an engineering first company. Now its just about chasing some timeline because a middle manager promised the higher up something without having any in-depth understanding. - Middle management is there to take credit of deliverables by IC by putting their name on it. And blaming the ICs for anything wrong. - If you are joining at leadership level and into games of politics. it could be a fun place, because each leader is trying to prove their own worth by taking as much credit as they can, As IC you wont get any appreciation for your work. - Expectation is to also work on weekends or late hours. - Trust on the leadership has went down to a great extent. This was also called out anonymously in the latest tech meet feedback. - Recent anonymous feedback highlighted all these point to the engineering leadership, not sure if they are going to fix anything. - If you are in leadership role you can bring any of your relative or friends into the company. no hiring bar for them
- No scope of growth, because the early middle managers refuse to make way for junior folks to grow and they want to stay in the company forever playing their games of politics. - Tech leads are running the show and pulling most of the management works. tech leads work as substitute to the managers. managers barely interact with the team.
- Get rid of a lot of middle managers who are just there for politics. Let the engineers drive things. The culture and productivity both will increase. You don't need these many middle managers, go back to having flatter hierarchies. - There are no pure architects. Looks like even architects are middle managers. Get seasoned and experienced architect who are devoted to tech and not politics.
Additional Ratings
Was this helpful?
CRED Interview Experiences
Software Engineer
I applied through a recruiter. The process took two weeks. I was asked a coding challenge that consisted of designing a key-value store with support for multiple attributes and indexing functionality within two hours, pretty much like AWS DynamoDB,
Software Engineer
I applied through an employee referral. The process took 3 days. I got a call from HR and received a coding round link with 3 questions on HackerRank. The problems were based on arrays and strings. There was 1 easy question worth 20 points, 1 medium
Software Engineer
I applied through a recruiter. The process took 2 weeks. There were four rounds: - Machine coding - Problem solving 1 - Problem solving 2 - Hiring Manager round The problem was to design a system to send email notifications based on the LOB the use
Software Engineer
Bengaluru, Karnataka, IndiaMarch 28, 2022I applied through a recruiter. The process took two weeks. I was asked a coding challenge that consisted of designing a key-value store with support for multiple attributes and indexing functionality within two hours, pretty much like AWS DynamoDB,
Software Engineer
December 9, 2019I applied through an employee referral. The process took 3 days. I got a call from HR and received a coding round link with 3 questions on HackerRank. The problems were based on arrays and strings. There was 1 easy question worth 20 points, 1 medium
Software Engineer
Bengaluru, Karnataka, IndiaOctober 17, 2024I applied through a recruiter. The process took 2 weeks. There were four rounds: - Machine coding - Problem solving 1 - Problem solving 2 - Hiring Manager round The problem was to design a system to send email notifications based on the LOB the use
