I'm a senior engineer on a European pharmacy retailer's e-commerce estate. Since early 2026 I've also been doing solution design — the storefront, the integration layer and the systems underneath — and I write the React and Node code that proves a design works.
Remit
Current work
Most of my time goes to one programme: bringing customer offers and loyalty together across a pharmacy retail estate. It touches loyalty, trading, pricing and content teams at once, which means the hard part is rarely a single component — it is holding one coherent picture while four groups describe the same thing in four vocabularies.
In practice that looks like consolidating stakeholder input, reconciling it against the solution outline design, and keeping the unresolved items visible and owned rather than quietly assumed — identifier mapping between systems, the taxonomy offers get filtered by, and which scope honestly belongs in a second phase instead of this one.
Track record
European pharmacy retail · Senior Software Engineer, performing solution-architect duties since early 2026
Architecture across loyalty, trading, pricing and content teams: reconciling stakeholder requirements against the solution outline design, tracking scope and open decisions in one place, and sequencing the work so delivery teams can build against something stable.
Lead engineer · multi-team programme
Worked alongside architects and business stakeholders on proposals: options, estimates, and the unglamorous check that what was being promised would actually integrate with the platform already in production — and with the organisation's own engineering standards.
React · Node microservices · edge routing
Led a team that lifted navigation out of a CMS-rendered site: microservices bridging authored content into React components, edge routing updated so new pages resolved correctly, and a deliberate cull of legacy scripts and asset handling that made the experience measurably more responsive.
React · Node · Kafka event bus
A component that let customers manage consent by type, backed by event-driven services publishing to an external platform, plus migration jobs that moved existing consents and topics off the legacy system without a gap in compliance.
React · Node orchestration · Java · Azure
Custom journeys for treatment services, and an authentication flow spanning several operational domains: a reusable front end over a Node orchestration layer, with the business rules held in a Java service so identity logic stayed in one place.
Agritech start-up · Ember.js
An interface that turned ground-sensor readings and satellite imagery into something farmers and agronomists could read at a glance and act on the same day.
Global energy sector · distributed team
Features and ordering-process work for applications moving onto a cloud platform, aligning requirements with backend, middleware and management functions spread across three continents.
Procurement software · ExtJS · AngularJS
Several applications built from scratch — a web shop, an invoicing application, and a form builder reused wherever other products needed forms — along with the test and build tooling around them.
Method
Stack
Background
My degree is in communication and public relations, from Transilvania University of Braşov. I came to engineering sideways, through a front-end internship, and I have stopped treating that as a gap on the CV: a large part of this work is getting four teams to agree on what a word means.
Beyond work