You're about to go into your interview with a prospective employer. There's bound to be a technical test and they'll likely ask all sorts of "personality" questions, but interviews are a two-way street. What should you ask THEM?
Computer science is a mathematical, binary discipline that considers ideas such as efficiency, performance and logic. Yet software development is much more than those things when taken in context with the wider problem of creating a solution to a given problem. Coding requires creativity, imagination and innovation to be truly effective, so what things in our industry contribute to that and what factors create an environment where the process becomes harder, more rigid and inflexible?
How does the language used to describe software development affect different teams? What assumptions do we make in our enthusing about DevOps, shipping or sprints that exclude or neglect developers who work in a capacity that is slow to adopt these best practices and what are the risks in ignoring those disparities? Understanding and measuring the relationship between our industry's language and its effect on our people directly affects our teams' engagement and productivity.
What are the conditions within a team dynamic that contribute to a feeling of safety and respect? The signals being sent to a team can affect how a team culture is perceived, for better or worse. Ensuring the formal ethos is congruent with the informal messages picked up by a team has a huge impact on how that team works together, shares information and volunteers ownership and accountability.
When it comes to the hierarchies of software teams, there seem to be some pervasive and toxic attitudes. What is it we should actually expect from our seniors and what are some of the entitled views that we could do without?