MTGIBBS.XYZ
I'm a problem solver, craftsman, engineering leader, and mentor.
Most of my career has been spent working through complexity and helping teams untangle it. I've modernized legacy systems, designed platforms that scale, and helped turn unclear problems into software that lasts. Along the way, I've worked across finance, application security, and data platforms, often in systems that had to be both reliable and easy to reason about.
I'm particularly drawn to product engineering and developer experience. I care about building systems and teams that make good work easier, and about demystifying technology so it feels more approachable and less fragile.
ExperienceCLASS: EXP_LOG //ADDR: 0xEX_10
Senior Software Engineering Manager
2021 - PresentData Strategy & Audit Intelligence Platforms2021 - PresentIn my current role, I’m responsible for the strategy and delivery of data analytics platforms that support inventory audits and portfolio risk analysis. The work requires balancing speed, accuracy, and trust, and building systems that customers can rely on when making real decisions. I work closely with Product and UX partners to turn loosely defined problems into clear technical direction. A large part of my focus is helping teams navigate trade-offs, establish ownership, and build solutions that are resilient and understandable over time. I care deeply about technical standards and about creating an environment where engineers can move quickly without cutting corners. Alongside the platform work, I established and continue to lead DataScan’s engineering internship program in partnership with several local universities, including Georgia Tech, Kennesaw State, and Georgia State. What began as a small effort has grown into a repeatable pipeline for developing early-career engineers, and it remains one of the most rewarding parts of my role.Software Engineering Manager
2020 - 2021Platform Modernization & Cloud Readiness2020 - 2021As a Software Engineering Manager, I led a fully remote team of full-stack engineers through a significant platform modernization effort. The goal was to make long-standing products cloud-ready while improving how customers interacted with them, all without disrupting existing workflows. Much of this work involved balancing immediate delivery needs with long-term architectural health. We introduced stronger continuous integration practices, improved developer tooling, and created safer ways to evolve the system. I spent a great deal of time supporting engineers at different stages of their careers, helping them grow while maintaining momentum on a complex and evolving codebase.Lead Software Engineer
2018 - 2020UI Engineering & Developer Experience2018 - 2020In this role, I served as the lead UI engineer, responsible for frontend architecture, tooling, and quality standards across teams. My focus was on consistency and reducing friction, particularly through better CI integration and shared patterns that made the codebase easier to work in and maintain. Equally important was the opportunity to mentor and coach peers. Teaching new frameworks, testing strategies, and engineering practices became a natural part of the job, and it’s where I developed a lasting interest in growing people alongside the software.Lead Software Engineer
2013 - 2018Fortify on Demand (SaaS Application Security)2013 - 2018At Fortify, I was a lead engineer on Fortify on Demand, an enterprise SaaS platform used to manage application security risk at scale. The platform supported tens of thousands of applications and users, which required careful attention to performance, reliability, and usability. I worked across teams to design and deliver features that helped customers understand and act on large security portfolios. I also pushed for code reuse and inner-source practices, helping teams share components and reduce duplication. During this time, I was involved in early efforts to integrate security analysis into CI pipelines and to guide open-source engagement as those approaches were still emerging.Software Engineer
2012 - 2013Master Data Management2012 - 2013Earlier in my career, I led development of a Master Data Management platform intended to consolidate and validate company-wide data. The system emphasized correctness while providing an interface that allowed users to safely understand and update records. This work supported downstream capabilities such as fraud detection and prevention, and it reinforced the importance of data quality, validation, and careful design decisions early in a system’s life.Application Developer
2009 - 2012High-Volume Policy Processing Systems2009 - 2012I began my career working on high-volume, automated policy processing systems built on a mix of Java and mainframe technologies. This included integrating with DB2, COBOL, and other legacy services, and required a strong focus on correctness and operational safety. Those early years taught me how large systems behave in production and how to change them incrementally without breaking the business. That mindset has stayed with me throughout my career.
ProjectsCLASS: PROJ_DB //ADDR: 0xPR_8
FIELD_REPORTSCLASS: FLD_REP //ADDR: 0xFI_13
While building a risk-analysis platform, I identified a core architectural challenge in our audit trail implementation. We were applying standard relational normalization to audit logs—linking records to configuration rules via Foreign Keys. While this is the standard for managing active state, it creates a "temporal conflict" in an audit system: if a rule changes today, history is effectively rewritten.
[19:12:05] INF: DATA_INTEGRITY >> VERIFIED [19:12:10] INF: PATTERN >> IMMUTABLE_PROJECTION
As our product and sales pipeline grew, our traditional quarterly release cycle hit a scaling bottleneck. The "Big Bang" approach created high-pressure delivery windows where a single certification delay could impact the entire payload. This often led to intensive "heroic" efforts during deployment weekends to ensure downstream data feeds remained synchronized.
[19:15:30] INF: DEPLOY_CADENCE >> MONTHLY_STABLE [19:15:45] INF: HOTFIX_RELIANCE >> DECREASING
I joined a greenfield project that had encountered a common modern challenge: architectural over-correction. In an effort to avoid the technical debt of our legacy monolith, the system had evolved into a highly distributed landscape of microservices and Lambdas before the core business requirements were fully anchored. While the tech was modern, the infrastructure overhead was beginning to outpace our delivery velocity for what was essentially a complex C# rules engine.
[19:20:12] INF: CI_CD_PIPELINE >> ACTIVE [19:20:25] INF: INFRASTRUCTURE_ALIGNMENT >> COMPLETED