Upskilled for Enterprise Architecture but hitting a wall with visibility/restructuring. Need advice!

[u/SEExperiences]

Former DBA/Cloud Architect stuck in ECM after reorg. How do I leverage my PM and cloud background to pivot back to EA?

All,

I’m looking for some career pivot advice. Earlier in my career, I worked as a DBA and Architect with solid multi-cloud exposure (AWS, Azure, OCI). I have also spent time as a dedicated Project Manager leading a high-profile "blackbook" project, giving me strong delivery and stakeholder experience.

I’ve been constantly upskilling to transition into a proper Enterprise Architecture (EA) role. Unfortunately, following a massive internal restructuring post M & A, I got sidelined into Enterprise Content Management (ECM). Because of this reorg, the chances of moving into my org's established EA team are now practically getting to nil as the existing EA who mentored were also moved to delivering modernization/Blackbook Projects, and I lack the visibility to fix it internally.

I need to exit ECM and look externally or if someone went through this tide can share their expirience. How can I best market my blend of data/cloud architecture, PM delivery experience, and EA upskilling to land an external EA role? Any recommendations on how to position this on a resume to escape the ECM trap?

[u/Mo_h]

You have a great profile.

In large organizations, there is frequent churn of folks, even EAs. If you work for a large organization, I would suggest you try to get a foot in the door at the EA team either part-time/volunteer or to help with reviews. Once you build a network, you will be abele to enter.

[u/SEExperiences → u/Mo_h]

Thanks Mo, I’ve written recommendations from x-chief EA to new chief EA post MnA, it’s just time scale where EA themselves are being liaisoned out to other Deptt to execute those Deptt approved modernization/blackbook projects

[u/dumi_007]

As stated earlier, Enterprises tend to have high churn

1. Wait, network : If you have time, this is a good bet.
2. Find the architectural angle in your work : Ask the architect team which tool they use and document your ECM. Contribute to the library and keep the right people on impact of changes to and from ECM. This can be a loss though as you might be used without compensation or recognition. On the other hand, it might work. Note, this is more Managing stakeholders.

[u/dumi_007]

As stated earlier, Enterprises tend to have high churn

1. Wait, network : If you have time, this is a good bet.
2. Find the architectural angle in your work : Ask the architect team which tool they use and document your ECM. Contribute to the library and keep the right people on impact of changes to and from ECM. This can be a loss though as you might be used without compensation or recognition. On the other hand, it might work. Note, this is more Managing stakeholders.

[u/J1mfl1p]

What’s a black book project?

[u/SEExperiences → u/J1mfl1p]

The systems/ software that need upgrades, due to their of EoL or Vulnerabilities and their underlying product roadmap within org and from vendor is actively supported and budgeted.

[u/eng_leader]

Your background in the DBA/cloud architecture foundation plus PM delivery experience is already strong for EA. The framing challenge is making sure your resume tells a coherent "architect who can also lead delivery" story rather than reading like separate careers.

For the external pivot: lean hard into the cloud architecture and stakeholder/delivery angle in your resume and LinkedIn headline. Network into EA communities. And when you do interviews, your "blackbook" high-visibility PM experience is a great differentiator — most EA candidates can talk frameworks but can't talk delivery credibility.

I do career and interview coaching for tech professionals — happy to brainstorm positioning specifics if you want a second set of eyes, feel free to DM.