The primary function of the role is to do writing, not engineering - and the success of the role will be measured in terms of marketing, not engineering - so to me the title we went with makes the most sense. I can definitely understand the discussion here though :)

Thank you. This is exactly my point.

The only way making them a function of "marketing" makes sense, is if the leadership of Ghost view user docs as something primarily to bring in (new) sales.

As a person who has often done implementation roles in their career, having to rely on docs written by "marketing" people rather than engineers is generally a lousy experience. :(