I Survived My First Faculty Evaluation (And So Will You)

Like approximately half of all academic librarians, I’m classified as faculty. This year, I went through my first faculty evaluation . . . and our evaluations fall in mid-October, six weeks after I started my position.

It was an intense six weeks.

My portfolio is 80% teaching/librarianship and 20% service. In six weeks, I assembled ten artifacts to represent my teaching, librarianship, and service; wrote a cover sheet for each artifact; wrote my teaching philosophy; and, of course, updated my CV (which it seems like I am never done doing). 

When I started this process, I was totally overwhelmed. How could I effectively present my case with only six weeks under my belt? I didn’t even know where all the restrooms were yet! But I just got my evaluation letters back, and I’m happy to say everything turned out well. Today, I want to share the five biggest lessons that helped me succeed during the faculty evaluation process. 

1. Stay calm.

This is the most important lesson I learned. Your first faculty evaluation will likely feel overwhelming and stressful, but remember: The librarians evaluating you want you to do well. Seriously! They want you to succeed in your role (otherwise, why would they have hired you?), and evaluation is about recognizing that success. 

Since my first evaluation only covered the first six weeks I was in the role, the pressure was even lower. As my faculty mentor said: “Don’t burn down the library, and you’ll be fine.”

2. Start now.

I consistently worked on my portfolio during those six weeks, and I still scrambled to make the deadline. This year, I’m determined to avoid any last-minute panics. Once I turned in my 2025 portfolio, I immediately started a list of items I wanted to include in my 2026 portfolio and jotted down notes for the cover sheets. I’m also trying to be more proactive about keeping my CV up to date. Once the fall semester begins, I’ll block out two hours in my calendar every week to work on my portfolio. 

3. Understand your context.

What does success look like in your library, to your professional assessment committee (PAC) and department head? Finding this out will help you establish clear, achievable evaluation goals. Meet with your PAC chair and department head well in advance of any deadlines and ask what their expectations are for you in your first evaluation. Keep an open line of communication going for feedback and questions. 

As I spent time co-working with new faculty colleagues across campus who were also preparing their portfolios, I noticed that evaluation procedures and standards varied from department to department. Every department has its own departmental standards and criteria, which explain what “Needs Improvement,” “Meets Expectations,” and “Exceeds Expectations” ratings mean in that particular department. It was important to focus on what my PAC and department head wanted to see from me during my first six weeks, rather than comparing my portfolio to those of my friends in chemistry, education, or business. That could have led to faulty expectations for my rating or to time wasted creating portfolio components I didn’t need. 

4. Don’t be afraid to ask for help. 

I’m not sure if this is just me, but I have a bit of a complex around the idea of “cheating,” which I think is left over from my undergraduate days. When I was assembling my portfolio, I was afraid to ask for help because I worried it would be considered cheating to ask my colleagues for feedback on my portfolio before I turned it in. But nobody covers this stuff in library school, and you’re never going to learn how to do it if you don’t ask. Plus, as previously stated, your colleagues want you to succeed, not to flounder helplessly in silence. 

I found it helpful to explicitly voice this concern, directly asking my PAC co-chairs and other colleagues how it would be acceptable to get feedback before I turned in my materials. To my surprise, everyone was happy to share examples of their own portfolios, answer my formatting questions, and provide feedback on which artifacts I’d chosen.

5. Don’t be afraid to advocate for yourself. 

My portfolio is 80% librarianship/teaching and 20% service. However, I also had quite a few scholarship items I wanted to include, including a conference presentation, my tenure guest editing a literary journal last fall, and a handful of creative and critical publications. In my opinion, I would have easily been able to “Meet Expectations” for scholarship if scholarship were part of my portfolio, but it isn’t. This is because my contract is for a three-year term and not a tenure-track position. I knew that my predecessor had been tenured, and the reason I’m not able to be on the tenure track is more a result of budgetary issues than anything else. It felt unfair that my predecessor would have been recognized for the very same work I was doing, but I wouldn’t be recognized due to factors outside my control. 

