Skip to content
Skip to content

Senior Software Engineer AI Enablement & Technical Delivery

Brandon A. Calderon Morales

I make complicated engineering work easier to run.

I work where AI-assisted delivery, application security, automation, and documentation meet. The job is to turn cross-team work into documented, reviewable systems that engineers can operate and improve.

Scope over labels

Ownership at the seams.

My title is senior software engineer. The work is platform-shaped: I own the connective systems around security remediation, AI-assisted delivery, documentation, and release governance.

From a backlog to a repeatable operating model.

At Fiserv, I am the technical delivery owner for AI-enabled vulnerability remediation across 20+ engineering teams. During one two-week effort, I helped reduce a third-party-identified security backlog from about 4,000 findings to about 200 remaining.

The meaningful part was not a single script. It was building a shared path from intake and triage through assignment, remediation, pull-request review, and deployment, while keeping engineers responsible for the decisions.

Intake / Triage / Assignment / Remediation / Review / Deployment

20+
engineering teams
About 4,000 to about 200
security findings
Two weeks
coordinated execution

The boundary matters

Coding agents handle repeatable work. Engineers retain judgment through a Driver/Reviewer model, approval gates, audit logs, security checks, versioned workflows, and rollback plans.

What the work looks like

The systems behind the outcome.

I tend to work on the connective tissue teams feel immediately when it is missing.

01

Secure agentic delivery

Design repeatable coding-agent workflows with approved inputs, versioned prompts and tools, human review, observable handoffs, and rollback plans.

02

Vulnerability remediation

Correlate signals across security platforms, reduce duplicate noise, establish priorities, and make ownership unambiguous.

03

Delivery infrastructure

Standardize GitHub Actions, CI/CD, secrets, service accounts, and release governance so automation has a dependable path to production.

04

Documentation as infrastructure

Treat documentation as a maintained system: versioned, tested, deployed, and useful during onboarding, triage, and change.

Built in the open

Public projects are where I test the ideas.

Docs as code / Retrieval / Cloud delivery

My Life as a Dev

This site is both a portfolio and an experiment in documentation as maintained infrastructure. The broader project has also been a test bed for retrieval-backed research over project history and engineering notes.

View the project source

The engine is incidental. The point is documentation that can be reviewed, tested, deployed, and used by people and tools.

The path here

Precision came before software.

Before engineering, I served in the United States Marine Corps as a Legal Chief and Court Reporter. Precision, confidentiality, and operational readiness were part of the job.

That experience still shapes the systems I build. Ownership should be visible. Decisions should be traceable. Automation should be reviewable. The next person should have enough context to act.

Make the next step obvious, then make the handoff dependable.

  1. 2024 to present

    Fiserv

    AI enablement, secure remediation, CI/CD standardization, and cross-team technical delivery.

  2. 2023

    Insight Global / SAIC

    High-security .NET services and change-controlled enterprise releases.

  3. 2021 to 2023

    Leidos

    React decision systems and reusable Jenkins pipelines for mission software.

  4. 2014 to 2019

    United States Marine Corps

    Legal Chief and Court Reporter.

Education in progress B.S. in Multidisciplinary Studies with a Computer Science concentration, University of Nebraska at Omaha. Expected May 2027.

You can find me here.

Code, project notes, and the most direct way to reach me.