30 years in technology.
18 in fintech.
Systems architecture, enterprise assurance, and applied AI, grounded in hands-on integration and IT leadership. I connect records, ownership, and dependencies so teams can see what needs action and leaders can understand what is holding work up.
Operating experience. Engineering judgment.
My career spans data and telephony systems, IT leadership in insurance, and long-running assurance work in payments. I have operated the systems, worked with the teams accountable for them, and built mechanisms to make evidence and decisions easier to follow.
That combination matters when a problem crosses a technical boundary: an unclear control owner, a reviewer dependency, a disconnected record, or an application that needs the right operating model around it.
Senior Security Compliance Analyst
Bettendorf, Iowa · Remote. Joined TriSource Solutions in March 2008 and continued through its acquisition by REPAY in 2019.
Governance, risk, and compliance work across 13 business units and five shared-service functions. Coordinated 12 audit engagements in 2025, working with approximately 70 control owners.
- Connect program status to the work. Built a normalized Hyperproof compliance view from portfolio status to requests, evidence, owners, and their sources. Submission and acceptance remain separate so an owner’s next action is distinguishable from a reviewer’s queue.
- Build the integration and analysis path. Connected Hyperproof and Snowflake data with APIs; developed Arctic semantic retrieval and natural-language workload/evidence workflows with source-linked answers and control-intent review leads.
- Keep review accountable. Built an AWS Bedrock/Claude workbench for evidence and requirement context. AI-assisted flags support investigation; people review the source and make assessment decisions.
- Resolve gaps with the right owners. Identify internal control and evidence gaps before external audits, then coordinate risk tickets and remediation with engineering owners, reviewers, and security leadership.
- Review the deliverable. Review and correct Reports on Compliance (ROCs) and Attestations of Compliance (AOCs) with security leadership and auditors, connecting the report narrative to scope, system behavior, and supporting evidence.
- Make handoffs repeatable. Develop evidence workflows, scoped approvals, status reporting, and owner/reviewer coordination across products and shared services.
Director of Information Technology
Led the internal IT team and vendors supporting an insurance brokerage, connecting daily operations with the firm’s technology priorities.
- Supported agency-management workflows for client and policy records, renewals, commissions, electronic files, and carrier connections.
- Managed servers, networks, workstations, applications, access, security, backups, and business continuity.
- Used Citrix remote access, scripts, reports, and integrations to support staff and connect business workflows.
- Worked with leadership on priorities and budgets, purchasing, contracts, and vendor relationships.
From data analytics to IT leadership.
Data Analytics Specialist → Information Technology Specialist → Director of Information Technology. Responsibilities expanded through successive acquisitions, from lead data and application integration to telephony infrastructure and IT operations.
- Completed a 100-seat predictive-dialing implementation using nine fractional T1 circuits, six dual-channel Dialogic cards, Informix, and SCO Unix.
- Scripted Dun & Bradstreet lead-data processing and linked incoming-call identification (ANI) to customer-record screen pops.
- Evaluated IGA and Nobel dialer vendors in Atlanta and worked with Nobel to develop telephony integration after the initial system underperformed.
- Configured customer-service and sales call-routing vectors on a Lucent G3R PBX to support the March 2002 Red Hat Advanced Server 2.1 launch.
- Coordinated T1/ISDN providers and hands-on wiring, PCs, and punch-down connections as part of operating the full system.
Mechanisms you can explore.
I use AI-assisted development while remaining responsible for the architecture, validation, and review decisions.
Assurance Navigator
The public example shows how evidence status, ownership, and reviewer dependencies become an inspectable next step. It uses 805 synthetic requests; the fictional records illustrate the mechanism separately from private integration work.
Inspect the synthetic demo ↗ · Read the implementation approach ↗
Applied AI workbench
My Bedrock/Claude workbench brings evidence and requirement context into review. It is separate from the synthetic Navigator demo and the separate Claude Code evidence review.
Axiom / completed migration, continuing research
I built retained memory and weighted context outside a single AI service. After losing the original connection, I completed re-embedding with Arctic, connected a fresh Claude instance, and tested that memory retrieval and weighting worked in the replacement setup. This supports a practical recovery and handoff approach for context that would otherwise depend on one conversation.
Read the migration account and inspect Axiom ↗ · See tooling and experience distinctions ↗
Navigating People.
Navigating Complexity.
I’m curious, conversational, and direct. I ask questions, think out loud, and appreciate people who bring a different view. I take the work seriously and enjoy a laugh with the people doing it.
I work across engineering, business functions, and executive leadership. I adapt how I communicate, give others room to contribute, recognize their work, and keep the focus on solving the problem. If there’s something I’ve missed, I want to hear it.