After some hesitation, I decided to bring these concerns to my PAC co-chairs. They encouraged me to include my scholarship in my portfolio, just under the “service” category. In my portfolio documentation, I made the case for how my scholarship could be understood as service and argued that with the combination of scholarship and service I was documenting, I should receive a rating of “Exceeds Expectations” in the service category. But the moment I submitted the portfolio, I felt a rush of embarrassment. I mean, who did I think I was? I’d only been here six weeks, and I thought I should receive “Exceeds Expectations”? I was overwhelmed by the urge to scrub all my scholarship, which surely wasn’t very good anyway, from my portfolio. But I’d already submitted it. There was nothing to do but wait.

As new librarians, it can feel precarious to advocate for ourselves; not only are we new to our institutions, we’re new to the field as a whole. Sometimes, we need to pick our battles, but some battles are totally worth fighting. When I got my evaluation letters back, I found that my PAC gave me an “Exceeds Expectations” rating for service, and my department head gave me the highest level of “Meets Expectations.” I know I would have received lower ratings if I had not advocated for myself. If you notice an element of the evaluation process that feels unfair, don’t be afraid to bring it to your colleagues and suggest a change.

Epilogue: Personal Reflections 

In the process of writing this post, I realized something: When I graduated from library school and entered the workforce, I had no idea that I would need to undergo a huge mindset shift regarding the evaluation of my work. I was raised to understand that “going above and beyond” is a success, and “just” doing what you’re supposed to do is a failure of will and intellect. If you’re only “meeting expectations” in the classroom, not exceeding them, are you going to get an A+? Are you going to land a GAship? Are you going to stand out in a brutal job market? 

But this mentality just doesn’t translate to a 9-5 job setting—or at least, not to mine. It’s like trying to use a meat tenderizer to prepare spinach or a salad spinner to prepare a steak. I remember how flabbergasted I was when my department head said he expected and wanted me to get a “Meet Expectations” rating. Let’s step back. Doesn’t it make sense that your supervisor wants you to meet their expectations? But I was so identified with the idea that “succeeding = exceeding,” I genuinely couldn’t understand him. What do you mean, you want me to meet expectations? I thought. Isn’t that like getting a C? 

That’s what makes this so tricky: Relentlessly obsessing over “going above and beyond” during my MLIS led to me acquiring the experiences and accomplishments that helped me land this job. But now that I have a job, I need to evaluate myself using a different mindset than the one that got me here. It took me months to realize that how success is evaluated in the workplace is different from how success is evaluated at school. Although tedious, the faculty evaluation process was a valuable exercise because it forced me into a new perspective. I had to go point-by-point through the departmental standards and criteria and connect them to the work I’d done, which forced me to see my work through the eyes of my colleagues (librarians with decades of work experience) rather than through my own (heavily biased, for reasons already discussed). More than any of the other lessons I learned during the evaluation process, it’s this mindset shift that will help me succeed in my 2026 faculty evaluation. 

Lessons Learned from Auditing 100 LibGuides

Last fall, my library undertook an ambitious—and necessary—overhaul of our LibGuide catalog. This was spurred on by the new requirements added to Title II of the Americans with Disabilities Act in 2024, which requires publicly-funded entities (such as universities) to ensure our digital content is accessible. However, before we could begin accessibility remediations, we needed to audit our LibGuide catalog to understand what we were working with. A couple weeks after starting as the new social sciences liaison, I was tasked with auditing the nearly 100 LibGuides in my subject areas and deciding which ones to remediate—and which ones to scrap. 

When I began this project, I felt totally lost. I had to quickly figure out the faculty and student stakeholders, pedagogical context, intended purpose, and actual users of each guide. I also wanted to be respectful to my predecessor, who had put so much hard work into creating and maintaining these guides. And I had some emotional hangups about deleting guides. When I saw a guide with only 15 visits a semester, I imagined those visits as one dogged student who had lovingly bookmarked the guide years ago and still returned every week. I didn’t want any patrons to feel ambushed by the loss of a favorite resource. Still, it was becoming clear that the number of guides I had inherited was no longer sustainable to maintain. 

