Agreed that technical skills are not the be all and end all of this job. When I posted in the other thread about questions on the OSI model, those are questions I myself had been through, not set (and, for the record - I couldn't remember it all either, so fluffed a couple of entries, but still got the job as NM).
There is so much in terms of technical knowledge needed to deal with a modern school system that it's well above the payscale most LEA's advertise at. You can advertise your wish list but you are not ever going to get someone with all the technical skills required, nor should you expect to.
There is still a vast ocean between theoretical knowledge and practical knowledge in tech support. Yes, the theory is fabulous to know, in order to understand (and not just follow) best practice, and to be fulyl conscious of what you are doing. If it came down to it, though, I would employ someone with the practical knowledge over the theoretical, unless I was deliebrately hiring for the long term and could afford to have "half a man" while the theory specialist gained some experience.
As others have said, the most important thing would be troubleshooting and communication. Troubleshooting isn't following a checklist, either; it's the logical outlook and ability to break everything down into steps and cover the ground thoroughly. Communication is, sadly, a priority for schools as well; schools have the widest range of users of any location. What other industry would you support end users ranging from 11 to 70 with a range of skills from "can't work out computers need plugging in" to "hacked your network and stole your stuff"? You need to be able to talk to all of these people at the appropriate level, and quickly; neither students nor teachers are the most patient of people with technology.
As an example, my predecessor in this job was fantastic technically, but wasn't as hot on his communication skills; the end result now is that the network is working beautifully from the ground work he did, but I'm getting the praise because people find me more approachable. I could never have done the work he did, it was heroic; but nobody outside our department realises this because he built himself an ivory tower.
To summarise my ramblings: the kind of person is far more important for a technician than the qualifications. Techie is a first rung on the ladder; you won't get the expert, so get the good worker.
Hmm well the last questions I had at a job interview (for a 3rd line role) surprised me in that they said they were going to ask technical questions only ie none of this what have you achieved, whats your greatest weakness etc.
Fair enough but they then asked 5 (not very) technical questions
1) What is a Domain?
2) What is Active Directory?
3) How would you administer Server 2003?
4) How do you keep your server patching up to date?
5) How would you backup a server?
and that was the end of the interview
1. A collection of computers that are joined by a server or servers so as to apply security settings etc.
2. A database of objects ( users, computers , etc )
3. ??? not sure on this one would be good to get clarification or the answer ( group policy or what exactly ? )
4. WSUS ?
5. backup software to tape / nas or the likes with at least some way of taking a backup off site on weekends / holidays etc
Surely things like what you consider your greatest achievements would be included on your covering letter? ie. That letter would be crafted to highlight your biggest achievements from your previous role, whilst ensuring that they are relevant to the organisation you are applying to.
Asking someone about their greatest achievements would be a little odd if they've already discussed them on their letter.
Whereas, with technical skills, it is very difficult to list everything you know on your CV. My CV would be 10 pages long if I listed everything I knew relevant to a school's IT. Not to mention, a person can easily write that they can manage a 2008 AD domain but whether or not it is true is another matter!
Yes, non-technical skills (communication, ability to learn, enthusiasm etc...) are important but if they lack the technical skills, you'd be hiring someone who is actually going to slow you down and increase your workload for quite some time to come. If you wanted someone like that, why not look into apprenticeships?
In one case I recall, implementing a multimedia suite turned out to be litle more than unpacking boxes & plugging cables in..... & watching while someone else imaged the systems.....
Remember, there are an awful lot of 'professional' CV writers out there....... people should be prepared to have their claims & knowledge tested at interview.
With cutbacks in public spending, media techs and web administrators are likely to be amongst the first luxuries that schools will find it can live without, especially when it has those skills duplicated in the IT Support dept.
I was intrigued by the "Media Technician" comment earlier, and have just spoken with LEA re; job descriptions;
A Media Technician does not exist as a post in our LEA. An AV technician post does not exist within the structure either.
Their suggestion, is to adopt the policies of other secondary schools and to advetise for an IT Technician, but to write in context statements that include all the AV/Media work you will be expecting them to do.
I know what some of you are thinking...an IT techncian shouldn't be asked to do any of them!
So, is anyone else in the same position where they take on AV & Media work? Do you refuse, or like me, does the historical structure of IT Support mean you take on lots of things, that aren't technically in your job description.
Personally, i quite like my Tech and I being involved in the AV/Media work, and i try to be accommodating in most things when i feel i can be helpful, on the JD or not.
There are currently 1 users browsing this thread. (0 members and 1 guests)