I build software to turn real problems into reliable, maintainable products — from APIs and web applications to process automation and offline-first experiences.
I'm Kauan Kelvin, a Software Engineering student focused on Back-End Development, Java, Spring Boot, Python and automation.
I enjoy projects where engineering decisions matter: understanding the business flow, modeling the domain, designing APIs, protecting data, handling failures, automating repetitive work and validating that the solution actually solves the original problem.
Problem → Domain → Architecture → Implementation → Tests → Delivery → Improvement
- 🎓 Software Engineering student
- ☕ Main back-end stack: Java + Spring Boot
- 🤖 Automation/RPA with Python + Selenium
- ⚛️ Full-stack projects with React + TypeScript
- 🧪 Interested in testing, architecture, security, CI/CD and observability
- 🌍 Open-source contributor
- 🇧🇷 Based in Brazil
| Area | Stack / practices |
|---|---|
| Back-End | Java, Spring Boot, Spring Security, Spring Data JPA, REST APIs, Node.js, Express |
| Automation | Python, Selenium, OpenPyXL, batch processing, logging |
| Front-End | React, TypeScript, JavaScript, Next.js, Vite, Tailwind CSS |
| Data | PostgreSQL, MySQL, Firebase, Firestore |
| Quality | JUnit, Vitest, Testing Library, validation, linting |
| DevOps | Docker, GitHub Actions, Linux, Vercel, CI/CD |
| Engineering | Clean Architecture, Design Patterns, modularization, monorepos, API design |
These are the projects that best represent how I currently think about software engineering.
🪶 Leve
Personal agenda designed around data reliability, synchronization and offline usage.
The architecture was built around one principle: user data should not silently disappear or be overwritten.
Engineering highlights:
- React 19 + TypeScript + Vite
- Firebase Authentication + Firestore
- Express API as the only write path
- Shared Zod domain schemas
- Optimistic concurrency with expected revisions
- Idempotent commands
- Offline outbox and synchronization
- Explicit conflict handling instead of silent last-write-wins
- Installable PWA and per-device notifications
- Versioned import/export
- Free-tier-conscious architecture
A product project where reliability, conflict resolution and failure scenarios were treated as first-class requirements.
RPA project built to automate a real dental billing workflow.
The automation reads operational data, navigates insurer portals, validates guides, fills forms, matches attachments, uploads documents and produces execution logs.
| Indicator | Before | After |
|---|---|---|
| Time per guide | ~8 min | ~40 s |
| Attachment errors | Frequent | Eliminated in the documented workflow |
| Traceability | None | Execution logs |
Approximate reduction in processing time: 91.7%.
This project represents what I value most in automation: measurable operational impact, repeatability and traceability.
🧬 Cinesia
Study platform for Physiotherapy combining organization, active recall and interactive tools.
Highlights:
- Rich-text summaries
- Flashcards with SM-2 spaced repetition
- AI-assisted quizzes
- Conversational study assistant
- Digital whiteboard
- 3D atlas experiments
- Pomodoro and study organization
- Real-time synchronization
- Installable PWA
🏢 Omni
Multi-tenant SaaS experiment for clinic operations and patient confirmations.
Explores:
- Java 17 + Spring Boot 3
- Multi-tenant architecture
- React + TypeScript
- PostgreSQL
- JWT authentication and refresh flow
- Automated confirmations
- Docker / Docker Compose
| Project | What it explores |
|---|---|
| Syntax | Programming and logic study environment organized as a monorepo |
| Sistema de Agenda Ocupacional | Scheduling, capacity, documents and workflows for occupational medicine |
| KKMovies | Movie/series catalog with React, TypeScript, Node/Express and TMDB integration |
| Jogo-de-Xadrez | Chess implementation in Java with graphical interface and game rules |
| SearchInPDF | Python utility for searching text in PDF documents |
| socplug-fix | Windows automation for Java/SOCPlug environment recovery |
I contribute to open-source projects using the real GitHub collaboration flow: fork → branch → implementation → review → pull request → upstream.
One of my contributions to the official RustDesk repository was merged upstream:
- ✅ rustdesk/rustdesk#16135 — Brazilian Portuguese Android/Fastlane metadata
- 🔎 See my RustDesk pull requests
The contribution involved repository conventions, review feedback and changes submitted directly to the upstream project.
| Principle | In practice |
|---|---|
| Understand the problem first | I try to understand users, workflow and business rules before choosing technology. |
| Design for failure | Network errors, retries, conflicts, invalid input and partial execution should be expected, not ignored. |
| Keep code maintainable | Clear responsibilities, modularity, readable naming and documentation matter beyond the first release. |
| Automate repetition | Repetitive operational work is a candidate for a reliable and auditable process. |
| Validate with evidence | Tests, logs, metrics and real usage are more useful than assumptions. |
| Improve continuously | Delivery is a checkpoint, not the end of the engineering process. |
Java & Spring Boot ███████████████████░ Back-End
Software Architecture ███████████████░░░░░ Growing
Automated Testing ███████████████░░░░░ Growing
Python Automation █████████████████░░░ Practical
React & TypeScript ████████████████░░░░ Full-stack support
Open Source ████████████░░░░░░░░ Contributing
I'm currently deepening my knowledge in Java/Spring Boot, software architecture, testing, APIs, security, CI/CD and production-oriented engineering practices.
