Somebody on a tech-writing mailing list just asked what kinds of questions we tend to ask interviewers when we're interviewing for jobs. The person had already mentioned, specifically for hardware-related jobs:

• Do you test the documentation? How?
• How does legal review work (for things like liability)?
• Availability of subject-matter experts for reviews?

Here's what I wrote in response:

My experience is in software, which might be different from hardware, but I always want to know:

• How early and in what way are writers involved in development? Do writers participate in functional and design reviews? Do we have input into the user interface? Are we part of the team, or do we come in later, take what they've built, and document it?

• Can I use the product? As much as I want?

• What processes do both the dev and doc teams follow? (If they say "agile" there are more questions.) How is doc reviewed and by whom?

• (How) do we make doc improvements that aren't directly tied to new features or bugs? (For example: larger reorganizations, improving indexing, adding runnable examples, tools improvements.)

• (How) do you use source control for documentation?

That's off the top of my head, without digging out my notes from my last round of interviews.

So that's not a complete list either, but these are the kinds of things I tend to be thinking about. (I also try to find out if I have access to the source code, but since he was asking about hardware I didn't bring that up.)

I also want to know where the documentation group is placed, organizationally speaking, but I usually learn that indirectly.

In the comments, somebody wrote:

I don't think I've ever been involved in an Agile process that included Doc in the core team, but now that you raise the point, that's clearly a process failure.

I responded:

After my first (full, not intern) position where I was included as part of the core team, I've made it a hard requirement. Fortunately, since then, I've been able to insist -- meaning that (a) so far I can afford to be picky and (b) I have a very solid track record that means I don't get dismissed out of hand. People just starting out won't necessarily have those traits, but I always advise people to, at the very least, prefer companies where they'll be part of the core team if they're comparing offers.

The cost, to the doc person, of being included early is that you might have to redo some work and/or relearn some things, because until the feature is finished it can still change even though everybody agreed on a design. That happens -- QA discovers a performance problem that can be alleviated if you make this small change to the interface contract, or it turns out that this is inconsistent in some way that matters with that feature over there that's also going into this release, or whatever. (But I don't need to lecture you about this; you know how software-dev works.) So that's the cost, but against that there are huge benefits for the team. You alluded to UX benefits; specifically, doc people are already looking at things from the user perspective so they'll spot things or have suggestions that people deep in the implementation might not think of. In most organization, in my experience, there are a lot fewer writers than developers and a writer might be working with more than one dev team -- and therefore might know some of what's going on in that team over there that affects this one here. And a really big one IMO: trying to explain something is a really good way to find problems in it. You know this from rubber-ducking. So even if some work might have to be revised, I want a writer to be trying to explain the new thing early, early enough to make changes when those problems emerge. (A writer, in turn, learns to use a breadth-first approach and focus on key areas for early deep dives. If you're working like this you don't start at the beginning of the doc and work your way through it in order.)

Of course, I've too-rarely worked anywhere that had genuine professionals doing the documentation to begin with, which says something in and of itself.

That's true lots of places, yeah. And, to be fair, there are more than a few technical writers out there who don't know how to work in this kind of environment, who struggle with changing requirements, or who just want to start with a finished thing so they can take an orderly approach to the doc instead of helping to make the thing. It'd drive me nuts, but not everybody is like me. There's also a lot of poor "walk the menus" (or equivalent) documentation out there that makes people think that's all technical writers can do, and that doesn't help. I've had several senior developers and dev managers say to me, after some time working together, variations on "I had no idea that tech writers could do what you do" -- they'd never seen it before. I'm not saying this to brag; this is as much about mindset as it is about raw skills, after all. But it's something I've tried to imbue in every junior writer I've mentored over the years.

Somebody asked a question on Stack Exchange about batch-converting document reference numbers (like ISBNs but for papers, not just books) to full citations, which sounded like a "simple matter of programming web services", so I did a little poking around. I have a (single) peer-reviewed publication, so I looked up its reference number (DOI) to test with.

That's how I found out that I have two publications. Er, what? Apparently that paper ended up in a book several years later, and apparently the process of doing that calls for neither permission from nor notification to authors. Or at least second-string authors; maybe the lead author was involved. (I wouldn't know; I haven't interacted with him in ages.) It's a paper in computational linguistics; I was just the (main) programmer, not the linguist or the PhD.