InfoQ online certification cohorts · machine-readable overview Read as Markdown →

InfoQ Online Certification Cohorts

Five-week live online cohorts for senior engineers and software architects, ending in an InfoQ certification.

Each week, participants watch a QCon talk on their own time, then join a four-hour live session where they apply the framework to a decision they are working on right now, alongside senior engineers from other companies and industries. Sessions are not recorded, so the group can talk about live decisions in confidence. 5 programs currently run on the site: Architecture, AI-Assisted Engineering, AI Security & Privacy Engineering, High-Performing Teams, and AI Engineering. USD1,470 per cohort. Four hours a week, for five weeks.

Run by C4Media, the team behind InfoQ and QCon.

See upcoming cohorts →

Key facts

The cohorts

CohortCredentialFacilitatorNext intake
Architecture InfoQ Certified Architect Program Luca Mezzalira October 9, 2026
AI-Assisted Engineering InfoQ Certified AI-Assisted Engineering Program Zichuan Xiong and Premanand Chandrasekaran October 19, 2026
AI Security & Privacy Engineering InfoQ Certified AI Security & Privacy Engineering Program Katharine Jarmul October 26, 2026
High-Performing Teams — — November 17, 2026
AI Engineering InfoQ Certified AI Engineering Program (ICAEP) Hien Luu Dates to be announced, waitlist open

Architecture

Published intakes

IntakeDatesTime (with timezone)Location
October Oct 9, 23, 30, Nov 6, 13 Friday, 10:00AM EDT Online (Zoom)
January Jan 22, 29, Feb 5, 12, 19 Friday, 09:30AM GMT Online (Zoom)

Week by week

  1. Architecture. The evolving role of the architect and core resilience patterns for distributed systems, including timeouts, retries, and idempotency. Weigh infrastructure choices and articulate the trade-offs to a CTO.
  2. Decentralized Decisions. Enable teams to make their own architectural decisions, with the boundaries that keep changes from causing system-wide issues.
  3. Platform. Platform engineering as a sociotechnical practice. The tensions between standardization and flexibility, and how to get real developer adoption rather than shadow IT.
  4. AI. The architectural challenges AI introduces. Systems thinking for AI agents and multi-agent architectures, focused on constraints and trade-offs rather than capability evaluation.
  5. AI in Architecture, and Capstone Presentations. The practical state of AI in the software development lifecycle. Most of the week is capstone presentations and peer discussion.

Capstone: a technical article of 2,000 to 3,000 words drafted across the cohort and presented in week 5. The best are published on InfoQ. Published examples: https://www.infoq.com/architecture-icsaet/

Who it is for: senior software architects, senior software engineers, principal architects, principal engineers, senior staff engineers, and technical leads with at least five years of experience who are involved in setting technical strategy.

AI-Assisted Engineering

The harness is everything in an AI coding agent except the model: the context you give it, the permissions it runs under, the sensors that catch mistakes, and the review and CI gates it has to pass. Over five weeks, participants build one against a real brownfield codebase and log their own results.

Published intakes

IntakeDatesTime (with timezone)Location
October Oct 19, 26, Nov 2, 9, 16 Monday, 09:00AM PDT Online (Zoom)

Week by week

  1. Comprehending the Codebase, Onboarding the Agent. Use an agent to understand an unfamiliar brownfield codebase and capture what you learn as durable context files. Onboard the agent like a new team member, with least-privilege permissions and sandboxing.
  2. Making the Change Well. Turn a thin ticket into a requirement an agent and a reviewer can verify against. Add characterization tests and the sensors that let the agent correct itself.
  3. Independent Verification Before a Human Sees It. Separate generation from review. Use an independent review harness rather than asking the generating agent to grade its own work, then triage what actually needs a human.
  4. Integrating: CI as the Team's Harness. Move verification from your own loop into the pipeline. Place each sensor by cost, add drift and health checks, and govern agents running unattended in CI.
  5. Propagating and Proving It. Codify recurring review findings into rules a new team could adopt, then compare five weeks of logged data against what you predicted in week one. The session also covers the capstone presentations.

