What job title should I be aiming for?

1 points by softwarefounder ↗ HN
I've been consulting as an independent consultant (full-stack dev/software architect/lead technical point) with a national company for several months. They _really_ want to hire me.

In order to set aside my independent consulting practice, they're willing to offer a nice salary and title. Since the IS/IT department is so small at the moment, there's room to really choose my title.

My role will involve high-level architecture, and detailed implementation. It will also involve working with c-suite execs and product strategists to transpose the product vision into code, and guiding the companies technological decisions.

I've entertained the titles CTO, Chief Architect, CEA (Chief Enterprise Architect), etc. I want to choose a title that fits my responsibilities, as well as a title that is level with the high salary I'm aiming for. In this area of the country, "Senior Dev" or "Software Architect" aren't "high" enough to match a high salary, nor do they truly match some of the roles that I encompass.

What are your thoughts on the title that I should aim for? What "lofty" role still involves direct implementation of code? In this regard, the IS/IT department is kind of like a startup.

2 comments

[ 4.3 ms ] story [ 20.8 ms ] thread
Whatever you want your next job title to be.