Founder & engineering leadership
Dmytro Nasyrov
Founder and CTO Pharos Production
Founder of Pharos Production, PhD in Artificial Intelligence and lecturer at Igor Sikorsky Kyiv Polytechnic Institute.
About
Dmytro Nasyrov is the founder and CTO of Pharos Production, a software development and AI engineering company since 2013. With 23 years of engineering experience and a PhD in Artificial Intelligence, he leads engineering culture at Pharos and lectures at Igor Sikorsky Kyiv Polytechnic Institute.
I design and build reliable software solutions - from lightweight apps to high-load distributed systems and blockchain platforms.
PhD in Artificial Intelligence, MSc in Computer Science (with honors), MSc in Electronics & Precision Mechanics.
Education and credentials
- PhD in Artificial Intelligence
- Lecturer, Igor Sikorsky Kyiv Polytechnic Institute
- Alumnus, Igor Sikorsky Kyiv Polytechnic Institute
Areas of expertise
- Artificial Intelligence - LLM integration, RAG, agents, ML platforms
- Blockchain protocols - DeFi, NFT, smart contracts, dApps
- FinTech platforms - payments, compliance, RegTech
- Custom software development - web, mobile, enterprise
- DevOps and cloud architecture
- Engineering leadership - strategy, technical due diligence
Career timeline
-
Founder and CTO, Pharos Production
Software development and AI engineering. 90+ engineers, 110+ apps for 200+ clients across 28 industries. Aligned with ISO 27001, SOC 2, HIPAA, PCI DSS and GDPR frameworks.
-
Lecturer, Igor Sikorsky Kyiv Polytechnic Institute
Teaching engineering at Ukraine's leading technical university.
Ideas from practice
Articles by Dmytro Nasyrov
ML Model Rollback
An ML model rollback restores the last validated release, but the previous model behaves as it did only if its features, preprocessing, threshold and serving runtime come back with it. The guide below covers the pin manifest, the choice between rollback, roll through, retraining and fallback, drift triggers calibrated by batch size and how to rehearse the path.
Smart Contract Deployment Checklist: From Testnet to Mainnet
Authorize a mainnet release through a versioned manifest and ordered checks. The runbook assigns owners, required evidence and stop conditions before deployment and before enabling user activity.
Prior Authorization API
CMS-0057-F requires payers to run a Prior Authorization API on FHIR R4, US Core and SMART and only recommends the Da Vinci CRD, DTR and PAS guides, while since October 1, 2026 certification to 45 CFR 170.315(g)(31)-(33) has required CRD 2.2.1, DTR 2.2.0 and PAS 2.2.1. This guide maps each component to its builder, governing text and failure mode, with a version matrix, conformance testing and build orders for both sides.
Payment Orchestration Retry Logic
Payment orchestration retry logic decides whether a declined payment is tried again, when, on which route and with what changes. This guide maps Visa's four decline categories to retry and routing decisions, explains why cascading is not settled by the rules, treats SCA soft declines as a step-up and keeps every attempt idempotent.
Popularity Bias in Recommender Systems
Popularity bias makes a recommender show already popular items more often than users' tastes justify, and retraining on the resulting clicks makes it worse. This guide computes popularity lift, exposure Gini, coverage, novelty and miscalibration from serving logs, ranks the fixes by engineering cost and covers what the DSA asks of recommender systems.
Smart Contract Testing and Acceptance: What to Verify Before an Audit
Link each smart contract requirement to an expected result, evidence and reviewer. The escrow matrix covers permissions, terminal states, expiry, pause behavior, transfer failure and unpaid obligations.
Last updated: