Senior Director, Software Development — Oracle
I lead the globally distributed engineering organization behind Oracle Fusion GRC / Risk Cloud — a platform I helped architect from its earliest stages, now the compliance backbone for Fortune 500 companies. My current work: shipping agentic AI into regulated environments, responsibly.
I'm a senior engineering leader who grew from software engineer to Senior Director at Oracle, leading globally distributed teams. I helped architect Oracle Fusion GRC / Risk Cloud from its earliest stages into the enterprise compliance platform it is today, used by Fortune 500 customers worldwide.
My current focus is at the intersection of AI and enterprise software. I designed and shipped an agentic AI security-assessment application for Oracle Fusion, built on AI Agent Studio — it reconstructs every identity's inherited access paths, evaluates them against segregation-of-duties and sensitive-access policies, and delivers risk reporting with approval-gated remediation. I'm also defining Oracle's AI strategy and governance for our GRC platform: agent boundaries, audit trails, and alignment with emerging AI regulations.
I'm passionate about bridging enterprise-grade software capabilities with real-world business needs. Outside of Oracle, I build AI-powered workflows and automation systems as personal projects — voice agents, content pipelines, lead generation systems — because I believe the best way to understand where this technology is going is to keep building with it.
I lead a globally distributed organization of roughly 20 engineers across multiple teams, owning the full lifecycle of a compliance platform Fortune 500 companies run their audits on. This is how I run it.
I care personally and I challenge directly. Feedback arrives early, while it's still cheap to act on, and it runs in both directions — the people on my team are expected to tell me when I'm wrong, and nothing bad happens when they do. Trust is built by being useful, not by being agreeable.
Ownership, curiosity, and a bias for action. Ownership means carrying a problem past the edge of your own component. Curiosity means going and reading the incident, the code, the regulation. Bias for action means shipping a reversible decision this week instead of a perfect one next quarter.
Across time zones, decisions have to survive without me in the room. That means written acceptance criteria, one accountable owner per workstream, and roadmaps visible before they're committed. When priorities collide I'd rather cut scope in the open than let a team quietly miss.
I've served as a key interviewer for engineering hires across the broader organization and helped shape the bar we hire against, so I treat team composition as a design problem rather than a headcount problem. The same lens applies internally: I'd rather grow a senior engineer into a lead than backfill the role from outside, and I plan for that well ahead of needing it.
I mentor early-career programmers, and the advice hasn't changed now that AI writes a great deal of the code. Nobody was ever paid for lines of code. You're paid to turn an unclear requirement into a working system, and to be the person accountable when it breaks in production. That's the skill I coach for, because it's the one that compounds.
AI changes how the work gets done. It doesn't change why the job exists.
Lead the globally distributed engineering organization for Oracle Fusion GRC / Risk Cloud. Shipped an agentic AI security-assessment application built on AI Agent Studio. Led the monolith-to-Kubernetes migration that cut infrastructure costs ~90%. Define Oracle's AI governance strategy for regulated environments.
Managed teams of up to 10 engineers across Fusion HCM and On-Premise GRC — parallel workstreams, different stacks, one delivery standard. Established code quality and profiling practices that improved application throughput by 80%.
Designed a business performance engine using web ontologies; created domain models and UML specifications for core GRC platform components — work that seeded several of 12 U.S. patents.
Built compliance-violation monitoring for EBS/PSFT user responsibilities — early foundational work in what became Oracle GRC.
Flagship — shipped 2026
It ingests an enterprise's full account population, reconstructs each identity's inherited access paths, evaluates them against segregation-of-duties and sensitive-access policies, and delivers audience-tiered risk reporting with approval-gated remediation — AI with real responsibility, held to audit standards.
Built from the ground up for Oracle Fusion HCM.
Concept to production delivery, end to end.
Reputation management at enterprise scale.
I write regularly on LinkedIn about AI architecture, enterprise engineering, and where software development is heading. A few recurring themes, and the posts behind them:
I argue for treating AI agents as untrusted actors rather than trusted infrastructure. The controls that matter — tool allow-lists, data boundary rules, human checkpoints, kill switches — only work when they're enforced outside the agent's own process. Guardrails an agent can talk itself out of aren't guardrails.
I think the engineers who thrive won't be the best coders — they'll be the best managers of AI agents. Directing an agent and growing a junior developer need the same things: clear acceptance criteria, real code review, honest task decomposition. The dividing line forming isn't technical versus non-technical. It's delegators versus non-delegators.
Hands-on lessons from building multi-agent architectures: prefer specialized agents over monolithic ones, reserve the model for work that genuinely requires understanding, and let deterministic code handle everything else. The AI is roughly 20% of the build — architecture, data flow, error handling, and testing are the other 80%.
I publish research-backed deep dives on retrieval-augmented generation, citing Stanford HAI and Google DeepMind, and I make the case for hybrid retrieval — BM25 plus dense — re-ranking, and plain honesty about what RAG can and cannot do.
More on LinkedIn.
Nexus by Yuval Noah Harari
When I'm not building software, you'll probably find me on the water. I'm an ASA-certified sailor — keelboat through bareboat charter, monohull and catamaran — and a few days of coastal cruising with no signal is still the best reset I've found.
I picked up pickleball a couple of years ago after a long run with soccer and got hooked almost immediately.
Chess has been a constant for years — there's something about it that never gets old.
Common questions from recruiters and hiring managers.
I'm based in Irvine, California, and not looking to relocate. That said, I'm open to hybrid roles in the greater Los Angeles or San Diego areas.
I'm focused on engineering leadership positions — Senior Director, Head of Engineering, or VP of Engineering — where I can drive AI strategy and lead high-impact teams. I'm specifically looking for companies where AI is central to the product strategy, not a bolt-on.
No — I'm only considering full-time opportunities.
I have deep expertise in GRC, compliance, and enterprise SaaS — but I'm open to any domain where there's a serious engineering leadership challenge and a meaningful AI opportunity. The quality of the team and the ambition of the product matter more than the vertical.
I treat AI agents as untrusted actors, not trusted infrastructure — the same Zero-Trust principles that apply to network security apply to AI systems. That means least-privilege access, hard boundaries, behavioral monitoring, human checkpoints on high-stakes decisions, and well-defined kill switches. I've applied this framework at Oracle for GRC use cases and write about it regularly.
I currently lead approximately 20 engineers organized across multiple teams in a globally distributed setup. Prior to that I managed teams of up to 10 engineers running parallel workstreams with different deadlines and technology stacks.
An AI assistant trained on my full background answers in seconds — leadership style, how I run teams, what I'd build in your context. Recruiters can leave a message right in the chat, or reach me on LinkedIn.