About
I build and modernise operational software for corporate intelligence and fraud prevention. I got here through human resources and an English classroom, which matters more than it may sound.
I grew up around computers, largely because my father was a web designer and journalist. I was always drawn to games and PCs, but it took time to see software as work rather than only a hobby.
I taught English for two years, then spent six years in human resources at an American automotive multinational. I started as an intern and became a personnel administration analyst, working with payroll, time-and-attendance systems, onboarding, offboarding, and management reporting.
The part of that job I enjoyed most was building reports. I spent years cross-referencing data in Excel, understanding what a number meant, and presenting it so someone else could act on it. In 2020 I began studying Python and JavaScript in the evenings with the specific goal of changing careers.
I joined ODEEN in January 2022 as a junior frontend developer. I progressed to frontend developer and then to full stack developer, working with React and Next.js on the interface and Node.js, Express, and MySQL behind it. I completed a degree in Systems Analysis and Development while working full-time.
The HR years are the least obvious part of my CV and the part I would defend hardest. Six years of payroll teaches you that some mistakes are not recoverable, that the person facing a bad interface is having a worse day than its developer, and that documentation only works when it is easy to use. I build operator tools now. It is the same responsibility with different inputs.
How I work
I care about conventions more than most people find reasonable. On my current team I helped move linting from ESLint to Biome, standardised pnpm, and introduced release-based branching plus naming and documentation rules. These changes were not assigned to me, and they were adopted after discussion with the team.
I like being involved when technical decisions are made, making alternatives and costs explicit, and then supporting the decision the team takes.
I use AI tooling heavily and I am direct about it. It has changed how much I can take on, but I still treat the output as something I am responsible for understanding and reviewing.
English has been part of my professional life since before software: I taught it for two years, used it with a US organisation in the automotive industry, and earned an EF SET C2 certificate in reading and listening.
Skills
Grouped by how deeply I actually use them, not by how many I can name.
- Working daily
- TypeScriptJavaScriptReactNext.jsNode.jsExpressMySQLSQLREST APIsTailwind CSSGit
- Used in production
- WebSocketZustandReact QueryComponent librariesFeature-based architectureBiomepnpmAgile / ScrumJira
- Platform context
- Google Cloud PlatformCI/CDJWT / OAuthRole-based access controlLGPD
Platform context means exactly that: the systems I work on use these technologies and controls, but infrastructure, delivery pipelines, and authentication are owned by other people on the team.
Resume
Let’s take a good
idea out of the backlog.
Open to remote roles. C2 English, UTC−3, and happy to talk about product, code and everything in between.