The audit took about three months, and it was at times invigorating (Yes! I figured out how to organize the history guides!) and at other times grueling (Dear Lord, how many more are there?). Today, I want to share some of the lessons I learned from going through a major LibGuide weed as a new librarian. 

First of all: It’s okay to delete LibGuides.

The first time I gave the okay to take a guide down, I had visions of my inbox filling with emails from irate students and faculty demanding my resignation for destroying essential library resources. But that didn’t happen.

Yellowstone didn’t erupt, campus wasn’t struck by a tornado, and I wasn’t mobbed by angry patrons on my way to the staff lounge. And if you take down an old LibGuide, I can (almost) promise you won’t be either. 

This is partly because:

Delete/keep is not a binary. 

During the audit, we identified many guides that fell into a grey area between “permanent deletion” and “keeping public.” We used a variety of strategies to address these cases. 

Strategy #1. Quite a few course guides were used little enough to raise a yellow flag, but not so little that I felt comfortable permanently deleting them—especially because I hadn’t yet built relationships with the faculty who’d requested they be created in the first place. Additionally, I expected course-specific guides would have less use than general-purpose guides, even when active. In many of these cases, we decided to set the guide to private (if it wasn’t already). Then, we’d hide all guide content except the Home page, which we changed to display this message: “This guide is currently unavailable. Don’t worry—we’re still here to help! If you were using this guide for a class or need research support on this topic, please reach out to us at library@uni.edu.” This removed the need for us to remediate these guides, since we only need to remediate materials available to the public. With all the content hidden, the public can’t see it. But I can still access, restore, and remediate these guides on a case-by-case basis if a professor reaches out. 

Strategy #2. Some guides featured well-curated, high-quality content that was no longer relevant to our patrons. For example, I was faced with the decision of whether to delete several wonderful guides associated with courses no longer on offer. In these cases, I unpublished the guide. When a guide is unpublished, I can see it and patrons can’t. That means I can reference the resources my predecessor collected (and republish the guide if the course is offered again in the future!), but since patrons can’t see it, we don’t need to worry about Title II remediation right now. 

Strategy #3. Our guide catalog was a little bloated when we began the audit, so many of our guides contained overlapping content. For example, we had three guides for undergraduate primary source research. In these cases, we would choose one guide to overhaul, consolidate all the most important material onto it, and set the other guides to redirect to it. If anyone had saved links to the extraneous guides, they would be seamlessly sent to the newly-overhauled one. 

Strategy #4. For any guides we did decide to delete, we used a phased approach. Guides will be unpublished first. Then, after six months, they will be permanently deleted. This buffer period helps mitigate the chance of permanently deleting a resource that’s regularly being used by a patron. 

We also added new guides.  

This may sound counterintuitive. But even though we aimed to reduce the overall size of our LibGuide catalog, we also kept an eye out for needs that were not being addressed. The name of the game wasn’t “reduction,” it was “precision.” For example, by looking comprehensively at all our offerings, I realized the criminology program did not have a general-purpose research guide, so we created one. However, as I’ve discussed above, we also consolidated, unpublished, or deleted quite a few guides. Each guide should be evaluated in the context of our other offerings and our patrons’ needs. 

One more time: It’s okay to delete LibGuides. Even popular ones.  

There was a handful of popular guides I agonized over for a long time. They weren’t attached to any particular department; they were general-purpose AI and media literacy guides. But they were absolutely massive, and much of their content was already out of date even though they’d been updated fairly recently. I knew I did not have the capacity to continuously update these complex guides on fast-moving current events.

By talking to my colleagues and analyzing our usage statistics, I determined that no librarians were regularly using these for information literacy instruction, and the vast majority of traffic came from outside the university community (via Google searches). As a public university, we have a duty to serve Iowans beyond the boundaries of campus. But my colleagues pointed out that if I got too bogged down maintaining these resources, it could take me away from helping students and faculty. As much as I wish I could clone myself and help everybody, it’s just not possible. 

