Document your ability to be a team player.

Most of my experience has been in the development of complex 
systems. The ability to collaborate with other team members is 
essential for the success of any challenging, extensive project. 

In addition to formally defining interfaces, I am often engaged in 
multiple tasks in which all participants must cooperate just as 
mountaineers tied to the same safety line would. I am accustomed to 
a highly interactive style of collaboration, often spanning across 
organizational boundaries.

Recently at FSI International, we faced a situation when the 
database management process started to consume too much of processor 
resources. Working side-by-side with other developers I profiled the 
processes and found the solution, but it required some trade-offs 
and a change to an internal API. I was able to structure the 
database management changes in the way minimizing the overall 
company resources spent on the change.

I feel comfortable working with equipment (<-clarify) and am often 
assigned to inter-discipline teams. There is no strict hierarchy 
between team players. But I quickly establish rapport with my 
counterparts, hardware and systems engineers. 

Another example: at SDRC, I was quite successful in my role of 
improving the development process to advance the organization to the 
next CMM Level.  In that instance, I devised procedures streamlining 
the deployment on multiple platforms. 

My priority when being a team member is the success of the team. 
Usually, it leads to developing of friendly, non-adversarial team 
spirit. Sometimes, it helps to mentor a team member or share a 
knowledge in another discreet peer-to-peer way. 

In matrix organizations, I am sometimes a team member working on a 
project led by a person who is a member of another team for which I 
am a project manager. As a disciplined and productive team member, I 
take that personšs direction.