SERGRDZSERGIO RODRIGUEZ

PUBLIC WORK

Choose something to inspect.

Cutline ↗

Reverse engineering

Ghidra output, C source, native builds, and inputs that expose a buffer boundary.

Afterimage ↗

Regression analysis

An independent replay of a published urllib3 redirect flaw, with the upstream discovery credited.

Countersign ↗

Authorization design

Signed call grants, one-use nonces, and tests for changed call arguments.

Prooflane ↗

Research tooling

Recorded sessions, offline transforms, and an archived CTF solve.

Support intake ↗

Technology operations

A help desk demonstration built around sample requests and receipt checks.

Today ↗

Interface design

A browser planner with saved tasks, time budgets, and a JSON export.

Download the project catalog ↓

BEHIND THE PROJECTS

One place to plan
the next step.

My local dashboard connects project evidence with study plans and career preparation. A task keeps its source and the date I checked it, so an old portal snapshot doesn’t become current just because I rebuilt the site.

A project can link to a résumé task or interview preparation. School records, applications, and submissions stay in the private workflow.

The public export contains project names, links, summaries, and skills. It excludes academic records and private task details. These are independent projects.

INTERNSHIPS & COLLABORATION

Let’s talk about the work.

I’m interested in Python automation, technical support, technology operations, and security research. If your team has a role in one of those areas, send the role and a little context. I can walk through the code and the decisions behind it.