 |
 |
Hi, You've gotten some great replies from techies. I'm a manager-type in a digital library team, so I thought I'd give you my perspective. We tend to need people with some coding skills, when we hire. That said, I'm much more interested in what people have done and how they think than what their title is. We don't have too many librarian/coders in the group but I'd welcome more of them. Having a librarian background is an asset, because you can understand our customers and translate what they are asking for into actionable tasks. Those of us who came up strictly through IT don't always understand that. We also have two groups in our tech services department that consist mainly of librarians with tech skills. When they hire, they need librarians, specifically, and the tech part is negotiable. I'm thinking it matters less what you put on your resume than it does which jobs you apply for. Don't fall into the female trap of thinking you have to know everything before you can apply. If you've got 2-3 of the bullet points, then press the button. Hiring managers like me don't expect to get everything we are asking for, but we ask for a range of experience to give people a better chance to match. I also want to address the topic of fixing rather than building. Most people would rather build than fix. Your skills would be an asset to any organization you apply for. Maybe you do want to modify your resume, just enough to point out what you enjoy doing. I know I'd love to hear that someone wants to make things better and not just build shiny new things! Hope this helps. -Carol On Wed, Sep 26, 2018 at 5:23 PM Salazar, Christina < [log in to unmask]> wrote: > > Thoughts anyone? > > > -- Carol Kassel Senior Manager, Digital Library Infrastructure NYU Digital Library Technology Services [log in to unmask] (212) 992-9246 dlib.nyu.edu