In the end, we decided to either delete or unpublish all the guides in this particular set. The library continues to provide support on these topics through more sustainable means, like e-resources, workshops, and credit-bearing courses (including the one I’m teaching next month). 

Overall, this project has shifted my LibGuide approach from “just in case” to “just in time,” similar to how many of us are adjusting our collection development models to account for dwindling resources. I realized that the vast majority of my LibGuides were created “just in time,” in response to a direct faculty request. But as campus needs shift over time, a guide that was once created “just in time” might now be hanging on “just in case.” I need to regularly evaluate my guides to prune those that are no longer serving the campus community and create space for new guides to flourish. 

Many thanks to Claire Bowling, our Instructional Design Specialist, who spearheaded this project, implemented all the accessibility edits, and answered my endless questions. 

Let’s Discuss: How Should We Handle AI in One-Shots?

Whenever I teach a one-shot, there’s an AI-shaped elephant in the room. The rapid advancement of AI technologies has changed so much about how students approach completing assignments, which shapes the dynamic in the one-shot classroom. I worry that students, never the most enthusiastic one-shot attendees, now feel that library research skills are less relevant than ever.

On the surface, it appears that consumer-focused AI tools like ChatGPT are useful for student research. They can help students quickly locate sources, learn about a topic, summarize difficult peer-reviewed articles, and cite their sources—all tasks that are relevant to the learning outcomes of my one-shots. However, as I’ve discussed previously on ACRLog, I believe that higher education should be a place of particular caution when it comes to AI. The hazards of AI, such as copyright infringement, hallucinations, bias, lack of privacy, and the potential erosion of critical thinking skills, are particularly dangerous in an educational context.

Moreover, as Allison and DeRewal (2024) have pointed out, the missions of AI companies are directly opposed to our missions as libraries and universities. The goal of products like ChatGPT and Comet—and even AI tools built into educational products, like Primo Research Assistant—is to make tasks as easy as possible for the consumer. Our goal is to educate students, which cannot happen by making things as easy as possible. We intentionally build friction into our assignments and activities in order to help students develop the skills necessary to overcome inevitable difficulties in the research process. ChatGPT’s goal is to eliminate challenge; our goal is to strategically introduce it, because students can’t learn without it.

Here are the research-related AI applications I’m most worried about in regards to undergraduates I teach:

  • Using AI tools to find sources (“Find 5 peer-reviewed articles about climate change.”)
  • Using AI tools to learn information (“What are the main causes of climate change?”)
  • Using AI tools to summarize articles (“What are the main ideas of this article?”)
  • Using AI tools to generate citations (“Please format this list of sources into an MLA Works Cited page.”)

(In general, I’m also worried about students using AI tools to generate the text of their papers. However, that falls outside the scope of one-shot instruction, so I will not address it here.) 

With all of this swimming around in my head, it can be overwhelming to try to productively address AI issues in a 50-minute one-shot, especially when I have so much else to teach. Whenever I feel lost about how to tackle an AI-related issue, I return to three touchstones: clarity, transparency, and guidance. I believe that undergraduate students today deeply value these qualities in the classroom. So when I tell them a proactive, firm “no” (clarity), I immediately follow up with transparency (“here’s why the answer is no”) and guidance (“here’s what you can do instead”). 

I want to use the remainder of this post to share three of the strategies I’ve been using to address AI in one-shots—but I am just one librarian, liaising with the social sciences at a regional comprehensive university in the midwestern United States. My context may be very different from yours. I would love for folks to jump into the conversation and share strategies, thoughts, and questions in the comments below. 

Strategy #1: Address AI upfront

I always start my one-shots by talking about AI for a few minutes. I don’t want students zoning out the entire session, thinking “I’ll just use ChatGPT for this,” so I try to capture their attention by posing the question: Why don’t you just use ChatGPT to research this paper? Why are you here at the library today? Per my transparency touchstone, I’m explicit about my intentions with having this conversation. I know this is something some of you might be wondering, and I often get questions like these from students, so I wanted to take a couple of minutes to talk about this before we dive in.

