The Anthropic Certified Architect, Foundations is the first official Claude technical certification. It is also brand new and still in an early-adopter phase, which makes it hard to value. The free Anthropic Academy courses are the part worth doing today. The credential is a bet on a job market that does not exist yet.
Anthropic managed agents and office agents are different products with confusingly similar names. Managed agents is a developer API for running autonomous Claude agents on managed infrastructure. The interesting part is the brain-hands split: Anthropic runs the agent loop, while the sandbox can run in your own environment. This is what it is, and when to use it.
The Anthropic partner program, the Claude Partner Network, launched in 2026. The surprise is how open it is: membership is free and any organization bringing Claude to market can join. That means joining is not the achievement. It is a box of enablement tools, and it gives you a multiplier, not leads. Here is what it actually is.
What is an applied AI engineer? Someone who builds reliable production systems on foundation models they did not train. The role is defined less by a skill list than by one trait: failure-mode thinking. Here is what the job is, how it differs from ML engineering, and what makes a good one.
Should you get a Claude certification or an AWS certification? They certify different things. The Claude Certified Architect is product-specific, agent-native, and brand new. The AWS, Azure, and Google Cloud AI certifications are broad, years old, and openly bookable by anyone. Here is how to choose.
Claude Ask Your Org connects Claude to Slack, Microsoft 365, and Drive in one project. Its security model is sound, permission-aware and not indexed. The question it makes easy to skip is scope. Here is when to use the broad tool and when to scope Claude yourself with a filesystem MCP server.
Claude Code ships with five built-in agent types: Explore, Plan, general-purpose, statusline-setup, and claude-code-guide. Most people know two of them. The other three run constantly and shape how much your sessions cost. This is the full catalog, what each one is for, and why knowing them changes how you read your own terminal.
Is there a BAA for Claude Code? Yes, but the coverage is narrow. A BAA can cover the Claude Code CLI, but only with Zero Data Retention enabled, and the self-serve Enterprise HIPAA toggle does not include it. What is covered, what is not, and why.
A large context window in Claude Code feels free, and it is the opposite. Every token you load is re-billed on every turn after. The prompt cache that should make that cheap expires in five minutes, turning a tenth-price read into a higher-price write. And accuracy fades as the window fills. Here is the real cost.
Claude Code effort mode looks like a cost dial: turn it down to spend fewer tokens. The official docs say otherwise. Effort is a behavioral signal, not a strict budget, so low effort does not reliably cut spend and can quietly raise it. Here are the five levels, where they stop, and how to set effort with intent.
Most guides to running Claude Code in an enterprise stop at the install. That is the easy ten percent. The real work is the security design around an agentic tool that runs commands and reads files: the audit trail, prompt injection, permission modes, and a managed policy file.
The general-purpose agent in Claude Code is not the main agent and not something you pick. It is a built-in subagent Claude routes to on its own for complex, multi-step work. It inherits your model and, in current Claude Code, spawns as a fork of your conversation. This post explains how it actually works and what that costs you.