Started coding at the age of 13, now a professional software engineer and Scrum Master, creating and maintaining enterprise solutions. Eat - Sleep - Code - Lift - Repeat 💪🏾
My card says "Software Engineer". Internally most of my collegues see us as "just" developers. But in my opinion the title fits to what we do besides developing during the day - which is much more than developing!
Short excurse:
We are developing an ERP system and we constantly need to find solutions for not so trivial feature requests of customers. Therefore we have consultants who work out the possible solution with the customer and we "Software Engineers" have to implement it later.
Back to the title:
We need to understand the requirement of the customer. Then we also need to understand the suggested solution our consultant worked out and why it should be this way (mostly in cooperation with a dev).
We help finding those solutions and help writing the specs. Additionally we sometimes need to explain them their own requirements because people tend to forget whats not written down into the concept...
And "engineering" fits also to the social aspect:
We need to figure out how to talk with the consultant in a way that we both come to an acceptable point in discussions, we then also need to find a way to explain technical limitations or better solutions as the suggested ones to the customers.
I personally explain it as developer most of the time to friends, but I think "Software Engineer" is a good term to describe that we are doing way more :-)
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
My card says "Software Engineer". Internally most of my collegues see us as "just" developers. But in my opinion the title fits to what we do besides developing during the day - which is much more than developing!
Short excurse:
We are developing an ERP system and we constantly need to find solutions for not so trivial feature requests of customers. Therefore we have consultants who work out the possible solution with the customer and we "Software Engineers" have to implement it later.
Back to the title:
We need to understand the requirement of the customer. Then we also need to understand the suggested solution our consultant worked out and why it should be this way (mostly in cooperation with a dev).
We help finding those solutions and help writing the specs. Additionally we sometimes need to explain them their own requirements because people tend to forget whats not written down into the concept...
And "engineering" fits also to the social aspect:
We need to figure out how to talk with the consultant in a way that we both come to an acceptable point in discussions, we then also need to find a way to explain technical limitations or better solutions as the suggested ones to the customers.
I personally explain it as developer most of the time to friends, but I think "Software Engineer" is a good term to describe that we are doing way more :-)