I state that in general, when students ask me this question, I do not recommend the use of AI for completing research assignments. I share specific examples of times I’ve witnessed AI-assisted research going wrong: Cornerstone students combing the stacks for books that were never written, law students tearing their hair out as they search for Supreme Court cases that don’t exist. I try to get vivid and lean into the storytelling. 

I don’t want that to be you, I say. So today, we’re going to walk through how you can research this paper without running into any of those issues. Sound good? 

Strategy #2: Demonstrate better open web searching

Let’s be honest: Using Google is miserable. Half the websites are paywalled, and the other half are sponsored links that relentlessly spam you with pop-up ads. No wonder students are increasingly turning to Google’s AI overview and AI chatbots to find information. The interfaces are far cleaner and easier to navigate; this not only provides a better user experience, it also appears more professional and, therefore, reliable. 

But as information professionals, we know these AI tools aren’t actually more reliable, considering the frequency and magnitude of hallucinations. To provide an alternative when students want to search the web for information on a topic, I show them how to limit their search results by site domain (or even a particular website, if relevant to the course). I generally recommend .edu, but I sometimes show .org and .gov as well. I may also show how to use phrase searching or the intitle command in a basic Google search. Students are often surprised and excited to see how simple tricks can make Google searching so much easier. 

Strategy #3: Cultivate college-level research skills 

In most cases, it is currently illegal for a student at the University of Northern Iowa to download an article from one of our subscription databases and then upload it into a generative AI tool, such as ChatGPT. In some cases, it is not the student who would be liable for this action, but the library. 

Whenever I tell students this, it makes an impression. They’re especially shocked to hear that in some cases, their actions could lead to the library getting in trouble. I clarify that this is a result of the agreements we make with scholarly publishers in order to make their books, articles, and other materials available to UNI students. I explain that students often ask whether or not they can use ChatGPT to summarize sources for their research papers, and this is part of why their librarians and professors are telling them no.

However, I emphasize that I understand why students ask me this question—because, truly, I do. It’s difficult enough to understand peer-reviewed research when you’re new to academia and/or to a particular discipline; on top of that, many students are never actually taught how to read research, how to read in college. It’s very different from how we read for leisure or how they read to perform well on standardized tests in high school. Students may feel lost, like asking ChatGPT to summarize a difficult passage or even an entire article is the only way they can succeed in class. 

There’s only so much I can do in a one-shot; reading research is a skill, and real skill development takes guided practice over an extended period of time. Nonetheless, I try to plant a seed. I reassure students: It’s okay if reading peer-reviewed research is hard. I provide a few tips about strategic reading, such as starting with the abstract and conclusion, making multiple passes, and annotating key points. I love this guide from Brown University and often share it with students. I also take a few minutes to explain citation chasing. Citation chasing is another college-level research skill that seems second nature to us, but it won’t occur to most freshmen until somebody takes the time to teach them about it. You don’t need to ask a generative AI tool for “5 sources about climate change” because once you find one good article or book chapter, there are tons of additional sources right there at the end. 

—

I am in no way an expert on AI or one-shot instruction; this is only my second semester of teaching. I don’t come to this with the intention of sharing expert knowledge, but with the hope of starting a conversation. I would love for the comments section to become a place for folks to share experiences and brainstorm strategies around addressing AI in one-shots. Here are some questions to get started: 

  • How have you been thinking about AI in your one-shots? 
  • What strategies have you used to address AI in your one-shots? What has worked well, and what has not worked as well?
  • What kinds of conversations have you had (or not had) with your faculty about classroom AI policies, AI usage in research assignments, and so on?
  • Any other thoughts or questions that this post prompted for you!

Let’s Talk About It: AI and the Academic Librarian Job Search

Last week in the credit-bearing course I co-teach, we asked students to listen to a podcast episode from MIT Technology Review about how AI is impacting the job application process. Listening to the spirited classroom discussion led me to reflect on my own job search this year and the role AI may have—or may not have?—played.