Capstone: this cohort does not use the shared article capstone. Participants work a single brownfield repository across all five weeks and submit three things: the harnessed repository, one rule or agent skill codified from their own recurring review findings, and a write-up comparing their logged results against their week-one predictions.

Who it is for: senior, lead, and principal engineers, staff engineers, software architects, technical leads, platform and SRE engineers, and engineering managers and directors with at least five years of experience who already use coding agents on production code.

Tooling: the hands-on exercises anchor on Claude Code, and Claude Max or API access is recommended. The principles transfer to Cursor, GitHub Copilot, and other agents. Participants work against a shared brownfield capstone repository provided for the cohort, so everyone starts from the same point and can compare approaches.

How it differs from AI Engineering: the AI Engineering cohort is for engineers building AI systems, covering RAG and context pipelines, agent design, evaluation, and the infrastructure underneath. This cohort is for engineers building any software with the help of coding agents. If you ship a product that has AI in it, start with AI Engineering. If you ship a product that AI helps you write, start here.

AI Security & Privacy Engineering

Published intakes

IntakeDatesTime (with timezone)Location
October Oct 26, 28, Nov 2, 4, 9, 11, 16, 18, 23, 25 Mon & Wed, 03:00PM - 05:00PM CET Online (Zoom)

Week by week

  1. Working with Sensitive Data and AI. What counts as sensitive, where it leaks, and how to handle it before it reaches a model.
  2. Threat Modeling and Red Teaming. Prioritize the threats that matter and run hands-on red teaming against an LLM, drawing on STRIDE, LINDDUN, and Plot4AI.
  3. Necessary Controls: Guardrails, Data Flow Controls and Sandboxes. Guardrails, data-flow sanitization, and sandboxes, including open-weight guardrail models. Decide which control belongs where.
  4. Observability, Testing and Evaluations. Check the controls actually work, using observability tools such as Arize Phoenix, and build evaluation suites that catch failures before users do.
  5. Building out Governance and Auditing. Who owns safety, privacy, and security, and the governance and auditing to back it up, plus the group capstone presentations.

Capstone: a documented risk assessment and mitigation report for an AI product architecture, written as a technical article of 2,000 to 3,000 words and presented in week 5.

Who it is for: software engineers, AI/ML platform engineers, privacy and security engineers, software architects, and technical leaders with at least five years of experience working on AI security and privacy engineering in regulated industries.

High-Performing Teams

Published intakes

IntakeDatesTime (with timezone)Location
November Nov 17, 19, 24, 26, Dec 1, 3, 8, 10, 15, 17 Tue & Thu, 04:00PM - 06:00PM CET Online (Zoom)

AI Engineering

Published intakes: none currently. Dates are to be announced. Join the waitlist.

Week by week

  1. Becoming an AI-Native Engineering Team. Identify where AI changes daily engineering habits and architectural trade-offs in your own organization, and where it does not.
  2. Designing and Building RAG and Context Pipelines. Retrieval architectures, knowledge graphs, and memory pipelines that stay grounded as data changes and queries get harder.
  3. Designing and Building AI Agents. Agentic systems that survive contact with production, from single-purpose tools to multi-agent orchestration, including the trade-offs between autonomy and control.
  4. AI Platforms and Infrastructure. The platform layer that keeps AI systems running without overspending on inference. What to centralize, what to federate, and how to route batch and real-time workloads.
  5. AI Operational Excellence: Evals, Trust and Reliability. The evaluation and operational practices that keep AI systems dependable in production, plus the group capstone presentations.

Capstone: a co-authored technical article of 2,000 to 3,000 words, presented in week 5. The best are published on InfoQ.

Who it is for: software engineers, AI/ML platform engineers, software architects, and technical leaders with at least five years of experience who are involved in setting technical strategy.

How each week works

  1. Watch a QCon talk on your own time before the session.
  2. Join a four-hour live session with your facilitator and your cohort.
  3. Apply the framework to a decision from your own work, sharing what worked and what did not with the group.
  4. Take away something you can use at work that week.

Time commitment: four hours of live sessions per week, plus time-boxed homework of up to two hours. Most intakes run those four hours as a single weekly session; some split them into two shorter sessions in the same week. The total live hours and the five-week span are the same either way — the per-intake time above says which pattern an intake uses. Sessions run on Zoom. Participants also join a private Slack workspace for peer discussion between sessions.

