Web Development Director
Remote from Mexico, working with US-based companies. I lead the teams that ship web systems — and I still own the architecture, the delivery process, and the parts that break at 2am.
Made in Mexico
I'm Oscar, a web development director based in Mexico with years of experience working remotely for US-based companies. My profile is rare because I sit at the intersection of engineering, systems thinking, design, and leadership.
I don't just write code — I build maintainable systems that scale. I think in workflows, failure points, and automation opportunities. When something breaks, I don't just fix it; I prevent it from breaking again.
const developer = {
name: "Oscar Flores",
location: "Mexico",
role: "Web Development Director",
focus: [
"Systems Architecture",
"WordPress Ecosystems",
"Team Leadership",
"Process Automation"
],
mindset: "Build once, scale forever"
};
// ownership mindsetThe commercial core: the platforms, the pipelines, and the people who ship them.
Where the work actually flows, and where it stalls.
What breaks first, and what it takes down with it.
Anything done twice by hand is a defect waiting to happen.
The next person inherits my decisions. Usually that's me.
Where the systems thinking gets stress-tested. Game code punishes bad architecture faster than anything on the web — state desyncs, exploits, and frame budgets don't negotiate.
REC · currently building
├── Server
│ ├── DataManager
│ ├── EconomyController
│ ├── ValidationService
│ └── WorldGenerator
│
├── Client
│ ├── UIController
│ ├── InputHandler
│ ├── LocalEffects
│ └── OnboardingFlow
│
└── Shared
├── Types
├── Constants
└── Utils
The same separation I'd defend in a web codebase. Authority on the server, presentation on the client, contracts in the middle.
C# gameplay systems built modular from the start — composition over inheritance, data-driven config, and the discipline to keep gameplay logic out of MonoBehaviours.
Recompiling and porting graphics paths to Metal on Apple silicon. The hard part isn't the syntax — it's that Metal's explicit command encoders and argument buffers don't map cleanly onto APIs that assumed a mutable global state machine.
The client is a renderer, not a source of truth. Every economy-affecting action gets validated server-side, because anything else is an exploit with a countdown on it.
Save schemas that survive their own migrations, and sinks that hold up when players find the loop you didn't intend. Modelled in Lua on Roblox first; the lessons carried.
Structure isn't bureaucracy. It's what lets a team move fast without stepping on each other.
The details are the product. Everything else is a description of the product.
A good process makes the right thing the easy thing. A bad one gets routed around.
Slightly. Shipped and maintainable beats perfect and theoretical.
If it only lives in my head, I've built a dependency on me. That's not leadership.
A selection of projects that showcase my approach to building systems. Focus is on architecture decisions and real impact.
Built and maintained a network of 20+ WordPress sites with shared components, centralized updates, and integrated marketing stack.
Details available upon request
End-to-end lead capture and routing: forms to CRM to call tracking, with the reporting layer that tells you which of it actually worked.
Details available upon request
A persistent world built the way I'd build a production service: server-authoritative, data-driven, and instrumented from day one.
Not yet public
Currency, sinks, and progression modelled as one system, with the validation layer that assumes every client is lying.
Not yet public
More detailed case studies and code samples available upon request.
Whether you need someone to lead a web team, architect a WordPress ecosystem, or think in processes and scalability — I'm available for remote opportunities with US-based companies.