u/EfficientRhubarb5329

I’m currently in a stable government software development role using a more niche tech stack (Apex, PLSQL). I may have a 2-year opportunity that would give me hands-on experience in a much more marketable technical area (AWS).
The downside is that I may lose my permanent status.

Work revolves around:
- cloud account setup and management,
- installation and configuration of vendor products,
- some ongoing maintenance of those products,
hands-on technical work,
- development and maintenance of supporting documentation,

- From a career-growth perspective, is 2 years enough time to build valuable experience and pivot into better opportunities later?
- Is giving up permanent stability too risky in the current Canadian tech market?
- I’m early in my career and trying to decide between stability now vs building more marketable skills for the future.

Would appreciate honest advice.
Thanks.

I’m considering a 2-year opportunity on a platform engineering team and trying to understand whether the work would be valuable for long-term career growth.

The role is helping application/project teams onboard to cloud, supporting cloud account/environment setup, helping with installation and configuration of software on cloud, creating reusable images or setup processes, and helping transition project work into an operational service model.

My concern is that I would be leaving a stable permanent role for this 2-year opportunity, so I want to make sure the experience would actually build marketable platform engineering skills rather than just being coordination/process work.

For people working in platform engineering:
- Does this sound like real platform engineering experience?
- What parts of this role would be most valuable for future DevOps/platform/cloud roles?
- What red flags should I watch for to avoid ending up in mostly coordination/process work?
- If I take this role, what skills should I focus on building during the first 6–12 months?

I’m early in my career and trying to weigh stability against stronger technical growth.

I’m currently in a stable government software development role using a more niche tech stack. I may have a 2-year opportunity that would give me hands-on experience in a much more marketable technical area (AWS).
The downside is that I may lose my permanent/indeterminate status.

\- From a career-growth perspective, is 2 years enough time to build valuable experience and pivot into better opportunities later?
\- Is giving up permanent stability too risky in the current Canadian tech market?
\- I’m early in my career and trying to decide between stability now vs building more marketable skills for the future.

Would appreciate honest advice.
Thanks.

I’m currently an indeterminate in the federal public service. I have an opportunity for a 2-year term role in another team that would give me stronger experience in a high-demand technical area.
The concern is that I may have to give up my indeterminate status.

For those familiar with federal staffing:
- how risky is this?
- Is leaving an indeterminate role for a 2-year term ever worth it if the experience is significantly better?
- What should I confirm in writing before even considering it?

Would appreciate honest advice.

Thanks.

EDIT: My ultimate goal is not government.

I am aiming for a high paying role in the private sector. This term role might help me get there. I am considering this opportunity also because it’s difficult to find a junior/entry level role with this skill. So I am hoping I build this experience in the 2 years term and eventually move into the private sector.

View Poll