ISO standards

[j4]

If you were trying to recruit an Information Systems Officer, as per  this job spec, what questions would you want to ask them in a technical interview?

Just, you know, wondering, out of curiosity, like.

Comments

[caramel-betty.livejournal.com]

The thoughts below mostly assume that you're expected to start in the job without technical training, but mostly just "Okay, this is your task and here are our house-styles/standards" sort of training. And I'm leaving out things like "Can they write?", "Can they manage people?" and "What's their project/time management experience like?"

The common thing that a few people I know have had in such interviews is that they seem to like asking fairly basic CSS questions to see if you're bluffing entirely or not - the difference between a block and a div, the difference between a class and an ID, that sort of thing.

Looking at that list of essentials, I'd be tempted to ask for details of a large roll-out you've done whilst listening for details such as: preparation/the system being used; how it was checked/tested; how/when it was rolled out (corporate policy for such changes where I am tends towards "early in the day, early in the week"); change management; and how you would have backed out if everything died.

If you claimed any knowledge of relational databases/SQL, I'd ask a few questions around that to see if you know the difference between a relational database and a computerized card-file, and poke about a bit to see if this is basically just "Well, my content management system keeps everything in MySQL so I know about databases really!" Similar sorts of questioning for Perl, Java, or XML/XSLT claims, if possible. If possible, seeing some examples of code (produced on the spot, or brought with) would be nice. Not that it needs to conform exactly with my own personal Nazi-ish preferences, but things like using comments and indentation reasonably would be good.

If they seemed a bit light on that side of technicalities, but I still thought they might be useful, I'd be interested to find out a bit more about the scope of documentation they'd created before. Is their extensive use of Microsoft Office applications restricted to a few 5-10 page essays, a poster in Publisher and pretty slides in PowerPoint?

Oh, one thing my manager has instituted for the role I'm in is a marketing test. Can they provide useful feedback on the look and feel, things which feel out of place, things which are wrong etc. on things like external websites or brochures. Not exactly technical, but seems to give her some useful information.

[j4.livejournal.com]

Gosh, that's a really comprehensive answer -- thank you! None of that lot would fill me with dread if I was asked it right now (which is reassuring in itself!) but I will make sure I've thought about sensible answers...

extensive use of Microsoft Office applications

I realise with horror that I've been using Word for twenty years. Made me the man I am today. 8-)

The marketing test sounds interesting, & a jolly good idea. If it's not 'confidential' I'd be interested to see the sort of thing you do for that. Not so much for this interview, as for general interest (and because one day I might be recruiting people myself!).

[caramel-betty.livejournal.com]

The marketing test is nothing special. It's usually just a print-out of a recent-ish copy of the corporate websites' front pages. Our group (documentation) has to balance the concerns of marketing on one hand (who want whizzy shiny things), designers on the other hand (and we've had a spate of really good print designers, who think very little about online considerations), and end-users/us on this other, magical third hand. So we're trying to fight the case of usability, accessibility, optimizing pages as best we can for Google, decent navigation etc., whilst there's a definite corporate brand being stamped on it by marketing/the designers.

Essentially, this means that there's scope for suggestions and improvements. Some of them would probably piss someone else off because of something the interview candidate doesn't know about (e.g. we have graphical menus we really, really want to get rid of, but marketing won't let us), but that's fine. It shows the candidate is thinking, and you can use that sort of conflict to drive the debate if you get a good flow here.

Mostly, my manager just wants someone here to say something that isn't completely bonkers. If they say "Oh, but that's all lovely" - either because they think it is, or because they think they should be a yes man and not criticize things, or because they just won't speak up for their own ideas - it's a mark against them. It's not a completely critical mark if they sail through everything else, but I gather that my manager likes people to do well here, even though it's essentially a five-ten minute browse of some print-outs (while a written test from the interview is marked, or whatever), and a ten minute chat.

[j4.livejournal.com]

Thanks! Sounds like a good way of seeing how people think about 'improving' a site. Though I'd want to make the point that I don't see any need to dive in and start "redesigning" just for the sake of it, to make my mark, shake things up, etc. ... okay, maybe that makes me too much of a yes-man, but really it's more if-it-ain't-broke-don't-fix-it.

So we're trying to fight the case of usability, accessibility, optimizing pages as best we can for Google, decent navigation etc., whilst there's a definite corporate brand being stamped on it by marketing/the designers.

Sounds familiar... "And it needs to be more webby." :-/

[caramel-betty.livejournal.com]

Sounds familiar... "And it needs to be more webby." :-/

My favourite incident like that recently was with a US designer. (One bit of the company is largely based in the US for sales/marketing/events purposes, because 95% the customers are in North or South America.)

Really very nice design came through, which would have been fabulous if we'd been printing it out on shiny card and sending to people as an invite-cum-agenda. But it didn't work well for the intended purpose of email flyer. Between a couple of us, we managed to massage the text and pictures into a half-way decent HTML+CSS email, which looked okay in the end.

One of the many concerns my manager took back in a three-way conference call with marketing+designer was a mention about how much information was being put in graphics. (For example, each day had its date done in a pretty little logo showing a sort of hand-drawn-ish box for that date, and the dates either side, with the middle one highlighted in a different colour.)

My manager pointed out that company policy is to not embed images in outgoing mails, but to leave links in. We find that embedded content like that hits too many spam filters. However, we are aware that many people won't download the images because many recent clients don't do it by default (privacy concerns when spammers do it, etc.)

"Oh," says the designer, "mine does that."

I believe at this point, I borrowed *headthump* from you.

[imc.livejournal.com]

Not that it needs to conform exactly with my own personal Nazi-ish preferences, but things like using comments and indentation reasonably would be good.

Heh. Last time I had a (somewhat informal) interview, the interviewer said something of the form "Well normally I would ask how well you think you can program, but I've seen your IOCCC entries (http://www.de.ioccc.org/winners.html#Ian_Collier) so I think we can assume you're reasonably competent."