Dmitry M. - System Analyst / Solution Design Analyst¶
I work on system analysis and solution design for enterprise and product systems.
My strongest area is turning complex business domains into implementable system models: data structures, roles, user scenarios, integration flows, API contracts, constraints, edge cases, documentation, and development-ready tasks.
I have a hands-on engineering background: years of infrastructure and internal IT systems experience, Java/Spring, SQL, PostgreSQL, integration specifications, GIS/data tooling, and applied prototypes. This allows me to work not only with requirements, but also with the technical consequences of design decisions.
Professional Focus¶
- System analysis for enterprise and B2B systems
- Technical solution design
- Data models, reference data, and entity lifecycles
- API contracts and integration flows
- RBAC, access rights, and context-specific constraints
- Data import, validation, processing, and traceability
- Development-oriented documentation: C4, DFD, BPMN, ADR, specifications
- Backend-aware analysis: design with implementation, operations, and support in mind
Where I Bring the Most Value¶
I am useful in situations where simply “collecting requirements” is not enough.
Typical cases:
- the domain is complex, ambiguous, or poorly formalized;
- a business idea has to be translated into a system structure;
- processes, data, roles, integrations, and constraints have to be connected;
- development teams need clear models, contracts, and scenarios;
- an existing solution has to be analyzed, stabilized, or prepared for further development;
- there is a missing technical layer between business, analysis, architecture, and engineering.
Engineering Foundation¶
Analysis and design: System Analysis, Solution Design, Data Modeling, Integration Design, API Design, ETL Specifications, C4, DFD, BPMN, ADR.
Backend and data: Java, Spring Boot, JDBC, PostgreSQL, SQL, Python.
Infrastructure and delivery context: Docker, Linux, Nginx, GitHub, GitLab, AWS basics, S3-compatible storage, observability basics.
AI-assisted systems: controlled LLM execution, tool registry, execution traces, evidence-backed responses. I treat AI not as a replacement for architecture and analysis, but as an additional system layer that requires boundaries, verification, and traceability.
Key Projects¶
Botanical B2B SaaS¶
A B2B SaaS platform for botanical collection management: multi-tenancy, RBAC, scientific taxonomy, plant specimens, departments, locations, lists, Excel import, images, QR labels, and public organization pages.
My role: system design, domain modeling, data structure, backend/frontend coordination, import flows, access control, architecture decisions, and MVP implementation.
DocCompile¶
A SaaS platform for compiling professional artifacts from Markdown: local-first rendering with Mermaid, architecture icons, and PDF export; AWS serverless backend; Cognito; credit-metered AI transformations; and a documented pivot from proprietary workspace to a processing layer.
My role: Founder — product owner, system architect, and implementation owner.
Enterprise GIS / Railway Graph Tooling¶
An internal tool for working with railway infrastructure data: graph preparation, geodata processing, visualization, editing, and data-loading optimization.
My role: system analysis, data model design, prototyping, Java/Spring Boot, PostgreSQL, OpenLayers, and preparation of the solution for internal use.
FMCG Decision-Support Initiatives¶
Participation in analysis and solution design for demand forecasting and production planning initiatives in an FMCG context.
My role: system analysis, process description, integration flows, DFD/C4, SQL, specifications, and collaboration with R&D, DS and architecture teams.
AI Operational Intelligence Prototype¶
A technical PoC of controlled LLM execution for evidence-backed analytics: chat-like UI, experimental LangGraph flow, tool registry concept, execution traces, and answers grounded in synthetic data.
My role: System Designer, AI-assisted Prototype Engineer — execution flow design, scenarios, synthetic datasets, tool registry concept, prototyping, and validation of the approach.
Internal Initiatives¶
Serverless Transcriber¶
A serverless prototype of a transcription service on AWS: audio upload, file storage, processing execution, result persistence, and API access.
My role: solution architecture, backend/API design, AWS Lambda, S3, API Gateway, DynamoDB, Terraform, and Python.
Target Roles¶
- Senior System Analyst
- Technical System Analyst
- Solution Design Analyst
- System Analyst on a Solution Architecture track
- Associate / Junior Solution Architect in a team with a strong architecture function
Positioning¶
I do not position myself as a pure business analyst, pure backend developer, or full enterprise architect.
My working area is between business context, system models, data, integrations, constraints, and implementation. I help turn complex or unclear problems into systems that can be discussed, estimated, implemented, and evolved.