Technical Director

I went to a panel discussion about working in the video game industry yesterday, and at one point in the discussion, it sounded like they were talking about me, in a room full of computer science students. One of the speakers explained the role of the technical director: the intermediate between the technical aspects of production and the artistic aspects. The person who brings those two things together and translates for them.

A technical director needs to know about all of the technology, science and math behind the work, but they don't really need to be great programmers. They need to be able to learn new tools very quickly. They need to be able to think up tools and how to design them for artist to use. They need to be able to help artist use the tools which they are being provided.

A technical director needs to be able to explain to an artist how to make the art work within the framework of the technology. A technical director needs to make the art work with the tech.

They need to have a wide array of knowledge and always looking out for what is new.

They need to be able to solve problems.

Every thing they said just seemed to fit in a check box of the skills I have and the check boxes of the things I like to do.

This could be my direction into the industry. It would be great to get into the industry as a technical director and then use that as a step to simply get to the position of director.

I think the thing that got me most excited was when they explained that such a person, with both a knack for the arts and for tech, was a rare breed.

In the time it took too write this post my whole career direction probably just shifted a few degrees

Kyler

No comments: