# FVP, Clearing Technology — Axos Bank

- Location: Hq - San Diego, CA
- Posted: Nov 20, 2026
- Status: open (checked Nov 20, 2026)
- Apply (employer's site): https://axos.wd5.myworkdayjobs.com/Axos/job/HQ---San-Diego-CA/Head-of-Clearing-Development_JR5827
- Employer record: https://visajobs.io/company/axos-bank.md

## Sponsorship history
- Tier: Employer history only
- With this exact title: 0

## Description
Axos Clearing LLC Target Range:
$175,000.00 /Yr. - $210,000.00 /Yr. Actual starting pay will vary based on factors including, but not limited to, geographic location, experience, skills, specialty, and education.
Eligible for an Annual Discretionary Cash Bonus Target: 12.5%Eligible for an Annual Discretionary Restricted Stock Units Bonus Target: 12.5% These discretionary target bonuses may be awarded semi-annually based upon your achievement of performance goals and targets.
About This Job
Axos Clearing is looking for a First Vice President of Clearing Technology to lead the engineering teams behind the Clearing platform: the Clearing API (cAPI), application development, back office and data, market risk, and quality assurance. You will lead roughly 49 people, including augmented staff, within Securities Technology and report to the SVP, Securities Application Development.
You will deliver the Clearing roadmap as Axos converges its APW, AUC, AAS and Clearing platforms, including the ALF-to-Beta back-office migration, FIX connectivity, and cAPI as the integration layer between systems. Deep knowledge of capital markets and securities clearing, strategic thinking, and strong business acumen are essential.
You will also lead Clearing's move to the AI-driven development lifecycle (AIDLC), in which AI agents assist across planning, build, test, review and documentation while named humans keep approval, risk and security accountability. This is a hands-on technical leadership role: you are expected to roll up your sleeves and code where necessary.
This role is remote eligible, depending on your location.
This role is remote eligible, depending on your location. Responsibilities:
Platform and delivery leadership
Lead the Clearing API (cAPI), application development, back-office and data, market risk, and QA teams.
Deliver the Clearing technology roadmap with the SVP, Securities Application Development, aligned to the convergence of APW, AUC, AAS and Clearing.
Deliver cAPI as the integration layer between APW, ACP, AUC and Beta, including trading, market data and back-office file services, and onboarding of endpoints to the Axos APIM standards.
Lead the ALF-to-Beta back-office migration, including mutual funds and ACATS, through testing and release against DTCC-driven deadlines.
Deliver order-flow capabilities: basket and block trading performance, and FIX connectivity for trading venues and external trading partners.
Oversee Clearing's share of data modernization, including the SSIS-to-Databricks ETL and reporting migration
AI-driven development lifecycle (AIDLC)
Lead Clearing's adoption of AIDLC: an AI-native delivery model with Linear proposed as the work-management hub and future engineering system of record, replacing ADO Boards over time.
Own the entry criteria for Clearing: migrate repositories to GitHub first, then map AIDLC gates to existing SDLC, change management, segregation-of-duties, security and audit controls.
Keep humans accountable: agents do not merge, every pull request has a named human approver, and higher-risk work (securities transactions, allocations, books and records, settlement, regulatory reporting, entitlements) passes mandatory authorization gates.
Introduce spec-driven development through a governed shaping stage, so that work has clear contracts, acceptance criteria and rollback expectations before it is delegated to agents.
Select bounded pilots with measurable baselines (quality, throughput, PR aging, escaped defects, review time, cost) and manage reviewer, QA and architecture capacity so that faster code generation does not outpace verification.
Run team onboarding, enablement sessions and office hours, and define data boundaries for AI tools: no customer data in prompts or logs, approved context sources and scoped access.
Work with Cursor, GitHub Copilot and other approved runtimes while keeping the lifecycle portable across model vendors.
Hands-on engineering
Stay close to the code: write, debug and review SQL, Java and Groovy directly where it unblocks delivery, for example production issues, data validation and reconciliation, scripts and integration fixes, and review of agent-generated code.
Set the engineering standard by example, and step in on critical incidents and migrations rather than only directing others.
Software architecture and engineering fundamentals
Own the architecture of the Clearing platform, and decide when to use microservices and when a modular monolith is the better fit, weighing deployment independence, team boundaries, data ownership, latency, operational cost and failure isolation.
Set module and service boundaries and integration contracts (REST, messaging, files) for cAPI and its neighbors, and apply software design patterns where they reduce complexity, such as adapter, facade, strategy, circuit breaker, retry with backoff, idempotent consumers, outbox and saga.
Make data-structure and algorithm choices explicit, and use Big-O analysis as the common language for performance tradeoffs: time and space complexity of hot paths, caching, indexing and query plans, batching, and queue and stream throughput, always checked against measurement under realistic volumes.
Apply these tradeoffs to Clearing workloads such as order flow and basket/block trading, market-data fan-out, end-of-day processing, reconciliation and large file ingestion, where latency, throughput, correctness and recoverability all matter.
Run architecture and design reviews, record decisions and their tradeoffs, and hold agent-generated and human-written code to the same design standard.
Operations and resilienc e
Improve platform stability and resilience: containerizing cAPI services on Kubernetes, disaster recovery, and the move of monitoring to Datadog.
Own production change and release readiness with ProdOps, InfoSec and Infrastructure: change requests, patch windows, and war rooms for critical issues.
Work with the NOC and production support so that more L1 and L

> History, not a promise: past H-1B filings do not mean an employer will sponsor you or a given role. Data: U.S. DOL OFLC LCA disclosure (FY2024–FY2026 for role counts, certified LCAs) and the USCIS H-1B Employer Data Hub. Not legal advice. Methodology: https://visajobs.io/methodology
