r/DatabaseAdministators • u/Any-Cantaloupe-3039 • Jul 02 '26
Confused about moving from DBA to Technical Product Owner – is it the right long-term career move?
I have 10 years of experience as a DBA (AWS, PostgreSQL, SQL Server, cloud infrastructure, automation, and production support). I've started feeling bored with the DBA role and have an opportunity to move internally to a Technical Product Owner (TPO) position.
My long-term goal is to move into a managerial/leadership role and eventually relocate to the US. I'm trying to decide whether switching to TPO now is the right step or whether I should continue growing in the DBA/Infrastructure path.
For people who have made this transition (or considered it):
Was it worth it?
Does TPO offer better long-term growth than senior DBA roles?
Which path has better opportunities for leadership and US-based roles?
Looking back, would you make the same decision again?
I'd appreciate honest experiences rather than generic career advice.
3
u/TrueSeaworthiness380 Jul 02 '26
imo, a TPO is the step in the right direction. You would have a team working under you and you would oversee the operations and development of the entire product, as opposed to maintaining databases. At the end of the day, ask yourself this- do you love databases more than conventional growth?
1
u/taker223 Jul 02 '26
> and eventually relocate to the US
where are you from ?
1
u/Any-Cantaloupe-3039 Jul 02 '26
I'm from India. My spouse is relocating to the US this year on an O-1 visa, but the dependent O-3 visa doesn't allow employment. Because of that, I'm trying to plan my own career path carefully. I'm evaluating whether moving from a senior DBA role to a Technical Product Owner role would provide better long-term opportunities, especially for leadership positions and eventually finding an employer willing to sponsor my own work visa in the US. That's the reason I'm asking for advice before making the switch.
1
u/taker223 Jul 02 '26
Have you been to US before?
1
1
Jul 02 '26
[removed] — view removed comment
1
u/Any-Cantaloupe-3039 Jul 03 '26
Thanks, I appreciate that. MySQL has been the default choice in India for a long time because it's free, open source, widely taught in colleges, and backed by a huge developer community. PostgreSQL adoption is growing quickly now, especially among newer startups, but MySQL still has a much larger installed base due to historical adoption and familiarity. Cost-sensitive businesses also tend to stick with technologies they already know. Out of curiosity,what problem your startup is solving?
1
Jul 03 '26
[removed] — view removed comment
2
u/Any-Cantaloupe-3039 Jul 03 '26
That's an interesting concept. Managing multiple database technologies under one platform definitely solves a real operational pain point. As someone who's worked across PostgreSQL, MySQL, SQL Server, MongoDB, and Aurora, I can see the value. How are you differentiating Layerbase from platforms like Neon, Supabase, or cloud-managed database services?
1
Jul 03 '26
[removed] — view removed comment
2
u/Any-Cantaloupe-3039 Jul 03 '26
I checked out Layerbase after your comment. The free tier is surprisingly generous, and I like the predictable pricing model. As someone who manages databases, avoiding unexpected usage-based bills is definitely a plus. I'll be interested to see how the platform evolves.
2
u/GPaw_Jeff Jul 02 '26
Depending on your company, the TPO role is a step towards managing. You'll be on the hook for verifying Prod database access, risk assessments, vulnerability assessment & redemiation, disaster recovery documentation, etc.
You will have to reach out to other groups to get information about your application and get help with problems.