During my job search (November 2024-March 2025), I experienced a lot of AI-related anxiety, just like my students feel about their own impending job searches. What I remember most was the anxiety triggered by not knowing. Would a human ever look at my CV and cover letter (which I spent hours customizing for each application), or would an AI tool scan and discard it in seconds? What does AI even look for in CVs and cover letters? How could I craft a job application that would stand out to both human and AI reviewers? If I was not offered an interview, was it because my CV didn’t include keywords an AI tool was programmed to look for, or was it because a human had holistically reviewed my application and determined I was not the right fit? How could I revise my materials to have a better chance at future applications? It felt like I was throwing spaghetti at a wall I wasn’t allowed to see. 

I applied to positions at 26 academic libraries, and only one—at Gwynedd Mercy University—gave me the ability to opt out of having an AI tool scan my resume and opt in to the guarantee of a human reviewer. This was accompanied by a statement that my selection would not affect my chances of being offered the position. No other universities provided either a) information on if or how AI would be used to evaluate my application or b) the ability to opt out of AI being used to evaluate my application and/or opt in to the guarantee of a human reviewer. 

AI’s impact on the job search is far-ranging and ever-increasing. Current AI applications include employers using AI to conduct interviews, research candidates, and write job ads and job seekers using AI to write applications. But today, I’m going to focus on employers using AI for the initial scan of an applicant’s materials before an interview is offered.

I understand why, on the surface, tools like AI resume scanners may seem like positive additions to a library search committee’s toolkit. As job creep and budget cuts worsen year over year, librarians are stretched more thinly than ever, constantly asked to do more with less. Additionally, many library positions are being eliminated or left unfilled, which results in a shrinking job market with larger applicant pools for the few available positions. Using AI to scan resumes and evaluate cover letters could save valuable time, freeing search committee members to spend more hours on essential library work. 

However, I suggest that “saving time” is an insufficient positive to counteract the negatives of using AI to evaluate job applications. One significant cause for concern is the influence of algorithmic bias. Some advocate for the use of AI to evaluate job applications because they believe it will eliminate human bias, but unfortunately, that isn’t the case. AI is built by humans and trained on data created by humans. If a hiring algorithm is trained on a biased, incomplete, or nonrepresentative dataset, unfair outcomes may result.

One notorious example of this occurred at Amazon a few years ago. They trained a hiring algorithm on the resumes of people who already worked at Amazon, then deployed it to evaluate incoming applications. The problem? Like much of the tech industry, Amazon is dominated by men. The algorithm accidentally learned that candidates whose resumes included the word “women’s” or mentioned all-girls’ schools were less likely to succeed at Amazon. It penalized those applications in favor of applications from men. This led to the algorithm being discontinued in 2018.

AI tools may overlook qualified candidates for other reasons as well. Without the ability to reason like a human, AI may discard strong candidates due to non-standard resume formatting or unusual (but applicable) work experience. Data privacy is another issue that should be particularly worrisome to librarians, given how our profession values privacy as an essential component of free and fair societies. These AI tools may be operated by third-party vendors that do not adhere to the same privacy standards we do, and resumes, CVs, and cover letters contain very sensitive information. Who is collecting this information? Who can access it? How long is it being retained? 

In short, although the job market for academic libraries is getting worse, AI is not the solution. It will only introduce more problems, such as discarding strong candidates, and intensify problems that already exist, such as bias in the profession. As a profession, we need to be proactive about discussing these issues and setting standards. Do we think it is acceptable to utilize AI to evaluate job applications? If so, when and how? For the reasons briefly explained above, I argue that we should not use AI to evaluate job applications at this time. 

