The problem is encountering a hiring manager who treats book writing as a red flag: perhaps the candidate is more interested in self promotion and vanity projec

The problem is encountering a hiring manager who treats book writing as a red flag: perhaps the candidate is more interested in self promotion and vanity projects than doing real work; perhaps they are too "academic" and don't have real experience; perhaps their book is one of these trash books that is nothing more than the open source docs (that the author didn't write) hastily thrown together; etc. That's not to say the candidate won't get the job, but that they get grilled harder in the interview to overcome these suspicions. I only mentioned this in the first place as a counterpoint to the idea that books may have a lot of value in an interview. I think it has value in _getting_ the interview, but you might find the interview is now a little bit harder. And thinking that your book matters most may sound too arrogant. I have recommended that people write books over the years (I'm not anti-book!): I just wouldn't list the interview as a perk. A big perk is getting to help people worldwide (my books have been translated into other languages), including those who don't have access to bay area conferences or other local experts. Another perk is assembling a technical review team of fellow experts and working on the draft with them, listing to their feedback and learning from their experiences to improve the book.