frontpage.

I have a BS/MS in computer science and somewhere around 9 years of experience, where the first half was spent working as a backend developer and the second half I've been working in product owner roles. I switched from development to product because I simply realized that I wasn't very good at implementation and system design work to be honest. I wanted to work with tech from a more overarching level, and let the experts who were much more skilled than me handle the implementation work.

Around 8 months ago I switched companies and am still working as a PO, but this organization I am working in is a terrible fit for me. I don't want to go too far into why I really dislike this job, but a big part of it is that the organization wants me to make technical design decisions which I am just really not good at, since the development team doesn’t have this experience themselves. This is making it completely impossible to deliver on the project I’m responsible for.

This has really made me think about what I should do for my next role. I fully admit that I was and still am a mediocre developer, which is why I moved into a PO role in the first place around 4 years ago. I have such a huge amount of respect for people who are great developers and architects. It's a challenging role and I can imagine it's exciting if you are creative and like to build new things. But I am just not cut out for it. I am not very creative, and I often have no clue where to even start when I need to build new things.

The parts I've enjoyed the most in the various roles in my career have been things like:

- 2nd/3rd line ticket management and troubleshooting. It's been quite fun going through logs and trying to figure out what went wrong, perhaps trying to recreate the situation in a test environment with an API client.

- Supporting customers. For example helping customers with installations of software. It honestly gives me a huge sense of accomplishment when I get to see a customer making use of our products, and helping them investigate why something may not be working.

- Being an interface between business and tech. I've always thought of myself as someone who is able to understand both business needs and technical needs quite well. Even though I'm not good at implementing software, I can understand limitations of software, read and understand existing codebases, and so on.

- Testing software. It's a lot of fun to test software to see if there are any issues before we go live!

- Just working with people in general! I really like to do whatever I can to support my team and the people that I work with.

I thought I'd ask for some advice to see if you guys have any recommendations for career tracks to consider, given that I am just much more comfortable supporting existing software than building new software. I like working with people. I like achieving results. I'm just not cut out for system design and building new software.

