A scrum master now is having a same title as level 6 analyst.
And then another scrum master is now Director IT project manager.
Level 6 & 7 roles used to be hard earned positions here.
One squad lead is Director while other is Engineering leader.
And a chapter lead is now Director, Engineering.
Explain to me the hierarchy now, it's confusing as fu-k and offensive to see someone who was merely a pencil pusher be in a same title as me...
In what world is this fu--ing fair???
@hm, do I have to remind you this is year 2026? You sounds like the dinosaur who don't know the most efficient way of climbing the corporate ladder, rank and money wise, is to keep switching jobs.
Oh, maybe you can't find a job outside Fido.
if you're title confusion worries you regarding your work after Fidelity, then perhaps you shouldn't be here.
I struggled with this, a lot when I joined as a systems analyst and I worried about my future at different companies with this title. The disconnect here is that you’re assuming future hiring managers evaluate candidates based on the HR title printed on a badge rather than the scope of work they actually performed.
A Product Manager is not defined by the words “Product Manager” appearing in Who’s who. They’re defined by ownership of product strategy, prioritization, stakeholder management, roadmap decisions, requirements definition, and outcomes. If you spent your time deciding what gets built, balancing business priorities, gathering customer feedback, writing requirements, and partnering with engineering, that’s product management work regardless of whether Fidelity called the role Systems Analyst, Product Owner, or something else.
Likewise, a Systems Analyst isn’t automatically a Product Manager just because a company changes a title. Traditionally, systems analysts focus on translating business requirements into technical solutions, process analysis, documentation, and implementation support. That’s a different discipline.
The reason many experienced hiring managers don’t get hung up on titles is because they’ve seen every variation imaginable. Banks, insurers, healthcare companies, and Fortune 500 firms have spent decades creating their own naming conventions. During an interview, nobody is forced to say “I was a Systems Analyst therefore I only did Systems Analyst work.” You explain your responsibilities and outcomes.
If your concern is marketability, that’s fair. But the solution isn’t pretending titles don’t vary across companies. The solution is clearly articulating what you actually owned. A resume bullet that says “Owned roadmap prioritization for trader-facing platform features” tells a hiring manager far more about your qualifications than whatever HR happened to call the role.
The real question isn’t “What was your title?” It’s “What decisions were you responsible for making?” That’s the distinction future employers care about.
@ff I think as long as the job description has the key words then that’s what matters for getting noticed at other firms. Seems easy enough to explain hen interviewing externally.
@dj, how do I not get hung up with the titles, if Fidelity is just one stop of my career? How am I explain to my future hiring manager "no I'm not a product analyst who collect product usage data with SQL after the product is built, rather I'm the product analyst who decides what features to build into the product", my future hiring manager would think I'm lying, as "deciding what features to build into a product" is a "product manager"'s job.
Not even worth it to get hung up on job titles at fidelity and even then its still completely separate from pay grades. Many banks and large companies call Product Managers “Systems Analysts,” “Product Owners,” or something else due to legacy HR structures, compensation bands, and org design like we are seeing now.
Seeing some of those legacy titles come back indicates a reversal in some direction, but not quite sure where. For years it was Product & Engineering reporting upwards towards their trade. Project managers owned the delivery and go live. Those individuals had previously worked as software engineers and got promoted upwards.
The industry titles in tech:
Most people wearing those hats and have been here longer than 10 years don’t give a rip what they are categorized in the system as long as their comp is reasonable along with their shares displaying “loyalty”
@bd ya like thought leader - there are some easy cuts right there. So useless.
Most of the titles at Fidelity are inflated.
Scrum masters were manager, senior manager and director levels (5,6,7)
Fidelity doesn’t care about what degrees you have. It’s all about a55k1551ng
Being in the office full time will solve everything.
A squad leader with a Ph.D. is now an analyst. No point to make sense, just leave.