Ask Alex: The Blogger's Dilemma
This month's question came to me via email, and kept me thinking for a good long while. As always, I'm happy to take questions here in the comments, but you're more than welcome to email me if you'd like to ask privately. I'll always double-check to make sure it's okay to post the question here.
A lot of book bloggers—myself included—hope to get the chance to be a published writer or end up working in the publishing industry in some other fashion someday. But I've always wondered, is this acceptable? I'm sure it's fine when the reviews positive, but what if you don't like a book? If you plan to join the publishing world someday, should you just not post about those?
This topic seems to pop up a few times every year and the discussion is always very interesting. I'm going to pro-con-pro this for you and try to come at it from a few different angles. Agree or disagree, I hope it gives you guys some food for thought—and I would love to hear your take!
To answer your first question, is it acceptable? Yes, of course. If you're interested in working in publishing, the one key benefit I can see of keeping a book blog is that it shows you can read critically and form educated opinions. (Side note: this is somewhat harder to prove if 100% of your reviews are just GIF reactions.) Actually, one reason my first boss gave for hiring me was that I read widely in the kidlit realm and knew what the house was publishing in addition to competitive titles. Book bloggers: you have a serious leg up on the casual applicant because you know your books. You're a target for promotions and advertising, so you can discuss the campaigns you've seen and absorbed. You're networkers, and you help connect readers to books they may potentially like. That right there is 40% of my job.
Even if you choose not to mention it during the interviewing process, even if your real name isn't attached to it, you should still eventually disclose the fact that you're a blogger to your boss to make sure that you're in line with corporate communications policies and standards. It becomes critical that you don't appear to speak on behalf of your employer or fellow employees and that you don't, even unintentionally, show favoritism, reveal company secrets, hold contests for company books without permission, or criticize the company/your boss/your authors. I know that's a bit of a no-duh, but it's always good to repeat it.
To play devil's advocate, I'm going to give you a few potential drawbacks to consider about leaving negative posts up, many of which apply to blogging in general.
First things first: potential boss and maybe even the HR person will almost definitely visit the blog and will likely go through it. If not them, then your new coworkers. With both of my jobs, I had now-friends admit that they went through my author website and blog. Like, really, extensively went through the archives and sent each other messages to discuss it. It's natural for people to be curious about new hires and pretty standard for employers to Google you before or after the interview. This is why you get so many warnings to be careful of what you're putting out there. If you're presenting yourself online in a way that isn't actually how you are as a person, you run the risk of having people make assessments of you before you even start working there.
Further, you may, at one point or another, express an opinion that's at odds with what your potential boss believes and he or she could feel strongly enough about it to factor it into their decision. Skills and experience are only one aspect of the hiring process—your supervisor has to feel like you click personality-wise, too. That's really a risk you run with having any visible online presence, though.
You asked specifically about whether or not a negative review could potentially come back to bite you. One thing to understand is that people in publishing are well aware that not every reader will like every book. I don't love-love-love-love every single book we publish, but I'm still responsible for taking care of them and championing them. By investing their time and energy, employees take ownership over what they're editing, pitching, and marketing--I'm not going to lie, it stings to see a book you've put considerable effort into get dinged. Would it prevent you from getting a job, though?
One negative review of an in-house book (and by that, you know I mean a thoughtful, well-written review) probably isn't going to be a red flag for a supervisor. Maybe they'll even agree with you about it privately. But if that book is one of the big, huge titles the house is backing? If it's multiple titles or multiple in-house authors? It could give him or her pause, if only because it might come across as your tastes not being in line with the company and therefore not compatible with the personalities or books they plan to continue publishing. (To be fair, some people would see getting passed over for that reason as dodging the potential bullet of having to work on a million books they despise. But, honestly, it's hard to get a job in publishing these days. You have to make yourself an attractive candidate to everyone.)
Here's something I never really considered until I was a year into my second job: authors, unless they are champions of self-restraint, do look at their bad reviews and they remember the really painful ones. Even if you don't see a review as being particularly harsh, they're viewing it through a different, potentially sensitive lens. If you make it known on your blog or twitter (or they somehow find out) that you're working for their publisher—and therefore on their books—it's likely to be uncomfortable for everyone involved, and you'll have to work harder to maintain that professional relationship. You may think there's a one in a million chance of that happening, but the children's publishing industry is actually quite small and authors move around between the houses a lot more than they used to. Believe it or not, I've had the inverse happen to me. One of our authors (who wasn't our author at the time, but just a reviewer) left a terrible review of my first book on GoodReads—one that was hurtful enough that when I heard his/her name at list launch I actually felt that same flush of humiliation that hit me when I first read the review. I still feel a weird sense of embarrassment every time I have to talk with the author. They clearly don't remember me, but I remember them and the way they made me feel. I imagine s/he'd feel similarly if our positions were reversed. Basically, it isn't end of the world territory if this happens, but it is uncomfortable.
This isn't really an issue of authors seeking to retaliate against reviewers who criticize their work, which I know is a fear some of you may have. I bring this up because when you do have a job in publishing, you'll be constantly working with an eye toward what industry types call "Author Care." Essentially, it boils down to each publishing house striving to make sure an author knows they value them, their work, and that they'll take care of their needs and help them find success. Do you see how publicly criticizing one of your company's books--even if you were reviewing it in The New York Times!--might be perceived as working against this?
Finally, in terms of whether or not it would affect your chances of being published, I almost see it as being more of an issue when it comes to navigating relationships with other authors[1. As I mentioned before, the industry is very small, and you will very likely, at one point or another, run into someone whose book you didn't like. They may know this. It may be unbearably uncomfortable, even if you're polite to one another. I have a feeling that this alone would complicate your feelings towards publicly posting negative reviews, but, obviously, I can't speak from experience about this one.], rather than editors. Obviously a potential editor is not going to be super thrilled if you hate every other book they publish (if that is the case—are you sure they're the right editor for you?), but blogs are still seen as great marketing tools. A big following is like having a built-in audience to market to, which is always a plus when the editor brings the project into acquisitions.
What do you guys think? Agree? Disagree? Have you experienced any of this this firsthand?