Professional Development

Why the 2nd job you ever get in libraries may be the most important of your career

I have a theory: I think the 2nd job you ever get in libraries is the most important. We’ll come on to the why in a minute – first of all I wanted to see if others’ experiences backed up my hypothesis. I put a poll on to Twitter, asking this: Which job was most significant in getting you to where you are in libraries now? Which most influenced you onto your current path?

I didn’t want to prejudice the outcome so I didn’t mention my theory. The results were interesting – they did seem to (just!) back me up:

 

36% said 2nd job, 34% said 1st job

Now, this is a very specific question. I’m not asking which factor is most significant to where people are now (a lot of people would say professional development outside of their 9-to-5 jobs, or their Masters perhaps) and I’m not asking which job is the most important in terms of people being in the information profession at all (presumably that’d be the first job for the vast majority of people) – it’s all about where you are, the path you’re on, the area of librarianship you’ve ended up in or the role you’re currently doing.

So I believe the 2nd job you ever get in libraries is arguably the most important because it dictates much SO of what happens to you afterwards. Obviously all jobs have an effect on what comes after them to some extent, but the 2nd job is something of a tipping point whose significance is, I’d imagine, not appreciated at the time most people are applying for it. Most people’s first library jobs fall into one of two categories – securing an entry-level position prior to doing the Masters (or becoming a graduate trainee), or securing an entry-level position because you’ve sort of stumbled into libraries accidently, and then finding it was a lot more interesting than you thought, so you stay in the sector. As has been discussed before, almost no first library jobs are beyond the entry-level – even people who have the Masters have to start at or near the bottom.

So – as a result of this, there’s not much proactive career choice about your first library job: you just need a job. Most people start as something like a ‘Library assistant’ – often a customer facing role, in the library itself, issuing books and helping with queries etc. You only really start to mould you career when you apply for that 2nd job – and my argument is that you need to make a really sound choice here, because it has a vital domino effect on your subsequent career. And actually, it’s tricky to divert off the path you choose for yourself at that 2nd job choice, because the 3rd job will (probably) be a higher up or better or related version of that 2nd job and (probably) pretty good, meaning you build a career off the back of it.

I’m obviously generalising here, and of course there will be exceptions – and throughout I’m imagining someone staying in more or less the same place, rather than having accrued several jobs at the same level on their CV simply because they’ve relocated a few times. But generally speaking, if you’re in that position that so many of us were in – you’re in your first library role, thinking it’s actually pretty good, wondering about making it into a career – you need to think carefully about the path you choose and, not least, how long that path is in reality.

I’ll take the academic library as an example, because that’s what I know best. Your first role was in Lending Services on the desk, so where do you go next? If you choose to stay in Customer Services then you’re looking at a Reference / Enquiries Desk role perhaps, otherwise there’s a big jump up to something like Customer Services Manager or Site Manager. If you go into the cataloguing side of things you could go for an Assistant Cataloguer post. You could try and move towards the subject librarian side of things by going for a Team Assistant post in an academic librarian subject team. Or there might be a ‘Digital Library Assistant’ type role, to do with digitisation or e-Resources. Whichever of these you choose, your 3rd job will probably also be in this area, is my point. And your 4th job too, perhaps. Of course people change all the time, but it’s quicker to develop a career in a roughly straight line. (I know this, because I didn’t - and have only in the last few months arrived at the job I actually wanted to do all along, and have much younger colleagues who took a more direct route…)

Part of the reason I’m writing this is because I know some people who’ve been working in libraries a good while, and are just sort of treading water – because that second job took them down a path, and now that path is blocked for whatever reason. There just aren't any more senior jobs than they're already doing, in the area they've come to specialise in. So I’d recommend getting hold of one of those organisational structure charts for your library (or the library you’d like to work in) and literally plotting your ideal route upwards, seeing what’s feasible, where the obstacles are, when you’d be waiting an age for people to retire or leave, etc. Some paths have very few destinations so are more competitive. Some might not even exist by the time you get to the good bit. Some paths might look like their beyond you in terms of expertise, but actually you could get there over time. Some paths have loads of destinations but aren’t well paid. Money certainly isn’t everything, but progression means a lot – you don’t want to get stuck in a rut.

It would be nice just to live in the moment, just to ‘be’ and not worry about all this stuff. But librarianship is a hugely competitive profession, with far more qualified librarians than there are jobs for qualified librarians. So it’s really never too early to be thinking about the career path you’re embarking upon – ideally, you need to start making informed choices almost from the very start.

If you’ve made it through all that - do you agree with my 2nd Job Hypothesis?

- thewikiman

#libday7: a Multimedia Journal

It's Library Day in the Life time again! Here is a week in my life as an Academic Liaison Librarian - works best in full screen mode:

.

