note
Errto
<p>Being in corporate-land, I get the bizarrely meaningless title of "Systems Analyst." (<strong>update</strong> - the full title is actually "Systems Analyst - Business Solutions"</strong>). I'm not entirely sure what a Systems Analyst means, but in my case it consists of not quite equal parts of:</p>
<ul><li>functional design of software</li>
<li>database design</li>
<li>coding and debugging</li>
<li>testing</li>
<li>end-user support</li>
<li>systems administration</li>
<li>something akin to what they called "evangelism" in the late 90's</li>
</ul>
<p>My business card and resume say "Systems Analyst" because I feel like that's the honest thing to do. Plus it's a lovely setup for a potential future interview question.</p>
<p>By the way, since I work for a company that manufactures large and complex machines, there's no danger of people calling me an Engineer. Which is fine by me.</p>
<p><strong>Update</strong>: I found out that the above is only true because I work in an IT division. The developers who write code for the company's software-related products <em>are</em> called Software Engineers.</p>
360849
360849