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.
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.