(Here's a link in case you're viewing this in Google Reader and the embedded content doesn't display.)

I don't normally write much for this (last time round I did a video) because I think people are often over-saturated with LibDay posts - but I'm making an exception this time because my new job is so much more interesting than previous roles! Also, subject librarian is one of those roles which people find very difficult to really get a handle on - no two days are the same, so finding out what subject librarians actually DO is tricky. So the journal above is a fuller account.

Let me know if you have any questions about the job, particularly if it's an area you're wondering about going into yourself...

- thewikiman

Average is no longer enough? Noted. Now let's move on.

Picture of a spoon A lot is being made of the fact that in librarianship, Average is No Longer Enough. Was average enough at some point previously? Possibly; it doesn't matter. What matters is that there are enough librarians in the profession who love it enough that they don't want to be average, rather than reluctantly excelling themselves because they've been told to do so at a conference or by a blog post.

I predict that the total number of information professionals (in the current understanding of the word) will shrink at a fairly steady rate during my career. The Average will probably be the first to go (the Really Bad being, in my experience, remarkably stubborn). It'll be a Darwinian process - the people that really love this will probably be strong enough to survive, because they're the ones likely to be enthusiastic about embracing new challenges.

In a job market where there are far more qualified professionals than there are professional posts, the whole idea of trying to turn the drifters into yet more super-librarians is perverse anyway. The people who think average is enough are probably never at the kind of events where people say it isn't. Let's stop telling each other what we already know, take the non-existence of THE SPOON as read, and use our time in conferences and on social media to talk about something more useful - like specifically HOW to find your 'extra' rather than just the fact that you need to.

- thewikiman 

p.s Please use the Comments section for all puns about what mean-spirited post this is. :)

The MACHINES are Coming! Recent advances in library technology

Earlier today I did a session on technology and libraries, for the Prison Libraries Group at CILIP HQ. Prison Librarians are extremely limited in their access to technology - essentially they operate under the same restrictions as the prisoners, so not only can they not use Twitter, they can't even Google it at work! Here is the Prezi I used - it's a whistle-stop primer of recent advances, and while normally I try to make my presentations stand up on their own I'm afraid this one is really only the bare bones and I filled in a lot of gaps with what I was saying. (Works best on full-screen mode.)

I had a really good time even though I had to leave early due to starting my new job tomorrow. It reminded me again how diverse our roles are, and how two people called 'librarians' could go for years potentially without doing the same stuff. Having to make sure certain prisoners don't get access to fiction which glorifies the very crimes they are incarcerated for is not a Collection Development decision I'll be needing to make any time soon. And having to retain the catalogue in my head because not only is it not online but there isn't even a card catalogue is a skill I'm glad I don't need - I'd be really bad at that...

For the delegates

So for anyone who was there today, here are the links I mentioned that I'd include in this post:

- Thanks for having me, I had a great time! And especially thank you to Sibylla for inviting me. :)

- thewikiman

 

 

What's the key to a good interview - beyond the usual truisms we all know already?

