Expert publishing blog opinions are solely those of the blogger and not necessarily endorsed by DBW.
Lately there have been rumors within the profession that it’s becoming harder and harder to hire a good ebook developer. Is this true?
In my personal experience, it is.
But I also think there are broader issues at play than just a shortage of talent. A conversation on the subject during a recent #eprdctn hour (hosted weekly on Twitter under that hashtag from 11am to noon EST) pointed to several possible explanations.
For one thing, learning the skills and toolsets required of an ebook developer is neither easy nor cheap. There are college-levels programs and courses (at Emerson College, Simon Fraser University, Ryerson University and via the eBook Ninjas, to name a few) whose ebook development classes are taken by post-grads, sometimes on their own time in the evenings. Others can cobble together self-taught courses at Code Academy and Lynda in order to synthesize an education on their own. Still, all these approaches take considerable investments of time and money.
Second, the skills required of any ebook developer worth her salt are deep and technical. So the wage reward of the average entry-level publishing job just doesn’t usually line up with the knowledge-level required of most qualified candidates.
As ebook production skills are an offshoot of web development skills, it is my sneaking suspicion that many with that skill-set just wouldn’t contemplate a $30,000-a- year salary, as one tweeter pointed out:
I have no evidence/anecdotes to back this up, but I wonder if some of it is related to the tech skills required vs. pay offered #eprdctn
— Chelsea Hanna Cohen (@chelseahannac) June 10, 2015
Given the opportunities available in other industries, someone with rockstar coding skills probably is not going to like the “pink-collar” pay levels publishing typically offers. (Which isn’t to say that I don’t have many, many outstanding rockstars as colleagues.)
The maturity of both the tools and the subcontractors is also a factor. Very good EPUBs are being turned out of both overseas conversion houses and publishers’ own production departments, through tools like InDesign and CircularFlo. In fact, the outsourcing marketplace is almost certainly shrinking, owing in great part to the increasing sophistication of in-house staff and tools.
Finally, the precarious, shifting-sands nature of ebook development itself is also a factor. My own experience has shown me that it can be a head-bangingly difficult space to work in. I have to compete with overseas developers on price and figure out in near isolation all the formats and devices on which my projects will need to operate.
I also have to work closely with less educated clients, some with little or no experience in ebooks or digital production, who then tend to transfer their dissatisfaction with the format to my company’s work. (That’s my least favorite part, for certain.)
So because this work is contracting, are fewer people now entering the field?
It’s tough to say, but it’s certainly possible that ebooks still aren’t an especially valued part of a publisher’s output and hence suffer from underinvestment in their workflows, especially since growth for the format has flattened out. For production professionals, at any rate, one of the big truths is that ebook development skills, particularly in-house, aren’t going to open many avenues for advancement, as Baldur Bjarnason earlier observed.
I prefer to remain optimistic about ebook development at large, but that may be because I am so invested in the job I do. And I like Iris Febres’s take on the opportunities afforded ebook developers:
I think #eprdctn can also present avenues to content strategy & product management. You’re transforming content. All about mediums.
— iris amelia (@ePubPupil) June 10, 2015
One thing I can say for certain is that the troubleshooting and problem-solving skills of your average ebook developer will always be very powerful. And that’s a fine, fine transferrable skill.