Marcus Valente Software development

README.md

Open to software engineering internships

Marcus Valente

I build software. I connect systems and people.

I study Computer Science at Inteli and build applications and integrations. At Inteli Júnior, I work with teams on architecture and client deliveries.

Current role
Director of Projects · Inteli Júnior2026 — present
Education
Computer Science · Inteli2025 — 2028, expected
Experience
Freelance at Zelar IA · Developer at Inteli Júnior · Co-founder of Nexus Skill
Main stack
TypeScript · Python · Java · React · Next.js · Node.js · PostgreSQL
Recognition
1st place at ICP WCHL 2025 · 2nd at Global HackMeridian 2025
Location
São Paulo · from Manaus

projects / avericode.tsx01 of 6

Independent product · 2026

AveriCode

Creator & developer

A platform to follow GitHub contributions, connect repositories and make team activity easier to track.

Technical decisions

  1. Starting with the team. Workspaces group repositories and expected contributors, giving project leaders a reference for following their team.
  2. Events and scheduled updates. Webhooks receive GitHub events; scheduled synchronizations update the information queried by the application.
  3. Workspace-scoped persistence. Stored data follows the workspace structure, connecting repository information to each team's overview.
  • Next.js
  • TypeScript
  • PostgreSQL
  • Prisma
  • Auth.js
Open the case study →
PreviewAveriCode
avericode.tsxView as code
1// Independent product · 20262export const avericode = {3  role: "Creator & developer",4  stack: ["Next.js", "TypeScript", "PostgreSQL", "Prisma", "Auth.js"],5  decisions: [6    { title: "Starting with the team", why: "Workspaces group repositories and expected contributors, giving project leaders a reference for following their team." },7    { title: "Events and scheduled updates", why: "Webhooks receive GitHub events; scheduled synchronizations update the information queried by the application." },8    { title: "Workspace-scoped persistence", why: "Stored data follows the workspace structure, connecting repository information to each team's overview." },9  ],10  caseStudy: "/en/projects/avericode/",11};

projects / zelar-ia.ts02 of 6

Freelance · Nov 2025 – Mar 2026

Zelar IA

Freelance developer

Evolving an AI assistant through refactoring, integration fixes and new channels connected to the product.

Technical decisions

  1. Explicit command execution. Some actions were routed through commands and menus executed in code rather than sending every request to the model.
  2. Context for conversations. I improved AI instructions to guide the assistant's behavior within messaging flows.
  3. Validation before use. I checked changes locally and then with real users, verifying integration flows and product behavior.
  • Node.js
  • TypeScript
  • Express.js
  • PostgreSQL
  • Supabase
Open the case study →
PreviewZelar IA
zelar-ia.tsView as code
1// Freelance · Nov 2025 – Mar 20262export const assistenteIa = {3  role: "Freelance developer",4  stack: ["Node.js", "TypeScript", "Express.js", "PostgreSQL", "Supabase"],5  decisions: [6    { title: "Explicit command execution", why: "Some actions were routed through commands and menus executed in code rather than sending every request to the model." },7    { title: "Context for conversations", why: "I improved AI instructions to guide the assistant's behavior within messaging flows." },8    { title: "Validation before use", why: "I checked changes locally and then with real users, verifying integration flows and product behavior." },9  ],10  caseStudy: "/en/projects/assistente-ia/",11};

projects / por-partes.tsx03 of 6

Inteli Júnior · 2025

Por Partes

Mobile frontend, backend and infrastructure

A published bill-splitting product using AI to read receipts.

Technical decisions

  1. A receipt as input. AI reading is part of identifying bill information to help participants split costs.
  2. From interface to infrastructure. My implementation covered the mobile frontend, part of the backend and deployment of the services forming the infrastructure.
  3. Planning the next features. I planned advertising and in-app purchases and assigned implementation tasks to another team.
  • Vercel
  • Supabase
  • OpenAI
  • AWS
Open the case study →
PreviewPor Partes
por-partes.tsxView as code
1// Inteli Júnior · 20252export const porPartes = {3  role: "Mobile frontend, backend and infrastructure",4  stack: ["Vercel", "Supabase", "OpenAI", "AWS"],5  decisions: [6    { title: "A receipt as input", why: "AI reading is part of identifying bill information to help participants split costs." },7    { title: "From interface to infrastructure", why: "My implementation covered the mobile frontend, part of the backend and deployment of the services forming the infrastructure." },8    { title: "Planning the next features", why: "I planned advertising and in-app purchases and assigned implementation tasks to another team." },9  ],10  caseStudy: "/en/projects/por-partes/",11};

projects / argus.py04 of 6

Inteli + Grupo Globo · August — September 2026

Argus

AWS infrastructure and Flask backend

A distributed backend to collect, normalize and process events from different platforms.

Technical decisions

  1. Partner-provided data. Loading the dump into RDS made the dataset supplied by Globo available to the application.
  2. Windowed replay. Periodic consumption in 15-minute windows simulated a time sequence for processing.
  3. Application and infrastructure. Flask provided the API; Gunicorn and Nginx formed part of the backend runtime setup. My work included this foundation and part of the AWS services.
  • Python
  • Flask
  • Gunicorn
  • Nginx
  • AWS EC2
  • RDS
  • S3
  • CloudWatch