There are myriad sources of advice for interviewing well, available online. A lot of them say the same things - anyone who turns up late, doesn't dress to impress, isn't attentive and engaging, only asks questions about things like the pay, or mumbles, frankly is probably not going to be the type of person who even knows they need advice on interviewing well. So what are the things you need to think about when going for a decent job, up against good people are who aren't going to make obvious mistakes? I have a weird relationship with interviews - I always think they've gone well, but I never get the job. My first library job in customer services, I didn't get it but was put on a call-back list for next time they had a position. My second job, as a Project Assistant, I came second and I only got the job because the successful candidate pulled out. On the JISC project I just completed, I was encouraged to apply and was the only person they interviewed - so short of putting my feet up on the desk and listing 'a penchant for theft' among my weaknesses, I was pretty much guaranteed to get the job. In between all that, I had two unsuccessful interviews (at York University) and one application that didn't even GET an interview, and prior to even working in libraries I had two unsuccessful interviews for researchy roles (thank God I didn't get those) - and in all of these cases, I thought the interview went well, because I don't get nervous for that sort of thing and I work so hard on preparing that I remember to make all the points I want to make, and I make them.

I finally broke this cycle a couple of weeks ago, when I interviewed successfully for a maternity cover at York - it's in basically my ideal job for now, the role I've been aiming for since I knew I wanted to do this as a career. I'll be the Academic Liaison Librarian for Music (where I did my MA, and know all the academics really well) and for Film, Theatre and TV Studies - that's all one Department, with a fabulous new £24 million building, below:

Picture of a lovely new building, the TFTV Dept at York University

So anyway, I got to thinking - what did I do differently this time than before (one of the panel had even interviewed me previously when I'd not got a job, which was lower graded and far less competitive) and what advice did I take into the interview that I found really useful?

Here are some things I did differently:

  • I wore a tie. I've not worn a tie since school, as I don't like them much - I don't wear them for weddings or job interviews, normally. I really wanted this job, so I figured I'd sacrifice my tie-related-principles in this instance… Did it make a difference? Maybe it did, I like to think my experience and ideas clinched the post though…
  • I went in with a better idea of what was really important about the post. When I wrote the Essential Advice for New Professionals blog post a while back, one of the most interesting things that came from the Comments that people wrote on it was the idea that not all Essential Criteria are created equal. Yes, they are of course all essential and therefore very important - but some of them will constitute a huge part of the job and others only a little. So it's important to have lots to say about the most essential of the essential criteria. I spent a good deal of time thinking about this beforehand, and talking to people I knew within the organisation who might know useful things. (Big thanks to Tixylix who pointed out the importance of working out which criteria are more vital than others!)
  • I revisited the feedback I'd had from my previous unsuccessful interviews. We all know how important it is to get feedback - how often do you actually read it again after you first receive it? In particular, the last interview at York (in an academic liaison assistant role) had had a lot to do with Information Literacy involved with the post. When they asked me about info lit in the interview I said everything I wanted to say - when I didn't get the post I was really disappointed as I actually thought I was over-qualified for it. But when they gave me the (very constructive) feedback, I realised they were completely right, and that I hadn't done nearly as well as I thought I had. I'd talked about Info Lit, demonstrated an understanding of it, listed my experience - but I’d not said anything innovative, original, or ideas based. Much of the role was about devising Info Lit programmes, so of course they wanted someone with a little creativity - I'd not shown any. So this time, as the role I've just got is also heavily Info Lit based, I was ready to hit them with some actual IDEAS, not just a summary of what I've done. (By the same token, I did just give them a summary of what I'd done in other areas - there's no point in explaining how you're going to take over the world in an area for which you won't actually have any responsibility if you get the job.)
  • I had to do a presentation. Previous roles haven't been high up enough to require this, but I made the most of it. We only had 5 minutes, and we weren't allowed slides or anything - but we could use handouts. In that situation, there's so little opportunity to make much of an impression, you have to use what is available to you, so I made good handouts. I had six anonymised quotes from academics that I’d spoken to when researching the topic (actually five, plus one from Andy Priestner) that related to the points I was making, and one of those quotes was from one of the academics on the panel. I think this went down well (could have backfired of course…) as it showed I'd done my homework - and it was directly relevant, not just crow-barred in there. So I think making the most of whatever opportunities there are open to you is important.
  • I left them with a CV. In Higher Education, everything is application form based. York's system is all online, and there is a fairly strict character limit so you literally can only just fit in what you need to say - as a result, lots of stuff I’d done wasn't on there. So I asked if they'd be interested in a CV so they could see all the other things that weren't on the form.
  • I tried not to JUST answer the question so much. By which I mean, every question in an interview is designed to assess you against set criteria – I tried to work out which of these criteria a particular question was pertaining to, and address that, rather than just the specific question. In the public sector there are no real spontaneous questions and nothing is asked without a purpose – they have to do everything incredibly fairly and openly. So there’s a grid of criteria, with questions that relate to those criteria, and each question you get asked will result in the panel writing down the evidence that shows you meet that criteria. Each question is given a score, then the highest total score wins. It really does seem to be that explicit and that simple – so you have to be hitting those criteria. It’s a question of asking yourself, what do they ACTUALLY want from me with this one..?
  • I answered the questions like the panel hadn’t ever seen my application form. I have a suspicion that application forms just get you the interview, but are then forgotten about once the interviews happen (and you get the job almost entirely based on the interview). So when I was asked a question I answered it fully, at the risk of repeating what they’d already read, rather than risking them not remembering what was on the form. ...

On top of this, I prepared answers for around 20 questions – there was only 1 question in the interview where I had to truly think on my feet. For what it’s worth, I had examples ready for:

1.  Prioritising workload

2.  Prioritising resources

3.  Knowledge of resources

4.  Working under pressure

5.  Managing a budget

6.  Creative problem solving

7.  Handling a difficult situation

8.  Delivering bad news

9.  Effective written communication

10.Effective oral communication

11.Information Literacy pedagogy

12.Recording and analysing user feedback

13.Working well in a team

14.Something outside of work that might help me in the role

15.Short-term plans

16.Medium-term plans

17.Questions to ask the panel

18.Why I wanted the job

19.Why I’d be good at it

20.Strengths and weaknesses

A lot of these came up, either directly or indirectly, so I was pleased I put the work in. Incidentally, back in the day when I had exams (A-levels and that sort of thing) a lot of people said things along the lines of "no point in revising on the day - if you don't remember it by then, you never will." I find this to be utterly misleading - personally I found reading my crib sheet right up until the 5 minutes before I went and announced myself was really valuable.

Anyway, that’s enough of that. What would you recommend people know about interviewing, that goes above and beyond all the usual stuff you can easily read online?

-    thewikiman