M&A Technology Integration
A phased serverless carve-out, network consolidation, and engineering standardization program for post-acquisition technical independence.
Primary outcome
Contributed to technical independence, stable integration, and the planned termination of the TSA.
The problem
Integrate heterogeneous infrastructure after an EV charging business acquisition and exit a high-cost Transitional Service Agreement without disrupting operations.
Constraints
- The migration had to preserve live EV charging and public-data integrations.
- Legacy and acquired systems used different networks, deployment practices, and ownership boundaries.
- Technical independence had to advance incrementally within the TSA exit schedule.
Approach and key decisions
- 01
Placed API Gateway in front of the legacy monolith and progressively separated priority functions into AWS Lambda services.
- 02
Consolidated VPN routing and network topology across public institutions, the existing business, and the acquired business.
- 03
Reorganized OCPP, SNS, SQS, and DynamoDB connection flows by operational domain.
- 04
Standardized repositories, code review, deployment manifests, notifications, and shared modules after the acquisition.
Outcomes
- Led the core carve-out migration stream and phased serverless transition supporting transfer of operations.
- Resolved routing conflicts and stabilized integrations among public institutions and both business environments.
- Improved consistency of engineering and deployment practices after the acquisition.
Technology and methods
Evidence and disclosure scope
This owner-authored summary omits internal topology, credentials, commercial terms, and security-sensitive migration details.
See the full resume context