Live data from Hacker News

Working the System at a BigCo

expatsoftware.com

11–20 of 53 posts

Re: Working the System at a BigCo

#11
post #9

I would be interested in reading any advice for developers/engineers on how to "handle" management. Based on some limited reading I've done, the goals of management and what engineers intuitively think management wants are often very different. Basically, what behaviors do I need to adopt to make my relationship with technical or non-technical managers as mutually beneficial as possible?

I think it is not enough to be good, you also have to look good. What I mean by that is you have to make sure your contributions are visible and comprehensible to your bosses. This should establish some level of credit with them. Once you have that credit you can build on it to have more informative discussions, perhaps during one-on-ones. Dare to ask. Unfortunately, I have seen managers, technical and non-technical,…

> I think it is not enough to be good, you also have to look good.

[emphasis mine]

This rings true in a lot of large places and in some medium places. If your butt is in a chair in the office, you better be working on something. It doesn't matter if you clear your plate, took a few tasks from someone else, finished those as well, and are looking at the Software Engineering or Code Review SE sites or OWASP to help holistically contribute to your project. Your billable time better be used for tangible results that can be demoed or shown on an agile board. Never mind that you crushed estimated 50 hours in 30 - you don't get to be a warm body.

Re: Working the System at a BigCo

#13

I would be interested in reading any advice for developers/engineers on how to "handle" management. Based on some limited reading I've done, the goals of management and what engineers intuitively think management wants are often very different. Basically, what behaviors do I need to adopt to make my relationship with technical or non-technical managers as mutually beneficial as possible?

Simply try to understand the incentives of everybody involved. Not just the goal of the organization as a whole.

Re: Working the System at a BigCo

#15

I would be interested in reading any advice for developers/engineers on how to "handle" management. Based on some limited reading I've done, the goals of management and what engineers intuitively think management wants are often very different. Basically, what behaviors do I need to adopt to make my relationship with technical or non-technical managers as mutually beneficial as possible?

It almost all boils down to more and better communication. Likely, both you and your manager aren't as good at it as you could be - but you can only change what you do.

* Get to know your manager. What do they value, what do they care about? What's their style - analytical, from the hip, super-organizer, likes to try things...?

* Ask for feedback, ask for the things you want. Managers aren't mind readers. (Make sure you have regular 1:1s!)

* Ask for what their goals and expectations are, what they're looking at on a strategic level. Unless you got a heavy politician, most managers love sharing that, they just don't always know you want to hear it. (If you got "The Politician", learn politics or find a new manager)

* Communicate often. Your manager has likely a few more reports than you, and keeping up with all of them is hard. Worse, if your manager doesn't see how you're doing, you're likely more affected than they are. Make sure they see.

* Communicate clearly. If your manager is a veteran who wrote the system, sure, slay'em with jargon. If they're non-technical, or lack knowledge of the system, explain things so they can understand. Without being patronizing.

* Communicate respectfully. Both with your manager - that's just plain survival ;) - and with your team mates. Because it's your manager's job to fix those issues, and making more work is not a good way to win their heart. No matter how technically brilliant you are.

* Keep context in mind. All that info you're now communicating - do they need it right now? Can it wait? Is it turning out to be noise for them? Or, alternatively, will this lead to a crisis if not addressed urgently? Adjust accordingly. Managers are strange beasts, they both desperately want more information and are drowning in the wrong kind of it.

In other words, treat them like a human being, and treat them like somebody whom you want to help. Congratulations, you're well on your way to be good at "managing up". ;)

Re: Working the System at a BigCo

#16
I had a guy work for me once, I was trying to transition him from hourly to salaried. He had some longer weeks prior to this, and made the assumption that this would always be the case. He said, "I don't want to do this, because I will make more money this way."

Sounds like the article, right?

Except ... this extra time was a very temporary scenario, and he would be getting benefits, an effective hourly raise, etc. Even more to the point, when we didn't need his services ... and he didn't grasp this part, we wouldn't bring him in and pay him, though, as a salaried person, I would expect he would be doing self-education while we had "down" time, so he'd increase his value and utility to the organization.

Basically, I was trying to provide value to both the company and to him. As we were a very small company, I was able to see the value aspect very clearly, and I made the bet (later proven wrong as it turns out) that he would make a stronger contribution to the company if he had a steady source of income, with less worries about billable hours.

The big reason why he was getting more hours was that he was helping us set up our lab space. That project was almost complete ... maybe 2 more weeks of longer weeks, after which ... we'd need him 25%-50% time at best. I did need someone with expanded skills that he didn't have, and thought (mistakenly) that I could grow this particular individual into that role ... he expressed a strong interest in it.

The incentives aren't usually well aligned in BigCo and employee. We are, effectively, cannon fodder, for their plans, up through and including the senior exec ranks. Your incentive alignment with the corporation varies inversely as some power of the distance from the strategic decision making.

In SmallCo and employee, there are typically better alignments, though still not perfect. For someone like me, an entrepreneur CEO/CTO at the time, I was looking to build a culture, an environment, where we took a long view, beyond the next billable event. Where value took time to grow, where we cultivated it, where we grew people into roles that they wanted but might not have been able to do at the time.

The problem is, when you are sufficiently removed from the decision making process, your alignment is entirely economic. When you can't impact outcomes, and gain professional satisfaction and positive reputation from helping to steer a better course, your focus is, correctly, on other matters that benefit you personally.

To a large extent, this is the way things work. What benefits you personally and professionally, and is the compensation, work, and culture, aligned to mutually maximize the value of all of these things. In the case of the OP, no, the compensation was specifically architected to minimize cost to the BigCo, and maximize the benefit to the big co, even at the expense of the employee. Which would, undoubtedly, negatively impact the culture, and the way the employees interact with BigCo.

I am sorry to say this is to be expected ... but it isn't the first time I've heard this type of story.

For me personally, I remember working for some small silicon valley outfit in the 90s, where they treated some of the specialist developers like crap, but paid the contractors something like triple the hourly rate to use their expertise. So, a fairly sizeable cohort of my colleagues resigned, formed small consulting groups, and were hired back at (then) outrageous rates to do effectively the same work.

This misalignment is manifest in many large Cos.

Re: Working the System at a BigCo

#17
In a past life, I ran a consulting team at a BigCo whose business centered on T&M contracts like OP's. BigCo had 10k employees, mostly associated 1:1 to contracts with the same "bill exactly 40 hrs, but never overhead" constrains.

Our little team had 100 employees, but we matrixed those guys across all our contracts. While the clients disliked the idea of not having "their guy," they really liked having access to the technical depth of 100 guys vs. just the 10 they could afford. Turns out being able to have a Linux kernel guy, OS X kernel guy, Android kernel guy, database expert and hardware hacker on call at all times is incredibly valuable.

Since we matrixed across contracts, we managed to instuitionalize the "overtime hack." The guys were exempt status, so they didn't get time and a half for hours over 40, but they did get paid for every hour they worked. It was a phenomenal hack - guys were routinely making 20-50% more than their base salary. We intentionally understaffed by a bit, to make sure there were always extra hours to burn.

That team is 15 years into existence at a BigCo, and the hack still lives. If you find yourself in a consulting org and think you can make something like this work, don't think for just yourself, but shoot for the moon - set it up so it works for everyone and outlasts you.

Re: Working the System at a BigCo

#18
Most executives and managers don't know how, or don't want to, solve problems. So they dump those problems onto employees, vendors, even customers. Anyone to avoid having to do their job. Their most valued employee is the one in whom they can see value without having to work at it.

Re: Working the System at a BigCo

#19
There's a gray area between "good worker mode" and happily salaried. If they're taking advantage of that, then you need to leave BigCo. There are other SmallToMediumEvenSomeOtherBigCos out there who'll pay what you're worth; even if that coincides with 50 or 60 hour weeks.

Re: Working the System at a BigCo

#20

Why did the employee need to fill out any paperwork to be taken off of the performance plan? Shouldn't that happen at the direction of their manager? Feels a little bit like a deus ex machina.

I agree, but I have also learned never to underestimate the bureaucracy of a big co's paperwork.
Post reply on HN