The distinction lies in problem-solving ownership. A configurator solves problems within the boundaries set by the template creator. An engineer defines the boundaries themselves based on the unique constraints of the project.
That’s the exact definition I was aiming for. It’s the difference between being a user of a tool and an architect of a system. When you own the boundaries, you stop fighting against the framework’s limitations and start building solutions that actually fit the specific constraints of the problem.