The Work · 28 years
One pattern, run three times: make the fragmented one.
My career reads as a sequence of consolidations — divided products, separated teams, and competing roadmaps merged into single unified platforms. Read the thread below from the bottom up: it starts with the first consolidation in 2002 and ends with the role I just concluded, where the same playbook drives next-generation HCM strategy. The ember nodes mark the three times I ran the pattern.
Career thread · most recent first
NOV 2017 – JUN 2026 · MALVERN, PA Most recent role · concluded
Vice President of Software Engineering / Frontline Education
Led the HCM Solutions division: 150 global engineers delivering ~$200M in revenue (~55% of company total). Operated as a CTO-level partner to the executive team on technology strategy, AI direction, and M&A. Promoted from Senior Manager to VP across four progressive roles. Unlocked a $40M revenue opportunity, built the offshore org from a 2018 pilot to 170+ engineers in India, and led legacy modernization onto AWS serverless with zero customer disruption.
CONSOLIDATION 3 →Unified five HCM solutions — Absence, Time, Frontline Central, Professional Growth, and Recruiting & Hiring — onto a single platform: the same playbook from Connectiv, applied at enterprise scale.
DEC 2012 – AUG 2016 · BETHESDA, MD M&A integration owned
Director of Software Engineering / WeDo Technologies
Carried the Connectiv platform and team through nearly four years of post-acquisition integration with no disruption to delivery. Owned end-to-end integration of the acquired team, codebase, and roadmap into the parent org while delivering against enterprise commitments. Earned the M&A integration playbook now central to my leadership approach — managing competing roadmaps and cultural mismatches without sinking the acquired product.
OCT 2010 – NOV 2012 · BETHESDA, MD
Director of Software Engineering / Connectiv Solutions
Owned the entire engineering organization — front-end, back-end, architecture, and DBA — through Connectiv's growth phase and the lead-up to its successful acquisition by WeDo. Owned the technical roadmap, architecture, hiring, and delivery for the SaaS platform serving enterprise customers.
JUL 2007 – OCT 2010 · BETHESDA, MD Signature consolidation
Manager, Web Development / Connectiv Solutions
Built and scaled the team that became the backbone of the engineering organization. When the business decided in 2009 to consolidate Connectiv's two separate product solutions into one platform, led the effort end-to-end and launched the unified platform in 10 months.
CONSOLIDATION 2 →Established the platform-consolidation pattern later applied to Frontline's next-generation HCM strategy.
MAY 2006 – JUL 2007 · BETHESDA, MD
Senior Software Engineer / Connectiv Solutions · 7th employee
Joined as the 7th employee on the payroll. Built core components of the SaaS platform from the ground up, writing foundational code across both early product solutions — the basis for the unified platform that powered Connectiv's growth and acquisition.
1999 – 2006 · EARLY CAREER
Foundation · telecom · federal · commercial software
Senior Software Engineer — RGII TechnologiesFairfax, VA · 2005–2006
Senior Software Engineer — Romulus SoftwareFairfax, VA · 2002–2005
Software Engineer — TECNET Inc.Dallas, TX · 1999–2002
Consolidation 1 → At Romulus, led the consolidation of two web applications into a single unified platform delivered as eonetwork.org — the first instance of the pattern that would define key inflection points across the career above. At TECNET, wrote the calling-card rate engine for the flagship switch-network management platform.
Proof of judgment · the AI shift, firsthand
KarmaClock
A DELIBERATE TEST OF AI-NATIVE DEVELOPMENT ECONOMICS · 2026
Setting AI direction for an enterprise org credibly means understanding the new economics firsthand, not from a vendor deck. So while running the day job, I built and shipped a production-grade mobile app end-to-end using an agentic-AI workflow — to pressure-test what the technology actually changes about cost, speed, and delivery discipline. The spec-first method, CI gates, and agentic patterns proven here now inform how I lead enterprise SaaS modernization.
TRADITIONAL DELIVERY
6–8 weeks
small team + partial QA / DevOps / PM
→
TRADITIONAL EFFORT
~1,000 hrs
~2 devs plus support roles
→
AGENTIC-AI DELIVERY
~30 hrs
solo · ~5× faster, ~30× fewer person-hours
Rigor 211 passing tests at ~90% coverage · 4-lane CI/CD · documentation accuracy enforced as a CI gate
Method Spec-first: functional & non-functional specs with acceptance criteria mapped to named tests, before code
Transfer Spec-first discipline, CI gates, and agentic-skill patterns now directly applied to enterprise SaaS modernization
Method Spec-first: functional & non-functional specs with acceptance criteria mapped to named tests, before code
Transfer Spec-first discipline, CI gates, and agentic-skill patterns now directly applied to enterprise SaaS modernization
The pattern is portable. Point me at what's fragmented.
© 2026 Siva NathanCTO · SVP Engineering · Available now