Production AI architecture, code, evaluation, and system monitoring

Contribute to Jam With AI

Share the AI/ML lessons people only learn by building.

We publish original technical writing for practitioners and share strong work with 650,000 followers across platforms. Real systems, useful evidence, and no disguised product pitches.

Editorial brief

Write what you wish someone had told you.

Jam With AI serves engineers, data scientists, researchers, and technical leaders. The best submissions explain a real decision, show enough evidence to trust it, and leave readers able to act.

Read an example article

01

Postmortems

What broke, what changed, and what your team would do differently after shipping.

02

Architecture deep dives

A technical decision, its constraints, alternatives, and measurable trade-offs.

03

Hands-on guides

Working code and a complete path through building, evaluating, or operating a system.

04

MLOps lessons

Reliability, monitoring, cost, evaluation, and the work that keeps AI systems running.

A strong submission

  • Shows original thinking or hard-won production experience.
  • Explains the constraints, trade-offs, and measurable outcome.
  • Includes working code or evidence where the subject requires it.
  • Sounds like the author, with clear ownership of the claims.

Not a fit

  • Vendor pitches presented as independent education.
  • Rewritten documentation without a new technical perspective.
  • Unverified AI-generated writing or invented results.
  • Buzzword-heavy commentary without decisions or evidence.

Topics

Technical depth across the AI stack.

RAG systemsAI agentsLLMsMLOpsNLPSearchAI/ML system designFine-tuningModel servingRecommendersAgentic programmingCareer and leadership

Length and structure

Aim for 1,500-3,000 words. Start with a clear thesis, use descriptive headings, and finish with practical takeaways.

Code and evidence

Include working code, architecture diagrams, benchmarks, or screenshots where they help readers verify the idea.

Tone and style

Write directly for a technically fluent colleague. Prefer concrete decisions and real numbers over broad claims.

Originality

Submit original work, cite sources, disclose conflicts, and bring your own expertise and voice.

Submission process

Pitch first or send a complete draft.

Use the template when it helps, then share a viewable document through the form. We review every submission and give you a clear next step.

01

Draft or pitch

Write the complete article or a focused two- to three-paragraph outline.

02

Editorial review

Expect an initial response within five to seven business days.

03

Collaborative edit

We work with you on accuracy, structure, clarity, and presentation.

04

Publish and share

You approve the final article and receive full author credit and links.

Contributor questions

Do contributors get paid?

We do not currently offer paid contributions. You receive full author credit, a byline linked to your profile, and promotion through the Jam With AI audience.

Can I pitch before writing the full article?

Yes. Send a two- or three-paragraph outline with the topic, angle, and key takeaways so we can confirm fit before you invest in a full draft.

How long does review take?

We aim to send initial feedback within five to seven business days. A complete edit and publication cycle usually takes two to three weeks.

Can I write about a product I work on?

Yes, when the article provides technical value beyond promotion. Focus on the problem, implementation, decisions, evidence, and lessons learned, and disclose your relationship to the product.

Can I republish the article?

Yes. You retain ownership. We ask for a 14-day exclusivity window after publication, followed by a canonical link to the Jam With AI version when you republish.

Submit

Send your pitch or draft.

Make the linked document viewable so the editorial team can review it.