Senior Software Engineering · Integration · DevOps

Vasil Vasilev

I design, build and operate business-critical software systems.

Independent engineer in Munich. I connect custom software, enterprise integration and DevOps, with responsibility from architecture through long-term production support.

ENGINEERING RESPONSIBILITY E2E
One connected system. Select a layer to inspect its responsibility.
ENGINEERING MODELEnd-to-end ownership
Engineering model: applications flow through integration and delivery into operations, with continuous feedback.
Since 2006
Building and supporting production systems
End-to-end
Architecture, implementation, deployment and operations
Long-term
Maintenance, reliability and technical ownership
Munich · Remote
Across Germany and Europe, including distributed teams

01 / Selected work

Systems built with care.

Enterprise platforms. Connected devices. The software and operational work that brings them together.

01Enterprise platformFlagship

MidleoCORE

Enterprise middleware monitoring, governance and controlled automation in customer-controlled environments.

Connect operational visibility with workflows, approvals and deployment evidence.

  • PHP
  • JavaScript
  • CSS
  • Bash
Midleo CORE dashboard preview with middleware navigation, workflow and automation-job widgets.
Midleo CORE dashboard · Select the image to view the larger preview.

02Institutional publishing

PMG Lovech

The official school website, bringing academic information and announcements together for students, parents and teachers.

Structure institutional information for regular editorial updates and long-term maintenance.

  • PHP
  • JavaScript
  • CSS
  • jQuery
Archived PMG Lovech school website, showing the school building and public information.
Information for a school community.
Archived website
Archived project interface

03Booking platform

zapazi.bg

An online booking platform connecting appointment availability, reservations and customer interaction.

Move appointment management from telephone scheduling into a web-based workflow.

  • PHP
  • JavaScript
  • CSS
Archived zapazi.bg booking website, with specialist search and a calendar illustration.
Availability. Reservations. Connection. Archived website
Archived project interface

04Operational visibility

Middleware monitoring

Monitoring scripts and operational tools for runtime metrics, service health and middleware support.

Turn runtime signals into information that supports daily operations and incident analysis.

  • .NET
  • JavaScript
  • Angular
  • Bash
Conceptual system visualization

05Repeatable delivery

Middleware automation

Reusable scripts and Ansible workflows for middleware deployment, service management and recovery.

Make operational workflows repeatable across environments through infrastructure as code.

  • Bash
  • Ansible
  • Python
  • Java
Conceptual system visualization

06Archived project

WebControl

An earlier home-automation project, no longer in use. The source code is available as a reference.

02 / Engineering expertise

Four layers. One responsibility.

The application is only one part. Integration, delivery and operation are architectural decisions from the beginning.

LAYER 01 / UI / API / WORKFLOWS

Software shaped around the business.

Custom applications, internal tools and APIs turn business requirements into maintainable software.

  • Business workflows
  • Web and native applications
  • Maintainable interfaces
Explore the systems

LAYER 02 / EVENTS / MESSAGING / DATA

Connect the systems that already matter.

APIs, messaging and controlled data flows connect modern applications with enterprise and legacy environments.

  • Messaging and middleware
  • Data migration
  • External services
Explore the ecosystem

LAYER 03 / BUILD / VERIFY / DEPLOY

Make change repeatable and controlled.

Automated builds, verification and deployment workflows carry changes from source to production with clear operational evidence.

  • CI/CD pipelines
  • Infrastructure as code
  • Deployment automation
Follow the engineering process

LAYER 04 / OBSERVE / MAINTAIN / IMPROVE

Remain accountable after deployment.

Monitoring, incident analysis, security updates and ongoing maintenance keep production systems understandable and dependable.

  • Observability
  • Incident analysis
  • Long-term maintenance
Meet the engineer

03 / Working together

Clarity before code.

Direct collaboration with the engineer doing the work. A practical path from an uncertain requirement to a system people can operate.

  1. PHASE 01

    Understand the constraints

    Start with the business workflow, existing systems and operational requirements. Agree the boundaries before choosing tools.

  2. PHASE 02

    Make decisions explicit

    Define interfaces and implementation choices. Verify the software and make deployment repeatable.

  3. PHASE 03

    Plan for the handover

    Include monitoring, documentation and maintenance in delivery. Keep production feedback connected to the next change.

Operational feedback informs the next architectural decision.

04 / Technology ecosystem

Depth where it matters.

Application engineering, enterprise messaging and production automation. Selected tools first; the wider experience is available below.

Core engineering

Applications, interfaces and data.

  • Java
  • PHP
  • Python
  • Angular
More experience (8)
  • App development
  • CSS
  • Dart
  • Flutter
  • Mobile app dev
  • MySQL
  • Spring Boot
  • SQL

Enterprise integration

Messaging and connected business systems.

  • IBM MQ
  • IBM ACE
  • SAP Integration Suite
  • RabbitMQ
More experience (6)
  • Apache ActiveMQ
  • IBM MQ FTE
  • IoT Development
  • Node-RED
  • SAP Cloud Integration
  • TIBCO EMS

Platforms & infrastructure

Runtime environments, containers and cloud.

  • Linux
  • Docker
  • Kubernetes
  • Amazon Web Services
More experience (11)
  • Apache HTTP Server
  • Apache Tomcat
  • IBM Bluemix
  • Microsoft Azure
  • Microsoft IIS
  • SAP BTP
  • SAP BTP Cockpit
  • SAP BTP Connectivity
  • Splunk
  • System Administration
  • WildFly

Delivery & automation

Repeatable builds and operational workflows.

  • Ansible
  • Jenkins
  • Bash
  • GitLab
More experience (6)
  • Apache Maven
  • Atlassian Bamboo
  • GitHub
  • IBM UrbanCode
  • PowerShell
  • Salt

Enterprise & legacy systems

Experience with the systems businesses depend on.

  • IBM WebSphere Application Server
  • WebLogic Server
  • IBM Db2
  • z/OS
More experience (5)
  • AIX administration
  • AngularJS
  • Lotus Notes
  • Oracle Application Server
  • Solaris

Engineering practice

Supporting tools and disciplines.

  • Home automation
  • Jira
  • Photoshop
  • Project management

05 / About

Technical ownership from idea to reliable operation

I am an independent engineer based in Munich, helping companies deliver complex technical initiatives with clarity, reliability and long-term maintainability.

Education

Automation, Information and Control Engineering

I graduated with honors from a mathematics and science high school, specializing in mathematics and computer science. I then studied Automation, Information and Control Engineering at the Technical University of Sofia, where I earned an engineering degree followed by a Master’s degree.

Engineering foundation

The interdisciplinary program combined control engineering, system modeling and analysis with electrical engineering, electronics, computer science, microprocessor systems, measurement technology and programming.

There I developed a strong foundation in analyzing and designing control and automation systems for complex technical processes—a foundation I now apply to software architecture, automation, infrastructure and reliable operations.

06 / Start a conversation

A clear path to reliable operation.

Describe the business context, current constraints and systems involved. I will respond with a practical technical approach.

Start a conversation