Beyond the Job Title: Library IT DevOps Engineer

A library tech job interview with Vickie M. Karasic

A librarian learning more about a Library IT DevOps Engineer job

Core to LibTech Insights’ mission is demystifying the broad and dynamic field of tech librarianship in higher ed. In this series, we interview a librarian every month to learn a little more about their position. As library tech jobs proliferate, they sometimes come with unfamiliar, jargony, or intimidating titles. We want to go beyond the title and look at the responsibilities, skills, and joys that make up the job. We hope this series will increase your knowledge of library tech jobs and skills and offer you greater insight into the working lives of your colleagues.

For this installment, we spoke to Vickie M. Karasic to learn more about her job as the Library IT DevOps Engineer II. Check out our archive of job profiles. 💫


What is your job title and responsibilities? 

My current job title at Princeton University Library (PUL) is Library IT DevOps Engineer II. Very broadly, my responsibilities involve maintaining—including updating, patching, monitoring, migrating, and decommissioning—the physical and virtual infrastructure on which the library’s applications run. The DevOps part of my title means that my Operations team collaborates heavily with our developers to make joint architectural decisions.

Originally, I was hired at PUL as a Systems Administrator to manage both externally and locally hosted applications, including Springshare, Confluence, Drupal, and ILLiad. Even though all these products have since migrated to hosted solutions in the four years I’ve been in my position, I still provide user support for many of these services, including troubleshooting and training for library staff. 

Other parts of my work involve library- and campus-wide collaborations. For example, I sit on library committees for our web management and governance policies. I also work with folks from our central IT office (OIT) on architecture and security reviews when we introduce a new application to the library, and collaborate on joint efforts, such as authentication for our applications.


New White Paper from Choice

“Academic libraries are not starved for data: they are overwhelmed by it, and library leaders frequently find themselves paralyzed,” writes Sam Suber in Choice’s latest white paper.

 

In “The Optimized Library: Prescriptive Foundations for Resource Stewardship in an Era of Fiscal Austerity,” Suber shows how the wealth of data libraries collect, paired with the right mathematical framework, can help transform difficult decisions into strategic, defensible actions that maximize institutional value.

Download now

Can you describe your career trajectory leading up to this position? 

In college, I majored in Comparative Literature with a minor in French, and when I asked my advisor what most graduates do with a Comp Lit degree, he said, “They go to law school.” Not the answer I wanted to hear! I tried a few different fields before settling on librarianship: I applied to English/Comp Lit Ph.D. programs, tried teaching eighth-grade reading, and gave my advisor the benefit of the doubt by working as a paralegal for a couple years.

Ultimately, I reflected on my favorite jobs during and immediately after college, and they were all in the library. I loved helping people find the information they needed for their research and, mostly, getting to work with the library staff who made it all possible. Like any good future librarian, I researched careers that would let me combine my passions for literature and connecting people with information, and that’s when I decided that I wanted to become an English subject specialist librarian. I went on to get my MA in English/Comparative Literature and then my MLIS, concentrating in academic libraries, as the first steps toward a career that would let me keep up with my academic interest areas and research and publish in my field.

When I applied for my first library school internship, there were two positions available: a humanities research and instruction intern and a technology/information commons intern. I did not consider myself tech-savvy at all, but I applied to both, thinking that the humanities position was a no-brainer for me. However, the first interview I had was at the information commons, and honestly, the rest is history from there. Working in technology was exciting and pushed me out of my comfort zone in the best way. I ended up getting a lot of what I was looking for early in my career when, as a Digital Literacy Librarian, I had the opportunity to take on the role of liaison and bibliographer for the French and Francophone Studies department because of my French background. Although I enjoyed both the subject specialist and technology sides of librarianship, I decided that I wanted to focus exclusively on educational technology, where I could partner with faculty and students on really fascinating digital projects in my subject areas of interest. 

As many of us discovered, the COVID-19 pandemic put a wrench in our career plans! Working remotely forced me to start doing more of the behind-the-scenes work of managing the ed tech applications I worked with, including the online learning systems and Zoom, troubleshooting as well as liaising with developer teams to manage security, upgrades, and maintenance schedules. As I kept diving deeper into this technology, I would often hit blockers and get frustrated when I wanted to make a change to a UI or do a customization, for example, but I had to pass this work off to the developers. If I wanted to learn these skills, it would have been on my own time, and there wasn’t the opportunity to learn on the job while working in ed tech. And so, the unicorn, for me, was finding a position that would let me learn how to do development work as part of my job and be willing to teach me about application management as I went. That’s how I switched over to systems administration work and have since gained the skills to move on to a DevOps Engineer II level on my team. 

Does your position require any specialized tech skills, coding languages, and/or software knowledge? How or when in your career did you develop them?

