Spot the bug in this LCEL chain that pipes a prompt template into a parser before the model

Attempt it

Click any words you think contain an error. Click again to unmark.

Mark at least one word to submit.

Quick reference

TL;DR

The parser is in the wrong slot. Output parsers consume model output; the model has to run first. Reorder to prompt | llm | StrOutputParser().

Memory aid

Sign in for the mnemonic that makes this stick. See Pro pricing.

Easy to grasp

Picture an assembly line. You write a request on a card, the chef cooks the food, the waiter plates it. The bug here is that the waiter is plating the card before the chef ever sees it. Then the chef gets the plated card and tries to do something with that. Reorder so the chef goes between the card-writer and the waiter, and the line works.

Key concepts

LLM frameworks

Quick scan · 2–4 min

Everything important, quickly.

3 minutes: identify the misordered parser, walk the type contract along each pipe, propose the corrected order, and connect the bug to LangChain's permissive runtime behavior.

Code example

python

from langchain_core.prompts import ChatPromptTemplate
from langchain_core.output_parsers import StrOutputParser
from langchain_openai import ChatOpenAI

prompt = ChatPromptTemplate.from_template('Summarise: {text}')
llm = ChatOpenAI(model='gpt-4o-mini')

# CORRECT order: prompt produces ChatPromptValue, model consumes it and returns AIMessage,
# parser extracts the .content string.
chain = prompt | llm | StrOutputParser()
result = chain.invoke({'text': 'A long article...'})
assert isinstance(result, str)

# Introspect the chain's input and output types if you want a static check
print(chain.input_schema.schema())   # expects {'text': str}
print(chain.output_schema.schema())  # str

Real-world examples

Real products, models, and research that use this idea.

LangChain's official LCEL examples uniformly show prompt | model | parser ordering
LangSmith traces of this buggy chain visually expose the misordered hops as type-mismatched steps
Production teams running Claude Opus 4.7 and GPT-5.5 chains add chain-output type assertions in CI to catch this class of bug
Vercel AI SDK avoids this category entirely by exposing model calls as functions rather than pipes

Interviewer follow-ups

What an interviewer would ask next. Try answering before peeking at the approach.

QWhat does StrOutputParser actually do under the hood, and when would PydanticOutputParser be the right choice instead?

Sign in or go Pro to see the approach for this follow-up.

QWhy does the chain not raise a clean TypeError even though there is a type mismatch?

Sign in or go Pro to see the approach for this follow-up.

QHow would you write a unit test that catches this bug regardless of model availability?

Sign in or go Pro to see the approach for this follow-up.

60-second cheat sheet

The night-before-the-interview bullets. Scan these on the way to the call.

Sign in for 5 unlocks/day or go Pro for unlimited revision sheets. See Pro pricing.

References

Primary sources. Skim if you want the original framing.