<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:st1="urn:schemas-microsoft-com:office:smarttags" xmlns="http://www.w3.org/TR/REC-html40"> <head> <meta http-equiv=Content-Type content="text/html; charset=us-ascii"> <meta name=Generator content="Microsoft Word 11 (filtered medium)"> <o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="PostalCode"/> <o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="State"/> <o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="City"/> <o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="Street"/> <o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="PlaceName"/> <o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="PlaceType"/> <o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="place"/> <o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="address"/>  <style>  </style> </head> <body lang=EN-US link=blue vlink=purple> <div class=Section1> Susan,<o:p></o:p> <o:p> </o:p> Our director is aware of the problem of limiting the hiring pool to <st1:State w:st="on"><st1:place w:st="on">Colorado</st1:place></st1:State>.  He keeps hitting a wall when it comes to reclassifying the position.  But, I really think the primary obstacle is $$$ versus the workload and required expertise. I know there are qualified techs here in the state that would be attracted to the position if the salary were reasonable.  One tech I know said that he looked into the position, and would have applied, except our University no longer offers free tuition for children of faculty and staff. <o:p></o:p> <o:p> </o:p> I don’t know what the long term solution is.  I just know it is a battle I don’t want to fight.  I think in the end, the level of service demanded by the faculty will determine what happens.  The more the faculty complains, the faster change will occur.  If the faculty remains apathetic and complacent, the position and the pianos will deteriorate.  I can explain the deficiencies in pay, resources, humidity control, tools, work-space, care of the instruments, etc. until the cows come home, but after the first round, it is too easy to tune me out.  It is when the faculty begin to complain that things will get done.  The problem is that when faculty complain, the technician often gets the blame, not the lack of resources or the fact that there is enough work for two full time technicians.  I’ve made a noticeable improvement in service since I have been here (the last technician was part-time, so improvement over that was not too difficult), but I have no budget for new pianos and I have to request every new part I order.  It is only a matter of time before the bubble bursts.<o:p></o:p> <o:p> </o:p> All of that said, if you are a brave technician who would like a lot of experience quickly, and the opportunity to have a positive impact on an enthusiastic, highly skilled musical community, and don’t mind working for a year or two in a job that is under paid, this is a golden opportunity.  It’s been worth it for me.<o:p></o:p> <o:p> </o:p> Jeremy<o:p></o:p> <o:p> </o:p> <o:p> </o:p> <div> Jeremy Gould, Piano Technician<o:p></o:p> <st1:place w:st="on"><st1:PlaceType w:st="on">University</st1:PlaceType> of <st1:PlaceName w:st="on">Northern Colorado</st1:PlaceName></st1:place><o:p></o:p> <st1:place w:st="on"><st1:PlaceType w:st="on">School</st1:PlaceType> of <st1:PlaceName w:st="on">Music</st1:PlaceName></st1:place><o:p></o:p> Frasier Hall 3 , Campus <st1:address w:st="on"><st1:Street w:st="on">Box</st1:Street> 28</st1:address><o:p></o:p> <st1:place w:st="on"><st1:City w:st="on">Greeley</st1:City>, <st1:State w:st="on">CO</st1:State>  <st1:PostalCode w:st="on">80639</st1:PostalCode></st1:place><o:p></o:p> 970-351-1132<o:p></o:p> </div> <div> <div class=MsoNormal align=center style='text-align:center'> <hr size=2 width="100%" align=center tabindex=-1> </div> From: Susan Kline [mailto:skline@peak.org] Sent: Friday, March 16, 2007 3:44 PM To: College and University Technicians Subject: Re: [CAUT] University Position in <st1:State w:st="on"><st1:place w:st="on">Colorado</st1:place></st1:State><o:p></o:p> </div> <o:p> </o:p> At 07:44 AM 3/15/2007, you wrote: <o:p></o:p> Please keep in mind that this is an in-state position, meaning only <st1:State w:st="on"><st1:place w:st="on">Colorado</st1:place></st1:State> residents may apply.  <o:p></o:p> Yes, Jeremy, <st1:City w:st="on"><st1:place w:st="on">Greeley</st1:place></st1:City>'s piano department has a very good reputation. Glad that you got along so well there. However, I wonder if anyone really stopped to think of how tremendously they are limiting their pool of applicants by insisting on only <st1:State w:st="on"><st1:place w:st="on">Colorado</st1:place></st1:State> residents. How many decent concert and institutional technicians can there be in the state, who also want to move? I grew up in <st1:City w:st="on">Fort Collins</st1:City>, but I still wouldn't qualify, even if I wanted to leave <st1:State w:st="on"><st1:place w:st="on">Oregon</st1:place></st1:State>, which I certainly don't. Susan Kline <o:p></o:p> </div> </body> </html>