What Job Descriptions Taught Us

 When we began reviewing instructional design job descriptions, we expected to learn about tools and requirements. What we did not expect was how clearly they would reflect the gap between intention and practice.

Across roles in healthcare, government, nonprofits, and higher education, a pattern kept showing up. Employers are not just looking for people who can build courses. They are looking for people who can take unclear problems and turn them into structured, usable learning. They want designers who can listen, simplify, and guide action.

This matters more than it first appears.

Many job descriptions list the same skills. Needs assessment. Working with subject matter experts. Building eLearning. Applying adult learning principles. Measuring outcomes. Accessibility. At first glance, it reads like a checklist. But when we look closer, it is not about tasks. It is about thinking.

It is about how we move from complexity to clarity.

In our work across disability inclusion, workforce systems, and public policy, we have seen this challenge often. Information exists, but it is not always usable. Systems are in place, but they are not always understood. Job descriptions reflect this reality. They are asking for designers who can bridge that gap.

One thing that stood out to us is how often accessibility is mentioned, but rarely explained. Many roles require “accessible design,” but do not define what that means in practice. This is where deeper thinking is needed. Accessibility is not just about compliance. It is about whether someone can understand, navigate, and use what is in front of them. It is about clarity, structure, and respect for different ways of learning.

Another insight is the strong emphasis on collaboration. Instructional designers are not working alone. They are working with experts, teams, and systems. This means communication is not an extra skill. It is central. Being able to listen, ask the right questions, and translate knowledge into clear learning experiences is part of the work.

At the same time, these job descriptions also show where growth is needed. Many employers expect clear examples of technical work. Not just ideas, but built solutions. They want to see how learning was designed, how it was tested, and what changed as a result. They are looking for evidence of impact, not just intention.

This is an important shift.

In many portfolios, including our early work, the focus is often on what we planned to do. But employers are asking a different question. What actually happened? What improved? What did learners do differently?

This points to something that is often overlooked. Evaluation is part of design. It is not something that comes at the end. Good instructional design includes feedback, reflection, and revision. Without that, the work is incomplete.

We also noticed something else that is rarely discussed. Ethics in design. Some job descriptions mention diversity and inclusion, but very few explain how those values are carried into real decisions. How do we choose language? How do we design for people who feel excluded by systems? How do we ensure that accessibility is built in, not added later? These are not small questions. They shape the quality of the work.

Our experience has shown that strong design is not only about tools or frameworks. It is about judgment. It is about knowing when to simplify, when to explain more, and when to step back and listen.

For example, when designing learning for workforce systems, the challenge is not simply to explain policy. It is to help someone make a decision in a real moment. A counselor supporting a client. A manager making a hiring decision. A service provider navigating limited resources. If learning does not support those moments, it does not serve its purpose.

This is what job descriptions are quietly asking for.

They are asking for designers who understand context. Designers who can connect theory to practice. Designers who can move beyond content and focus on use.

For us, this reflection has helped sharpen our direction. Our strength has always been in clarity, storytelling, and systems thinking. What we are doing now is making that work more visible. Building stronger examples. Showing outcomes. Demonstrating how design decisions lead to real change.

Job descriptions, in this sense, are more than hiring tools. They are signals. They show where the field is moving. They show what organizations are struggling with. And they show what kind of work is needed.

If we read them carefully, they do not just tell us what to learn. They tell us how to think.