3 ms·
Field Application Engineer or Solutions Architect are excellent transitional roles to other things. You get to work with customers, a variety of customers. Then
by throooooway1 6y ago
Field Application Engineer or Solutions Architect are excellent transitional roles to other things. You get to work with customers, a variety of customers. Then you arent stuck being with the one customer (whatever product company you are working for). Variety is good.
If you work with a range of external customers, opens more avenues for escape, also. Pure development is pretty tedious, you are treated like a cog.
Not enough people talk about how much software engineering actually can suck. I couldn't stand having a "SCRUM MASTER" breathing down my neck, demanding timelines for every bug, dragging and dropping tasks on me.
- iKevinShah 6y agoPlease do not take this the wrong way, I am genuinely curious, apart from constant learning / re-learning, what are the other things which people don't talk about when talking about Software Engineering (developer role). I have worked as a consultant, sysadmin and developer but I was a fresher (when developer) at a $BIG_FIRM and everything had a process (Requirement gathering, analysis, etc. etc.) so it was not that Agile. curious to see how it is right now.