However, I understand that while our profession leans more AI-critical than some, many librarians are not quite as AI-critical as I am. Therefore, I also suggest that if AI is used in order to evaluate job applications, the following safety measures should be in place:

  • A clearly worded, prominently displayed way for the applicant to opt out of AI being used to evaluate their application and opt in to a 100% human review.
  • A clearly worded, prominently displayed guarantee that whether or not they opt out of AI review will not impact their chances of being selected for the position.*
  • A clearly worded, prominently displayed explanation of applicants’ data privacy rights in the case they select AI review (who will have access to their information, how long will it be retained, can they get it deleted (if so, how), and so on).  
  • Clearly listed contact information for somebody the applicant may reach out to with questions or concerns about any of the above.

Finally, whether or not AI is used in order to evaluate job applications, a transparency statement must be included on all academic library job ads, explaining the following:

  • Whether or not AI will be used to evaluate applications. 
  • If yes, how AI will be used (in detail: at what stages, which platforms, and so on).
  • Why this is the library’s policy.

Additionally:

  • This transparency statement must be clearly worded, detailed, and prominently displayed on the job ad. 
  • There must be clearly listed contact information for somebody the applicant may reach out to with questions or concerns about the transparency statement.
  • This transparency statement must be accessible at all times during the application process. If the job ad is taken down before the position is filled, for example, this statement could be attached to email correspondence with applicants under consideration. 

*As I’ve explained above, I actually do think that AI evaluation negatively impacts a qualified candidate’s chances of being selected for a position. However, I presume that somebody who chooses to use AI to evaluate applications would disagree with this. What I’m trying to get at with this bullet point is that the applicant should have a tangible record clearly stating that applications will—theoretically—not be preferenced based on mode of review (human or AI) but will be judged based on content, with the same rubric applied regardless of the mode of review.

–

In this post, I have chosen to focus on AI usage in evaluating job applications, but there are many other intersections of AI and academic library HR that should be frankly and transparently discussed. For example, considering the ethics of our profession, what standards should we implement around using AI to interview candidates, monitor employees, or evaluate employees?

I am not an HR professional, nor have I ever sat on a search committee. My perspective is that of a recent job seeker, and my intention is to jumpstart conversation among academic librarians more broadly. To that end, I would deeply appreciate hearing your perspectives in the comments. Here are some questions to prompt discussion, but I would like to hear any thoughts this post has brought up for you. 

  • For all: What do you think of the policies I’ve proposed in this post? Do you have questions, concerns, or additional or alternate suggestions?
  • For those who have recently searched for a position within academic libraries: What AI-related concerns or experiences did (or do) you have throughout your job search? How much transparency did you experience regarding how AI was used to evaluate your application? 
  • For those who have recently served on a search committee: Have you used AI or considered using AI to evaluate job applications? If so, how and why? I’m also wondering how much choice we have in the digital HR infrastructure we use for academic library job searches. For example, if the university typically uses AI for a first-round scan of applications, would it be possible for the library or other academic departments to opt out (or vice versa)? What would this process look like?

What I Wish I Knew Before My First Library Conference

Last month, I gave my first lightning talk at a library conference, the Iowa Library Association Annual Conference (ILA). I’ve wanted to present at a conference since I started graduate school, so this was an exciting milestone. My lightning talk was about conducting an e-journal overlap analysis, and it went smoothly—but that’s not what I want to talk about today. 

As I reconnected with old friends, jostled to get morning coffee before it ran out, and relaxed on the sunny patio between sessions, I found myself reflecting on how different I felt compared to when I first attended ILA last year. This year, even though I was a little nervous about presenting for the first time, I felt comfortable and confident navigating the conference and talking to other librarians. But when I first started out as a library professional, working part-time and getting my MLIS, conferences scared me. I knew they were valuable opportunities, but I felt lost and overwhelmed trying to navigate them. 

Here are the four things I wish I could go back and tell myself before my first library conference. 

Pace yourself.

This might have been the hardest lesson for me to learn. I’m a little notorious among friends and family for my Scrooge McDuck disposition. At first, I refused to skip a single session of any conference I attended; I figured that I had already paid for the entire conference, so if I didn’t attend the entire conference, I was flushing my money down the drain. I’m sure you can imagine the mental burnout and physical exhaustion that followed. 

