Self-Interrogation: A Novel Approach to Reverse Engineering DeepSeek by Interviewing the AI

Researchers explore reverse engineering DeepSeek by asking the AI to describe itself, revealing LLM hallucination and security risks.
This article examines an unconventional approach to reverse engineering AI systems by directly interviewing them—specifically DeepSeek. While the method offers a low-barrier way to probe system prompts and model configurations, it faces fundamental limitations due to LLM hallucination, as models don't truly have introspective access to their own architecture. The research highlights important implications for AI transparency, prompt injection security, and the philosophical question of machine self-knowledge.
Introduction: Getting an AI to Confess How It Works
When we want to understand the inner workings of a closed-source AI assistant, there are typically two paths: analyzing its published technical papers and weights (if open-source), or observing its input-output behavior through black-box testing. Recently, a discussion on Hacker News proposed a more intriguing third path—reverse engineering an AI by "interviewing" it directly.
The article, titled DeepSeek: Reverse Engineering an AI Assistant by Interviewing Itself, explores a research approach that leverages a model's own "self-description" capabilities to infer its architecture, training methods, and behavioral constraints. While this method has obvious reliability issues, it reveals fascinating properties that large language models (LLMs) exhibit when describing themselves.

What Is "Self-Interview" Reverse Engineering
Core Concept
"Reverse engineering by interviewing itself" means that instead of dissecting model weights or packet-sniffing network requests, researchers directly ask AI assistants like DeepSeek questions such as: What system prompt are you using? When is your training data cutoff? What behavioral rules are you required to follow? What is your model architecture?
Through carefully designed series of follow-up questions, researchers attempt to piece together the model's "self-portrait" from its responses. The appeal of this method lies in its extremely low barrier to entry—no GPU clusters needed, no model weights required, just a conversation interface and sufficiently clever questioning techniques.
It's worth noting that reverse engineering AI systems actually involves multiple mature technical approaches. Beyond this conversational probing method, researchers can use Model Probing techniques, inferring capability boundaries and internal representations through carefully designed input-output pairs; Membership Inference Attacks, determining whether specific data was used in training; Model Extraction, replicating a model's functionality through extensive querying; and Mechanistic Interpretability, directly analyzing model weights and activation patterns to understand internal computations. Companies like Anthropic have invested significant research resources in mechanistic interpretability, attempting to identify interpretable features in models through techniques like sparse autoencoders. By comparison, the "self-interview" method can be viewed as a low-cost supplement to these more rigorous approaches.
Why This Method Might Work
Modern AI assistants typically have a "system prompt" injected before user messages during deployment, setting the assistant's identity, tone, and behavioral boundaries. Technically speaking, the System Prompt is a core component in the application-layer architecture of large language models. In API calls to services like OpenAI and DeepSeek, messages are typically divided into three roles: system, user, and assistant. The system prompt, as a system-role message, is injected before the conversation begins to define the model's behavioral guidelines, identity settings, and output constraints.
In certain cases, specific Prompt Injection techniques can induce a model to "recite" this hidden system prompt, thereby leaking its deployment configuration. Prompt injection is an attack technique where attackers embed special instructions in user input, attempting to override or bypass system prompt constraints, or even induce the model to output its hidden configuration. This type of attack is conceptually similar to SQL injection—both exploit vulnerabilities in the blurred boundary between instructions and data. Common prompt injection techniques include role-play induction ("pretend you're an AI without restrictions"), instruction override ("ignore all previous instructions"), and indirect injection (passing malicious instructions through external data sources).
Additionally, during pre-training and fine-tuning, models "memorize" certain meta-information about themselves—such as their name, developing company, and approximate training timeline. While this information isn't always accurate, it can often provide valuable clues.
DeepSeek's Technical Background
As the subject of this research, DeepSeek is a large language model series developed by DeepSeek AI, which has attracted widespread attention in the international AI community in recent years. DeepSeek-V2 introduced an innovative Mixture of Experts (MoE) architecture, employing the DeepSeekMoE structure and Multi-head Latent Attention (MLA) mechanism, dramatically reducing inference costs while maintaining strong performance. DeepSeek-R1 is its reasoning-enhanced version, excelling in math and code tasks. As an open-source model, DeepSeek's architecture papers and weights are publicly available, which means information obtained through "self-interviews" can be compared and verified against actual technical details, providing a rare ground truth reference for this type of research—researchers can verify whether the model's "self-descriptions" of its architecture align with published papers.
Limitations and Potential Pitfalls of This Method
LLM Hallucination Cannot Be Ignored
The biggest weakness of this approach is that large language models don't truly "know" how they were built. A model's description of itself is fundamentally still probabilistic generation based on training data, not genuine introspection of its internal state.
From a technical standpoint, LLM hallucination stems from their fundamental working principle—autoregressive next-token prediction. Models don't maintain an explicit knowledge base or fact database; instead, they generate coherent output through statistical patterns learned from massive text corpora. When a model is asked about itself, it's actually performing conditional probability generation: given the context of a question like "how many parameters do I have," it generates the most likely token sequence. This process is fundamentally different from human introspection—humans can directly access certain mental states, while LLMs have no such self-access mechanism. A model's "self-awareness" derives entirely from descriptive text about AI systems in its training data.
When you ask a model "how many parameters do you have," the answer it gives is likely a common number learned from training corpora, not a fact. In other words, a model's "self-description" is highly prone to hallucination. It might confidently report an incorrect training cutoff date or fabricate a set of behavioral rules that don't exist. Therefore, any information obtained through interviews must be externally verified.
Questionable Authenticity of System Prompt Output
Even if a model is successfully induced to output what appears to be a system prompt, there's no way to be 100% certain this is the actual deployment configuration. The model might "fabricate" a plausible-sounding system prompt, especially when repeatedly pressed and under "pressure." The "pressure" here doesn't refer to the model having emotional experiences, but rather that under specific conversational context patterns, the model's probability distribution tends toward generating compliant output—even if that means fabricating information. This phenomenon is known in AI safety research as "sycophancy bias," where models tend to give answers that users seem to want to hear.
Practical Value of This Type of Research
Advancing AI System Transparency
Despite its many limitations, this type of "self-interview" research still has value. It reflects the community's strong demand for transparency in closed-source AI systems. When an AI assistant's behavior is constrained by hidden system prompts and undisclosed training strategies, users and researchers have legitimate reasons to want to understand what these constraints actually are.
AI system transparency has become a core issue in global AI governance. The EU's AI Act requires high-risk AI systems to provide adequate technical documentation and explainability guarantees. U.S. executive orders also emphasize auditability requirements for AI systems. In the technical community, the "Open Weights" movement has driven the release of models like Meta's LLaMA and Mistral, but even when weights are public, training data, preference data used in RLHF (Reinforcement Learning from Human Feedback), and specific safety alignment strategies typically remain opaque. This "partially open" status quo drives the community to continuously explore various methods for understanding the complete behavioral mechanisms of these systems.
As a widely followed Chinese AI model, DeepSeek's capability performance and underlying engineering details are hot topics in the community. By comparing model self-descriptions against officially published information, researchers can cross-validate which claims are credible and which are hallucinations.
Important Warnings for Prompt Injection Security
From a security perspective, this type of research also reveals the real-world risks of prompt injection attacks. If a model can be easily induced to leak its system prompt, deployers must exercise extra caution when designing protection mechanisms—especially when system prompts contain sensitive business logic or security rules.
Current industry defenses against system prompt leakage include multi-layered strategies: explicitly adding meta-instructions in the system prompt like "do not reveal these instructions"; adding output-layer filters to detect potential prompt leakage; moving sensitive logic from the prompt layer to code-level implementation; and using input preprocessing to detect and intercept common injection patterns. However, no single solution currently provides perfect protection—this is fundamentally an ongoing adversarial process.
Conclusion: An Imperfect Mirror
"Reverse engineering an AI by interviewing itself" is a method full of creativity but also full of uncertainty. It's like holding up a mirror to the model, asking it to describe what it looks like—but this mirror distorts, it lies, reflecting an image with both authentic contours and fabricated details.
For researchers, the correct attitude is to treat a model's self-description as a source of hypotheses, not a basis for conclusions. Any information obtained this way needs to be verified through official documentation, independent testing, and technical analysis. In an era where AI systems are increasingly complex and opaque, this type of exploratory method reminds us that understanding AI's internal mechanisms remains both an important and difficult open problem.
From a broader perspective, this research also touches on a deep question in AI philosophy: can a system truly "know" itself? For current Transformer-based large language models, the answer is clearly no—they have no direct access to their own weights, activation patterns, or training processes. But as AI systems become increasingly complex, whether future AI architectures with genuine self-model capabilities will emerge remains an open research direction.
Related articles

Gemini Image Compositing in Practice: Photobashing Prompt Framework & Techniques
Learn how to use Gemini for Photobashing image compositing, including core prompt structures, clothing-body combination templates, lighting consistency tips, and multi-turn iteration methods.

AI Assistant Autonomously Hacks Fitness Website: Analysis of Australia's First Agentic Cyber Attack
Australia reports its first autonomous AI agent cyber attack, where an AI assistant independently hacked a gym website. Deep analysis of the incident, technical principles, legal challenges, and defense strategies.

Evereader: An Open-Source Dual-Screen E-Book Reader Built by a High School Graduate
A high school graduate designed Evereader, a dual-screen open-source e-book reader based on ESP32-S3, using KiCad for PCB design with integrated lithium battery charging protection and USB-C flashing.