Pick the 2026 task where an encoder-only transformer still beats a decoder-only LLM

**Encoder-only** transformers like BERT and the 2024 ModernBERT family stack only the encoder half of the original 2017 architecture. Every token attends to every other token in both directions, and the model outputs one hidden vector per input position. There is no decoder, no causal mask, and no way to generate the next token. This shape is excellent at one specific job: turning a piece of text into a fixed-size representation that downstream code can use. Two flavors of that job dominate in 2026. First, **dense retrieval embeddings**. A vector database stores one embedding per document chunk. At query time you embed the user query and run a nearest-neighbor search. Encoder-only models produce these embeddings faster and at higher quality per parameter than asking a decoder LLM for its hidden state. ModernBERT at ~150M parameters outperforms most retrieval setups that use a 7B decoder LLM as the embedder. Second, **reranker base models**. A cross-encoder reranker reads the query and a candidate document together and outputs a relevance score. Encoder-only is the right base because you need full bidirectional attention over both inputs and you only need a single number out. What encoder-only models cannot do: chat, write essays, reason step by step, call tools, or generate any text at all. Those are all decoder jobs.

**The shape determines the job.** Encoder-only transformers stack only the encoder half of the 2017 architecture: every layer is bidirectional self-attention, no causal mask, no generation head. The output is one hidden vector per input position, which you then pool (CLS token or mean pool) into a single fixed-size representation. BERT (2018) introduced this design for **masked-language-model pretraining** plus a CLS token for classification. The bidirectional context is the load-bearing feature: token t can attend to every token before and after it, which produces richer per token representations than a decoder's left-to-right context can offer. In 2026, encoder-only still dominates two roles: 1. **Dense retrieval embedders.** ModernBERT (~150M params, 8k context, 2024) is the modern reference. It produces 768-dim embeddings that beat embedding setups using 7B decoder LLMs as encoders, at a fraction of the latency and memory cost. Every production vector database (Pinecone, Weaviate, Qdrant) ships pipelines that default to an encoder-only embedder. 2. **Cross-encoder rerankers.** A reranker reads `[query, candidate_doc]` together and emits a relevance score. Bidirectional attention across the joined input is exactly what encoder-only provides. Decoder LLMs as rerankers are slower and rarely meaningfully better. The distinguishing question for the multiple-choice options is generation. Chat, long-form writing, and chain-of-thought reasoning all require autoregressive generation. An encoder-only model has no generation head and no causal-attention path. It can only consume text and produce a fixed-size representation. So the only option that fits the encoder-only sweet spot is dense retrieval: consume text, produce a 768-dim vector, no generation needed.