But, if the company is actually big enough that Marketing and Engineering have serious problems communicating with each other, perhaps it's time to reorganize into product divisions, so that all the people whose cooperation is needed to perform the daily work to support a given product, are under the same reporting structure, and so that the product team that needs another developer can just hire another developer, rather than having to plead with the IT department to allocate them one.
About a year ago the development team was on a separate floor and communication breakdowns with business were endemic. Treating marketing like a customer didn't work and worse, they would come up with the ideas and we would implement them.
Relocating to the same floor helped and development was more involved with planning and ideas.
We have now gone a step further and organised along product lines with each team consisting of a mix of devs and business (account and project managers). There is still a marketing team who are primarily involved with PR, advertising and social media and sit alongside the database/analytics team.
Devs still report to the Development Manager while Marketing, Business and Accounts report to their respective managers.
Seems to be working so far.
So what happens in practice is exactly what smacktoward described: the B-level engineers are sent to the marketing department because Engineering doesn't want them around.
What it does always do is bifurcate your technical staff...
Edit to add: not necessarily at the same company. Creating marketing automation applications is a great entry level job that makes your resume more attractive to future employers.
At Knewton, someone who was not up to standards wouldn't be shifted out of the way to another department, they would be let go. That is a pretty rare occurance because the hiring standards are strict (in my opinion, maybe too strict, I think we get a lot of false negatives, but that is another topic). Any company that had a policy of sticking another department with an employee they disliked would not last long because you'd end up with a lot of poor talent being shuffled all over the place.
In that case how they found a dev team for marketing was to go trolling for the best Devs from their previous companies (the marketing team being very deep in start up experience). That's how they found me, that's how they found my coworkers and I like to think that we were the best engineers in that company. Or at least the most pragmatic, and profitable.
Anyhow - every single company that isn't founder by a coder has this problem, and many of them make it past it somehow.
---
I would say that there were political problems in this company, and if wouldn't do it this way myself. For unclear reasons, engineering a policy was to hire only c coders in 2003. And there was a need for full fledge ecommerce site - for which they were quoting multiyear lead times. Which is why marketing just built it. And a bunch of other stuff.
If the problem is that marketing and engineering can't talk to each other, the solution is for management to be able to talk to both of them, not for people whose skills would put them in one group to be embedded in the other. Going that way just creates "B teams": the good engineers (the "A team") are in Engineering; the ones Engineering doesn't want get shunted over to Marketing to get them out of the way. Which doesn't do Marketing any favors, since those are the ones least likely to be able to understand what Engineering is doing in the first place.