testadicazzo writes: I currently work for small startup, funded by a university. My background is computational physics, and I work three PhD's developing scientific software for engineering applications Because the company is a startup and has limited resources, I agreed to work for less money than I would normally expect, in exchange for a casual work environment, flexible hours, work at home, and several other soft compensations that are pretty important to me. I also get to pick my job title, to help me if I ever decide to move on. My problem is I don't know what to call myself. My job is essentially being the IT expert in the group. I set up our server, I chose, set up, and instructed everyone in the use of our version control system. I make most of the decisions regarding coding strategy (I have, by far, the most programming expertise in the group). I do a lot of programming, mostly getting the alpha-level code we have ready for sale, but I also evaluate and implement various algorithms, but I also do stuff like research and figure out how to set up payments, license management, web distribution, etc. Since 2 of the other guys are actually part owners of the start-up, I'm at the bottom of the heap, but in practice I'm in charge of the biggest chunk of the day-to-day technical decisions. So what's a good job title?