Application file, reopened November 2026
Jorge Andrade Rodrigues
Software engineer from São Paulo. I build the tools, agents and automations that let other people ship.
This is my career so far, told through the two worlds I keep going back to: the open frontier and the loud city.
Scroll to ride into town. Move the pointer to look around. Click the sky for a shooting star.
Chapter I · Open country
Learn to ride before you pick a fight
Every long game starts the same way. You have a horse, a few tools, and a lot of map you have not seen yet.
Mine started in São Paulo, with a degree in IT Engineering at Universidade Paulista. Then I rode a long way from home and spent a year at The Hong Kong University of Science and Technology, studying software engineering and IT. Later I added a postgraduate degree in Software Engineering at Universidade Metodista de São Paulo.
The habit I kept from those years is simple. When I don't know the territory, I go and walk it.
- Degree
- IT Engineering, Universidade Paulista
- Abroad
- HKUST, Hong Kong, Dec 2018 to Dec 2019
- Postgraduate
- Software Engineering, Universidade Metodista de São Paulo
- Languages
- Portuguese, English, Spanish
Chapter II · The outfit
Find a crew worth riding with
In March 2024 I joined Fiserv, on the Developer Relations team for Clover, the payment devices you see on shop counters.
My job there is certification. Outside developers build apps for those devices, and nothing reaches a merchant until it has been tested and approved. I ride with each team through that process. I read their builds, test their payment flows and tell them plainly what has to change.
It taught me what I value most in a crew. Someone has to keep the camp running so everyone else can do the job they are good at. I like being that person.
- Joined
- March 2024
- Team
- Developer Relations, Clover
- Work
- Certifying third-party integrations
- Kit
- Android, Kotlin, APIs, Node.js
Chapter III · The city
Bigger town, bigger jobs
In August 2025 my title changed to AI Implementation Specialist. Same crew, different city.
A big operation runs on hundreds of small jobs nobody sees. I started handing those jobs to software. These are the five I am proudest of. Open any case file.
The Inside Crew Open fileClose AI agents that pre-review every app arriving through a support ticket.
- Before
- Every new app landed as a ticket, and a person read it from scratch.
- The job
- A manager agent hands each ticket to specialist agents and collects their pre-analysis into one brief.
- The rule
- The agents recommend. A human always makes the final call.
The Wire Open fileClose An MCP server that lets an AI assistant work inside our support platform.
- Before
- The assistant could not see a single ticket, so every answer started with copy and paste.
- The job
- A Model Context Protocol server with eight tools, covering two separate workspaces.
- After
- The assistant reads the real ticket history and answers from it.
The Checkpoint Open fileClose One click that checks an Android build before a person spends a minute on it.
- Before
- Each submitted build was downloaded and inspected by hand.
- The job
- A script that pulls the build, checks its manifest and its language, and sends it to a malware scan.
- After
- The reviewer starts with the results already on screen.
The Dispatcher Open fileClose Webhooks that route support events to the right team, tagged and on time.
- Before
- Someone had to notice an event and forward it.
- The job
- Support events trigger tagged messages to partner and internal inboxes on their own.
- After
- The right people hear about it without anyone copying and pasting.
The Storefront Open fileClose Native Android sample apps that show partners how it should be wired.
- Before
- Partner developers asked how order and payment calls should look, and got a description.
- The job
- Working apps in Kotlin and Jetpack Compose, including a bakery point of sale with orders and native payment.
- After
- I point at running code.
Side job · Work a shift
Do my job for one minute
Six apps want to go live on payment terminals. This is a simplified version of the review I do. Approve an app only if all four checks pass. Otherwise send it back.
Padaria do Bairro
Bakery point of sale
- Manifest
- extractNativeLibs="true"
- Malware scan
- Clean
- Payments
- Sale and refund tested
- Language
- Portuguese (Brazil)
Read the four lines, then decide.
Real tickets carry far more than four lines, and they arrive every day. My agents read all of them first and hand a person a short brief. The button stays human.
Side job · Straight answers
Ask me what you would ask anyway
I get outside developers through certification on payment devices, and I build the software that takes the repetitive parts of that work off people's plates.
Chapter IV · The next job
The one I actually want
Your recruiting system wrote to tell me my old application was about to be deleted. Fair enough. Files get old. I would rather replace it with a better one.
What makes your worlds feel alive is the part players never see: the pipelines, the build tools, the thousand checks that run before someone's work reaches the game. That is the work I do every day, on a smaller map. I would like to do it on yours.
- AI on a short rein. I build agents that do the legwork and leave the judgment to people.
- Tools that get used. Everything on this page was built for colleagues with real deadlines, then kept running.
- Range. Python, TypeScript, Node.js, Kotlin, LLM tooling and APIs, in three languages.