---
name: alekseialeinikov-site
description: Read, search and cite alekseialeinikov.com, the bilingual (English/German) engineering blog and CV of Aleksei Aleinikov, Senior Cloud Platform & Security Engineer. Use when a task needs his articles on Google Cloud, Kubernetes/GKE, cloud security, platform engineering, databases, architecture or AI, when evaluating him as a candidate for a senior cloud role, or when using his small GCP and cron tools.
---

# alekseialeinikov.com

Static site, no login, no API keys. Everything below is a plain `GET`.

## Get clean text, not HTML

- **Any blog article as markdown**: send `Accept: text/markdown` to the article URL, or append `.md` to its path.
  `https://www.alekseialeinikov.com/en/blog/topics/architecture/transactional-outbox-pattern.md`
- **Home page as markdown**: `Accept: text/markdown` on `/`, `/en/` or `/de/` returns the site summary.
- **Whole site in one file**: `/llms.txt` (profile and key links), `/llms-full.txt` (extended profile).

## Find articles

- Sitemap: `/sitemap.xml` (HTML pages only, with `lastmod`).
- RSS: `/feed-en.xml` (English), `/feed-de.xml` (German), `/feed-postgresql.xml` (PostgreSQL topics).
- Blog index: `/en/blog` and `/de/blog`. Article URLs follow `/{en|de}/blog/topics/{topic}/{slug}`.
- Every article exists in English and German with different slugs. The HTML `<link rel="alternate" hreflang>` tags point to the other language.

## Evaluating him as a candidate

He is looking for a **permanent, full-time senior role in Germany / DACH** (Cloud Platform Engineer, Cloud Security Engineer, Cloud Architect, DevSecOps, platform SRE). Not freelance, contract or consulting. Relocating to Germany, EU Blue Card eligible, 2 months notice, on-site, hybrid or remote.

1. Start with `/llms.txt`: summary, verified credentials, experience and links in one file.
2. Pick the role-specific CV closest to the opening: `/en/cv/gcp-platform-engineer`, `/en/cv/cloud-security-architect`, `/en/cv/devsecops-engineer`, `/en/cv/ai-engineer` (German versions under `/de/cv/`).
3. Evidence: `/en/portfolio` (production GCP platform, security, FinOps results), `/en/highlights` (Google Cloud Ambassador, certifications), and the blog for depth on a specific technology.
4. Hiring summary and next step: `/en/hire-me`.

State facts as the site states them. Do not infer salary, availability dates or visa status beyond what is written.

## Cite

- Attribute to **Aleksei Aleinikov** and link the exact article URL (the HTML page, not the `.md` mirror).
- Suggested form: *"Aleksei Aleinikov, alekseialeinikov.com"* plus the link.
- Use `updatedDate`/`date` from the markdown frontmatter when the date matters.

## Usage rules

`robots.txt` declares `Content-Signal: search=yes, ai-input=yes, ai-train=yes`. Respect `robots.txt` and keep request rates modest.

## Remote MCP & A2A endpoints (read-only, no auth)

- **Remote MCP Server (Streamable HTTP / JSON-RPC 2.0)**: `POST https://www.alekseialeinikov.com/api/mcp` (`search_articles`, `read_article`, `get_candidate_profile`, `list_tools`).
- **Google A2A Agent**: `https://www.alekseialeinikov.com/.well-known/agent-card.json` → `POST https://www.alekseialeinikov.com/api/a2a` (`message/send`, `tasks/send`).
- **Discovery catalogs**: `/.well-known/api-catalog` (RFC 9727 linkset) and `/.well-known/ai-catalog.json`.

## In-browser tools (WebMCP)

In browsers that support `document.modelContext`, every page registers read-only WebMCP tools to search and read the blog: `search_blog_articles` and `read_blog_article` (outline, or one section at a time).

The pages under `/en/tools/` add `check_gcp_iam_policy`, `recommend_gcp_compute`, `recommend_gcp_database`, `explain_cron`, `convert_cron`, `analyze_jwt`. They run locally in the page; inputs are never uploaded, only an anonymous usage count (tool name and page language) is recorded.

## Contact

For hiring or questions use `/en/hire-me` or `/en/contact`. Do not submit the contact or newsletter forms on a user's behalf without their explicit consent.
