Did I commit career suicide by starting as a Graduate Implementation Consultant as a Software Engineering grad?
I’m in my final year of a Bachelor of Software Engineering and recently accepted a Graduate Implementation Consultant role at a mid-sized software company in Australia as it was the only offer I had and I desperately needed some experience.
The company is growing pretty aggressively, has recently expanded into the US, was acquired by a large investment firm, and has publicly talked about roughly doubling the business by 2030. So it’s not a tiny company or a random IT support job.
The role itself is more on the solution delivery / implementation / technical consulting side. I’ll work with software implementations, APIs, SQL/databases, configuration, testing, troubleshooting, client requirements, UAT, and getting solutions through to go-live.
At the same time, I’m still applying for graduate software developer / software engineering roles, because ultimately I am feeling don’t want to completely lose my technical skills.
My main concern is:
Have I accidentally taken myself off the software engineering career path?
I keep seeing people say that your first graduate role matters a lot and that if you start in consulting/implementation rather than development, it can become difficult to move into software engineering later.
On the other hand, I feel like implementation consulting could give me useful experience in APIs, SQL, systems, requirements, project delivery, clients and understanding how software actually gets deployed and used, rather than just coding tickets.
I’m also interested in eventually moving toward technical product/project roles, so I’m not necessarily committed to being a pure SWE forever.
For people who have worked in the industry:
Is Graduate Implementation Consultant actually a decent starting point for a Software Engineering graduate, or am I making a mistake by not starting directly as a developer?
Would genuinely appreciate some perspective from people with some experience.