Traditional Unix permissions are broken down into: so answer is 3 read (r) write (w) execute file/access directory (x) Each of those is stored as a bit, where 1 means permitted and 0 means not permitted.
I'd say 9, since the three bits you have mentioned have to be multiplied by the three user groups (owner, group, others). rwxrwxrwx
Nuanced answer - day to day then not at all, and I don't exactly have a monstrous ego that needs constant fuelling, however I wouldn't wish to work in an environment where nobody is appreciated, and like any human then the odd bit of recognition is always nice. In some cases, I'd actively pass the credit on to others, as it may be important in their development, so I'd be happy in myself, simply knowing I'd done the right thing, and seeing the business improve. Oh, sorry, it seems I can't actually explain my answer, I need to pick a number from 1-10. Um, 6?
Through questions like this, interviewers are mostly trying to test your skillset (and its relevance to the role) as robustly as possible, so be prepared for multiple offshoots and followups. It could be a useful exercise to do mocks with friends or colleagues in Spotify to get a real sense of what the interview is actually like. Alternatively Prepfully has a ton of Spotify Engineering Manager experts who provide mock interviews for a pretty reasonable amount. prepfully.com/practice-interviews
Some of the Key Questions in Round 1: HR Round 1. Tell me about yourself and your past experience. I think they were just checking communication skills. Also depth of experience 2. What am i looking in my next role? 3. Salary expectations
What ever applies to your situation, just explain it.
The key in generic questions like this, is to make sure to cover the fundamentals. There's usually a back-and-forth with the interviewer. Might be worth doing a mock interview with one of the Spotify Software Engineering Manager experts on Prepfully? Really helps to get some real-world practice and guidance. prepfully.com/practice-interviews
So the recruiting team had done a great job preparing me for the interview process and nothing really took me by surprise on the day. Having said that, I am not a fan of role plan and I dreaded this question in advance. What I loved about this question was the best way to answer the question was to forget you were interviewing and just make sure you dealt with the issue at hand (the underperformance concern) just as you would in your current role and let your own personal style shine through.
There's a lot of elements to typically cover in these questions, clarifications, scoping, making sure you're answering the actual question the interviewer is looking for you to answer, etc. Could be worth doing a mock interview with one of the Prepfully Deliveroo Engineering Manager experts... they've worked in the role so they clearly know how to get through the interview. prepfully.com/practice-interviews
technical questions on scenarios you're given on the spot
It's essential to demonstrate that you can really go deep... there are plenty of followup questions and (sometimes tangential) angles to explore. There's a lot of Engineering Manager experts who've worked at Skyscanner, who provide this sort of practice through mock interviews. There's a whole list of them curated on Prepfully. prepfully.com/practice-interviews