Engineering leader / account owner / forward deployed engineer
I defined the engineering roles across a high 2-digit person engagement I now own end to end: P&L, hiring, performance. Forward deployed, still shipping. The throughline is making complex software actually move.
The useful version of the profile is not a job-title list. It is the connection between customers, delivery, teams, money, code, and the AI systems now changing how software gets built.
I own the account and stay hands-on in the code. Today that means full account ownership, current IC engineering, and agentic workflows that move a team of engineers faster without losing judgment.
Account health, delivery execution, budgets, forecasting, staffing, technical decisions, AI workflows, and the judgment to know when a system needs more context instead of more activity.
The point is not where I sat. It is what each role added to the operating range: code, delivery, people, accounts, customers, and commercial judgment.
Since November 2025, on an enterprise energy engagement: a Dusseldorf-based energy major, one of Europe's largest power generation and energy trading companies. Sole engineer for the full stack and the deliverable. AI-assisted development as the default working mode, running on agentic systems and orchestrators I built and own.
November 2022 to February 2025, on the Aily Labs engagement: a Munich-based, 200+ person AI decision-intelligence scaleup serving Fortune 500 enterprises.
From 2023, step by step into full account ownership. Running to present.
On the Flyward engagement through Principal33: an aviation forecasting SaaS, during a product and delivery reset, February to November 2025. Took a struggling delivery setup to client-ready. Part of a handful-sized team on heavy delivery and performance expectations: set priorities, unblocked technically complex initiatives, and kept implementation aligned with product needs. Weighed in on hiring and team-fit decisions, rebuilt the frontend foundation on Material UI, and introduced AI-assisted development practices.
One of 8 Community Leads for a 500+ engineer web community across Romania, a level above Team Leads. Owned Continuous Personal Development plans across the group: set goals, ran 1:1s and reviews, delivered feedback, mapped career paths to live delivery openings, and built promotion cases. Managed the bench and staffing, ran technical interviews and onboarding, and owned thought leadership through internal and external content and event talks. Advised sales and prospects on stack and estimations, and built POCs in partnership with the Delivery Community.
Led a small team focused on velocity, quality, and client consultancy while delivering React, Context API, Material UI, GraphQL, and SCSS work. Managed career paths, SMART objectives, friction, and team health.
Maintained and evolved AngularJS-React hybrid applications, moved product surfaces from REST toward GraphQL and WebSockets, worked tightly with product, project, and UX roles, and interviewed and mentored across the frontend pipeline.
Two years of front-end and back-end delivery across AngularJS SPA functionality, automation tasks, WebAPI endpoints, WCF services, C#, JavaScript, CSS, SQL Server, and practical code guidance for colleagues.
Built an internal web application with MVC.NET, C#, JavaScript, CSS, Microsoft SQL Server, Bootstrap, and Entity Framework, covering front-end and back-end fundamentals in a delivery setting.
Early quality work across game projects while studying Information Technology, building the foundation in testing discipline, software engineering, algorithms, systems, and networking.
Six areas cover the actual range: agentic systems, product engineering, platform context, delivery operations, account economics, and leadership.
Model-agnostic workflows for modern AI coding systems.
Hands-on delivery when a product idea, fix, or technical decision needs direct code.
The platform context behind software that needs to reach actual users.
The operating discipline around delivery, quality, resilience, and real use.
The commercial reality behind healthy software engagements.
People systems that make delivery more reliable.
I do not care which model wins a demo. I care whether the system has enough context, whether the work can be validated, and whether the output survives contact with delivery reality.
The work has to stay useful under pressure: in front of customers, inside teams, inside budgets, and inside code that needs to keep running.
From 2022 I ran delivery and defined the engineering roles for the engagement. From 2023 the account needed a single owner, so step by step I handed the engineering-leadership scope to the client's structure and took the account end to end. Splitting my attention across both would have served neither. The account has run on full ownership since: 7-figure P&L, 50+ hires, 100+ performance cycles.
The leadership framework could have been a template dropped on the org. Instead I co-designed it with the client's Heads of Organization, Engineering, and AI, with C-level in the room. Career paths, promotion markers, and KPIs came from how the org actually worked, not from a deck. It held because the people who ran it built it.
Notes, tools, and experiments around agentic systems, context engineering, practical AI-assisted work, and the habits that make software delivery less performative.
Daily notes on practical AI engineering, Claude Code, agents, and developer habits.
A curriculum platform for training context intuition and better AI-assisted work.
A small index of systems, experiments, and personal tools outside the consulting timeline.
Current, hands-on engineering at a senior level.
Agentic systems and orchestrators built around forward-deployed engineering practice. Personal endeavour, core to how I operate day to day. The IP stays mine.
Since November 2025: single IC for the full stack and the deliverable of a product serving a Dusseldorf-based energy major, one of Europe's largest power generation and global energy trading companies.
