[AusNOG] Off Topic - Brisbane recruitment recommendations

[Matt Smee]

I can see the 1-2 model being applicable for many small-medium organisations, but as they grow and the red tape becomes longer there's an almost inevitable generic 'call centre/helpdesk' that's slipped under it, acting as the new "level 1".


Perhaps an easy solution is to relabel your existing levels (for potential employees) by saying:

level 1&2

level 3


when describing the roles?


Cheers,

Matt.

________________________________
From: AusNOG <ausnog-bounces at lists.ausnog.net> on behalf of Cameron Murray <cameron.murray at gmail.com>
Sent: Tuesday, 17 May 2016 9:05:28 AM
To: ausnog at lists.ausnog.net
Subject: Re: [AusNOG] Off Topic - Brisbane recruitment recommendations

Coming back on subject a little we are looking to define our process and align more with the industry levels. Being that we are an MSP the industry Level 1, 2 etc. don't clearly apply or match the skills required 100%

I'm keen to see what others classify their Levels as and what the requirements of meeting these levels are.

Currently we run a Level 1 & Level 2 model which match the industry Level 2 & 3 somewhat so demonstrating these to potential employees is confusing and frustrating at times.

Reference: https://en.wikipedia.org/wiki/Technical_support#Multi-tiered_technical_support

Do many agree with these levels?

TIA.

On Mon, May 16, 2016 at 1:15 PM, Thomas Cuthbert <tcuthbert90 at gmail.com<mailto:tcuthbert90 at gmail.com>> wrote:
?
I've almost concluded that if you want a career in this space, at the moment, it'll be up to you to find a niche position that suits your skill set.
 ?
Or relocate to where companies require talent over COTS tools. Which as has been the theme to my career progression over the last 3 years.


Regards,

Thomas Cuthbert

On Mon, May 16, 2016 at 9:38 AM, Tim Raphael <raphael.timothy at gmail.com<mailto:raphael.timothy at gmail.com>> wrote:
Exactly, DevOps is a different slant on the modern "infrastructure as code" idea when compared to "NetOps". Although a new and hardly used term, NetOps is probably the best description of the specialised knowledge that comes with networks and automating them. There are plenty of people talking about NetOps but few job adverts asking for it.

I've almost concluded that if you want a career in this space, at the moment, it'll be up to you to find a niche position that suits your skill set.

- Tim

On 16 May 2016, at 9:34 AM, Will Dowling <will at autodeist.com<mailto:will at autodeist.com>> wrote:

Although this appears to have gone off on a tangent, to bring it back to Cameron's original question: Where is the best place to get a consensus on the state of the industry with regard to this particular skill set?

+1 from someone who considers himself someone with this skill set and is confused by the market :(

Unless you're working with a big enough content provider (e.g.: Googles' "Network Systems Engineer" positions mentioned as AusNOG), people are probably hiring this as "DevOps" with all the pain that comes along with a buzzword title.

NoOps is the latest one, though I haven't seen any jobs in AU for this yet - but is probably more targeted towards consumers of networks than anyone on this list.

Otherwise (and more often than not) it sounds like personal connections are still king for this space.

Forget it if you're looking to be in the architecture/design/leadership side of this (and even more if you're based in WA).

Happy to be proven wrong :)


Will Dowling

E: will at autodeist.com<mailto:will at autodeist.com>

_______________________________________________
AusNOG mailing list
AusNOG at lists.ausnog.net<mailto:AusNOG at lists.ausnog.net>
http://lists.ausnog.net/mailman/listinfo/ausnog


_______________________________________________
AusNOG mailing list
AusNOG at lists.ausnog.net<mailto:AusNOG at lists.ausnog.net>
http://lists.ausnog.net/mailman/listinfo/ausnog



_______________________________________________
AusNOG mailing list
AusNOG at lists.ausnog.net<mailto:AusNOG at lists.ausnog.net>
http://lists.ausnog.net/mailman/listinfo/ausnog


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ausnog.net/pipermail/ausnog/attachments/20160516/72a86e22/attachment.html>