Aleksei Pikalov · Software Architect & Technical Lead · Munich
Architect who ships with the team.
Distributed systems, APIs and integration for 20+ years. Now building agentic AI platforms.
Career · 2004 → 2026
Telefónica Germany2024 — now
Deutsche Telekom2015 — 2024
YOTA2013 — 2015
Giesecke+Devrient2010 — 2013
Veeam2008 — 2010
Alcatel-Lucent · Reksoft2004 — 2008
Highlights
AI agent platform
Built independently at Telefónica. 45 skills, ~20 systems, daily use across departments.
8 development teams
Owned a domain architecture at Deutsche Telekom: service boundaries, APIs and data models, worked out directly with the teams.
Greenfield platform
Designed the IT platform and integration layer at YOTA that scaled from 0 to 1.5M customers in its first year.
Summary
Software architect and technical lead with 20+ years across software development, system integration and architecture. I work directly with distributed engineering teams to turn business requirements into system designs and working software: service boundaries, APIs, data models, design reviews and hands-on prototypes.
Most recently I independently designed and built an internal AI agent orchestration platform that is now used daily across several departments. Working language: English (German B1).
Experience
Telefónica GermanyJun 2024 — Present · Munich
Solution Architect
Service orchestration, workflow automation and AI-assisted engineering.
AI agent platform for engineering
Independently initiated, designed and built an internal AI agent orchestration platform: an orchestration layer on top of existing agent harnesses that connects agents to company knowledge, ~20 engineering systems and reusable skills, and lets them work in web applications through browser control to carry out multi-step tasks.
Grew it from automating architecture work to daily use across several departments and functions (architecture, business analysis, network planning), with 45 reusable skills, 11 of them built by users themselves.
Use cases include system analysis, interface and data-model comparisons, cross-system consistency checks, planning support and engineering documentation.
Service orchestration & network automation
Define solution architecture for end-to-end service orchestration and workflow automation across multi-vendor systems (telecom: 5G network slicing, OSS).
Align API contracts, data models and dependencies with delivery teams and technology partners, and guide implementation.
Beyond the architect role, acted as product owner: assembled the delivery team and set up its agile delivery model (SAFe/Scrum: backlog, planning and review cadence).
Order management and fulfillment in Germany’s largest fiber rollout program.
Owned the architecture of the order fulfillment domain: a high-volume, end-to-end order flow from sales capture through provisioning in downstream systems to customer activation.
Worked directly with 8 development teams on service boundaries, API contracts, data models and design reviews; resolved cross-team integration issues.
Designed the domain’s microservice architecture (Java/Spring Boot, REST APIs): service decomposition, API-first contracts and process orchestration with Camunda BPM for integrations with third-party and network systems.
Represented the domain in SAFe PI Planning, aligning technical dependencies and roadmap with product management; promoted CI/CD and cloud-native practices and mentored engineers.
Deutsche TelekomOct 2015 — Sep 2022 · Fiber rollout program
Solutions Architect
Fiber rollout program, from its early stage.
Designed early architecture for the program’s order automation: integration patterns, BPM practice with Camunda and microservice standards that the platform later grew on.
Acted as the technical bridge between business stakeholders and remote development teams: translated requirements into designs and guided implementation, working in English.
YOTASep 2013 — Oct 2015 · Mobile operator
Solution Architect
Designed a greenfield IT platform that scaled from 0 to 1.5M customers within the first year (J2EE, TIBCO ESB, SOAP web services; telecom standards eTOM/SID).
Automated CRM and B2B processes to absorb exponential growth without proportional team growth; coordinated delivery across vendors and in-house development teams.
Established a model-first architecture practice (Sparx EA) and led architecture reviews from requirements through integration and acceptance testing.
Led a team of 3–4 engineers building banknote processing software for central banks: architecture, planning, estimates and delivery; Scrum Master.
Designed and prototyped core system components and owned requirements from product owner discussions to detailed specifications.
Veeam SoftwareDec 2008 — Jul 2010
Lead Software Engineer
Developed cross-platform Java monitoring components integrating VMware vSphere with HP Operations Manager; the product later evolved into Veeam ONE.
Alcatel-Lucent · Reksoft2004 — 2008
Earlier roles
Software Architect, Alcatel-Lucent: greenfield OSS/BSS integration layer for Microsoft Mediaroom IPTV, deployed for operators incl. Wind, SingTel and Portugal Telecom (.NET, C#, SQL Server).
Software Developer, Reksoft: components for the Saxo Bank online trading platform (.NET, ASP.NET, WinForms).
Freelance architecture work alongside full-time employment: system design, process automation, technology selection and guiding development teams through delivery.
Logistics ERP: order management and shipment tracking platform for an international freight forwarder.
Fintech factoring platform: automated financial services for the partner ecosystem of a major oil company.