Honestly it might mean that I need to live with a lower salary, and that is fine with me. To be completely honest, given the fact that my current role is genuinely making me sick with severe anxiety (made a post about this a while back [1], I've learned that money isn't everything. There isn't a point to making more money if my job is literally killing me and I am losing my health. I'd much rather work with something I enjoy that isn't making me feel sick. Life is too short.

Thanks for reading this. I really appreciate any advice or thoughts you may have.

[1] https://news.ycombinator.com/item?id=49533073

Sounds like you may enjoy being a QA engineer. Good QA engineers are a really really good value add to a software team and can really save our ass. Technical QA engineers understand why things break, and are easy to coordinate with when preparing a larger release.

At my previous employer, the head QA engineer was the one pushing back at the PM when they were too ambitious. They basically owned the current "Is the next release still a buggy mess?" state.

Perhaps a sales engineer?

> I am just much more comfortable supporting existing software than building new software.

Having technical skills is required, but you'd be doing little to no coding or design work.

> Being an interface between business and tech.

A sales engineer matches this almost by definition.

> Just working with people in general!

The job is essentially entirely about working with people, both with the customers you're trying to sell to, and with the developers who are actually making the product.

This also has the added benefit of making a lot of money even by engineering standards in the right organization. Looks for large enterprise companies where custom demos and new customer hypercare are standard. I've been on the other side of the table a few times and often pre-sales cycles are months long and contracts start in the $2-4M range. Those are the places where sales engineers will be treated as first-class citizens and not just "hey grab one of the engineers for this sales call."

Developer Experience is gaining in popularity. Your clients are internal and your objective is to remove obstacles, create shortcuts, keep everyone happy and productive. Lots of it is communication, finding out everyone's pain points and discussing what is technically feasible to ease that frustration - so that may tickle your people/support string. Things that are/can be part of DevEx are DevOps/Platform Engineering/Infra/CI/CD, QA, IdP, internal frameworks, onboarding, etc. Fun stuff imo.

Technical pre-sales?

> Wanted to work with tech from a more overarching level

> I get a huge sense of accomplishment seeing customers user our product’

> Interface between business and tech

You might like trying your hand in Professional Services either at a System Integrator like Deloitte or first-party in a product company (now often re-labelled as ‘forward deployed engineers’).

Their main problem space is getting customers to successfully use the product through marrying your understanding of the tech’s limitations and sweet spots with the customer’s organizational goals and culture, so daily work revolves less around deep technical design and more about org alignment and strategy (which is why SIs sometimes get a bad rap on a tech forum like HNews).

It probably pays less, and it can be more stressful when you’re billing for (and justifying) every hour, but in my experience the way it tends to be more dynamic (new projects+teams+customers often) and how you get to see very direct impact is quite rewarding.

What about testing / QA / reliability? Plenty of such positions. Not particularly competitive to get into, as many view those jobs as "lesser" jobs.

Software sales engineering could be another, which probably also pays more. But, alas, more competitive.

Eh, SREs are generally considered harder to get into with more responsibility than regular development roles, unless I misunderstood what you meant with “reliability”.

We're in the AI era now, every job is a supporting role.

Modern big tech software engineering is 98% supporting and maintaining.

AI does this really well, even better than new development. I regularly use Github copilot to automatically read production logs from the app and backend services, find errors logs, deeply scan the codebases, create theories about the issue, verify the theory matches production evidence, verify the theory in a sandbox env, create a failing test, and then suggest a minimal code change in a feature branch, verify test is passing now in sandbox, and submit a pr, along with a detailed analysis doc and any future design optimizations to fix the class of error.

AI is also very good at scanning legacy codebases, and reverse engineering design docs, system interfaces, and trying to reverse engineer what requirements and design tradeoffs lead to that system. It's not perfect, but already at medium software engineer level.

Solutions architect post-sale fits better if you hate quotas. Same work, calmer.

If you have a secondary interest or hobby or real-world-knowledge about what consumers in a certain category want - you might be a good product manager in that field.

Many products require technical product managers.

Being people oriented and a "mediocre" technical engineer is not really a hinderance and can make your focus better aligned customer needs in a high level, not getting nerd-sniped on things that don't matter.

I suspect that engineers would prefer working under someone like you who doesn't have a god-like ego, and is likely to resolve conflicts between people.

I have a coworker who is incredible at the job it sounds like you want. The "keep customers happy" role. It's a massively important role in a company. It's part product support, part sales support and part product owner.

2026 has made him way more useful to us engineers. Before he used to send us tickets. Sometimes we delivered what the customer really wanted because of those tickets, and sometimes we needed a few iterations.

Now he uses AI to deliver pull requests that include full repro environments. These are slop, of course. Sometimes we can approve them almost unchanged. But more often they need to be completely rewritten. But even the latter is super valuable as a much more concrete representation of the bug or customer request than a ticket was.

Depending on where you start it could be a bigger salary drop than you expected, but it sounds like technical support might be your real passion. I’m the same way - I love in-the-weeds troubleshooting and helping people solve their business problems. I started out in SaaS sales, hated it, switched to IT during the pandemic. Another commenter mentioned systems integrators, you could also look at managed services. See if you can get into an escalations role so you’re not having to climb out of the help desk which you’re probably overqualified for. Look up companies that make products you love and see what openings they have. There’s no shame in supporting others.

Gemma 4 26B on a 24 GB Mac Mini M4: from 66% CPU to 100% GPU

Being Lazy in C++

Show HN: I Built a CLI for Proton Mail, Drive, Calendar, Pass and Contacts

Ask HN: MacBook Pro (Max) equivalent Linux laptop?

Show HN: AgentJIT – Compile dynamic LLM agent workflows into 0.1ms Python

Show HN: InterviewsRadar – Sell or find interview experiences

Show HN: I built ThreadShelf to reuse hard-to-export AI chats like OpenRouter

SQLite natively supports JSON as output format

Free domain monitoring through echelongraoh.io

Why AI Benchmarks Are Total BS

Solod 0.4: Better C interop

"Deciphering Visceral Instincts" by Diego Bohórquez [video]

Principal Component Analysis

Matt Mullenweg reportedly returns as Automattic CEO 2 days after getting booted

Why is the x86 undefined instruction called ud2? Why 2?

Texas puts a brake on its data centre boom

The Kirby Krackle

Generate-Ilograph: A skill to create auditable sequence diagrams of a codebase

Problem Archives – Project Euler

Dotnet-ef-scripts – A collection of handy scripts for .NET Entity Framework

Panic builds over bankrupt Spirit's looming data sale to Google

LLM Atlas: community intelligence board

Void Linux Maintainer Orphans 100 Packages over AI Policy Dispute

Ask HN: On the Contest of Meat and Machine

Work

Post on HN, get flooded with AI sales pitches

DietPi released a new version v10.7

I Asked 100 Agents to Hack Me

The SICP Challenge

Show HN: A Soup-inspired runtime for a real fruit-fly connectome =)

Ask HN: Career paths to consider if I am better at supporting than creating?

Comments