Proof portfolio

Proof you can open, not just claims you can read.

I'm a software developer whose strongest recent work lives across private company repositories, live products, and production client delivery. This page makes the review path explicit.

Owned code samples

Inspect the work, not just the story.

Three recruiter-safe excerpts from Synapse, an independently owned project. Company code stays private; these samples expose real testing, processing, and data-isolation decisions.

Code history in context

Private work. Public evidence. Clear ownership.

Current company work lives in a company-provided GitLab account and cannot be linked publicly. Earlier personal activity is split across GitHub and a personal GitLab profile; GitHub contains the earlier public repositories. The case studies therefore emphasize live products, sanitized artifacts, system decisions, and verification rather than a single contribution graph.

  1. 01
    Current company workPrivate, company-managed GitLab
  2. 02
    Earlier personal activitySplit across GitHub and personal GitLab profiles
  3. 03
    Primary review pathLive products, case studies, and sanitized evidence

Project evidence

Trace each claim to a surface.

Each project pairs my contribution with an inspectable path and a clear boundary around what cannot be published.

01 / Professional experience · full-stack product engineeringLive public products and working internal systems

Jakomu

Builds a multi-tenant small-business platform spanning live public sites, a guided demo showroom, AI-assisted site delivery, CRM-ready lead research, and a shared backend foundation.

My contribution

Software Engineer responsible for core Showroom brand controls, the tenant-isolated platform foundation, AI-assisted website-refresh workflows, and substantial portions of the AWS-first lead data pipeline. Source remains private because the work lives in company-managed GitLab repositories and cannot be published.

What can be checked
  • Live company site and guided Showroom for comparing complete demo directions and exploring brand fit.
  • AI-assisted website-refresh workflow with generated prototypes, visual checks, and human QA before customer delivery.
  • AWS-first lead pipeline that normalized 5,273 business records into a HubSpot-ready schema with company/domain deduplication and website enrichment.
  • Runtime architecture using one shared backend, a registry database, and isolated per-business databases to support tenant boundaries without duplicating infrastructure.
Evidence pathProfessional product-engineering experience across live public surfaces, internal tools, tenant-aware backend design, and launch gates.
  • Live Jakomu site and Showroom
  • Lead-generation workspace screenshot
  • Services/process screenshot
  • Multi-tenant system diagram
  • Launch-readiness and compliance receipts

Private company source, private lead/contact data, credentials, and unredacted operating docs stay out of the public portfolio.

02 / Owned product · technical deep diveUnder development · deterministic NASA demo

Digital Library / Synapse

A media research workspace that turns official NASA captions into searchable, timestamped evidence with deterministic source links, representative visual notes, and reviewer workflows.

My contribution

Owned product architecture, Next.js app surfaces, typed demo data, playback-sync helpers, NASA ingest tests, and the worker-result contract/importer.

What can be checked
  • NASA demo workspace with transcript chunks, evidence cards, source details, and playback sync.
  • Reviewer tool for approving, correcting, or sending back topic links and visual evidence notes.
  • Typed Python worker-result contract and importer boundary for structured processing output.
  • Vitest and Python tests covering demo data, playback sync, NASA ingest, and learning-link import behavior.
Evidence pathOwned product thinking: media evidence workspace, review workflows designed for future AI-assisted output, typed demo data, and worker-output contracts.
  • NASA media workspace screenshot
  • Reviewer console screenshot
  • Processing pipeline diagram
  • Vitest and Python test receipts

Private user libraries, credentials, raw uploads, and any future customer media are not public proof material.

03 / Production real-estate productIn production with guarded MLS PIN snapshot publishing

Move With Musto

A production real-estate website for Mai Ly Musto combining buyer and seller journeys, a periodically refreshed MLS PIN-derived property search, responsive list/gallery/map experiences, and compliance-aware publishing controls.

My contribution

End-to-end Next.js implementation, information architecture, responsive design, property search UX, MLS data workflow, compliance checks, and browser/e2e verification.

What can be checked
  • Production route set spanning home, about, buy, sell, neighborhoods, guides, properties, contact, privacy, terms, and unsubscribe.
  • Property search with filters, list/gallery/map modes, save/compare/contact actions, URL-restorable state, and on-demand listing details.
  • Reviewed MLS PIN snapshots feed a compact public search index while raw exports, review reports, quarantine records, compliance configuration, and geocode caches remain private.
  • Live-build and runtime freshness checks prevent stale or invalid snapshots from being presented as current inventory.
  • Brand rule checks for real-estate marks and affiliation language.
Evidence pathProduction client delivery: real-estate UX, MLS snapshot publishing, brand guardrails, and substantial property search.
  • Live production property-search route
  • Homepage/brand screenshot
  • MLS publishing workflow diagram
  • Brand, legal, and browser-test receipts

Raw MLS exports, review reports, quarantine files, compliance configuration, private cache files, and agent-only material stay private.

Source boundaries

Public enough to inspect. Private where it should be.

01

Public to show

Screenshots, portfolio case studies, local demos, public-facing pages, and sanitized architecture notes.

  • Portfolio pages
  • Screenshots
  • Browser demos
  • Architecture diagrams
02

Private by design

Company/client source, raw MLS files, private lead data, credentials, and unredacted business material stay out of the portfolio.

  • Shared company code
  • Raw MLS exports
  • Lead/contact data
  • Secrets and client records
03

Walkthrough-ready

When a repo cannot be public, the site still gives an interviewer a clear path through the decisions, evidence, and verification.

  • System diagrams
  • Receipts
  • Test/build commands
  • Honest launch status

Available now

Need a developer who can move from interface to system?

Actively interviewing for full-time software development roles.

Email RenaldoDownload résumé