I work for a company that provides a custom software platform that enables the building of large, complex enterprise apps. The primary engine is written in Java running in a JVM but we also use Groovy as a secondary scripting language in a secondary execution context for extending the platform and writing complex business rules. In fact the JVM has fantastic capabilities to allow late, runtime compilation using JVM-compatible languages (groovy, scala).
We have historically called this 'configuration' to give our clients the impression that the software is easier to deliver an application with and our consultants were 'configuration developers'.
But more recently we noticed that clients don't care so much about this wording. On the other hand, the developers using the platform don't like to be called 'configurators' and so we've gone back to call it development (which it really is) and have 'developers'.