Open for Contracts

Specs without ambiguity
> Visualized & Documented_

Senior System Analyst bridging the gap between Business and Devs. I transform chaos into strict JSON, PlantUML, and OpenAPI specs.

View Case Studies LinkedIn Profile

Microservices

SQL

PlantUML / Draw.io

analyst_profile.json

const analyst = {

name: "Anton Zakurdaiev",

role: "Senior System Analyst",

location: "Dnipro, Ukraine",

experience: 7, // years

domains: ["Fintech", "E-commerce", "Telecom"],

stack: {

docs: "OpenAPI / Swagger",

visual: "PlantUML / Mermaid",

tools: ["Figma", "Postman", "SQL"]

}

};

// Ready to deploy solutions

➜_

The "Visual & Doc" Approach

Requirements often fail because text is ambiguous. My workflow is different: I visualize first, then document.

Using tools like Draw.io, PlantUML and Figma, I create detailed flows that serve as a single source of truth. Once approved, I translate them into strict Technical Specifications and User Stories.

Visualization: Complex logic becomes simple diagrams (UML/C4/Sequence).
Documentation: Detailed specifications that developers actually understand.
High-Value Domains: Expertise in Fintech, E-commerce & Telecom.

INPUT (Ambiguous)

"We need a system to handle payments..."

MY PROCESS

Draw.io
Scheme

OpenAPI
Spec

OUTPUT: Ready for Dev

Tech Stack & Tools

Figma / Axure

UI/UX Prototyping

PlantUML / Draw.io

Code-based Visualization

SQL / API

Data & Integration

Documentation

SRS, User Stories, Tech Specs

Featured Case Studies

Examples of technical solutions for high-load domains.

FINTECHAPI Design

Fault-Tolerant Payment Gateway

Designing a zero-data-loss payment flow. Integration with 3rd party providers, handling timeouts, and Anti-Fraud checks.

IdempotencyPCI DSSSequence

View Artifacts

E-COMMERCESystem Analysis

Order Fulfillment Orchestration

Full cycle tracking: from "Order Placed" to "Customer Delivery". Integration with Warehouse logic, Order assembly, and Courier delivery services.

BPMN 2.0Event-DrivenSaga Pattern

View Artifacts