Open the case study →
PreviewArgus
argus.pyView as code
1// Inteli + Grupo Globo · August — September 20262export const globoTelemetria = {3  role: "AWS infrastructure and Flask backend",4  stack: ["Python", "Flask", "Gunicorn", "Nginx", "AWS EC2", "RDS", "S3", "CloudWatch"],5  decisions: [6    { title: "Partner-provided data", why: "Loading the dump into RDS made the dataset supplied by Globo available to the application." },7    { title: "Windowed replay", why: "Periodic consumption in 15-minute windows simulated a time sequence for processing." },8    { title: "Application and infrastructure", why: "Flask provided the API; Gunicorn and Nginx formed part of the backend runtime setup. My work included this foundation and part of the AWS services." },9  ],10  caseStudy: "/en/projects/globo-telemetria/",11};

projects / kaisen.ts05 of 6

Hackathon · 1st place ICP WCHL · 2025

Kaisen

Developer in a team

An educational prototype with AI-generated learning paths, study texts, flashcards and minigames, built as a team at ICP WCHL.

Technical decisions

  1. A goal as input. Generation starts with the learning goal and produces sections and content for the path.
  2. Questions with context. Questions sent to the model combine the user's message with the learning-path context.
  3. Gemini in the prototype. The team chose Gemini considering free-tier limits. Specialized minigame calls returned JSON data.
  • TypeScript
  • Next.js
  • NestJS
  • Prisma
  • PostgreSQL
  • Gemini
Open the case study →
PreviewKaisen
kaisen.tsView as code
1// Hackathon · 1st place ICP WCHL · 20252export const kaisen = {3  role: "Developer in a team",4  stack: ["TypeScript", "Next.js", "NestJS", "Prisma", "PostgreSQL", "Gemini"],5  decisions: [6    { title: "A goal as input", why: "Generation starts with the learning goal and produces sections and content for the path." },7    { title: "Questions with context", why: "Questions sent to the model combine the user's message with the learning-path context." },8    { title: "Gemini in the prototype", why: "The team chose Gemini considering free-tier limits. Specialized minigame calls returned JSON data." },9  ],10  caseStudy: "/en/projects/kaisen/",11};

projects / fireoff.java06 of 6

Inteli + Suzano · Feb – Apr 2026

FireOFF

Java backend and integrations

A web/mobile application and graph-based algorithm to support resource allocation for forest fire response.

Technical decisions

  1. Inputs for recommendations. The solution considers distance, risk and availability when allocating fire-response resources.
  2. The backend as the connection. My work connected the interface to the algorithm through the Java backend, using Spring Boot in the application.
  3. Complementary responsibilities. The team developed the application and graph logic; my responsibility was the backend and its integrations, not the algorithm itself.
  • Java
  • Spring Boot
  • TypeScript
  • Next.js
  • Supabase
  • Docker
Open the case study →
PreviewFireOFF
fireoff.javaView as code
1// Inteli + Suzano · Feb – Apr 20262export const suzano = {3  role: "Java backend and integrations",4  stack: ["Java", "Spring Boot", "TypeScript", "Next.js", "Supabase", "Docker"],5  decisions: [6    { title: "Inputs for recommendations", why: "The solution considers distance, risk and availability when allocating fire-response resources." },7    { title: "The backend as the connection", why: "My work connected the interface to the algorithm through the Java backend, using Spring Boot in the application." },8    { title: "Complementary responsibilities", why: "The team developed the application and graph logic; my responsibility was the backend and its integrations, not the algorithm itself." },9  ],10  caseStudy: "/en/projects/suzano/",11};

projects / others.md

11 more projects

Open the full catalogue →

about / experience.md

Experience

  1. Inteli Júnior · Director of Projects

    I work with teams and clients, review scope and architecture, and contribute to deployments and environment handovers.

  2. Zelar IA · Freelance developer

    I refactored an existing product, stabilized AI, WhatsApp and Telegram integrations, and added email, Google and Outlook calendars, and Supabase.

  3. Inteli Júnior · Developer

    I contributed to developing and delivering Por Partes, a published bill-splitting product that uses AI to read receipts.

  4. Nexus Skill · Co-founder & developer

    With the team, I turned our capstone into a learning app, working with React Native, Expo, Firebase and Android builds. My involvement has ended.

Recognition

  • 1st place · ICP WCHL 2025, with Kaisen
  • 2nd place · Global HackMeridian 2025, with 4Bridge
  • Mentor to the winning team · Inteli Júnior + Qi Tech Hackathon

about / education.md

Education

2022 — 2024 · Manaus

Fundação Matias Machline

Technical course in IT, where I started programming.

about / stack.json

Stack

Technologies applied in the projects and experiences presented here.

Languages

  • TypeScript
  • Python
  • Java
  • SQL

Applications & APIs

  • React
  • Next.js
  • Node.js
  • Express.js
  • Spring Boot
  • Flask

Data & AI

  • PostgreSQL
  • Pandas
  • NumPy
  • Scikit-learn
  • LLM integrations

Infrastructure & integrations

  • Git
  • Docker
  • OAuth
  • Webhooks
  • AWS in the Argus project
stack.jsonView as code
1{2  "Languages": ["TypeScript", "Python", "Java", "SQL"],3  "Applications & APIs": ["React", "Next.js", "Node.js", "Express.js", "Spring Boot", "Flask"],4  "Data & AI": ["PostgreSQL", "Pandas", "NumPy", "Scikit-learn", "LLM integrations"],5  "Infrastructure & integrations": ["Git", "Docker", "OAuth", "Webhooks", "AWS in the Argus project"]6}

contact.md

Shall we talk?

For software engineering opportunities and internships, with room to contribute through applied AI and data. I reply within 3 days.