Senior Software Engineer Lead
Aug 2025 - PresentOwned product delivery and technical direction post-CTO transition, leading architecture decisions, rollout systems, enterprise-grade integrations, and cross-team alignment while managing a delivery team of 8 developers (including 4 seniors) and 3 QC engineers.
Key contributions
- Engineered a .NET Core multi-tenant feature flag system (30+ tenants, ~40k users) with a priority rule engine, percentage rollout (tenant/segment/env), JSON-config values, and stateless runtime evaluation—powering mobile/web apps and enabling controlled, progressive production releases across high-traffic tenants.
- Built secure integrations with Gtel & Napas: RSA-4096 handshake, AES-256 payload encryption, mTLS mutual authentication, certificate pinning, retry queues, idempotent API contracts, and ACK-driven monitoring for unstable third-party services.
- Implemented Micro-Frontend architecture (Angular host + React modules) enabling independent deploy cycles and feature isolation—reducing regression surface and deployment coupling across teams.
- Introduced observability stack (PostHog + metrics pipeline + workflow) for rollout impact, feature adoption, anomaly detection, and regression tracing—cut debugging/analysis time significantly across release cycles.
- Assumed ownership of inherited infrastructure and kept the organization moving—quietly absorbing production fires, pipeline failures, cluster quirks, and integration instability so the product and teams never stalled; shaping ArgoCD, CI/CD, domains/SSL, and AKS/FKE/K3S/EKS clusters into systems that are diagnosable, recoverable, and stable instead of recurring unknowns.
- Built AI agents supporting code review, deployment assistant, service-quota validation, API health monitoring, and release analysis; shortened decision & delivery loops across product teams.
- Developed integration simulations and sandbox/demo modules to handle unstable partners and secure pre-contract validation with third-party ecosystems.
- Re-structured engineering organization after leadership transition: defined org chart, competency matrix, workload routing, and ownership boundaries—unlocking autonomy and reducing lead-time on technical decisions.
- Established a unified engineering playbook: branch strategy, commit convention, release tagging, rollout criteria, API/integration rules, and technical spec repository (RFCs, runbooks, troubleshooting guides).
- Led hiring and capability growth loops: structured interviews (QC/Fullstack), onboarding path, 1:1 coaching, performance review cycles, and cross-team conflict resolution to keep delivery collaborative and output-focused.
- Maintained delivery quality through documentation-first culture and process guardrails (checklists, handover rules, rollback readiness), ensuring predictable release cadences during scaling.