Domain understanding
I study the operational context before translating requirements into data models, APIs and interfaces.
AGRONOMY · BACKEND · DATA
Agronomy undergraduate at UFV
I connect field knowledge with software engineering to build APIs, data-processing workflows and experimental AgTech systems using Python, SQL, FastAPI and PostgreSQL.
01 · ABOUT
My strongest advantage is not claiming to know every technology. It is combining an agricultural background with growing backend and data skills.
I am a final-year Agronomy undergraduate at the Federal University of Viçosa and an early-career developer focused on backend systems and data.
My background helps me understand field operations, business rules and the contexts in which operational data is generated. I use that perspective to develop projects involving APIs, databases, automation, telemetry and data validation.
My primary stack includes Python, SQL, FastAPI and PostgreSQL. I also use Docker, Git, automated tests and continuous integration to make projects easier to reproduce and maintain.
One of my main initiatives is AgriSentry, an experimental portfolio ecosystem created to explore agricultural telemetry ingestion, asynchronous processing and data-quality rules. It is a learning and engineering project—not a production platform.
I am seeking an internship or junior opportunity where I can contribute to real projects, participate in code reviews and continue building solid technical foundations with an experienced team.
I study the operational context before translating requirements into data models, APIs and interfaces.
Projects are described according to what is implemented, tested and documented—not according to what sounds more senior.
I treat each project as a place to strengthen code quality, testing, data reliability and technical communication.
02 · EXPERIENCE
My professional experience began in agronomy. Software and data became tools for understanding processes and reducing repetitive work.
Scope note: the prediction application was an experimental prototype, not a production decision-making system.
03 · PROJECTS
The cards distinguish between implemented features, experiments and areas still under validation.
Experimental Rust service for receiving, validating and persisting agricultural telemetry through MQTT and HTTP.
Backend service for processing telemetry and applying configurable data-quality and anomaly-detection rules.
Reactive interface for exploring device status, telemetry records and operational monitoring workflows.
Data-analysis prototype created to explore poultry-weight forecasting, data cleaning and model evaluation workflows.
Tool developed during academic event operations to generate digital certificates from spreadsheet records.
Experimental static scanner that explores entropy and pattern-based detection for credentials and sensitive strings in source files.
04 · TECHNICAL TOOLBOX
Exposure, project application and core skills are intentionally separated.
05 · AGRIDEV
AgriDev is the idea guiding my professional direction: combining agronomic knowledge with backend development and data engineering to work on problems involving traceability, telemetry, operational records and decision support.
I do not treat agriculture as a decorative niche. It is the domain in which I learned to observe variability, document processes and understand that unreliable data can lead to unreliable decisions.
Read Professional IntroductionUnderstand the process, constraints and users before designing the system.
Validate, document and trace data before turning it into indicators or predictions.
Use tests, clear interfaces and technical documentation to reduce avoidable uncertainty.
LET’S WORK TOGETHER
I am interested in backend development, data analysis, data engineering and technology applied to agriculture.