01
ResistGate
Free, open-source Chrome extension with domain blocking, typing challenges, and temporary access.
Chrome MV3JavaScriptLocal storageMIT
Available for selected roles
Product-minded engineer with proof of work.
I build Chrome extensions, web apps, and tools that use AI where it actually helps, with Next.js, TypeScript, and Python. Open to remote roles and contract work.
Remote-first · Contract or full-time
Quick facts
- Role targets
- Full-stack Engineer, Product Engineer, AI integrations
- Best fit
- Chrome extensions, internal tools, web apps, AI features
- Stack
- Next.js, TypeScript, Python, AI APIs, Chrome Extensions
- Work style
- Remote-first, async-friendly, written updates, small steps with visible progress
- Proof
- Product pages, source code, and public case studies
Proof pack
Proof before promises.
A short scan of projects that show product judgment, technical execution, and follow-through.
02
Orlando’s AI Assistant, RAG Demo
Retrieval-based assistant built around supplied context, with a multilingual interface and streaming responses.
Next.jsCustom RAGi18n
03
Resume Q&A Chatbot
Python API designed to answer questions about my background using supplied context.
PythonFlaskGemini APIScoped context
Stack
Comfortable across frontend, backend, AI integrations, and deployment.
Frontend
Next.js / React / TypeScript / Tailwind CSS
AI integrations
OpenAI / Anthropic / Gemini APIs / chat features / document querying / retrieval-based assistants
Product surfaces
Chrome extensions / dashboards / APIs / conversion-focused pages
Delivery
GitHub / Vercel / Render / analytics events / documented final delivery
How I work remotely
Calm process, visible progress, practical communication.
Async first, not async only
I write decisions down, keep context visible, and use calls when ambiguity is blocking progress.
Small shipped increments
I prefer narrow slices with visible outcomes over large branches that hide risk for weeks.
Product judgment in the code
I care about the user path, the technical trade-off, and the maintenance cost at the same time.
Clear ownership
If I take a problem, I keep pushing until it is resolved, documented, or escalated with options.
Best fit
- Product-minded teams that need ownership, not ticket passing.
- Product and frontend roles where ownership and good judgment matter.
- Small teams with clear goals, fast feedback, and practical constraints.
- Contract or full-time roles where written communication matters.
Not a fit
- Purely maintenance-only roles with no product context.
- Teams that need only ticket execution with no ownership.
- Vague projects with no clear owner or outcome.
- Environments where speed means skipping quality entirely.
Ready for the next conversation