They support philanthropy and encourage you to as well, including on work time provided project deadlines allow.
Stable without hire-fire cycles to appease short-term shareholder value.
It used to be possible to be entrepreneurial, but no longer so.
Since they drank the Scrum kool-aid, micromanagement has worsened, and it's night on impossible to be entrepreneurial or innovative, except for very limited and managed "10% time" one day a fortnight.
A pointless return to office is being enforced with no exceptions or consideration for train strikes, childcare needs, etc., despite the last three years having proven the teams can work just as effectively (if not more in many cases) remotely.
Return to office is slowly creeping up from three days to four every week.
No justification or explanation is given for RTO; it's just "policy."
Hypocrisy of big internal marketing signs and slogans marketing "Bring your kids to work day by Bloomberg Working Families Community" while at the same time being told the small work from home allowance left is explicitly not to be used for childcare emergencies or needs. Talk of "the days of seeing kids in the background of Zoom calls" being over (I mean, how petty can you get? We want to pretend our workers are automatons who aren’t humans with lives outside work, so we can’t even see traces of any humanity or children; you must appear a corporate drone at all times).
Disastrous loss of morale with the RTO attitude and hypocrisy.
Be more rational and logical about WFH balance. Claims of valuing diversity and supporting working families are insultingly disingenuous when actions over RTO policy so obviously and harshly contradict the words.
It's a classical interview process. It started with an HR round, in which they wanted to know you. After that, there was R1, a coding interview, where they asked one LeetCode medium question. In R2, they asked another LeetCode medium question for cod
Round 1: Initial 30-minute Zoom call with recruiter. Round 2: 1-hour HackerRank session over Zoom. Round 3 and 4: 1-hour HackerRank session followed by a system design session. Round 5: In-person interview.
1. HR interview. 2. Leetcode interview with engineer. 3. 2-hour interview consisting of two parts: a. Leetcode easy interview. b. General technical knowledge around networking. 4. Supposed to be an interview with the manager, but HR kept ghos
It's a classical interview process. It started with an HR round, in which they wanted to know you. After that, there was R1, a coding interview, where they asked one LeetCode medium question. In R2, they asked another LeetCode medium question for cod
Round 1: Initial 30-minute Zoom call with recruiter. Round 2: 1-hour HackerRank session over Zoom. Round 3 and 4: 1-hour HackerRank session followed by a system design session. Round 5: In-person interview.
1. HR interview. 2. Leetcode interview with engineer. 3. 2-hour interview consisting of two parts: a. Leetcode easy interview. b. General technical knowledge around networking. 4. Supposed to be an interview with the manager, but HR kept ghos