Which role yo?

Oh man! Ad-blocking software has been detected! :'(

This website is run by the community, for the community... and it needs advertisements in order to keep running. Blocking our ads means your killing our stats!
Please disable your ad-block, or become a premium member to hide all advertisements and this notice.

I haven't being offered these roles but lets say that they both pay the same and same commute.

Which role would you think is better career wise.

Also I know it depends on the persons skills.

Role 1 Systems Engineer

Working as a Systems Engineer in a large team of 15 people supporting a large internal infrastructure and a hosting
enviroment.


Support a internal private cloud. Which involved high level of virtulization knowledge.

Deploy servers and configure servers

Support SAN (Storage area network)

Provide end user support help (30 percent of the role)

Work to meet SLA


Basic Network Administration of the routers/switches in the large hosting and internal infrastructure.

Travel to customer and remote sites to do upgrades on servers

Find root cause of technical issues and fix it.

Patch management.

Help Junior memebers

Participate in an on call roster



Role 2 Technical Consultant

Working as a level Technical Consultant. In a team of 4 for a small company for 19 people.

Designed, Implemented and supported Microsoft Cloud online services such as office 365, Microsoft, Sharepoint, CRM online to organisations ranging from 10 to 10000 users

Looked and over saw the internal data agency infrastructure (13 production servers, a couple of network switches).

Configure Active Directory Federation Services for single sign on to intergrate the internal systems of clients with Microsoft Cloud applications.

Configured Microsoft Identy Manager to control securtity access to the client infrastrastructure.

Windows Server support/tier 3 support for client.

Made documentation and elearning videos.


Travel around the country and consult and work with Internal Infrastructure specialist, IT Managers and General Managers and CEO to discuss the technical needs and whats and meet the needed requirements to deploy projects.


Mentor Junior members of the team.

 

Oh man! Ad-blocking software has been detected! :'(

This website is run by the community, for the community... and it needs advertisements in order to keep running. Blocking our ads means your killing our stats!
Please disable your ad-block, or become a premium member to hide all advertisements and this notice.

If this was my career, I'd narrow down that list to the differences that mattered (i.e they both have mentoring junior team members) and get rid of the obvious ( Find root cause of technical issues and fix it. Really!! In a tech support job?? Who'd a thunk it) and then see what was left. After that my personal preferences would come into play.

 

It depends on what fits you. For example, looking at the description, the Systems Engineer role seems to expose you to virtualization/storage more.... the Technical Consultant seems to expose you more towards messaging role (Exchange, Office365, AD, etc).

Personally for me, I like working in large teams with a large infrastructure plus having the added bonus of virtualization/storage would make my choice easy. But you'd have to chose what suits you and what you see yourself doing.

 

Actually I have done both roles in my career and the one that offered me the most from an experience stand point was the Systems Engineer role whilst the Consultant offered me more money (it's usually expected that as a consultant you already know everything anyway whereas as the Engineer you're given scope to improve).

I would honestly go with the Engineer role as it offers more exposure, whilst the company with only 19 people tends to more often than not stifle career progression within the company.

As it stands right now I am classed as a Senior Windows Engineer although my day job at the moment is more orientated towards VMware technologies, I took a chance with a role nearly 2 years ago to move back into a Permy role and so far I haven't looked back and asked myself why, it's a far cry from previous roles where I have been a TDA (Technical Design Authority) \ Systems Design Architect (admittedly at the smaller company scale than large Enterprise organisations).

You really need to decide where you want your career to be and look at what offers you the best chance of moving in that direction.

 

Lol all good information remember the sys engineer is 30 percent is end user Work.

 

You need to decide which you prefer like soundian said there are two stand out role differences :

1. Datacentre, SANs, Virtualization

2. Line of Business Apps / Consultancy, CRM, Sharepoint, SSO, Office 365.

You can have a great career doing either.

 

To me the consultant role is more appealing for various reasons and as has been said consulting can pay very well indeed.

Assuming I'm reading it right and it's a role where you are consulting for clients then you should get good exposure to a number of different businesses and build up a good network of contacts as well.

Depends on what you want to do though, the consulting role won't likely be as technical with a bit more business focus which some techies don't get on with as much.

It's the sort of role I prefer, others will want the more hands on type jobs.

 

eye sea