Instructional Designer vs. eLearning Developer: Key Differences
By Devlin Peck · Updated
Part of the Become an Instructional Designer guide
An instructional designer decides what a learning experience should teach and how: they write learning objectives, interview subject matter experts, and produce storyboards. An eLearning developer takes that storyboard and builds the working course in an authoring tool. In most corporate jobs today, one person is expected to do both.
If you're comparing these titles as part of becoming an instructional designer, there's also a 2026 wrinkle to factor in: AI is absorbing much of the production work, which changes which half of the skill stack is worth betting on. I'll get to that below.
What is the difference between an instructional designer and an eLearning developer?
An instructional designer figures out what a learning experience should teach and how, then they document that design. An eLearning developer builds that experience in tools like Storyline 360. The titles overlap heavily in practice, and plenty of job postings use them loosely.
If you know the ADDIE model, the split is simple: the instructional designer owns Analysis and Design (and often Evaluation), while the eLearning developer owns Development. Here's the side-by-side view:
| Instructional designer | eLearning developer | |
|---|---|---|
| Core focus | Deciding what to teach and how, grounded in analysis and learning science | Turning the design into a working course |
| Typical deliverables | Learning objectives, SME interview notes, scripts, storyboards, assessment questions | Prototypes, interactive modules, published SCORM/xAPI packages |
| Primary tools | Docs, slides, action maps, storyboard templates | Storyline 360, Rise, Adobe Captivate, the Adobe suite, sometimes HTML/CSS/JavaScript |
| Place in ADDIE | Analysis and Design, often Evaluation | Development, plus Implementation support |
| Key skills | Writing, SME interviewing, assessment design, justifying decisions with learning science | Authoring-tool mastery, visual design, programming logic, media editing |
| Typical US pay (aggregators, mid-2026) | Roughly $79k to $93k average | Roughly $96k to $105k average, on much smaller samples |
| Career ceiling | Higher on average: design work leads toward strategy and leadership | Lower on average, though specialists command premium rates |
I walk through this exact comparison, including the ADDIE framing and the earning-potential question, in this video:
What does an instructional designer do?
An instructional designer writes learning objectives, interviews subject matter experts, researches and writes instructional content, and justifies design decisions with learning science. Their main deliverable for an eLearning project is a script or production-ready storyboard, often with programming notes describing how interactions should function.
Traditional instructional designers do not build the end product themselves. They write the content, describe the intended structure and interactions, and hand off to a developer. They may also work with a graphic designer to curate the visuals the final course will use.
Traditional instructional designers are typically proficient in:
- Writing learning objectives
- Writing instructional content
- Interviewing subject matter experts
- Researching instructional content
- Writing test questions
- Selecting practice activities
- Justifying design decisions with learning science
That's the short version. For the full picture of the role, see what instructional designers do day to day, and for a deeper breakdown of the abilities behind it, see the instructional design skills employers look for.
What does an eLearning developer do?
An eLearning developer turns storyboards into working courses in authoring tools, handling the interactions, states, triggers, animations, and sometimes custom code that make everything function. Their work typically begins once the instructional designer finishes the storyboard and hands over the content and assets.
In my experience, eLearning developers are much more focused on the technical side: programming things in the authoring tools, knowing their way around the Adobe suite, and adding custom code when needed.
The first thing a good developer does is inspect the storyboard for red flags. Traditional instructional designers often don't spend much time in authoring tools, so they don't always know what those tools can and can't do. It's common for a storyboard to request an interaction that would be trivial in a face-to-face session but would require a big budget and custom programming to work in an eLearning environment. The developer's job is to catch those issues early and work with the designer to resolve them.
Once the storyboard is clean, the developer builds a prototype in a rapid authoring tool such as Articulate Storyline 360 or Adobe Captivate (or a lighter-weight tool like Rise for simpler courses), then implements all the assets, programming, and animation for the final product.
Great eLearning developers excel at:
- Developing interactive eLearning with rapid authoring tools
- Using custom web development skills as needed (HTML, CSS, JavaScript)
- Programming complex branching scenarios, interactions, and gamified courses
- Editing photos, vectors, and videos as needed
- Applying visual design principles, multimedia learning principles, and user experience best practices
How do instructional designers and eLearning developers work together?
The classic handoff has instructional designers running analysis and storyboarding, then the eLearning developer reviews, prototypes, and builds. After launch-ready drafts go out for feedback, the work splits: content changes go to the designer, functionality changes go to the developer.
Analysis and action mapping
The instructional designer works with stakeholders and SMEs to define the performance problem and the high-priority actions the training should support.
Storyboard
The designer writes the on-screen text, voiceover script, and programming notes, and gathers or curates the assets the course will need.
Developer review
The developer inspects the storyboard for feasibility red flags and collaborates with the designer to resolve anything that would blow the budget or break in the tool.
Wireframe and prototype
The developer (or the designer, on hybrid teams) sketches how content sits on screen, then builds a working prototype of one representative section in the authoring tool.
Full build
The developer implements every asset, trigger, state, and animation to make the end product function as designed.
Split feedback handling
When client or stakeholder feedback arrives, the designer handles changes to the instructional content and the developer handles changes to functionality.
Here's one of my process opinions: wireframes are the missing step between storyboards and interactive eLearning for a lot of instructional designers. Teams that jump straight from a text document to a built course burn development hours discovering layout problems a wireframe would have caught in minutes.
This division of labor exists for a reason. When one overextended person is forced to do everything, the end product suffers: they spend less time on the design work they excel at and more time fighting graphics, programming, and animation. Custom eLearning agencies recognize this, which is why many of them still segment the work exactly as described above.
Who earns more, instructional designers or eLearning developers?
On the big salary aggregators, eLearning developers currently average more than instructional designers. But the developer figures rest on much smaller samples, and in my experience instructional designers have the higher long-term ceiling.
Here's the data as of this update in 2026:
| Source | Instructional designer | eLearning developer |
|---|---|---|
| Indeed | $79,513 average (1,300+ reported salaries) | $95,883 average (only 46 reported salaries) |
| ZipRecruiter | $79,711 average | No comparable national figure published |
| Glassdoor | $92,670 total-pay estimate | $104,611 total-pay estimate |
| BLS Occupational Outlook Handbook | $65,850 median (May 2024), for the closest federal category: training and development specialists | Same category covers both titles |
Something I've said for years still holds: generally speaking, you have more earning potential if you can do more of the instructional design tasks. eLearning developers tend to have a lower pay ceiling than instructional designers, because design responsibility is what leads to senior, strategy, and leadership roles. The aggregator snapshots and the ceiling argument aren't actually in conflict: averages measure the middle of each title today, while the ceiling is about where each path can take you over a decade.
For first-party numbers from practicing IDs, including breakdowns you won't find on the aggregators, see my instructional designer salary data.
How is AI changing both roles in 2026?
AI is absorbing the production half of the stack: asset generation, interaction building, even working simulations from a plain-English description. That makes design judgment, like knowing what to build and why, the more defensible half of the skill set.
Industry research points the same direction: generative AI is reshaping production workflows while instructional design fundamentals remain the foundation of the work. The hours that used to go into building states, triggers, and media are shrinking. The hours that go into analysis, scenario design, and evaluation are not.
I see this firsthand because I build in this space. My company, devlin.ai, launched in 2026: you describe a scenario in plain English and get a working voice or text conversation simulation that embeds in Storyline, Rise, or any LMS, with AI evaluation and scores reporting back to the course. A build that once required a specialized developer and weeks of production now takes a designer 30 minutes. But the tool can't decide which conversations are worth practicing, what a rubric should reward, or whether the scenario reflects how the job actually works. That's designer judgment, and it's the part that AI hasn't touched.
That's also why I built tooling in the first place. I don't want instructional designers to have to spend three months learning backend code and security just to ship an AI-powered practice conversation. I want them doing what they do best.
Should you become an instructional designer or an eLearning developer?
For most people entering the field in 2026, the answer is neither pure path: build the hybrid stack of instructional design theory plus development skills. That combination has been the reliable route to in-demand roles for years, and AI makes the pure-production path riskier than it used to be.
Instructional design theory plus development skills has been close to a guaranteed path to a good ID role since I entered this field.
That fusion was true when I got into the field, and it's been true ever since. What's changed is the second half of the stack. As of mid-2026, I wouldn't advise anyone to pursue a dedicated eLearning developer career path, unless you're willing to dive deep in tools like Claude Code. AI-powered development tools will likely shrink the number of roles where your sole job is building in an authoring tool. It's an incredible time, though, for people who are good at instructional design and know how to ask AI for what they want. If you have the creativity and the vision, tools like Claude Code let you build quickly enough that a dedicated developer often isn't needed.
There's also a self-awareness question no salary table can answer: which work actually energizes you? I've noticed I enter flow state far more easily with development work. I can build until 2 a.m. with music on and stay completely in the zone, while instructional design subject matter takes real effort for me to focus on, so I have to create more space for it. Knowing that about yourself matters, because you'll spend thousands of hours on whichever half you choose to emphasize.
Answer a few questions and see which path fits your strengths:
Answer five quick questions about the work you actually want to do. I will rank the three paths from this article and link you to the right sections.
Whichever direction the matcher points you, your portfolio is what proves it. Hiring managers want to see finished work: a storyboard and a built course beat any title debate, and hybrid portfolios that show both are the strongest examples you can send. If you're starting from zero, here's how to land an ID job without prior experience.
For readers who want structure and support while building the hybrid stack, my licensed career school, Peck Academy, teaches exactly this combination: foundational ID theory, Storyline 360, and AI skills, with a curriculum reviewed by an advisory committee of 10 independent industry experts. It's my school, so weigh that disclosure accordingly.
What about curriculum developers, LXDs, and other titles?
Most neighboring titles are company-specific labels for the same core work. Before you rule a posting in or out by its title, read the responsibilities.
- Curriculum developer. Mostly semantics. AWS, for example, used to call their instructional designers curriculum developers on a lot of teams. Same work, different label.
- Learning experience designer (LXD). Good instructional design has always included the learner-centered work that LXD presents as new; the label changed more than the job did. I break down the overlap in learning experience design vs instructional design.
- Learning engineer. A role that sits at the intersection of instructional design and software engineering, well-positioned for the age of AI. Join the mailing list for more content on this (coming soon).
- Multimedia developer. Focused on the asset side: video, audio, graphics, and animation that feed into courses.
The practical takeaway: hiring managers screen for skills and work samples, not the title that you're using. My survey of what ID hiring managers actually look for found portfolios and demonstrated skills carry far more weight than whatever title your last role happened to use.
Frequently asked questions
What skills do you need to be an eLearning developer?
You need mastery of at least one rapid authoring tool (Storyline 360 and Adobe Captivate are the most common), plus visual design fundamentals, media editing, and the programming logic to build states, triggers, and branching interactions. HTML, CSS, and JavaScript help for custom work, and AI-assisted development skills are increasingly expected.
How much do eLearning developers make?
As of mid-2026, Indeed reports eLearning developers averaging $95,883 per year and Glassdoor estimates $104,611 in total pay, both above the equivalent instructional designer figures. Those developer numbers rest on small samples, though, so treat them as rough estimates. The full sourced comparison is in the salary table above.
Can one person do both jobs?
Yes, and most corporate instructional design roles expect it. Professionals who handle both the design and the development bring big efficiencies to a project, which is why hybrid instructional designers are consistently in high demand.
Is eLearning developer a dying job title?
The build-only version of the role is shrinking as AI absorbs more production work, so I wouldn't bet a career on development alone (unless you're developing in tools like Claude Code). Development skills themselves remain valuable; the durable move is pairing them with instructional design judgment so you're the person deciding what gets built, not just building it.