"What are some notable duties is the employee expected to perform, outside of software development?" I worked at one place that expected software developers to

"What are some notable duties is the employee expected to perform, outside of software development?" I worked at one place that expected software developers to stock orders in the warehouse, and to take phone calls in the call center. "Tell me about a recent time the team was allocated time to resolve some technical debt. Tell me about a recent time the team was NOT allocated time to resolve some technical debt." I worked at once place which shifted from outsource to in-house software development, discovered that some of the primary html views of the website were built using a jumble of string concatenation, and to add a new feature using the existing string concatenation. "What percentage of my time will I spend coding in this role?" Worked at one place which assigned excessive non-coding bureaucratic duties to developers. "How often do you release software?" Worked at once place which did not release anything for the 1.5 years that I was there. "How do you incorporate the lessons learned partway through a project into the remainder of the project work?" Worked at one place that could not pivot due to inability to admit that they didn't have a perfect plan from Day 1. "Tell me about some advanced design patterns that you don't use." Worked on a team that used every advanced design pattern that mankind had ever given name to, each in 200 places without an iota of consideration to the costs that go along with the potential benefits. "Do you plan on shifting your entire tech stack into something else that can scarcely be considered software development?" Self-explanatory, but has happened to me 2x now, so be on the lookout. Fifteen+ years into my career, I've discovered that every job will give you one or more damn good reasons to move on, and each of these lessons above took 1-2 years to learn, so my latest strategy is just optimizing for pay rate. :-)