What participants get

Certification

Certification is awarded on two factors: consistent attendance and active participation in the live sessions, and successful completion of the capstone. Participants are expected to attend at least four of the five live sessions.

The certification program is a joint initiative between InfoQ and QCon, both practitioner-driven brands owned by C4Media Inc. Certification program details and published capstone articles: infoq.com/infoq-certification-program

Pricing and payment

All amounts in USD.

ItemAmount
One cohortUSD1,470
Alumni discount on a second program147 off

Making the case to your manager

Most companies reimburse for professional development. A template to send a manager is at certification.qconferences.com/content/convince-your-boss

In-person cohorts

In-person cohorts run at selected QCon conferences, including QCon London and QCon San Francisco.

FAQ

What is an InfoQ online cohort?

A five-week live online program where senior engineers and software architects apply frameworks from QCon talks to decisions they are working on at work, alongside peers from other companies. Four hours of live sessions a week, plus up to two hours of homework. It ends in an InfoQ certification.

Who is it for?

Senior software practitioners with at least five years of experience who are involved in setting technical strategy. Titles vary by cohort and include senior, staff, and principal engineers, software architects, technical leads, engineering managers, and engineering directors.

Are the sessions recorded?

No. This is deliberate. Sessions stay unrecorded so participants can talk about live decisions, real constraints, and honest views of their own organizations in confidence.

What happens if I miss a session?

Participants are expected to attend at least four of the five live sessions, and attendance is one of the certification criteria. If you miss one, you can catch up through the private Slack channel, review the session materials and slides in the shared Google Drive folder, complete that week's homework, and ask questions in Slack.

What do I need to take part?

A stable high-speed internet connection, the current Zoom desktop client, access to the private Slack workspace, and a laptop or desktop. Mobile devices work but a computer is strongly recommended for the collaborative exercises. The AI-Assisted Engineering cohort also requires your own coding-agent access.

How do I earn the certification?

Consistent attendance and active participation in the live sessions, plus successful completion of the capstone.

What is the capstone?

In most cohorts, working groups co-author a technical article of 2,000 to 3,000 words applying what the cohort covered, presented in week 5, with the best published on InfoQ. The AI-Assisted Engineering cohort is different: participants submit a harnessed brownfield repository, a codified rule or agent skill, and a measurement write-up.

Why a cohort instead of watching the talks?

Because the work is defending the trade-offs in your own context. Hearing how engineers in other companies and industries think through the same decision is often as useful as the session content. The cohorts are built around a confidential peer group, live exercises, and facilitation by a working practitioner, rather than self-paced study.

Is this just another course?

The program assumes deep technical expertise already. Each week is built around a decision you are working on, not a case study. The focus is on the skills that are hardest to get from inside one organization: testing decisions with peers, articulating trade-offs to stakeholders, and making calls that are difficult to reverse.

How much does it cost, and will my employer pay?

USD1,470 per cohort. Most companies reimburse for professional development, and there is a template to send a manager at certification.qconferences.com/content/convince-your-boss

Can I get a refund?

Registration fees are not refundable.

Do you run cohorts in person?

Yes, at selected QCon conferences, including QCon London and QCon San Francisco.

Who runs the program?

C4Media Inc., the team behind InfoQ and QCon. QCon and InfoQ are trademarked and wholly owned brands of C4Media Inc., based in Canada.

What graduates say

"The single most valuable outcome has been improving how I write and think. I can now articulate trade-offs in a way that improves my proposals at work." Chinmay Sawaji, Senior Software Engineer @Klaviyo

"This cohort gave me structured time each week to step back and think about what it really means to be an architect." David Holliday, Product Manager / Product Owner @Munich Re

Links

Related events

About InfoQ and QCon

More than 1 million people read InfoQ every month, and 4,500+ attend QCon and InfoQ Dev Summit each year. InfoQ is a practitioner-driven community news site covering professional software development. QCon and InfoQ have given every major technology shift the same practitioner-led treatment for more than 20 years, with sessions chosen for technical depth and real production experience. The online certification cohorts apply that approach in a small-group format over five weeks.