SERGRDZSERGIO RODRIGUEZ

SERGIO RODRIGUEZ / IONA UNIVERSITY

Useful tools.
Clearer systems.

I build Python tools, work through technical problems, and make the results easy to inspect. I’m an undergraduate looking for a paid internship in IT support, technology operations, or automation.

For hiring teams Explore my work

Hudson Valley, New York Let’s discuss your team’s schedule.

Sergio Rodriguez
LEARN. BUILD. EXPLAIN.Good work should
be easy to check.Read the project brief

START WITH YOUR TEAM

Three ways
into the work.

01IT support & operations

Clear request status, useful next steps, and a handoff someone can follow.

Start with Support Intake 02Python & automation

Explicit inputs, repeatable tests, and checks that explain their decisions.

Start with Countersign 03Security & analysis

Read the source, compare behavior, and describe what the evidence shows.

Start with Cutline

SELECTED WORK / SOURCE INCLUDED

From a question
to something checkable.

Each project connects a concrete problem to an implementation, a way to inspect it, and what the result establishes.

01 / WORKFLOW DESIGN

Support Intake

Is the request actually resolved?

A help-desk workflow should make it clear what is known, what changed, and what still needs attention. This browser demo works through those decisions with synthetic requests.

JavaScriptHTML / CSSDecision logic
My work
An interactive request queue that checks source freshness, approval claims, and matching resolution records.
What to inspect
Change a scenario and follow the next action. Compare an attempted fix with a completion record that belongs to the request.
Scope
Invented requests and local demo state. A workflow demonstration, with no connection to a real help desk.
Try the workflow How it relates to the role

02 / PYTHON & TESTING

Countersign

What did the approval cover?

A tool name alone doesn’t describe an approved action. I built a Python experiment that checks the proposed call against the caller, target, arguments, and time window in a signed approval.

PythonSQLiteAutomated tests
My work
A request verifier, a replay ledger, and controlled cases for changed requests, expired approvals, and concurrent attempts.
What to inspect
The decision reasons, the source, and a standard-library test suite that can be run independently.
Scope
A local authorization experiment. It returns a decision and does not execute the proposed action.
Explore the experiment Source & tests

03 / REVERSE ENGINEERING

Cutline

Does the recovered code tell the whole story?

I wrote small C fixtures, compiled two versions, and compared Ghidra’s recovered code with native tests. Boundary inputs make the difference between an inferred type and a source contract visible.

CGhidraPython
Cutline showing recovered C code, Ghidra control flow, and instruction bytes

Original, inert fixtures. The recorded results cover the tested inputs; the browser view uses an arithmetic model.

Inspect the analysis Source & reproduction

Want a wider view? The project explorer includes patch studies, a task planner, and more technical experiments.

Open the project explorer

HOW I APPROACH A PROBLEM

Make the next step
easier to understand.

The same habits connect my technical projects and my interest in support work.

  1. 01

    Establish what’s happening.

    Separate the reported symptom from the available evidence. Identify missing context before assuming a cause.

  2. 02

    Make it repeatable.

    Reduce the problem to a small example, a clear input, or a sequence another person can follow.

  3. 03

    Check the change.

    Compare the result with the expected behavior and test the boundary cases that could change the answer.

  4. 04

    Leave a useful record.

    Explain the result, its limits, and the next action in plain language.

KEEP EXPLORING

The work behind the work.

Browse the research archive
SWIFT / APP MAINTENANCE

Clear status. Less guesswork.

A community-fork case study in signing dates, backup errors, and checkable status decisions.

DEBUGGING / PYTHON

Three bugs worth writing down.

Small examples of how assumptions become software behavior.

LEARNING / PROJECTS

Study connected to practice.

The skills I’m developing and the public work that puts them to use.

THE PERSON BEHIND THE PROJECTS

Curious.
Patient.
Still learning.

I’m Sergio, an Iona University undergraduate in the Hudson Valley. I’m interested in how systems work and how to help people use them more confidently.

My independent projects give me a place to practice Python, software testing, and technical investigation. I’m looking for a team where I can learn through useful, hands-on work.

Outside technology, I play the Great Highland Bagpipe and study Galilean Aramaic. Both reward careful listening and steady practice.

Music Aramaic Independent work

PAID INTERNSHIPS / LET’S TALK

Where could this
be useful?

IT support, technology operations, or Python automation. Share the role, location, and expected dates, and we can discuss the fit.

Project briefRequest résuméLinkedInGitHub