Your codebase called. It's scared.
MD.BUILDSSYSTEMS.
Greenfield or halfway on fire, I build it, move it, and harden it so it holds.
Technical Stack
58+technologies in production
REST APIs
RabbitMQ
SequelizeREST APIsRabbitMQSequelizeREST APIsRabbitMQSequelizeREST APIsRabbitMQSequelize
Microservices
JWTMicroservicesJWTMicroservicesJWTMicroservicesJWT
WebSockets
OAuth 2.0WebSocketsOAuth 2.0WebSocketsOAuth 2.0WebSocketsOAuth 2.0Where I've shipped
Professional Experience
Mediusware
Senior Software Engineer
• May 2025 - PresentLeading development of enterprise-level applications using cutting-edge technologies. Responsible fo...
Key Technologies Used
All Generation Tech
Software Engineer
• Dec 2024 - May 2025Developed scalable web applications and mobile solutions for international clients. Specialized in r...
Key Technologies Used
Selected work
Featured Projects
How I Work
Four phases. Transparent milestones. Working software every two weeks.
Discover
We dig into your existing system before writing a single line. Understanding what's breaking, what's slowing you down, and where the real leverage is.
What Happens
- Codebase and architecture audit
- Stakeholder alignment session
- Risk and bottleneck mapping
- Tech stack evaluation
Outcome
- Clear picture of what needs to change
- Shared understanding of scope and risk
- A migration or modernization strategy you can act on
Plan
No guesswork. We define the roadmap, sequence the work to minimize disruption, and lock in the approach before build begins.
What Happens
- Phased delivery plan
- Technical architecture decisions
- Integration and dependency mapping
- Milestone and checkpoint definition
Outcome
- A clear roadmap with no-surprise milestones
- Stakeholder-aligned priorities
- Foundation that the build phase won't need to undo
Build
Delivery in stages. You see working software every two weeks. Not at the end.
What Happens
- Feature delivery in short sprints
- Regular demos and async progress updates
- Continuous feedback integration
- Zero-downtime migration practices
Outcome
- A product that becomes real incrementally
- Faster feedback cycles
- Visibility into what's built, what's next, and why
Ship
Launch is not a handoff. We stay close through deployment, monitoring, and the first weeks in production.
What Happens
- CI/CD and deployment workflows
- Monitoring and alerting setup
- Launch checklists and release coordination
- Post-launch iteration planning
Outcome
- Smooth, lower-risk release
- Confidence the system can be maintained and improved
- A team that doesn't disappear after go-live
We dig into your existing system before writing a single line. Understanding what's breaking, what's slowing you down, and where the real leverage is.
What Happens
- Codebase and architecture audit
- Stakeholder alignment session
- Risk and bottleneck mapping
- Tech stack evaluation
Outcome
- Clear picture of what needs to change
- Shared understanding of scope and risk
- A migration or modernization strategy you can act on