Hacker News new | comments | ask | show | jobs | submit login

I absolutely hated my job as the dev lead for a medium size ($1 billion in revenue) non software company where we were a “cost center”.

I liked helping smart developers who wanted to learn, I liked having a seat at the table to decide my own destiny and the level of autonomy to decide the “how”. I didn’t like the red tape, the political jockeying, meetings and more meetings etc. I wasn’t really learning anything that could keep me competitive in the market.

I finished the green field project they hired me for initially, put it on my resume, quickly moved on to a small company and negotiated not to be made a dev lead and said I could help meet their objectives better by being a free agent and moving from team to team as needed and mentoring the younger leads.

I absolutely love my job. I have far more influence, autonomy, and a larger voice than I ever did at the larger company I left. I still mentor and advise, but I only have the responsibility as an individual contributor. I also get paid more because everyone including the CxO knows what I bring to the table.

I was in a similar position at the first place I worked for after the company I was at for 10 years. I was just a developer but I carried the weight of their biggest customer by myself as everyone else was trying to create the next project. I survived rounds of layoffs until the company folded.

Lesson I learned: I like small companies.






Promotions are just a form of vendor lock-in that (especially) small companies employ to keep people longer. I’ve seen barely two years out of college non cs majors promoted to senior engineer based on finishing some “large project” which anyone else in the engineering team could have done.

The real sleezy thing is that by promoting someone to senior who isn’t nearly qualified at all, the company has now made it exponentially more difficult for these engineers to switch companies. Esp funny is the promotion of unqualified individuals to “project lead”.

I’ve seen many of these individuals move to next companies and revert back to standard level software engineer.

It’s never about titles - you need to be aware that companies are using the titles against you rather than for you.

Also it pisses off the engineers in your organization who do deserve a raise to see unqualified promotions. Its a one way ticket for a small company to very quickly lose its true talent (80/20 rule) and talent follows talent. Once you get a few supporting cast leave, even the actually qualified senior engineers won’t want to stick around longer because they will feel intellectually isolated as well as feel like the engineering management are inept.


I wouldn’t even go that far. The dev lead over one of the teams is far more qualified to be the lead over that team because of his company knowledge - he’s been there for five years. He’s a smart guy but I don’t know how well he would fare outside of our company. This was his only job out of college.

I’m one of the three oldest developers - two of us are in our mid 40s and one in his mid 50s. The “architect” is well qualified but he has a lot on his plate. The other dev in his 50s also fought against being made a lead.

Edit:

I usually don’t comment on downvotes, but I’m really interested in knowing what could possibly be offensive or disagreeable about this post.


Yup, that was my last company . Had a bunch of inexperienced devs getting promoted to "Senior" all the time. I think I counted once and figured out that we had more people working there with the title Senior Software Engineer than we did regular Software Engineer's.

After one year of moderate effort I too got the promotion, with almost no pay raise. The problem of giving everyone a certain title is you basically completely dilute any meaning or status it conveys.

I soon went on to FANG and am now a regular ol' Software Engineer again. But I'd much rather be bottom rung at a top company than a "Senior" whatever at a company where it means nothing.


This applies at both small and large companies alike

I don’t care about titles at all. I care about three things when it comes to my job:

- Technology/Career enhancement - where will this job put me in three years if I want to find another job

- Environment - I’ve grown increasingly picky about my environment and work life balance.

- Money - at least pay me the local median wage for what I bring to the table. Don’t insult me. But beyond that, money is the least important criteria.


I'm super appreciative of my current role for this and other reasons. I'm the sole software developer on a team of 6 people in a mostly isolated corner of the code base. I'm getting a ton of experience making calls and collaborating with non-engineers, while still getting to be involved in some broader discussions.

A company of 20-50 programmers seems ideal to me now, with an overall company size of <300. I feel larger might require too much bueracracy and smaller might lose out on QoL and scale of work that can be accomplished.


I wouldn’t go that far. Being the sole developer you risk becoming an “expert beginner”. I know that held me back for over a decade, being the only developer for three years and working with two other developers who never worked at any other company for 9.

I’m might be in this boat, and it terrifies me.

What are some characteristics of a “expert beginner”? What did you realize you were lacking/weak points?


https://daedtech.com/how-developers-stop-learning-rise-of-th...

Unfortunately, you may not know until you get around people who have been developing as long as you have on paper but have learned from other people.

But this is my go to list of books.

https://news.ycombinator.com/item?id=18794561




Applications are open for YC Summer 2019

Guidelines | FAQ | Support | API | Security | Lists | Bookmarklet | Legal | Apply to YC | Contact

Search: