I just put "software engineer", or "senior programmer". It's all the same to me.
Software Architect is an altogether different thing, although in my career I've had to do a bit of it, it was never a principal task. And these days that job is often driven by "Tech Director" or "Tech Lead" or the 20 other titles that don't mean that much.
After 15 years as a "Programmer", I've done architecture, design, programming, debugging (so much debugging), instrumentation and iteration, integration, build management, team management, and lead/director tasks. Don't care what my title is, just pay me what I'm worth, and let me code.
I just put "software engineer", or "senior programmer". It's all the same to me.
Software Architect is an altogether different thing, although in my career I've had to do a bit of it, it was never a principal task. And these days that job is often driven by "Tech Director" or "Tech Lead" or the 20 other titles that don't mean that much.
After 15 years as a "Programmer", I've done architecture, design, programming, debugging (so much debugging), instrumentation and iteration, integration, build management, team management, and lead/director tasks. Don't care what my title is, just pay me what I'm worth, and let me code.