18 ms·
A conflict with a manager ended with me being disallowed to work at Spotify
- elmerfud 4y agoI understand the story is one sided, but if I take it as truth, the immediate red flag is how the manager failed to manage. In the first examples gave me all the things I would have needed to know to bail on that team. When technical decisions come up with no obvious correct answer, the manager saying it's up to the team while also disagreeing is just bad. The team provides input and offers their view on best direction but it's up to the manager and product manager to be technical enough to understand the team and then balance business needs (which may be unknowns to the team) and make a final decision. The team then should accept it. The push back of using a parallel kanban board is just dumb on the managers part too. Management and teams often need different tracking and reporting styles to get work done. Your direct manager should be familiar with both. If they are not or refuse to be, just run. Managers enable teams by empowering, deciding and then getting out of the way. Bully managers use passive aggressive non-sense like you had to deal with. For Spotify to not recognize and isolate this person is a problem all the way up there chain.... And again, assuming your version is correct.
- synergyS 4y agoYeah, losing good people this way does not look good for Spotify
- throw457 4y agoIf you are petty enough to make a website about how you made passive aggressive Jira tickets to show the manager who’s the boss I bet he is not one of the good people you want as employees.
- mavhc 4y agoThe problem isn't this one person though, it's Spotify itself, it has grown large enough to need multiple managers, but no one is managing them
- casion 4y agoMy view is that if this story is 100% true, the author is in the wrong, and the manager is in the wrong, and Spotify as an employer is in the wrong. Write a formal letter and pass it up the chain appropriately (without this petty retaliation baked in), transfer teams, find a new job, etc... Fighting the manager directly and consistently does not provide any business value, social value or goodwill. It's simply the wrong play. In an ideal world, pushing for what you think is correct is noble and moral, however it is not an ideal world. Rallying against (minor) wrongs is not always valuable or appropriate. Business magnifies that, and pushing back against (minor) wrongs becomes ever more subtly complex. Business environments require tact and that is absent here. Now we can take it a step further and assume that the author is making themselves appear less complicit than they are (we all do this to some level when writing about ourselves). The chance of that pushes this story from "innocent but socially immature dev against big bad manager" to a whole variety of stories where it's a troublesome developer and a manager trying their best (even if moderately poorly) to manage it.
- rockbruno 4y ago>Keep the hiring manager happy. Better work environment, completed work - that is only possible when the manager is cooperating. What is the point of improving the workplace if the cost is being ejected from that place? Some would take this as being very manipulative, but I find it to be great advice when working at large companies. I recommend reading "The 48 Laws of Power" for similar "immoral" advice if you can stomach the implications and use them only in self-defense.
- rk06 4y agoI have been on the other side of this, and the only reason I was not fired like OP, was because I was an FTE, instead of contractor. OP’s advice is 100% on the mark. Hiring manager is the face of company. And you won’t see anyone higher if HM hates you
- m00dy 4y agowhy all managers need to be suck ?
- capableweb 4y agoNot sure how far along your career you are, but all managers certainly don't suck, there are good ones out there. If you already have a long career with lots of different managers, and 100% of them suck, I'm afraid the problem probably lies with you.
- laputan_machine 4y agoThere are so many variables it can be hard to say. I've had the fortune to have some great managers over the years. However the country you work in and your industry means that the great:shit manager ratio can vary pretty wildly.
- dagw 4y agoThey don't. The majority of managers I've had in my career have been fine to great. I've probably only had one genuinely bad manager. However stories about perfectly competent managers who simply manage their teams to successfully completing projects make very boring blog and forum posts.
- rurban 4y agonot all, just about 50% of them. problem is that the good ones get promoted, and you might get a bad one later.
- moritonal 4y agoSorry, but this is your fault. As ever, your role as the employee (triply so as a contractor!) is to stay professional and follow directions. Yes, you and your manager had very different styles, but we are in a very fortunate position that if you dislike your employer you can just leave. What you shouldn't do, is tell your obviously unstable manager to go read a book on managing, created sarcastic backlog items to mock his micro-managing and directly went against his orders publicly? Your manager was bad, but you should have done your job and politely swapped teams. Instead you're portraying yourself as a poor contractor who only slightly mocked his manager, then blasted the company on a custom built blog.
- tankenmate 4y agoIf all you ever do is run away from your problems then all you leave behind you is a trail of problems.
- ImPleadThe5th 4y agoI agree with you that OP did make some mistakes, some of which he rightfully admitted. But at the end of the day the "mature" person in the interaction ought to have been the manager. This looks much worse for Spotify than it does for OP.
- dikei 4y agoYeah, it's really dangerous to be sarcastic when you cannot see the other party face to face. If you can't read the situation, even light-hearted jokes can be taken the wrong way and sour the relationship.
- Philip-J-Fry 4y agoIf everyone just sucks it up then nothing gets solved. Ever been told to do something by a developer and you firmly disagree? I'm not going to give in and do what he says, I'm going to make an argument and hope it changes things for the better. If I just put up with the shit then it's me who has to deal with it in the future when it all falls apart. Giving in to shit management will just reinforce it. Changing teams isn't a solution if your enjoy the team. Standing up for yourself and the team is. Could he have gone about things better? Probably. But your job isn't just to follow directions, especially as a senior engineer.
- robertlagrant 4y agoSorry to read this story. It can be really dangerous to have a manager who purports to be a technical expert to their peers/boss when they are not. They will have accidentally or deliberately developed the survival skills to protect that claim. Their career rests on this fiction being perpetuated.
- jakQj 4y agoYeah, the manager trying to get the details of the PRs that he was going to take credit for is a giveaway: "I am writing tickets for you and don't want to add overhead." I hope the Spotify CEO reads this and takes action. In many companies though the CEO is in on the game (e.g., in the scientific Python space this sort of thing is quite common).
- jessaustin 4y agoI was expecting something by Lee Camp? [edit: original title was "How I got banned for life from Spotify"] Seriously though, Spotify can jump in a lake. Maybe they started out with some sort of "musicians should get paid more" thing (how's that working out for you on Spotify, musicians?), but more recently their model is "we should take a cut of every podcast subscription". I have never installed that app, and never will. I'll listen to Rogan again when they fire him and his RSS feed comes back to life.
- iLoveOncall 4y agoBetween the one-sided story, some red flags from the employee himself ("go read that book about how to manage people", etc.) and the absolute over-reaction of creating a website dedicated to being fired from a contract, I'm gonna say that the manager was probably not the one mostly at fault.
- trollied 4y agoIf I were the OP I would take this site down, and re-think. Any prospective company that is looking to hire you in the future is going to google & see this. It does not reflect well.
- rcfox 4y agoIt's like the author is looking for more bullet points to add to the website. "I made a website to complain to the world about Spotify's management, and Spotify somehow held that against me."
- peteradio 4y agoWell, no, he created the website after being banned for life.
- honkdaddy 4y agoAgreed. OP didn't like the characterization of being a "bad culture fit", but to me, spending multiple hours to build a site, purchasing a domain name, and promoting it all over the internet is exactly the kind of pettiness and poor judgement which _would_ make a bad culture fit. I would never want to work with someone who would be willing to write up public manifestos about petty coworker drama. OP was definitely mistreated, but the mature and correct thing to do is to move on and find other work. Use it as a story for the "conflict at work" question in an interview, but otherwise, put it behind you.
- batch12 4y agoIt's also been more than a year since these events and OP just registered the domain three days ago. Reading quoted chats in addition to the OPs statement "At this point these conversations felt so weird that I started screenshotting the strangest ones" makes me think they are still holding onto these screenshots. I think it's time to move on.
- Aeolun 4y ago
- xnorswap 4y agoIn summary, a contractor had an issue working with their client and instead of firing their client or trying to resolve it through the appropriate channels decided passive aggressive JIRA tickets and undermining the manager was the way to go? Unless I'm misreading this blog and its tone then this blog serves as a red flag for working with this person.
- dm319 4y agoI don't think it is undermining to discuss an issue with more senior members if it is an issue that isn't being resolved.
- trollied 4y agoAgree. You're contracting, you've probably signed a contract with your client that includes an NDA. Client engagements are supposed to be professional. Last thing on the list that I, as a developer providing contract services, should do: Create a website to specifically bad mouth my customer, and make myself look bad in the process
- lawgimenez 4y agoI have the same personality with the OP and maybe a far similar experience way back. I just quit the company and find another, how ever it may be painful to leave a job you really liked, it is so much better just not to post stuffs like this and just move on. You are also at fault too.
- Maro 4y agoThere are always 2 sides of the story. I'm sure reading the other side would paint a different picture. Having said that, based on this description: yes, the manager seems weak, but as the OP themselves state, these were annoyances. Couple of pointless chat messages, badly run meetings. Annoying, but it doesn't sound like such a big deal. Esp. in a fully remote setting, where you don't have to sit next to an annoying person all day.. Also, towards the end it turns out the manager was new at the company (first 6 months), so they were probably figuring out whatever upward reporting culture Spotify has, and maybe that's why they were asking seemingly pointless estimation questions? In any case, openly challenging the other person in a group setting and making fun of them [with a ticket], which is what happened here, is not the right thing to do (whether a peer or a manager). Good options are: (i) have a separate 1v1 where you talk it over with the person (ii) put up with it for a while and/or (iii) switch teams (iv) switch companies, if it's that annoying. On the flipside, firing a person for what is described in the OP seems like an overreaction. But, judging based on one side of the story is not a good idea. Overall, I personally cannot draw any conclusions about Spotify based on this, nor do I want do :) Also, I'm questioning whether it's a good idea to write a blog post like this. I assume the contract had NDA / other clauses that prohibit this. In many cases, those clauses are a good idea. Eg. imagine if now Spotify, with all its marketing power, were to reply to this person's claims and represent their side of the story. That would probably suck for the author here. Fortunately that will not happen.
- ghaff 4y ago>so they were probably figuring out whatever upward reporting culture Spotify has, and maybe that's why they were asking seemingly pointless estimation questions Even not-so-new managers often want to be able to answer questions about what their team has been working on and what's coming next and when.
- cspike 4y agoYeah, I spent some time imagining how terrible this was for the manager. You are totally right that I am an unreliable narrator here. I agree with you that we shouldn't draw conclusions about Spotify as a whole here. It's a big company with lots of different approaches within it. What I disagree with is that firing me was an overreaction. I think it was sensible, since we both knew at that point we could not work together.
- smcl 4y ago> "Can you tell me how long X, Y and Z will take?" > "We're almost finished with X, so only days left there. Y will take a few weeks, but I cannot estimate Z. It's something we have never done before and without exploration time I don't even know the scope of the work." > "I need the time anyway. Provide it in a spreadsheet by end of day." I feel your pain man, that's one I've had a few times before. Just a complete failure by the manager to take the point on board, followed by a demand to just do it. That's a total morale and productivity killer.
- jefc1111 4y agoMeh ... give people what they want. "I cannot estimate Z" is a refusal and I would suggest an ego-driven one. I would just say "between 1 and 12 months", or something like that. If they were then not happy with that I would go into why that is the best I can manage given the circumstances. "failure by the manager to take the point on board" is not relevant really when you think of the manager's perspective. From their perspective they have a contractor refusing to do what they are asked.
- mojzu 4y agoI've not found vague estimates to work very well at all in this scenario. Managers will just continually ask for something more specific, they want a particular date they can remember/write down/enter into some project management software.
- creshal 4y agoUsually I'll just go with "by date X we can give a reasonable estimate", which tends to work well enough with their mental model that they leave us alone until X.
- jefc1111 4y agoYeah that's a good pragmatic approach. "I can't estimate that right now but if I spend half a day on it I can give you a figure".
- xzv 4y agoWhy do you do contract work still? Surely you should be able to find a full-time gig at this point?
- bilekas 4y agoSome people much prefer the contract lifestyle it can offer. It's not entirely strange to be honest.
- jamil7 4y agoNot sure if it's the case in Sweden, but you can often make much better money contracting in Europe.
- TickleSteve 4y agocontract work pays much better in many parts of the world, in some cases double. That makes it an easy equation to solve.
- jokethrowaway 4y agoGenerally, it's to pay less taxes and make more money without holidays and sickness and protections developers rarely need
- philipwhiuk 4y agoIronically the author really needed a union rep of course.
- abofh 4y agoContracting provides an immense amount of flexibility that FTE's don't have - from the amount I can put in tax advantaged retirements, the amount I can bill, my ability to maintain multiple client loads and the ability to fire my clients - it'd be hard pressed to be FTE somewhere looking for 9-5 ever again. On call? Bill. Useless meetings? Bill. Travel time? Bill. Overtime? Bill. Waiting for the IT department to get something done? Bill. Don't have enough work but you booked for a 40 hour week? Bill and work on another clients stuff. Clients infrastructure is a mess and they refuse to take advise? Some combination of bill for the time, fire the client, or suggest additional time to focus on their issues. Don't feel like working today? Don't bill, go walk the dog. I'm able to estimate my value on the market in near real-time, get cash instead of theoretical optional value, select clients on any metric I choose, and being able to live (virtually) anywhere I want in the world while maintaining a client base wherever I want - it's a pretty awesome gig. If I want to take a summer off? I just offboard clients and turn off inbounds until I'm ready to take on more. Why do you still FTE? Surely you should be able to fill a book of clients at this point :)
- hunglee2 4y agosounds like the manager really needed that estimate (!) that part of the story was really a microcosm of the gap that exists between individual contributor vs manager; the former 'does the work' whilst the latter needs to report the progress of that work 'upstairs', an archaic yet persistent organisation of labour
- mugsie 4y agoSounds like the manager was in over their head. Engineering team will always have items that are very hard to estimate without doing background work. A good manager would have said "what do we need to do to figure out times?" and then "Can we timebox that research to a sprint / two sprints / etc?" are reported the horizon one timescale up.
- hunglee2 4y agooh yeah sure, the guy was out of his depth, scrambling for numbers to support the story he was telling upstairs
- mib32 4y ago"When the X will be done?" "Tell me when it's needed to be done!"
- 4dregress 4y agoThe best solution would have been to escalate these problems to the managers line manager. It’s clear they were having problems which were impacting the team. Where I work we don’t have “engineering managers” our line managers are other engineers in different squads as I think it is great! In a previous company we did have an over zealous manager and the team feedback through the correct channels and the issues where resolved. This was also a team made up mostly of contractors who all had strong opinions. I thinks it’s important to remember that it was a really tough time for a lot of people during the lockdowns so maybe that factored into these issues.
- cosmiccatnap 4y agoThey did that in the call and it cause the initial conflict...
- vasco 4y agoWhenever you think about creating a public post like this on a company, consider first if you have grounds for suing them. In some countries, instead of suing you may instead look up if the situation has grounds to report them to the relevant regulatory entity (health or labor violations for example). If you don't, it is likely that the temporary satisfaction of publicly shaming the company will be less than the nagging feeling of forever doubting if you didn't get a job because someone read your previous post and thought you'd be "difficult" to work with.
- possiblelion 4y agoUnfortunately even with great companies where the "floor" of technical ability/intelligence/whatever is of course higher than the general population; there exists the same percentage ratio of competent people to non-competent people. A somewhat non-competent manager is actually fine in my experience, if they trust their team to know more about technical topics and try to stay pleasant. This case obviously wasn't one and I'm sad to hear it. However, as a young and aspiring start-up founder, these stories are a great help and inspiration on how to structure my own company to avoid, or rather, minimise such clashes. Thanks for sharing!
- PragmaticPulp 4y agoThe manager’s described behavior is bad, but the author’s reactions and responses are also bad. This reads like a meeting of two flawed personalities, neither of whom is willing or capable of adapting to difficult interpersonal situations. The appropriate response to the (obviously) unhealthy manager in the situations described is to tactfully de-escalate while beginning the process of switching teams. Instead, the author seems fixated on “winning” every disagreement. If you think you can undermine your manager and backseat drive their processes, however flawed they may be, you are not going to produce positive outcomes for yourself or the team as described in the article. A common misunderstanding of less mature employees is that only one person can be in the wrong in an interaction. The author writes as if the manager’s wrongdoings are a free pass for them to respond however they felt like, but the described responses come off as petty and unprofessional. Both parties can be in the wrong in interpersonal conflict situations, and these writings are a good example of what that looks like. Going so far as to create a website publicly defending one’s behavior while seemingly oblivious to the fact that the described behavior is not a good look is an immature move. If I found this person’s resume in our application queue I would be extremely hesitant to hire them anywhere except maybe under the close guidance of a very strong manager who could mentor them closely and who wouldn’t hesitate to remove them from the company if they started demonstrating signs of combativeness or being a disgruntled employee. Advertising your “disgruntled fired employee” status online is not a good look, especially when you describe your own unprofessional behaviors in the process.
- peteradio 4y agoIt seems like a genuine story at least, flaws are full front. Its not like some story I read where the employee was perfect and the manager was totally awful (from employee pov). This manager sucked something fierce, probably contributed very little to the company and through their inadequacy took it out on their employees. Dude here awkwardly plowed through it and was willing to make it work, he never really undermined his manager in ways that the manager did not already set himself up for failure. Why should a manager/manager's manager leave such a lasting impression on the hiring at Spotify vs dude here who worked longer than both on Spotify product? As far as hiring him, you know what you will get, he will probably have good instincts for dumb assholes.
- a254613e 4y agoEven in this completely one-sided story, out of which I'm sure many parts are missing or are presented as favorable to the employee, the employee sounds horrible. I wouldn't want to work with someone like that neither. Was the manager great? Absolutely not. Does the employee come off as someone that's a good culture fit in pretty much any work environment? Absolutely not.
- deleted 4y ago[deleted]
- andix 4y agoThat's a difficult story. There have been mistakes made at both sides. But I really get the author, some managers are just impossible to work with. And their strategy to protect themselves is to blame their employees. They have the ability to present the slightest mistakes as enormous problems to higher ups. They are just tricking and blinding their higher ups and stay in business for years. And everybody below them is just suffering.
- keraf 4y agoI've been in the same boat, twice. It's unfair and frustrating, especially when you feel you contributed a lot to the company and everyone else except these few managers showed appreciation towards you and your work. I also felt the urge to denounce their unprofessional behavior online, hoping that someone else would not end up in the same position as me, or make their customers aware of how bad their behavior is towards employees. But the truth is, it would not change anything and just paint me in a bad light. After reflecting on my experiences, I found that we were just not a fit. Their way of working was not aligned with mine. Instead of changing myself to fit in or them to accommodate me, we clashed and it ended badly. Both are at fault, I take the loss and move on to the next gig. Found my happy workplace now and I'm using these experiences to spot potential red flags early.
- jeroenhd 4y agoWeird to dedicate a domain to the story of how you got fired. Oh well. Without hearing the other side of the conflict, this whole thing could mean multiple things. It's possible that the manager himself was a bad culture fit, for example. If the manager wasn't actually a bad culture fit and his managing clashed with the author of this blog, then the author is actually a bad culture fit for Spotify. This is exactly the sort of problem I can easily see brewing with remote-only development. Conflicts escalating in DMs, opinions stewing on both sides because if limited interaction, and no good way to get body language across that might help add understanding to the situation. Telling your manager to go read a book on managing seems like a terrible idea. I don't know in what mindset this is acceptable. Using sarcasm and mocking someone remotely is also a terrible way to get your point across. Then there's the Kanban board thing. It's great that you communicated the problems you've been having in the sprint system. It's great that you came up with a working solution. What's not great is implementing this behind the manager's back. You can't go "oh yeah we changed the way we do this" to your manager and get defensive even if the team agrees with you, you should've taken his opinion into consideration before you even came up with a solution. Questions like "how long do you expect x to take" seem pretty normal to me. As a developer it's obvious that there's no real answer to this that will satisfy everyone, but companies need long term strategies and predictions to shift resources around. Dealing with this uncertainty is a manager's problem but asking for an estimate is hardly the unacceptable crime against dev teams that this blog makes it out to be. Reading through the emotional descriptions of what happened, it seems to me like both parties were heavily affected by covid, lockdowns, and forced remote work, but neither side seemed to get much of an understanding from the other. I think it's unfair to blame either party for this. I don't think there's anything wrong with publishing your experience per se, but come on, put it up on a blog somewhere, don't dedicate an entire website to the story of how you got fired. That just seems petty.
- mugsie 4y ago> I think it's unfair to blame either party for this. For the firing / termination of contract? Sure, everyone sucked. For termination tagged with a reason that meant that the OP was blacklisted, and interfering with them being hired by another team? HR and the manager definitely are to blame, and should be called out for it.
- mechanical_bear 4y agoI haven’t seen a more obvious case of someone pulling the tail on the cat and then being surprised when it scratches them. Then blogging about in a way where you try to put others on the hot seat. Take some ownership of your life.
- deleted 4y ago[deleted]
- jmyeet 4y agoAfter reading comments here I thought after reading this I would largely agree. It's true that sarcastic tickets don't help but they're not a fireable offense. It should be noted that this is one person's account of what happened. It's not clear to me where this contractor was. Sweden? Even as a contractor, knowing what I do about how large companies work, a manager can't typically just fire somebody. There is an HR process that needs to be followed. For people saying he should leave and/or put his head down and do his work, that seems to be part of the problem: the constant interruptions. I've had this situation before. In some cases I've had some success with "you've just asked me to do Y when I'm doing X. What do you want me to do: X or Y?" For decent to good managers they understand this is a prioritization issue. But for other managers this is viewed as insubordination. Managers have to be held to a higher standard by the company because a bad manager can do an awful lot of damage to the career of their reports. Unjustifiably low ratings, subpar ratings that may make team transfers impossible, even PIPs for really no good reason. Companies should be hypersensitive to bad managers but so often they just aren't. Bad managers will shift blame for their own failings and it can be extremely hard not to be collateral damage before you realize what's going on. As for Spotify not hiring this person back, that's just standard HR policy BS. There's probably not much you can do about that.
- laerus 4y agoIn my place the manager and the product manager make decisions about the design and architecture with the excuse that they have worked with related projects in the past. They constantly go against the suggestions of the lead dev and ask about estimations (sometimes twice a day) even before the requirements and the specs are clear. I think if devs were more desciplined we wouldn't need mediocre managers to tell us how to do our jobs.
- Aeolun 4y ago> I think if devs were more desciplined we wouldn't need mediocre managers to tell us how to do our jobs I’m kind of aware I need someone to bring me back down to earth once in a while. It’s still annoying when it happens, but necessary. Fortunately right now I have a manager I’m actually quite happy with (like, I feel like we can have a dialogue).
- naoru 4y agoSheesh. I had my fair share of bad interactions with management but in the end my contract termination landed me a much better job. And even much better afterwards. Huge corps with a lot of middlemen tend to become authoritarian, competent people who kickstarted the whole affair are being replaced with yes men^Wpersons all the time because at larger company sizes loyalty is much more preferable than hard skills (I'm not implying that I was competent, that's for others to decide, but I wasn't only one who got the pointy end of the boot though). I deeply sympathise with the guy, but there's time to enjoy and there's time to move on. Holding grudges against some kronenbergian bureaucratic machine ain't good for your mental health.
- bluehatbrit 4y agoWithout seeing the other sides it's impossible to really know where the relationship broke down. That said, the thing that surprises me most here is about how much the author and employer seem to be treating the authors role as an employee. In my experience contractors will often leave some sort of a longer term impact on a team they're there to perform the work as requested and get paid. The relationship here seems like it flicks back and forth between contractor and employee which feels confusing at best. Sometimes contracts don't work out, you fire them or they fire you, and you all move on. If this was authored by an employee then I'd get it and say maybe it sits somewhere around unfair dismissal, but as a contractor this is kind the gig - right? You work to keep a professional relationship where they pay you and you deliver the work and that's it. You get the benefits that come along with all the tax efficiencies and not having to participate in the corporate games as much, and they get a flexible worker who they can get rid of if things aren't working out.
- stapled_socks 4y agoNot saying it would solve ALL the problems described in the blog post, but keeping these conversations to shared channels would be the first thing I'd do. I my experience, the chance of professionalism goes way up and the risk of miscommunication goes way down when anyone can read the messages.
- SnowHill9902 4y agoIt’s okay to contradict your boss and even get into a heated discussion. That can be respected. But at the end of the day, after those discussions, you have to do what you are told. This reads as insolent behavior.
- weezin 4y agoWere there no retros? A lot of this stuff could have been addressed in retros. That being said I would not want to work with the person that wrote this blog. If you have issues address them separately with the manager not undermine the manager publicly repeatedly.
- tomohawk 4y agoNumber one rule of being a contractor: you can't care about the problem more than the customer. If the customer doesn't care about it, you're not going to be able to make them. If the customer cares more about some inanity (such as the processes they follow) than the problem you're there to solve, that's just how it is. If you don't like it, then find another contract.
- deleted 4y ago[deleted]
- nmalaguti 4y agoThe lack of empathy in the comments here is worrisome. The manager was clearly failing to manage effectively. Blaming the engineer for not managing up with a manager who didn’t want to listen doesn’t make sense. This scenario is my biggest fear as a people leader - that ICs are being mismanaged and I won’t be able to see it or intervene before it is too late.
- deleted 4y ago[deleted]
- mrcartmeneses 4y agoSo what you’re saying is there are sections of Spotify that have completed the inevitable metamorphosis into the Russian Communist Party circa 1970?
- antris 4y agoThere's lots of people pointing out that the developer in this case wasn't perfect. But the underlying problem here is an organization that's supposed to give autonomy to developers, with a manager that is actively working against that. The manager, by looking at their actions, seems to want the team to take responsibility for their work, yet wants also to command and control the team. Often hiding behind indirect threats and "guidance". Sure, if a manager is bullying you like this, eventually anyone will buckle under the pressure at some point. Now, if you come from an organization that is built for command and control, then also as a developer you are able to shift the responsibility to your manager and never do anything unless the manager explicitly tells you to do so. However, here the manager tries to have their cake and eat it too. They want you to do as told, yet take the blame if something goes south. This is extremely common: pretend that developers have autonomy, but still use control in subtle ways. If problems arise, you can blame the developers and the manager can wash their hands, because "it's the teams decision". It's a recipe for disaster, and when this eventually blows up, it's very nitpicky to blame the developer for making mistakes in such an environment that's set up for failure. Also, see the difference between the manager and the developer when they make mistakes. The developer promptly realizes going too far and apologizes. Meanwhile the manager shifts blame, denies their subtle control and keeps gaslighting the developers into thinking its all their fault. Another huge red flag is the backchannel communication and vague reasoning behind the firing. If a manager cannot have a direct conversation with all affected parties present, they are very likely to be hiding something. Firing someone without an open discussion first is just insane.
- doix 4y agoI feel like the author might benefit from reading a blog post that was posted on HN a while back[0][1], specifically the "two and done rule" and the "do it anyway principal". Yes your manager is wrong, but the way you handled it is very immature. There are "shit" managers everywhere, if you get one, suck it up and start planning your escape. If you really want, you can go higher up the chain and raise your concerns. If your concerns are dismissed, just drop it, there is nothing to gain by fighting. I also think that you made mountains out of mole hills in some situations. The time estimation "catastrophe" wouldn't even phase me. I'd just say some very high number (3-4 months) and if they weren't happy, I'd just reply "when we start working on it we'll do our best to pull it in". Yes it sucks that you have to do that, but you should really learn to play the game, at least a little bit. [0] https://madned.substack.com/p/an-old-hackers-tips-on-staying-employed https://madned.substack.com/p/an-old-hackers-tips-on-staying... [1] https://news.ycombinator.com/item?id=28141203 https://news.ycombinator.com/item?id=28141203
- treis 4y ago>your manager is wrong, but the way you handled it is very immature. There are "shit" managers everywhere, if you get one, suck it up and start planning your escape. They don't even sound that shitty to me. Managers like everyone else in the world have to work within the constraints of the system in place. Like Scrum vs Kanban. Maybe the manager couldn't care less but their director is the biggest Scrum cheerleader ever. And maybe they're getting hounded for the estimate and just need a number. And maybe skipping the internship program looks bad for the manager. And so on. Even if it's all the Manager's fault there's far worse sins in the world than dictating a methodology or asking for an estimate.
- watwut 4y agoThe manager went with Kanban, but expressed disappointment and looked "visibly annoyed". While the event does describes disagreement and sort of conflict between op and manager, I don't see anyone acting badly there. Its only significance seem to be that this might be one of reason why manager did not liked op, which yes, can happen with some personalities. But, op does not provide any part of story that would show that.
- ABraidotti 4y agoI'm sorry this happened. I sympathize with this guy! But a lengthy screed against a former employer is not going to open any doors, no matter how accurate it might be. Ideally, every nuanced interpersonal conflict could be handled by dialogue, but the typical hiring process doesn't allow for that. Personally, I wouldn't take the chance of ruining my own reputation by hiring a candidate with a site like this.
- matsemann 4y agoHow is this not abuse of employee laws by Spotify? If you're a single contractor hired to work as a normal full-time employee, you should have the same protections and rights as a normal employee.
- geuis 4y agoSorry, but this is an incredibly immature response from @cspike. You lost a job, just deal with it. Take whatever life lessons you can from it and move on. Creating a custom domain and setting up a one-off, one-sided story doesn't serve them or anyone else. Are you expecting this to somehow get you your job back? Or just to make yourself feel better by getting proverbial pats on the back? What you're actually doing is shooting yourself in the foot for future potential jobs. If you ever want to mention in your CV that you created and maintained a chat integration app for them, then anyone who ever read this thing will immediately connect it with you. You need to both take down your pity blog and delete this post on HN. Its not going to do you any good in the long run except to hurt your prospects.
- prmoustache 4y agoThis title and the linked website is strange. Regardless of the story and who is at fault, I wouldn't expect a company to hire again someone it had fired previously and I understand an HR department acting in a cautious manner. I also dismissed candidates that seemed ok on paper but had that huge red flag in their history.
- takethat 4y agohi Stanislav, thanks for sharing your story! Your manager was wrong and you were right. The only mistake you did was tolerating that behaviour for a long time and taking it personally, imho. If you feel you're in a team managed inefficiently, raise the flag, talk to the manager (once), if that does not work, resign on your own and let the manager's manager know why you take that decision.
- mechanical_bear 4y agoThe employee was wrong and weasel worded their responses: > “ Do you want to own product X?" > "It is a low maintenance system so it takes very little of our time. It's not expensive to own it." > The manager was displeased. Of course the manager was. They asked a straightforward question and didn’t receive a straightforward response. Multiple times. Once again: > Do you really think product X aligns with our team's mission?" > "Historically I can see why we own it. It sounds to me that maybe you don't want us to own it?" The response, again, does not answer what the manager asked. Employee goes on to write parody tickets. Employee goes on to grandstand in front of other manager, instead of taking it “offline”. Employee goes on to demand witnesses to simple meeting. Manager has had enough of employee’s nonsense, terminated. I don’t see how anyone could say it so authoritatively that the manager was wrong and employee was right. Unless you are just trying to coddle them, which if so, carry on.
- soneca 4y ago> "The ultimatum to produce an estimate ruined my entire weekend." I think my work-related superpower is that stupid things that happen in the work doesn't bother me at all. I would just give an estimate at the same conversation when the manager insisted. Sure, I would phrase it in a way to explain how weak was that estimate. Something like "It's new to me, I have yet to study the scope, it's subject to change in scope until then, and other tasks getting prioritized. That said, I would guess two months". And then I wouldn't think about that at all once the conversation was over. If those "two months" is used against me later on, I would explain the reasons why the initial estimation was off again. If I am still blamed for a delay, I would probably start looking for another place to work. Also, I would never try to "trap" my manager into a conversation with the Product Manager just to show them how right I was and how silly they were to ask a precise estimate. EDIT: I wrote a long reply to someone who has now deleted their comment asking how one can learn to not care. I took some time thinking about it, so to not waste that time, I will add my reply to the deleted comment here. Ha! There is a reason I framed it as "superpower". Seriously though, I had that conversation with my wife a few times. I just don't care about a lot of stuff, but she does. My advice to her "not care" is useless. Worse, harmful depending on the tone I use. But I do have some reasoning about how I developed that. No idea if it works as advice for other people though. First, I am 42 years old. I always kind of didn't care for a lot of stuff, but getting older makes it even easier. I think this usually happens to everyone. This is what I would call "wisdow". Learn about what not to care (and what to care more about, like community, time with good friends and family). Second point, check your ego. You feel offended if something hurts your ego. If you make knowledge about good software development practices a point of pride, your self-identity, your self-value, it will be hard to let it go if someone just don't get it. Or go actively against what you believe to be true. For example, I doubt that if the manager instead insisted in the author giving a precise number for tomorrow's temperature, that they would be that bothered. That it would have "ruined their weekend". They would just think that their manager is silly, that they don't understand how weather works, take look at weather.com and tell them whatever number showed up there. And that's it. Third point, understand that people take time to learn new things. Don't fight with all your forces against someone's opinion at the moment you learn about them. Learn to accept that you can voice your disagreement, explain your reasons, and they will remain thinking exactly the same at that moment. But if you are really right, with time, they might see it. In this case, give the estimate they wanted. Then, make a note to, when you get to that task, you will be studying the scope better and update the manager about a new estimate. Then, while you are working on that, make a point to make it clear that some urgent tasks or a bug, delayed the work, and pass the new estimate. Hopefully, when the task is done, they will understand better how that initial estimate was imprecise. And proabably didn't help anyone at all by having being created. OR... be open to learn that the manager, for some reason you didn't understand at the time, actually needed a number. I think that leads to my last point. Remember that you could always be wrong. Consider that there is a chance (even if you put that chance at 0.0001%) that the thing is not actually stupid. It just look stupid to you. It might be odd, or stupid but not that stupid, or stupid but for a reason, or not stupid at all and you were being stupid thinking it was stupid. If you always consider that there is a chance you are wrong, stupid things bother less.
- gnull 4y ago> Do you want to own product X? It's the team's decision. > Maybe the intern can learn the ropes This is what I hate about work environments that pretend to be all caring and non-hierarchical. Like the author, I worked in Sweden and I've seen examples of it. They avoid specifying clear rules for where one's responsibilities end, and who gives orders to whom, because that would be oppressive — and oh, we're too nice for that and we don't want people to feel bad. But the hierarchies and oppression don't go away if you pretend they don't exist. They're still there, they just take a new, less explicit form and give freedom for abusers to play around the grey areas. What I see the manager doing here is trying to push for some decisions without making it explicit and taking responsibility for it. I find it cowardly and harmful. People who are not interested or are unable to play with this niceness game are the ones who will lose in it. In a healthy system, a manager could just say, “we use product X, that's my decision” or “no, I decided we're not spending money on that” — optionally, motivating the decision. And later be held accountable for it. In a system too focused on being nice and not making people feel bad, a manager does not want to look oppressive and will have to make it look like this was everyone's idea, or choose a phrasing that will not directly say what the quotes say, but kind of imply that (“What do you think? Should we use product X? It's team's decision”. “Maybe we can go without spending money on that”). > it is also the Spotify convention of the right way to do things Another thing people of this sort do is insisting on their opinion by saying things with a tone of a convincing argument but with words that don't really address the point (“Didn't we agree on this already?”). If the other side is less experienced in fiddling with politeness, they may feel like they are being too persistent and mean objecting for 5th time. Telling this sort of abusive manager they are talking nonsense would sound mean (sometimes this would be the right thing to say though), and playing on their level is doomed to lose. Direct confrontation is normal, giving orders is normal, telling people they are/were wrong is normal. These should be acknowledged and regulated, not ignored.
- bayesian_horse 4y agoI think these HR systems also use "bad culture fit" to encode red flags they can't legally record: health issues, political disagreements. This already dubious mechanism can get further abused by badmouthing.
- cs137 4y agothese HR systems also use "bad culture fit" to encode red flags they can't legally record: health issues, political disagreements. This is absolutely the case. That said, you're probably not going to get fired over your politics unless you're either (a) seen as a union supporter (or, worse, organizer), or (b) so far right you've already been cancelled and are now a PR liability. If you're in the middle, they usually don't really care who you vote for, at least not enough to punish you for it.
- emilfihlman 4y agoI find the negative comments here very surprising and absolutely sympathise with op, especially the inane banned for life aspect of this.
- raffraffraff 4y agoYou live in Sweden? https://gdprhub.eu/index.php?title=Article_17_GDPR https://gdprhub.eu/index.php?title=Article_17_GDPR GDPR. You have a right to know all information they have about you on file. You have a right to get the information rectified. You have "the right to be forgotten".
- nailer 4y agoDoes GDPR apply to employment data? I wasn't aware of this.
- cs137 4y agoThis is atrocious and in a better world there would be physical consequences for people who pull things like what was pulled against OP, but ultimately, this is not unpredictable or surprising. The truth of the corporate world (we say "corporate America" in the US, but we've exported this disease all over the world) is that, as a subordinate, you exist for one reason: support your manager's career and reputation. Do that, and you can be sub-mediocre and you'll still get promoted. Miss that objective, and it doesn't matter what good you do for the company--you'll only piss people off more if they figure out what you're capable of. Bosses fire first the people who make them look bad and second the people they perceive as costing them time; competence is only a third- or fourth-order tie-breaker. The story starts off as a typical tale of a shitty manager who knows he can't motivate shit to stink and uses abusive practices ("end of the day" requests for things that aren't actually urgent, insistence on hard estimates that will turn into deadlines) because he thinks it's the only way to get work done. Where it gets disgusting (although, sadly, not surprising) and reaches the point where, in a better world, people would be held physically accountable, is where the disagreement with one manager leads to him being blacklisted within the entire organization. It shouldn't be this way, but unfortunately it is. I don't see a fix for this problem. A union could guarantee your job, but it'd probably be no more than a severance period insofar as the incentives on other hiring managers to circle the wagons (that is, ghost you upon realizing some other manager had a problem with you) are strong. The union would make it harder to fire you, but you'd never be seen as anything more than a problem by management. I know someone who was able to prove his boss was playing favorites--he got his performance review fixed, and his boss fired--and he still wasn't able to last longer than six months, because of his internal reputation as a "boss killer". The thing to understand is that corporations would rather be wrong and consistent than risk inconsistency, and they would rather put up a unified front of wrongness than allow anyone at the bottom to divide people higher-up against each other. Managers protect their own, always, even the ones they know are shitty--this is the same problem that exists, in the US, on police forces--and those who aren't willing protect the class get thrown aside. The OP had to be blacklisted in service to corporate consistency; to do otherwise would embarrass his manager and, ultimately, the company decided (as it always will, since to render any decision contrary to preexisting rank would be inconsistent by definition) the manager was more important than he was.
- 4y ago
- philipwhiuk 4y agoSeems very odd to be sending a contractor on training (or trying to).
- dsr_ 4y agoA corporation's culture is what it allows to happen and doesn't fix. My major takeaways from this: * Spotify doesn't have good oversight of their managers * Spotify doesn't value their individual contributors enough to provide them with a clear problem resolution path for this situation * Spotify has an HR shadowban procedure * The author doesn't have (or didn't have) great coping skills when presented with a corporate political problem outside of the usual context
- kcplate 4y ago> Spotify has an HR shadowban procedure Not sure about Sweden (where I assume this situation took place), but it’s common in the US to have “Ineligible for rehire” flags that can be placed place on a terminated employee’s file that effectively blacklists the employee from working for the company again. I can envision a situation where a person is terminated, another manager sought to hire the termed employee and HR stops the process because they employee doesn’t have rehire eligibility. Prospective future employers of the employee can contact the other companies the employee worked for and most HR departments will confirm employment, confirm salary, confirm hire/end dates, and will confirm rehire eligibility status. It’s why it’s really important to try and avoid getting termed for cause in the US…while it’s not a “blacklist”, it certainly can follow you.
- lakomen 4y agoI was un both situations. 1. Was at a startup in the 2k bubble. I was apparently unofficially made lead of a project. I was in way over my head. The company was about 50 people, most from other countries like Russia and Romania. I didn't even know what my role really meant and I struggled to learn C++ and now I was supposed to code on my own. The CTO wanted a flowchart, which I created together with the project manager, some older but nice guy from Iran. The CTO said it was ok but too detailed. There was a female intern doing flash. Well being an intern she couldn't pull that intro movie off and asked me for help. I had never done anything with flash and had no clue. I suggested she experimented and asked around on forums dedicated to flash movies. One of the Russian developers was a cocky bastard. He was experienced and had created a prototype in like 2 weeks. I felt useless, because that's what I was. Why was I made lead for this project? Because I said that we'd get it done, despite other devs, country native, said it was hard. But I thought being optimistic was good, you can't start something and believing it won't ever get done. Well I had an issue with my title and the Russian guy delivering and snoozing with the project manager. I felt left out, the Russian didn't respect my position and I started yelling at the morning and noon breaks. I got mental and called in sick. A few weeks later I got fired. It was my 1st job in the IT industry, early 2000 bubble. The company was a disaster. Open bureau with 4 people sitting on round tables 4 PCs. Wifi, computer electrosmog, no privacy, some young guy listening to loud music irritating everyone. The "ship" had three upper etage, owner, the middle, crew, and the underground, admin hell. All admins ever did was say no to requests for hardware and play games and chat all day. It was funded by a prominent TV moderator's brother. In the end they spent too much on booking Reamon so they couldn't pay the bills anymore. Funny thing when it all went downhill the "sail" outside went loose and the rats (employees like me) were leaving the sinking ship. The investors got the hardware, the boss and his wife fled to a nearby country and sold the product to a prominent telco cashing in big time. We sued because we didn't get our pay. We got nothing and were forced to drop the charges or else pay a big sum for the justice system. Anyhow I was really mad at that cocky Russian guy, so that was my "manager" part in this story. The other story is I was a contractor fixing some database import script in PHP. In PHP warnings aren't errors. I fixed the script but when ran it returned a warning, however doing its job. I sent in the script and got yelled at by some guy 10 years younger than me. WTF! Ok I did a file pointer check and did add a @ to suppress the warning. Sent in the script and never worked for this house again. I don't need to take abuse and that's where I draw the line. Sure he was right to criticize the warning but he stepped over the line by yelling and being rude. I didn't respond in the same way he did, but I was close to, because I don't take shit from anyone however I'm professional enough to remain civil. The way I read this case is you both did wrong but you're a contractor and it's the way it is, you have "no rights", even if you do. You get paid way more than the employees and you're free to go if you don't like it. You're not part of the family, you're an external asset. It's not your job to fight or change structure. Yes, you're the Russian from my story, more talented. But just do your job and if you can't, quit or talk to the manager you have a problem with. If that leads to no result go higher but do your job. You got cocky while being in a weaker position. And you paid the price.
- daniel-cussen 4y agoFired? Got fired? Just say fired. I've gotten fired, I've also gotten dumped. I can't hate on women for dumping me, they don't owe me anything, just accept the dump and move on. Sometimes it's better not to question it much, second-guessing the woman, it's over that's it, next. Well there's times not, like if the employer created the expectation of long-term employment, that's a debt. If he enters debt, that's a debt. If he cheats you of wages, that's a debt. Gotta collect. I have taken them to court, that's the whole point of a contract, enforcing contracts. Some people said that's violent but in fact it's the exact contrary, the only anti-violent resolution. If he just says, hey this isn't working out, in good faith, like doesn't extend a contract, fine. What needs to happen is it be more viable to do your own thing, be an entrepreneur. That was the case in the 19th century in America, after the Civil War, men just went and did their own shit. A farmer is an entrepreneur. Panning for gold is entrepreneurship (open even to slaves in the case of Brasil, you could earn your freedom in less time than the voyage). Bitcoin mining is entrepreneurship. And of course all the businesses in the Long Depression (which was not a modern-style depression like the current depression, but rather an industrialization process where everything kept getting cheaper, deflation through industry).
- rswskg 4y agoThis happened and he made a website about it? yikes.
- toyg 4y agoBad managers exist. If you'd previously managed to be in the industry for years without ever meeting one, well, you were lucky. You're clearly an enterprising and autonomous fellow, so chances are this won't be the last time you clash with "the man"; hopefully next time you'll be a bit more careful when picking your battles. But: this shit should stay offline, man... recalling an anecdote or two is one thing; buying a domain just to go on for several pages, with detailed descriptions of months of interaction with somebody who could be deanonymized fairly easily, is borderline libel. This won't get you back a job at Spotify, that ship has sailed. Put this effort into finding new clients - a task that won't be helped by having googleable proof that you can be "hard to work with", which is what this is.
- deleted 4y ago[deleted]
- mib32 4y agoIt's interesting, how much this question is controversial. I also have had similar problem. It was a bit different, but similar. Much time passed, but I still can't understand who was right. But I also can't understand, why I was fired, and the manager stayed. Was it me who is wrong, or the manager? I think it would be good to reach some kind of consensus. Is it okay for the manager to be rude and not listening to needs of developer?
- rk06 4y agoManager is higher in hierarchy, so manager stays. Contrary to naive belief, company is not fair and unbiased institution. OP should have left the team at first opportunity.
- mib32 4y agoThe problem is that, according to OPs Linkedin, landing at Spotify was a huge career goal. I think that he really thought high of himself + really wanted to stay. Maybe he even did not realize that he is "just a contractor".
- mib32 4y agoBut isn't it one of the manager role goals to keep the developers churn down? I wonder, how is this balanced, when it's more important to have the correct subordination, or keeping the churn down.
- deleted 4y ago[deleted]
- Patrol8394 4y agoThis is yet another great example of how HR only works in the interest of the company and never for the employees. I have never trusted HR, managers and alike. I would have simply left, no worth it discussing with a manager that clearly was no fit for that role. Also, the role of an engineering manager is simple: facilitate their reports work, support them, care for their career growth, clear any roadblock. The priority number one for them should be their team. After reading this story, I am not sure I will ever consider working at Spotify.
- cosmiccatnap 4y agoIt's very sad to see the amount of people here blaming an employee. I think under these conditions they didn't do anything more aggressive than the manager. Calling out a manager for bad behaviour shouldn't be vilified like this, especially when they are doing the same up the ladder to you. I think HN is just soaked in "fellow kids" types who are trying to stay hip and trendy and get their startup seen. This isn't a site for tech junkies, it's a site for managers and they hate hate hate that this describes many of them.
- rurban 4y agoSounds almost like a Booking.com manager. You could have switched teams, but normally such a manager is fired first, and the conflicts resolve itself automatically. In this case your ex-colleagues will leave sooner and later, and middle-management will notice when it's too late.
- andrew_ 4y agoThis makes Spotify look like Agile hell. Agile for the sake of Agile. Agile in name only. Looks like OP learned a lot from this, that's good to see. I had a similar snarky, snidely-playful, and unfiltered attitude and approach early in my career and it did me no favors. I made a lot of adversaries, had pay raises blocked, had promotions blocked, and had to bounce around a lot as a result. I landed under a few outstanding mentors that showed me that I didn't have to be that way, without sacrificing who I was, and mostly avoiding politics. That changed the trajectory of my career. Only big point I want to make is that Spotify may have been a startup, but it's now corporate. Many startup signs may still be there, but when Agile is a religion, you've gone corporate. Corporate environments are always going to be about playing politics in addition to whatever your regular job is supposed to be.
- bickering123 4y agoHaving been a manager and made the decision to never manage anyone again if I can avoid it. Nothing is more irritating than having a direct report start bickering nonstop. And by bickering I mean: Constantly turning every small discussion into an open ended micro argument. This is not “push back,” or “feedback,” or “input.” This feels like they are deliberately creating friction on every single decision to prevent productivity. It is a sort of strategy to avoid being managed and avoid doing work. It is also a nonstop questioning of your authority and it erodes your ability to manage them in a really sinister manner. Reading this story, it felt like the engineer was doing that. If you have never experienced it yourself, it is hard to stare just how irritating it is. Example: “ok, can you fill in the spreadsheet. I have to show something on Monday.” Them: “why are we using spreadsheets and not JIRA. Spreadsheets are not scalable.” Repeat this process across every single decision and it becomes completely intolerable.
- goindia 4y ago
- wayne-li2 4y agoI feel like half the comments here didn’t read the article and are basing their comments on a few top level comments. After the reading the article in its entirety it is clear the author acknowledges their own faults. In the “passive aggressive ticketing instance” the author clearly mentions that it’s a misstep on their end. The author also concludes with a possible perspective from the manager’s side. The article is not a rant. Its tone is balanced. It does not bash on Spotify. The author does not portray themselves as gloriously right. Of course it’s a biased article, but that’s to be expected. It reads like someone’s personal blog.
- AngeloAnolin 4y agoThere's always other sides of the story. Would love to see/read the story of the manager and the manager's manager who have also left Spotify provide their take. Clearly, with the person identified, the managers were painted in a negative light that similarly, this could be detrimental to their future aspirations. Lots of Spotify folks here could also attest to the story and perhaps provide their own take. Would clear any doubts and set the record straight.
- haspok 4y agoSorry to be blunt, but for a contractor to publicise their internal affairs with one of their named clients is extremely unprofessional behaviour, and I am wondering if they can be sued for damages. Even if they had been an employee this would have been questionable at best. If this website is for self-healing purposes, then that's fine, but should not and does not need to name the parties involved. (Do I see it clearly that the author even remains anonymous?)
- vladcodes 4y agoApart from higher compensation of your work, that’s the fun part of being a consultant, right? You get your payment and you move on.
- comprev 4y ago
- steveBK123 4y agoThese situations are best handled by leaving on your own timeline. Working for a manager who has strong but opaque opinions/thought processes is the worst. It’s like they think they are a grand master of chess moving pieces around the board and don’t want any of the pawns to know the grand strategy. I worked for a guy that insisted on having the hour++ long sprint retros every 2 weeks in which we’d get the same feedback from devs that he would argue against within the meeting. Sometimes he would complain its the same feedback, other times he would decide to have an argument over it. But always he would insist that the retro is super important to get devs feedback as part of the process so we need to keep having them. We would use physical post-it notes on a white board even though it was out in an open floor plan so other teams could watch/see, and we had 1-2 other offices dialed in via someones cell phone on speaker. It was insane. “Hey so we got some stickies that say x,y,z here.. what do you guys have??” Some managers I have found are like someone who is incapable of being an author but are very good editors. Unfortunately some of these are also incapable of coaching their feedback in constructive ways to get you to the best edited version of you work. This inevitably turns into repetitive games of “guess the number in my head”.. to which the answer is.. blue! Sometimes these situations are because your manager is at the end of their own rope politically and on their way out. Also could just be their first real manager gig. Other times its because they have something going in their personal life..
- wlonkly 4y agoI find the framing of this to be a little disingenuous.. I would expect that after getting fired (or the contractor equivalent) that I wouldn't be eligible for re-hire, even on another team. Regardless of who is to blame (both of them, IMO) I can't imagine a situation where the company would take the risk on this particular person again.
- trinsic2 4y ago> The interview went well, but then communication fell silent. One of the teams rejected me saying I was marked in an HR system as "bad culture fit". "bad culture fit" sounds like using how they use the "Do not fly list" against political dissidents. I'm really glad I am providing my services independently, free from control, and not have to deal with Corporate Culture. That culture is a poison to the human value of independent thinking.
- Szpadel 4y agoi do not see anyone here that thinks that employee in this situation, should report behavior of this manager to HR. I believe this is one of the purposes of they existence. they should talk more people there this manager works with and then discuss that with both sides. I'm also surprised that before firing, HR didn't try to discuss with employee about issues that manager was having.
- gwnywg 4y agoEvery business is built by people to deliver some value to other people, so I'd risk to say that technology alone is not enough to get on with people. This is a skill which I personally had to develop and it took me almost 10 years to get it 'sort of' right. I, like author of this post, was mismanaging relationship with people I was expected to report to, many times it was my lack of maturity. I remember the situation when I was first tech hire and had very good relationship with CEO, yet when CEO hired manager (who loved to micromanage) I failed to handle the situation as grown-up, instead I got attached to how much I brought into the company erc etc. Years after I left I got things right with people I worked with, and from perspecrive of time I think it is difficult to be humble and to communicate in such way that people want to listen and to try to understand my point of view. I think author of the blog could prevented escalation with manager he was reporting to, some words he was choosing when communicating were quite ... edgy. And it seems he is picking up his lessons, good that he sees there is something he could have done better.
- mib32 4y agoThe big question is - maybe we should really move away from capitalism, to something like communism, but more like crazy utopic communism, where everyone is CEO? So such kind of problems wouldn't really happen? How do you think, could it help? UPD: please don't downvote me, I am on spectrum
- cbozeman 4y agoYou're being downvoted because your idea runs counter to the nature of humanity. We do not like, and eventually will not tolerate, people who do not contribute a certain amount to the tribe. Members of the tribe that could not, or would not, contribute we banished to exile to die in the wilderness. This is why Communism in any form cannot and will not work. There has never been, and will never be, a perfectly equal distribution of work amongst the people in a tribe, a village, a town, a city, a state, a nation. You cannot distribute equal resources for unequal effort and expect cohesion.
- mib32 4y ago
- midislack 4y ago>He also mentioned that he was surprised that we had this sort of cultural mismatch since he had worked with many different ethnicities before. Was he Indian? I can picture this now.
- mib32 4y agoWhy has this post disappeared from the home page?
- taveragejoe 4y agoall in all, sounds like a new manager being a shitty manager, I would just start looking for a new job at the first few red flags and never ever work again for spotify, because if they support shitty culture, why would you even want to work there...
- groffee 4y ago> I was part of the technical community within Spotify, hanging out in various technical topic channels, helping people out. It might be a cultural thing, but you're not part of any 'community' or 'family', it's just a job. And like any other employer they'll fuck you over just as soon as they can.
- cheshire137 4y agoThe manager sounds exhausting.
- dangerface 4y agoYou did the right thing, I don't know why every one thinks their job is to sink the ship because their manager said so.