I tell people "I make websites". It's easy to understand, and sums up the design, development, and consulting I do for every project.
Only 10% of my time goes to writing code. Most of building a Drupal site comes down to installing modules and configuring them. Most of the time goes into planning, collaboration, and review. Figuring out what needs to get done, how things will fit together, and keeping the team and client on the same page is a large part of my role as a technical lead.
I write code to customize how things work in our project, or contribute modules and patches back to Drupal for others to use. As an open source project, Drupal is shaped by the people who use it. I uncover new needs for the platform as I bend in it in different ways to meet project requirements. If I can add a configuration option that let's me toggle on a feature I need, I can share that with anyone else who needs it too.
Because of this relationship between the platform I use and the project I'm on, I am a liaison between the two. Drupal is constantly releasing new features and the best ways to do things change over time. As we work to keep up with technology, some areas refine and mature while others fall behind in implementing the latest techniques. Knowing which technical options to use, or when to write your own becomes a critical area for making decisions that keep a project on time and in budget.
Most of the industry follows agile development practices. That generally means that we plan out the project in 2 week cycles, and meet regularly to discuss progress and next steps. Designers and managers work ahead to make sure developers have the requirements they need to get started when they're ready. It's supposed to be a methodology that keeps things running smoothly, but I find that there is no substitute for good leadership. Large projects can become very chaotic, and providing structure and process is a highly valued skill.
We will basically continue the sprint cycle until the project or launched or the budget is depleted. Along the way, I have asked questions, presented options, built things, refined them, shared my progress and opinions, and worked through many puzzles - design, people, and technical.
Some developers focus more on the technical aspect, some on strategy, and some on management. Since I'm a freelance contractor, consulting and selling my skills is a large aspect of my career. I bring a holistic perspective on how these things work together, in order to orchestrate a team in building the best sites we can.