Skip to content

Hello there!

About me, Josue

I'm Josue, based in Alajuela, Costa Rica. I design end-to-end systems where AI, cloud, data, and product constraints meet, so delivery stays predictable and teams aren't stuck babysitting brittle glue code.

My background blends hands-on development with a curiosity for design and communication: I enjoy translating fuzzy requirements into concrete increments of value, whether that's a migration plan, a contract-tested service, or a dashboard that actually gets used.

I'm a hands-on developer, I like rolling my sleevs up, sit down laser fouces and get this done. I'm a quick learner and I'm always looking for new challenges and opportunities to grow.

JavaScript and TypeScript power much of what I build on the web, while C# and .NET remain close collaborators when integrating with enterprise stacks.

Outside strict engineering work, I gravitate toward exploration, new tools, new domains, and ways of helping teams learn faster. That wanderlust shows up as relentless tinkering: spikes, proof-of-concepts, and internal docs that turn experiments into shared habits.

I actively participate in internal training sessions, providing lunch and learn sessions to the team, developing internal tools, CLIs and other tools that help the team work faster and smarter.

That's why I consider myself a problem solver. I love to solve problems, find cost effective solutions and deliver value, at the end that's what it's all about. We engineers are here to help the business and others succeed.

Today I operate as Principal Solutions Architect · Full-stack Engineer · AWS Certified partnering with product and platform peers to raise the bar on reliability, security, and pace, without lowering the standard for craftsmanship.

On the AI side, I go beyond wiring up an LLM: context, orchestration, and retrieval so outcomes are reliable and explainable, Vertex AI, Gemini, Azure OpenAI, and whatever fits the business, not the hype cycle.

Architecturally, I stay provider-agnostic across GCP, Azure, and AWS, thinking in components like Cloud Run, Pub/Sub, and Service Bus, plus secure networking patterns, always with lock-in and operability in view.

With stakeholders, I translate ambiguity into a small set of credible options, reusable frameworks and decision engines where they help, so pre-sales and solution design feel repeatable, not improvised every time.

architecture_flow

The mental model I apply end to end, from clarifying the product to shipping something measurable and safe in production.

Eight-step flow. Each stage follows the last: product framing, tradeoffs, design, tooling, economics, safety, humans and agents, then measurement, expand in sequence or jump to a step if you already know the context.

Recognition:

HatchWorks Hatchy Award

Related wiki notes

Search articles that expand on tools, patterns, and delivery, without leaving this page.

[ wiki // ]

Higher-order functions, composition, currying, pure functions, immutability, and avoiding shared state in JavaScript.
javascriptfunctional-programmingfpreact

[ wiki // ]

Interfaces as contracts, polymorphism, extensibility, testing, and why the extra files are worth it.
oopinterfacescsharpsolid

[ wiki // ]

A walk through Redux fundamentals: store, actions, reducers, middlewares, slices, combining reducers, and subscriptions.
reduxjavascriptreactstate-management

[ wiki // ]

Here's what I think about it, the role isn't disappearing. It's being forced to evolve faster to catch up with what organizations can process and offer in wild and AI-Hyped marketplace.
architectureaiengineering