Ask HN: Have you moved to a less technical role after failing as a developer?

First off, this is a personal question so you don’t have to answer it, but I encourage you to think it over. How are you doing mentally/emotionally? I don’t know you so can’t make many guesses as to your writing style, but you sound really seriously down on yourself.

I bring that up because career transitions aren’t uncommon, but you need some confidence to make it happen in an interview. There is a huge difference between “I failed” and “I am better suited to something else.”

If you’re in the middle of it and feel like shit, it’s hard to see your gifts. But from an outsider’s point of view, being likeable enough that others will gladly help you is a major strength. Add in some above average technical skills and you’d be fucking dangerous in all kinds of roles. You’re even a good writer - it’s a tough subject but you conveyed emotion and a strong voice.

Best of luck and be safe.

Honest question - how do you go 40 years and realize this now? I assume you've been doing this for your whole working life.

Is it possible to take on other kinds of tasks at your current company? No company is perfectly efficient, so figure out where they are struggling to perform and lend a helping hand. Best case scenario is you realize you're quite good at whatever you try doing, worst case scenario is you've helped out another team.

I've been hearing more and more as time goes by that development skills don't always necessarily include actually writing code. Following a shared process, breaking problems down, collaborating to find potential solutions, and evaluating the merits of candidate solutions are all "software development" but not "coding". You're on a team. The team has diverse talents. It's totally different than sitting alone in your basement writing the next hit indie game where you are the only one that can or will do any of it.

Have you asked the good coders you've paired with if they enjoy coding with you? Maybe you're a lot more useful and talented then you think.

There are plenty of tech roles where you don't have to be a superstar dev but can't still make out fine. Support is a good one - sneered at by many but actually incredibly important and can be really fulfilling in the right role (granted low level support roles can be horrendous). So many users get shit support that if you really put them first they will come to love you. There are also roles that combine support with a bit of sys admin, service engineer type roles. Can be well paid on the contract side of things.

If you are or can learn to be creative and enthusiastic and personable, presales can be fun. In most presales roles the emphasis is on broad rather than deep skills, so that might suit you. For me presales was brilliant because it forced me to confront my fear of public speaking.

Finally I've met loads of successful people in my career that cheerfully admit they couldn't hack the technology side of things. Chin up!

Have you worked at more than one place in your Developer career? Sometimes it could just be you don’t enjoy what you’re doing on the current job. For instance, I previously did some DevOp-at/infrastructure work and I really questioned my technical ability, but once I got back to front end development again I felt energized by my work, my self confidence went up, and I have more genuine interests in learning more about it. It could also be you just don’t enjoy the type of development you’re doing. There are many paths to go even for technical roles.

I'm sort of going through this dilemma. I'm not a superstar level and probably do better in other roles.

One trick is to go into teaching. It requires considerably less problem solving skill. You just solve a set of problems once then reuse that solution for the next class. You'll still have enough industrial experience to teach better than most.

One thing I'm trying is to switch to similar but junior technical roles. Try game development maybe, or something like testing, system analysis, support.

Have you ever completed any sort of ambitious project on your own? Let’s 10-50k lines of code, that correctly does something nontrivial? If yes, then you’re suitable for the job. If not, you should perhaps try it (it will require leaving the job for a while). If you genuinely cannot complete it, then you have your answer, but if you can, it will give you lots of skills for the next role (you learn much more when doing things on your own vs being in a team) as well as a confidence boost.

Here's the secret -- a good team is built around people who are solidly dependable. What that means is you can give a reasonable estimate for the work, are a positive person, and aren't too much of a bother to anyone. The team is pushed forward in meaningful ways by the really ambitious and smart ones, but they tend to move on quickly after becoming bored. These people are great to have while they are there, but they leave so often that it feels like a revolving door.

But that employee who I can give work to and depend on to be there in a year plus time frame? That's the one a good manager goes to bat for during the tough times.

There are a lot of people who realized being an SWE/Developer was not the right choice for them. This is for lots of good reasons - not having enough interaction with other people, feeling too insulated from the outside world, not liking the day-to-day life of a developer, etc.

I've worked with ex engineers who are now in Sales, Marketing, Support, Management (Product and People), Education, etc. Some of them are amazing at what they do. One of the best developers and I know moved to the education team in their software company because they got tired of what it meant to be a developer. In that education team they can't release crap just because somebody decided to release something quickly - this was something they got disillusioned with as a developer.

You haven't "failed" as a software developer. You're probably just realizing that being a software developer may not be a fit. Nobody will fault you for changing to a different role. Anybody who has worked for longer than 5 years knows that after some point you need new and different challenges. Nobody will see you as a failure unless you say "I failed as a software developer so I want to do something else." Say "I've been doing this for a line and I want to do something different. Since I was a developer, these are the strengths I bring to the role versus somebody who has never developed anything in their life."

I say this for myself. I enjoy writing code and I think I'm a decent developer. But the thought of being behind the firewall (basically where I only interact with other people in Engineering, not users) of an Engineering Org just doesn't sit well with me. That's how I ended up in Data Science, where I interact with a lot of people and still write code.

A long time ago I took a career counseling course and the teacher (A PhD researcher in Career Counseling) said people typically change their careers 6 or 7 (don't remember the exact number) times in their life. It was hard for me to understand at the time, but after many years of working it makes sense. Some people change their career 5 times over 20 years at the same large company.