fellow from the team was asked to do the estimate by manager - he said 2 weeks

then manager asked what if we add one more developer - he said, again 2 weeks and maybe add day or two

I was asked same question without knowing that they already asked fellow from the team same question - I said around two weeks, maybe day or two more! XD

as manager was confused and not satisfied with the estimates, goes to our team leader with the same questions - team leader said - 2 and half weeks and if you add one more dev to it, 3 weeks minimum

we didn't know that all of us were asked as manager did that behind our backs, in the end manager learned lesson in greed as we got to stick to team leaders estimate!

also that was very rude of underestimating someone's ability, same manager did had personal bias and frequently mocked us, for example when we said that that we will implement ML for cropping images at the right place (ie. crop part of the image where the face is) on the backend. Response was something like: 'You guys will do the ML? Are you shitting me? You're not /insert FANG company/!'

best team win ever!

second best team win ever is when whole team left the company in matter of weeks

How I work:

I drink lots of coffee and pass out for 12 hours.

It’s like alcoholism, just less productive.

The problem with PHP is not the PHP, the problem is how most PHP devs still live in 2010

Never worked for this guy, just saw it someone else's feed and thought it would be appropriate here. This is not leadership. This is bullying and stomping on people in a vulnerable situation which most likely has very little to do with their work ethic and more to do with company health. Yea, definitely elevate yourself and be that A+ person for you. Not for assholes like this. A good leader would empathize and provide resources for advancement and transformation to roles that are more aligned to the current environment.

My favorite kind of interview question/challenge is anything that is highly practical for the job. At the current company I work, the coding test/interview challenge was to design and implement an API very similar to the core functionality of the actual product. It’s fair, tests for skills relevant to the job, and is much better than irrelevant silly brain teasers and cs questions, I feel.

In terms of specific questions, one of my favorites is one that one of my colleagues suggested I ask to potential candidates: describe what you think your biggest failed project/task was in your engineering career, and what happened/what you learned. I think it’s a good reflective question that can tell a lot about someone.