This year's always-fascinating and very valuable DAM Foundation Salary Survey came out in February, and there were some interesting - though also, possibly worrying - trends to analyze. First, though, the positives: DAM jobs are becoming ever-more-global, as companies begin realize the value of their digital assets (or, perhaps more accurately, as they discover how disorganized or missing digital assets are a huge money pit). This is an encouraging trend, and one I would hope continues to grow. And the influx of those with MS-LIS and other library degrees suggests that the value of accurate metadata is being recognized - though I'll explore a concern that brings up as well in a moment.
Mapping job titles to skillsets and salaries was noted as a continued area of confusion, and one I have certainly seen borne out myself, as well as amongst my peers; while it's to be expected in a still-somewhat-nascent profession, it can be an area of frustration, not only for the postholder, but for potential recruiters and managers. It may seem a minor point, but given the volume of confused recruiter calls I receive, I think it's worth digging into it for a moment, given this background from the survey analysis:
“Those with the term â€œDirectorâ€ in their title tended to make the highest salaries, and those with the term â€œArchivistâ€ or Archivesâ€ tended to have lower incomes. There were no other clear correlations between title and salary. One listing that included the word â€œSupervisorâ€ in the title made as much as other â€œDirectorâ€s; many with the title â€œSpecialistâ€ showed no appreciable difference than those listed as a â€œManagerâ€. This suggests that when reviewing the resumes of experienced DAM workers, an analysis of their actual daily duties, tasks, and projects may be more of an indicator of skill level than job title.”
Indeed, I've had to explain on numerous occasions that my current title, Content Librarian, isn't 'just' a content management role, and that I'm fairly senior in the hierarchy, where my tasks include crafting policies, setting standards and analyzing IT solutions - so likening it to a position such as 'the' University Librarian, rather than 'a' librarian who happens to work for a university, only makes sense to those coming from academia. When speaking with those from a straight-IT background, I explain it's a bit like a product or program management role with a lot of taxonomy bolted on, though any DAM professional knows that's still only a portion of 'what we do.' And having worked in traditional library and archival settings as well as in IT-focused environments, that brings me to my chief concern - will having more (very useful) library skills drive down DAM salaries, over time, simply through assumptions made by employers over title and background?
I've experienced the disparity between IT and library-land salaries first-hand - I began my career in IT, building websites and managing content back when it had to be done by hand, before DAM and CMS solutions existed. Even as software to help corral and catalog content and digital assets came into being, my salary working with those tools remained quite comfortable. Then I went back to library school, with a view toward using my IT background, augmented by my new taxonomy and knowledge management skills, in the heritage/academic sector - libraries, museums and archives. Despite having additional skills and experience, moving into that world reduced my pay by more than 50%; at the time, it was a manageable reduction, and I had a fantastic work environment and great colleagues, but it wasn't sustainable in the long-term. I returned to IT, and immediately more than doubled my salary - using the same skills, but with a different job title and cost center. While part of that jump was down to non-profit vs corporate budgets, even in the for-profit world, I know other DAM 'librarians' and 'archivists' who have found that a change in job title made a vast difference to them in terms of salary. It's anecdotal, to be sure, but it seems that those whose titles are more 'techie,' and less 'librarian-y,' often have higher incomes, albeit for the same sort of work - and good luck figuring out who is more junior or senior, if job title is your guide! Clearly, we have some work to do.
As more librarians - and more women - come into the DAM field, there is a danger that salaries may become depressed; we already know that the youngest cohort in the survey results have lower salaries, and that they are overwhelmingly female, though they have more library degrees. Having said that, it's quite rightly noted that their youth and relative lack of experience is likely the key driver behind their lower pay. But historically, the 'feminization' of a profession (think teaching, or, going back much further, textile production) has never had a positive impact on salaries; quite the reverse. It would be nice to think that we can ignore historical precedent and that we've moved beyond that - and I've written elsewhere about what it's like to be a mid-career woman in technology facing those issues – but given the existing salary gender gap in DAM, it's something we should continue to be vigilant about - let's make sure that gap is truly reflective of a historical blip, and that it doesn't become wider.
I am a firm believer in the value of a library background in the DAM world - combined with solid IT and management skills, it's an ideal, broad-based skillset for an evolving field. And I completely understand someone coming from years in 'traditional' library settings jumping at the first salary offered in a DAM role; given the lack of funding in academia and public libraries, it's (sadly) likely to be a big bump, regardless of how 'low' it might be for an IT or marketing position. But it's been well-documented that failing to negotiate in salary situations leads to lifelong repercussions, and as we see more highly-skilled, and likely previously-underpaid people coming into DAM roles, we should continue to share salary surveys and job title information as we build toward a more well-understood profession. Likewise, as hiring managers, we should do our best to keep salaries fair, and to help our recruiters and HR departments understand that a great DAM professional might not be obvious from their last job title or training.
My longer-term hope is that by highlighting the value of librarianship in digital asset management, we can help enhance information work all around, making the wider world realize that it's a useful route into a technical profession, and one that deserves to be better-known and appreciated, and paid on par with other IT jobs. An MBA may be one ticket to a 'good' salary in DAM, but we need to demonstrate that it isn't the only one, and that men and women have an equal shot at long-term advancement in the field.
Consider this a call to action to make an impact before the next salary survey!