Some level of tiredness after a conference is inevitable, but once I discovered I could skip a Wednesday dessert reception without the sky falling down, I began to recover faster and feel less stressed about conferences. I slowly shifted my goals from “attend the conference” to things that were more measurable, like “talk to five new people” or “learn about open access.” I finished conferences feeling more successful because I was able to identify which specific sessions and opportunities were in line with my career goals. 

Plan your pitch.

As an introvert, I was incredibly anxious about attending conferences. I found it helpful to plan my “pitch” ahead of time, rehearsing it over and over again on the drive to the venue. 

My “pitch” is what I’d say whenever I needed to introduce myself to someone new. I soon figured out that an effective pitch didn’t just describe my present; it gave a sense of my future goals as well. I would lengthen or shorten my pitch depending on the situation, but the full version went something like this: I’m a first-year MLIS student at the University of Iowa, and I work in technical services at Iowa’s law library. This is my first conference! I’m here to meet librarians and explore careers in [conference demographic: academic librarianship/libraries in Iowa/liaison librarianship/etc]. Once I was job-searching, I said so explicitly. 

I also planned the questions I wanted to ask the librarians I met at the conference. I wrote them down in a notebook and reviewed them in the hallways between sessions to make sure I wouldn’t blank. (Bringing a notebook and pen everywhere also gave me something to do with my hands.) Some examples of the questions I asked:

  • What are your duties in your current role? 
  • What skills and experiences prepared you for your current role?
  • What are the biggest joys and challenges of your current role?
  • What’s it like working at [type of institution—community college, liberal arts college, R1, etc]?
  • What advice would you give to someone just starting out in the field?

Targeted networking is key.

Even though there are usually student discounts and scholarship opportunities, conferences still cost money. It’s important to spend that money as wisely as possible. For example, I always knew I wanted to be an academic librarian, and I hoped to be able to stay in Iowa after I graduated. That meant I needed to target my networking to academic librarians in the state of Iowa. Through trial and error, I discovered that the best conference for me was Iowa ACRL. 

Every conference has its trade-offs, and there isn’t one “best conference” for every librarian or library student. For example, the national ACRL conference would have been more valuable to me if I intended to leave Iowa and I wanted to network with other academic librarians across the country. If I were also exploring public librarianship, ILA would have been the most useful, since it attracts both public and academic librarians.

The bottom line: Think about what you want out of your career, and ask your mentors how you can target your networking to achieve those aims. 

You deserve to be here.

Seriously. Nobody is going to kick you out because you’re a student. When I started going to conferences, I was worried I didn’t have sufficient “credentials” to be there. But conferences are all about learning and networking. Being a student IS your credential! 

Maybe this is the Iowan in me, but I was also worried about being a “bother” or a “nuisance” to others. I would avoid talking to people because I didn’t want to disrupt their meal or interrupt them texting a friend. However, for better or worse, meeting new people is the point of conferences. Don’t be afraid to say “Excuse me, is this seat taken?” and sit down next to someone new. You never know where it might lead.

Here’s an example from my own experience. When I was a first-year MLIS student, I attended my very first conference: Iowa ACRL 2024. I forced myself to sign up for the Thursday evening dine-arounds, and, not recognizing the names of anyone who had already signed up, I just picked the restaurant with the most vegetarian options. But when I got there, I slowly realized I’d ended up at a table populated almost entirely by senior leadership at Iowa State University Libraries, University of Northern Iowa Libraries, and the Iowa Library Association.  

My first thought was “Oh my God, I’ve totally messed up. I should not be here. I don’t have anything worth these people’s time to contribute.” But (in true Iowa fashion), I felt even more strongly that it would be too rude to leave, so I forced myself to talk to the librarians at the table. I pulled my pitch out of my back pocket when they asked me about myself, and I made conversation by asking questions about their careers, working at Iowa State and UNI, and the challenges and joys in their work. 

The librarian I sat across from a year and a half ago is my supervisor today. You never know the kinds of connections that can take root at a conference. Pace yourself, come prepared, be intentional, and, above all, remember that you deserve to be here.