My experience is primarily not in the hands-on coding which in my business software world tends to be really primitive (read data, verify it, sum it up, write it somewhere, it is essentially primitive scripting), I don't think I have even seen an algorithm since school that was as complex as a quicksort which is first year exam material, as it is simply not done. In fact we constantly try to make frameworks where no coding is needed, just configuration, and employ non-programmer domain expert consultants as implementation specialists, but it always fails because people don't understand that properly that once your configuration gets that advanced that it loops over a set of data and makes if-then decisions, then it is coding again: just usually a poor coding framework. Example
Anyway it is more of a being a general troubleshooter. It is sort of difficult to explain (but actually this is the aspect that is likable about it, which is kind of balances the less likable aspects) that I lack a job description. A manager wants a certain kind of information in a regular report. To provide it, there needs to be software, bought or developed or both (customized), users trained, processes defined, and a bunch of potential other things and nobody really tells how to do it, nobody really tells what to do, it is just the need to achieve a result, an informational output just anyhow, with any sort of combination of technology, people and process. This is the good part of it, how open-ended it is but clearly far more than coding, and the coding part is usually primitive.
The bad part is coding the same bloody report the 100th time only slightly different... or answering the same stupid support call the 100th time because people keep making the same mistakes or forget the previous call. Of course both could be improved by reusable frameworks (often not supported by primitive technologies used), knowledge bases, or writing user manuals but that unfortunately does not depend on one guy, the obstacles to that tend to be organizational, usually short-sightedness.
Okay, then I likely underrated the skill difference between what you are currently doing and the work that exists in a startup like that.
If it's worth saying, but not worth its own post (even in Discussion), then it goes here.
Notes for future OT posters:
1. Please add the 'open_thread' tag.
2. Check if there is an active Open Thread before posting a new one. (Immediately before; refresh the list-of-threads page before posting.)
3. Open Threads should be posted in Discussion, and not Main.
4. Open Threads should start on Monday, and end on Sunday.