I learned most of the specialized tech skills needed for my current position on the job as a Systems Administrator (a title that changed to DevOps Engineer I shortly after I started), and some I gained in library school. In a library school web development class, for example, I learned the basics of HTML, CSS, and JavaScript, which I still use to maintain customizations for hosted applications like Springshare and ILLiad. One of the first and most critical skills I learned as a DevOps Engineer was how to use the command line to manage servers. My fabulous colleague created a command line curriculum on GitHub that anyone can access. I still refer to it often and highly recommend it to early-career librarians or those switching gears in their career to systems/DevOps work, as I did.

Another totally new area to me was server automation; at PUL, we use Ansible for this. Learning how to write Ansible playbooks felt like learning a new language at first; a lot of practice and pairing (working together over Zoom and sharing screens) with colleagues has given me a solid skill set. In my current position, I also had to learn some key differences between operating systems, like Linux and Windows, in order to maintain the library’s infrastructure, as well as networking skills like load balancing and firewalls, all of which I had only heard of but never worked with previously. 

So far, I’ve learned just enough coding/programming to have a coherent conversation with my developer colleagues! For example, many of our library applications are built on Ruby on Rails, and one of my first group projects as a DevOps Engineer was a “book club” where other developers and I learned Ruby together. It can be difficult to teach yourself these skills in isolation, and I’ve been extremely fortunate to work with colleagues who have been generous with both their time and mentorship. I’ve tried to pay that forward by working with early-career librarians to guide them through the command line curriculum and to model that kind of collaboration. Most importantly, I’ve learned that it’s okay—and even preferable!—to “mess up,” because that’s how the learning happens.

Like you, many library students begin in undergraduate humanities programs before pursuing a library degree. What advice do you have for making the pivot from the humanities to a more tech-focused library position?

The most valuable skills that my humanities background has afforded me include critical thinking, curiosity, and a willingness to grapple with—and see multiple vantage points of—hard questions. I’d argue that these skills are also what made me well-positioned to transition to technology work. Oftentimes in IT, a problem we’re trying to solve—a piece of code, a server command, or a configuration setting—only has one right answer. However, I’ve found that my humanities background has allowed me to ask questions that get me to that answer differently than my colleagues who come from more traditional computer science backgrounds. Sometimes I’ll ask a question, and a teammate will say, “Oh, I’ve never thought of it that way—let’s take that path,” and we both learn something new. If you bring to the table that curiosity, analytical thinking, and willingness to really dig into a question, the “easy” part becomes picking up the “hard” skills that let you solve the technology piece of the problem. 

My advice to those transitioning from a humanities background to a more tech-focused role would be: don’t be afraid of positions where you don’t have every “hard” skill listed. Your humanities background and the critical thinking skills you’ve honed will make a transition to technology work more seamless. Your ability to ask the “why” around a problem, in addition to the “how,” will be invaluable to implementing technology in a thoughtful and meaningful way for your colleagues and end-users.

Has AI reshaped the day-to-day tasks of your DevOps work?

Working in DevOps, and more broadly, at a university, we’ve been having more and more conversations about how AI is affecting and will affect our work. Personally, AI has not changed my day-to-day, but it’s in the background now. For example, one of the third-party applications I manage for the library recently changed their policy to include user data in feeding its AI models unless we opted out, which we did to protect our users’ privacy. Another broad way this has come into my work is that I am part of a pilot program for an AI assistant tool this fall. I’m hoping to use it to simplify workflows that are a means to an end, like converting a complicated spreadsheet into a diagram that we can put under version control. That’s something I don’t need to know the mechanics of for my job, but it helps make my team’s documentation more useful and approachable. 

As a whole Library IT team, we’re actively developing our policies and practices around AI usage for code generation. Getting back to the humanities angle, our focus continues to be our colleagues and valuing their diverse perspectives, problem-solving skills, and ability to communicate openly about our work. So, while AI tools may help us get to an answer more quickly, our priorities revolve around respecting each other and valuing the human engagement around the tech issues that drive our work.

Of course, we have to ask: What is your favorite part of your position?

In terms of my day-to-day work, I’d say that my favorite part is finding new ways to engineer a task from beginning to end to make the process more efficient for both the application and the people who manage and use the application. An example of this that I worked on recently is our EZProxy application, which we run locally from a server on premises. EZProxy allows users to connect to our e-resources from anywhere in a reliable and secure way. Our implementation of EZProxy requires several custom configurations, and much of that had been saved on the server locally, which caused issues whenever we had to upgrade or rebuild the server for any reason. 

This past year, I worked with my colleagues to automate the build of our EZProxy server using Ansible playbooks. We did our initial work on our testing server, so that when changes were ready to go into production, we would not expect any surprises. It required us to overcome a lot of roadblocks along the way, including the fact that our testing and production servers had been configured slightly differently. Once we achieved parity in our environments, we then engineered an Ansible playbook to build the EZProxy application in a way that brings up the service with a push of a button and configures it exactly as we expect. This kind of end-to-end engineering for efficiency is really fulfilling to me, especially since it makes access to our e-resources more stable and secure on a long-term basis.

The nontechnical answer to this question is that my colleagues are the best part of my position! Getting to work with driven, talented, and just amazing overall humans, in addition to providing access to some of the world’s most unique resources and collections, is truly what I look forward to each day.