What You Can Actually Do with an IS Degree in 2026

People ask me this more than any other question when I tell them I study Information Systems. "So what do you do with that?" Sometimes they ask it genuinely. Sometimes there is a kind of skepticism in the tone, as if IS is some orphaned degree caught between computer science and business, belonging fully to neither. I used to stumble through an answer. These days I think I have a cleaner one.

IS is one of the few fields where the core tension, how technology and organizations shape each other, is actually the research question rather than a background assumption. That positioning creates a surprisingly wide range of career paths, and in 2026 some of the newer ones feel more urgent than the traditional ones.

The traditional paths are still real. Systems analyst, IT manager, business analyst, project manager, and the long climb toward CIO or VP of IT are all careers that take an IS background seriously. The business analyst role in particular matches what IS training actually builds: someone who understands enough technology to talk to engineers and enough organizational context to translate for executives. My sense is that these roles remain steady demand even as job titles shift. What changes is the expectation that you also understand data pipelines, automation, or AI-assisted workflows. The "analyst" part of the title increasingly means something more technical than it did a decade ago.

The newer paths are where things get interesting. Product manager roles at technology companies now pull heavily from people who can think about both the artifact and the context it lands in. This is exactly the IS perspective: a product is not just code, it is code plus the organizational practices that form around it, the workarounds people build, the ways the tool changes the work rather than just supporting it. IS graduates who understand sociotechnical theory, even if they would never call it that on a resume, think about products this way naturally.

Data science is another path that has absorbed IS graduates well, but with a caveat. The technical floor has risen. Knowing R or Python, being comfortable with regression and text analysis and some machine learning basics, that is now closer to the entry point than a differentiator. What IS graduates can offer on top of that technical baseline is the organizational context. A data scientist who understands why organizations collect certain data, how it gets distorted by incentive structures, and what it means to actually implement a model inside a messy enterprise context is more useful than one who knows the math but has never worked near a real organization.

Digital transformation consulting has expanded enormously. This is probably the IS career path with the shortest gap between training and compensation, though the lifestyle trade-offs are real. Consulting at a strategy firm, a Big Four, or a boutique digital advisory practice pays well early and burns people out at a rate I find alarming from a distance. The work is real: clients genuinely need people who can diagnose technology adoption problems, design change programs, and communicate up to executives who do not want to hear about ERP implementation complexity. IS training maps onto this well. The risk is that consulting rewards speed and confidence over depth and hedging, which is precisely the opposite of academic training.

The academic path is the one I know closest, being inside it. It is slower and more uncertain than the others. The PhD itself takes four to six years depending on where you are and what your research involves. Then there is the job market. The academic IS job market is competitive, and placement into research universities, the R1 schools and top AACSB business schools where doctoral training typically points, requires publications in credible journals before you defend. The distinction between R1 research universities and teaching-focused institutions matters a lot for what the job actually looks like day-to-day. At an R1, you spend most of your time on research and doctoral supervision. At a teaching-focused school, the course load is heavier and research expectations are lower, though they still exist. Neither is better in some absolute sense. They are different careers that happen to share a job title.

What I find most compelling right now are the emerging paths that sit at the edge of what the field knows how to study. AI governance is one. Someone needs to figure out what good oversight of algorithmic systems actually looks like inside organizations, not just at the regulatory level, but in terms of internal practices, accountability structures, and the roles that humans play when AI is making or influencing decisions. This is an IS question. It sits at the intersection of technology design, organizational behavior, and institutional theory. The IS field is well-positioned to work on it, and the practical demand from organizations is real.

IS research itself as a practice is changing too. The kinds of questions that get funded and published increasingly touch AI, platform governance, digital health, and information security. A PhD student who can position their work at one of those intersections has more options than someone whose research sits in the middle of a well-established tradition without a clear connection to what organizations are struggling with right now.

Digital strategy consulting, distinct from the implementation-focused consulting I described earlier, is another path I see opening up. As more of what organizations do gets mediated by data and algorithmic systems, the strategic choices around technology architecture, data governance, and vendor relationships matter more and more. IS researchers and graduates who understand both the strategic logic and the technical realities are scarce in that space.

From where I sit at UNT, finishing my PhD and watching the job market carefully, I think the IS degree still has strong positioning. The tension that makes IS hard to explain at a dinner party, that it lives between disciplines and refuses to be just one thing, is actually the asset. The field studies the messy middle between technology and organization, and that middle is not going away.