Honestly, I'm not sorry that you started the thread. I think that there has been a lot of great discussion on titles and how they are used. Granted, I will be sending a personal appology to MNicolai to make sure that everything is good, but I think that this is a very valuable thread.
I originally typed this as a response to ruinexplorer's PM to me, but I realized it's far more appropriate to post it here directly:
I look at conversations differently than many people, and because of that I have a tendency to come off as an aggressor. I firmly believe that I never really know what my position is on something until I write it down, then read it out loud, then erase it, then write it again, then erase it again, then write it again and have someone tell me how wrong I am. That's why I'm always eager to get into a debate, even if it turns out I couldn't have been any more wrong about the topic at
hand. My hope is always that I'll walk away from a debate/discussion/conversation having learned something and heard some other perspectives.
From the different perspectives that have been expressed here, I think it's safe to say that I was wrong anyway. Every person in lighting or in audio has a different background, and it's unfair to characterize our entire discussion around Lighting Designers v. Sound Engineers. Very few people in our industry have duties that fit under a single job title, and even if they did, two people can have very dissimilar experiences that equally qualify them for the same positions.
There are many different aspects of both audio and lighting, each dealing with different balances of art and science. For that matter, one man's art is another man's science.
Personally -- I have no job title. To HR, I look like some guy who comes in a few days out of the month to do work on a show here or there. The way that my timesheet is setup, HR only even sees which events I've worked and for how long -- they have no idea which work I did for a given event. My boss sort of understands, but the most part I do things that need to get done so that they don't end up flying across his
desk and taking up his time (he already spends 60+ hours in the
theatre each week, with his record as high as 92 hours in a single week). As far as he's concerned, I've done my job well when things he shouldn't have to worry about don't get dumped in his lap.
What my boss knows that HR doesn't though, is that I do a lot of volunteer work. My volunteer duties (that I assigned to myself on my own accord) in the last couple months have included:
-> Reprogramming our
ETC Unison fader/
button stations.
-> Designing a rep
plot and all of the necessary paperwork to go with it.
-> Hanging 40
dead-hung points from the
grid for an event with
wire rope cables I made myself from materials I purchased myself.
-> Taking 3000 photos of events to grab another 20-30 photos for our marketing and promo purposes
-> Fixing a snag in our
fire curtain's tension
line.
-> Conceiving a sensible hiearchy for how the doors in the building are keyed.
-> Coordinating a PA rental and an outdoor PA setup for a full band on a day with light rain
-> Driving back and forth to
ETC's HQ and Full
Compass' HQ to
drop off gear for repairs and pick it back up.
-> Being the point-man for several clients looking for technical info on our facility.
-> Planning a workshop series this summer for our high school students and new additions to our
call lists so that they can become qualified enough to work our professional, rental, and school events.
-> Skyping with the VP of Luci Della Ribalta (who was in Italy and in China while dealing with this) on the problems we've had with our Canto 1200 followspots, then working with a technician out of Atlanta, GA to get the problems resolved.
-> Setting up a backstage blog to show the community the personality and "magic" that keeps our
theatre running.
-> Planning the capital projects for the year (buying a new
projector and
screen, installing a new lighting position, reorganizing the scene shop, contacting a real estate agent to scout for possible off-sites we could use for set construction and storage)
-> The list goes on...
I always feel a little dumb when a client asks me what my position is at our facility and the best I can say is that I'm an "unofficial technical advisor". Every time someone asks, I make up some new flavor of poo to describe what it is I do -- something that gives them enough of an idea of what I do without misleading them that I'm higher on the food chain than I am.
I cannot possibly describe what it is I do in a two or three-word job title. Back when I used to have business cards (when I felt I "needed" to have business cards), the least stupid descriptor I could put on them as my job title was "Live Event Technician". It's not wrong, but it barely scratches the surface on the roles that I
play in the projects I work on.
I'm willing to bet that most of the people here on
ControlBooth cannot sum up when they do in a single job title; a job title just isn't enough information. Unless you're the Commander in Chief, a job title doesn't effectively communicate the value of your skills and what it is that you do to earn your paychecks.