7 ms·
In addition to knowing which bucket your salary comes from, I think it is also useful to know how your organization values building software. Because this affec
by mooreds 3y ago
In addition to knowing which bucket your salary comes from, I think it is also useful to know how your organization values building software. Because this affects your career just as much.
* Is your company selling software development hours (consulting)? I'm this car you'll be valued for client relations skills and the ability to bang out acceptable software.
* Is your company selling a software product (product company)? In this case you'll be valued for your ability to build and run software.
* Is your company selling something else that has a software component or that software enables (pretty much every other company)? In this case, you'll be valued for your ability to deliver on or below budget and you'll never be the star of the show.
Funnily enough, these seem to map well to the three categories the author mentioned. Consulting to sales/marketing, product to research and development, everyone else to maintenance.
- zerr 3y ago> * Is your company selling a software product (product company) In the B2B world it is common to have a complex enough product that needs training services and tech support as well. Some vendors also add exams/certifications on top of it.
- mooreds 3y agoThat's fair, I was painting with a broad brush. Once you get to a certain size of consulting company, you may also have an r&d department or someone responsible for building common libraries or knowledge repositories, for example.
- Scarblac 3y agoOr a combination. I'm in a pretty small company (about 80 people total, 15 devs) and worked on all three of those last year.
- mooreds 3y agoI'm a bit confused. You worked as a consultant selling hours, one a software product sold for a price and also on an internal enablement tool for the same company?
- jaymzcampbell 3y agoNot the OP but I can believe it - where I work the main business is consultancy style work but to support that work there's custom generic software developed to sell/license to clients as part of a value add and there's dozens of internal tooling to support delivery teams. We have developers that will move between all 3 of those areas depending on their current allocation to client work.
- mooreds 3y agoSounds awesome! Thanks for illuminating me. How are these different work streams prioritized? At first glance seems like the last category would suffer unless someone was "on the bench".
- michaelt 3y agoScarblac's mentions a company that only has 15 developers. That means time spent on internal tooling like, say, improving the CI system has direct benefits for the other 14 developers, all of whom probably report to the same boss.
- IggleSniggle 3y agoIn a smaller company it's not hard for "invisible" (like CI) contributions to be actually seen and noticed by both leadership and by the people you work with every day. And on the other hand, if you're a dev working on product and getting work done is a lot harder than it should be, you've got a strong incentive to pause product work and focus on "maintenance" work. When almost a quarter of the company (15 devs) can both see and feel your contribution to make their lives easier and more productive, you've got a pretty strong political position even if you aren't directly producing product. This is true even if you produce, say, an internal dashboard: you're known as the one dev who took time out to help the 20 sales people sell better (or whatever); you know their names, and they know yours.
- jaymzcampbell 3y agoWe have a process whereby people can request a change after a certain period (and team permitting) to allow people to rotate amongst different clients and different work streams. I think it's usually after 6 months on one particular thing you are eligible to request reassignment. Won't always be approved ofc.
- verinus 3y agothis. first company is good for starters to get to know others. third should be avoided if you want to stay in software and not transition to management. You will always be seen as a necessary evil, your problems not understood while others working on core products will be perceived as an asset. second one is the one to make a career in software dev.
- resonious 3y agoI actually had a pretty good time at a third-category place. When you're writing software for a non-tech company, it means your customers are very close - often in the same building, working at the same time. You can watch them use the software, hear complaints in real time, and push solutions very fast. In my case, I might've been lucky, though. One of the co-founders had a CS degree and deeply valued the productivity boost we got from custom software.
- verinus 3y agoofc individual experiences might differ! it certainly depends on the company and leadership. From my experience in a bigger one understanding ended when leadership was needed in software areas, but leadership was recruited only from the other domain...
- rprospero 3y agoAlong those lines, one of the most toxic places I've ever encountered for developers was at a company that sold b2b software. You would think that developers would be valued for creating the product, but they were fully treated as a cost centre. The profit centre was the sales team who went out and got companies to send money. The developers merely existed because legal said that, for compliance reasons, the firm was required to provide the costumers with software after the client paid for said software (legal accounted for 24% of the company's budget while software development was 15%). If the sales team promised something that the software couldn't do (e.g. track the position of any cell phone in the country with just a phone number in the early 90's before smart phones), then any refund owed to the client would come out of the product team's budget. The salesman (they were all men) would not be required to return his commission, since he did his job and got someone to sign a cheque. Surprisingly enough, the company was not Oracle.
- michael_leachim 3y agoWhat category is Amazon? (the marketplace). It looks like a third category (company sells something else, but it has a software component supporting it). I am asking because I am working in a company with similar business model and I am trying to figure out what category does my work belong to. thank you. EDIT: fix msg
- strikelaserclaw 3y agoI think there is nuance here, even within a product company, not all software is equal. There's software to support core business (think ads in Google) and there's probably software to support internal dashboards (also in Google), I'm sure engineers working in ads in Google have much more leverage than those working in making dashboards for ops or some internal ticketing system. Conversely, I'm sure the companies we traditionally think software is just needed to support the core business also have software lines which generate income or is critical to their core business.
- michael_leachim 3y agothank you, maybe it is easier to understand when you ask whether business will halt and die if the system you are responsible for is down or suddenly absent or it is going to be a mild inconvenience. I think, defined like this makes it less ambiguous edit: fix msg
- mooreds 3y ago> when you ask whether business will halt and die if the system you are responsible for is down or suddenly absent This is a great way to put it. I also ask myself the question: "who are the rockstars" at a company. The folks that are celebrated. If it isn't a developer/engineer, you aren't at a category 2 company.
- michael_leachim 3y agothank you, I've got something to think about.
- vegetablepotpie 3y agoAs a third bullet point person, never ever attempt to solve interesting technical problems. I’ve made that mistake, I’ve been asked into meetings and asked “how’s it going” then promptly told “don’t tell me the details.” Working in bullet point three means working on boring, forgettable solutions. You may find yourself making valid technical solutions that are political suicide.
- Aeolun 3y ago> You may find yourself making valid technical solutions that are political suicide. If everyone else does the opposite, you can make a career out of making correct technical decisions. Seems to work for me anyway.
- jimbokun 3y agoTo simplify, you always always always want to be working in bullet point 2, if at all possible. In the other two, you are a cost to be minimized or eliminated. Only if you are working on one of the companies core products are you an asset bringing revenue into the company.
- hgomersall 3y agoMost companies should treat software as a core product. Not many do.
- jonfw 3y agoWith #1- you are the product
- Closi 3y agoAll jobs are transactional, the transaction is just more clear-cut with #1.
- Closi 3y agoI disagree - It depends on your career aspirations, your skillset, the company, and the type of software you like making. If you are a great communicator and have a great ability to just 'get stuff done', you might be a superstar in 1 & 3, and you might find working in bullet point two highly frustrating. With number 2 you are more likely to be working on a tiny part of a larger application. My brother went from bashing out big scrappy functional software with lots of client interaction (option 1 or 3) and moved to a bigger product organisation where he is suddenly working on a team building a microservice for a larger application, but doesn't feel like he is making the same direct impact (i.e. it can be more satisfying to make 10 people's jobs 10% easier compared to than making 1 million's peoples jobs 0.1% easier). He would rather build some scrappy tools that gets the job done than build highly refined software, just because the scrappy programming to meet an end is more satisfying to him (and is generally the bit where you can build fast value!).
- chii 3y ago
- electrondood 3y ago> Is your company selling software development hours (consulting)? From working with contractors, this bucket also motivates you to strongly optimize for number of sprint points delivered, not quality/reusability/maintainability.
- kayodelycaon 3y agoI chose to make a career out of #3, specifically logistics. I know how stuff gets from vendor to customer. This isn’t something you can buy out of a box. It’s usually heavily customized and made out of multiple systems were never design to work together. Every company does this differently. I enjoy this. I’m good at thinking through whole systems across a company’s many departments. This requires knowledge of internal politics to navigate through problems. This is were I’m valuable. As a programmer, I’m good, but can’t match the expertise of someone who makes a career out of programming.
- ted6767 3y agoBrother
- deleted 3y ago[deleted]
- ptsneves 3y agoI am in the same camp. I also don’t think it is bad in compensation terms because lots of this maintenance work is often called devops and devops is well paid from my point of view. I do the logistics for embedded or SaaS. It has been good and it is often cool to login to devices that are seen as a black box by any other person in the world. I also know that when something is on fire the maintenance guy is the one being begged by the sales guys and higher management. Maintenance people end up being debugging gods.
- DayDollar 3y agoMissing the hackernews part of product to research and development,: Is your company planning to use the exponential growth nature of software to enter into a overlooked niche or rapidly take over a existing industry? In that case, product development does not really catch the situation. Cause using the situation, closing time window till competition appears or funds run out, is way more important than the product or its quality
- shermantanktop 3y agoSeems like a variation of #1 where the rewards are probabilistic and lumpy. I agree that the motivations and resulting behaviors end up pretty different.
- irrational 3y ago> Is your company selling something else that has a software component or that software enables (pretty much every other company)? I'm not sure this is true? If my company sells food or clothing or shoes, they don't have a software component. I'm not sure what the breakdown is, but my gut feeling is "pretty much every other company" is wrong. I work for a company that makes clothing and shoes. We have an enormous tech organization, but we aren't a consulting company, don't sell software, and don't put software into our products.
- jeremyjh 3y agoThis is an article about software engineering - for software engineers. In this context it should not be hard to reason that companies that do not employ any software people are out of scope. Of course they exist.
- irrational 3y agoBut, my company does employ thousands of software people. We just don't sell consulting, sell software to other people, or sell products that use software.
- alephnerd 3y agoI'm guessing GAP.
- CRConrad 3y agoZara, Zalando...?
- digging 3y agoYou misunderstand. The third group is not only companies that sell software-based products, the third group includes companies that use software to sell their products or manage other aspects of the business. Having an in-house online store is an example. That presumably puts your company in that group, just like mine (or else I have no clue what thousands of software people would be doing on the payroll). I bet our two companies have very different reliances on technology, but we're both in the same group, because all of our software supports our sales of our actual goods and services.
- hackernoteng 3y agoMy experiences: 1) programmer in IT department of major newspaper: disregarded as IT geek. very small salary. the worst office spaces. 2) senior engineer in software startup: rockstar treatment, stock options, all the things you would expect as office culture 3) senior consultant at IT consulting company: must basically be a sales guy who writes good PowerPoints. Maximize billable hours. What ever you do dont complete a project quickly or with minimum amount of code. you can probably guess where I am now.
- hackernoteng 3y agoThe consulting company gig paid alright. and all the guys who stayed got really rich due to IPO. I left the second my options vested. Literally when the transaction went through... no regrets because it SUCKED
- granshaw 3y agoHow often do consulting companies ipo nowadays tho… heck ipos in general have dwindled to a tiny number
- jwineinger 3y agoAgree with these. I was a dev at a retailer that did catalog/phone sales and was starting to use web. Small salary, small PTO, no benefits. Pay increased when the business had an existential crisis and came to rely much more heavily on tech. Next was software consulting company churning out sites designed by marketing agencies, billed to the 15 min. Small salary, small PTO, some benefits. Then I went into SaaS (startup, then a public company). Nice salary + stock, great PTO, great benefits. Aside from the comp/PTO/benefits, I learned that consulting isn't for me. The client interactions felt... adversarial, where they were trying to get more work for less money, while we were doing the opposite. I did not like that constant tension in conversations.
- SOLAR_FIELDS 3y agoThe point you made about consulting interactions resonates with why I also ended up not liking consulting. It feels like incentives are not aligned when doing software consulting a lot of the time.
- golergka 3y ago> Is your company selling something else that has a software component or that software enables (pretty much every other company)? In this case, you'll be valued for your ability to deliver on or below budget and you'll never be the star of the show. Trading companies are one of the very innovative in IT and offer software engineers salaries that are higher that FAANG.
- hinkley 3y ago> you'll never be the star of the show. This is far too kind. If you work eg for a hardware manufacturer, not only won’t you be the star, but good luck getting any respect. You are a cost. One they wish they didn’t have to pay. Delivering on time and under budget doesn’t put you on their radar, it takes you off.
- badpun 3y agoDepends on the hardware manufacturer. From what I know, developers at Intel are treated pretty well. It all depends on how integral the software component is to the overall product's market success. In the case of Intel, a GPU with poor and buggy drivers is not gonna sell, so software is pretty important.
- hinkley 3y agoIsn't Intel struggling now because their definition of 'pretty well' wasn't good enough and they lost key people to competitors?
- deadbabe 3y ago#2 is the best because if you can do your job quickly and efficiently you can minimize the amount of actual time you spend working as long as you are delivering the software.
- mastersummoner 3y agoWell I agree with you, there are definitely developers out there who are completely happy with a 9 to 5 punch card type job.
- golemiprague 3y agoMany companies has the last two intermixed, some devision create support software for the business and some create value generating software. Think about a bank, creating the system for the back office is not the same as creating the HFT system. Sometimes consulting and in house product is also intermixed. In short, the distinctions are correct but it is not about the organisation, more about the division in this organisation.
- WWLink 3y agoooOoo I work at the 3rd kind... the thing is, our products have several different major engineering components, luckily we're all treated equally! That can also be a little bit of a downside sometimes, because the software industry definitely pays better at the top lol. But I'm still getting paid damn well for a job that isn't at a software company. Woo!