MR Mikhail RazakovEngineering portfolio

Professional profile / 02 — 03

Mikhail RazakovSYSTEMS / PLATFORM ENGINEER · .NET

I design and build .NET services and infrastructure with explicit module boundaries and recoverable, testable state. VpnMediator handles duplicate payment events and access recovery; UniversalToolchain checks dependencies before execution; in the LMS I own architectural invariants and review. Approx. one year of aggregate commercial development across a mixed stack.

Editable formats DOCX Markdown
01 / 04

Experience & practice

Commercial work, research and independent projects are presented separately, without inflating tenure.

Oct 2026 — present

ISP RAS · SharpChecker

Symbolic computation and structured C# code/declaration metadata for static analysis and AI-assisted defect recognition.

Jul — Aug 2026

MCST · compiler engineering internship

C++23/LLVM 22: experimental LICM with conservative legality checks; Python differential checks of before/after behavior.

approx. 1 year total

Commercial development · C#/.NET & adjacent technologies

Application and backend work with C#/.NET, Unity, ASP.NET Core, SQL/PostgreSQL, file I/O and servers. Duration is candidate-reported.

02 / 04

Engineering work

Real constraints, engineering choices and verifiable outcomes.

03
01 / 03

.NET · modular language/toolchain infrastructure · runtime architecture

UniversalToolchain · module contracts before runtime

Module contracts and dependencies form a validated LanguagePlan before runtime. Separate interpreter/CIL routes allow execution results to be compared instead of relying on module registration order.

Problem

Frontend, semantic components, IR/optimization passes, and execution backends should evolve independently while composing into one deterministic toolchain without hidden registration-order dependencies.

Approach

Typed contracts/capabilities, dependency/conflict resolution, deterministic contribution ordering, and typed artifact routes are resolved into one LanguagePlan before runtime materialization.

Outcome & limits

Implemented an end-to-end pipeline with frontend, IR, optimization passes, interpreter, and a CIL backend; current exact test manifest: 1,324/1,324.

02 / 03

.NET backend · payments · subscriptions · recovery

VpnMediator · payment/access consistency

Payment events and access entitlements are separate. Duplicate events are processed idempotently, provider state is reconciled, and operational scripts provide backup, health gates and rollback.

Problem

Payment, subscription, and actual access can diverge after duplicate webhooks, timeouts, or process restarts.

Approach

Explicit access and payment states, idempotent operations, audit trails, background reconciliation, migrations, and verifiable recovery paths.

Outcome & limits

Verifiable state transitions, backup/restore, health gates, and rollback-aware deployment; the public case study excludes secrets and user data.

03 / 03

In-development learning platform · agent-assisted implementation

TuringSquare-LMS · access control and implementation review

Role/course-access invariants and acceptance criteria for T-Bank sandbox payments. The project is in development; my focus is architecture decisions and review of agent-produced implementation.

Problem

Administrator, teacher, curator and student roles, course entitlements, and one-time/subscription payments must remain consistent under retries and network failures.

Approach

I define and review ASP.NET Core/PostgreSQL contracts and T-Bank payment requirements: order idempotency and authoritative provider state checks before entitlement grants. Parts of implementation were produced by AI agents.

Outcome & limits

Work in progress: checks and sandbox payments do not establish production readiness. No internal coin-wallet model.

03 / 04

Technical skills

Technologies are targeted to this CV edition; usage context is in the case studies.

  • C#/.NET, ASP.NET Core, EF Core, SQL/PostgreSQL, SQLite, REST/OpenAPI, async/await, Git/Linux
  • Idempotency, payment/access state, reconciliation, recovery/rollback; typed module contracts, dependency graphs, invariant checks

Reference projects

04 / 04

Education

HSE University — Software Engineering.

MEPhI Junior 2026, 1st-degree diploma; LangDev 2026 UniversalToolchain talk.

Evidence boundaries

Aggregate commercial tenure is candidate-reported. Source availability, a test manifest and freshly executed tests are different evidence levels. TuringSquare-LMS is in development: parts are agent-implemented, payments are sandbox only. None of these statements claim independently verified production behavior.

Read source limitations

Open to conversation / 02

Let’s discuss an engineering problem.

Mikhail Razakov · Moscow / remote

Mikhail Razakov © 2026All profiles ↗