Skip to content
Marcelo OS
Evolution roadmap / evidence-driven / 2026-2030

Roadmap 2030

A public, evidence-driven plan to evolve from fundamentals and projects in 2026 toward AI Engineering and MLOps, focused on the United States market, by 2030.

Professional direction

Primary track set: AI Engineering and MLOps.

The choice is made. The destination is building, evaluating, deploying, and operating AI systems in production. The realistic path runs through a strong foundation of Python, data, and cloud — aiming at the United States market.

01 / Primary track

AI Engineering & MLOps

Take machine learning models and LLMs from prototype to production, with responsible evaluation, deployment, and operations.

  • Python, data, and model APIs
  • Model evaluation, cost, and observability
  • Deployment, versioning, and monitoring (MLOps)

02 / Entry foundation

Data and cloud foundation

The practical base that supports AI in production and is the most pragmatic way into the track.

  • Python, SQL, and data engineering
  • Cloud, containers, and CI/CD
  • Pipelines, automation, and infrastructure

03 / Trust layer

Security and responsible AI

Treat security and responsibility as part of the AI system, not a separate final step.

  • Secure SDLC and dependencies
  • Privacy and data governance
  • Model evaluation, limits, and guardrails

04 / Differentiator

Technical communication

Turn experience in video, customer service, and product thinking into clear documentation, demos, and collaboration.

  • Bilingual case studies
  • Short architecture and model videos
  • Communication across engineering and business
Now / Next / Later

Enough focus to act without losing direction.

The long-term view guides decisions, while daily work stays limited to the next verifiable set of deliveries.

  1. Now 2026

    Foundation and positioning

    Choose the primary track, publish strong projects, and prove software, cloud, and delivery fundamentals.

  2. Next 2027–2028

    Experience and ownership

    Work in a real context, own deliveries, and document decisions, impact, and operations.

  3. Later 2029–2030

    Impact and global reach

    Deepen specialization, lead initiatives, and compete for international opportunities.

Annual plan

Goals from 2026 to 2030.

Each stage defines observable outcomes. Certifications and technologies support the plan; projects, experience, and impact remain the main evidence.

  1. 2026 Stage 01 / 2030
    In progress

    Build the public foundation

    Turn learning into proof that can be opened, tested, and discussed.

    Technical focus

    • Linux, Git, Docker, and SQL
    • Cloud fundamentals
    • Documentation and demos in PT/EN

    Expected evidence

    • Primary track defined: AI Engineering and MLOps
    • Publish three strong projects with architecture and lessons
    • Deliver one cloud application and one real pipeline
    • Complete one entry certification and one open-source contribution
  2. 2027 Stage 02 / 2030
    Planned

    Enter a real technical context

    Secure an internship, junior role, or freelance engagement involving software, cloud, data, security, or automation.

    Technical focus

    • Intermediate cloud
    • CI/CD and automation
    • Security in the lifecycle (DevSecOps)
    • Team delivery

    Expected evidence

    • Verifiable professional technical experience
    • One intermediate certification aligned with the track
    • Two complete case studies during the year
    • Recurring community or open-source participation
  3. 2028 Stage 03 / 2030
    Planned

    Take ownership

    Become responsible for a feature, service, or project across delivery, operations, and evolution.

    Technical focus

    • Observability and SRE
    • DevOps practices
    • Data engineering
    • Architecture and cost

    Expected evidence

    • Twelve to eighteen months of relevant experience
    • One documented delivery with clear ownership
    • One technical article per quarter
    • Projects with metrics, security, cost, and performance
  4. 2029 Stage 04 / 2030
    Planned

    Convert experience into impact

    Move into a higher-responsibility role across cloud, platform, security, data, or solutions.

    Technical focus

    • Track certifications
    • International cases
    • Technical English
    • Measurable impact

    Expected evidence

    • Technical results connected to real metrics
    • Professional-level architecture documentation
    • The complementary track acting as a differentiator
    • A portfolio ready for international evaluation
  5. 2030 Stage 05 / 2030
    Planned

    Operate at a global level

    Work in AI Engineering and MLOps at an international level, focused on the United States market.

    Technical focus

    • Technical leadership
    • Systems architecture
    • Cloud, security, and applied AI

    Expected evidence

    • Lead an initiative, not only a task
    • Make decisions across business and engineering trade-offs
    • Communicate architecture and impact in English
    • Compete for international technical opportunities
Current evidence

The roadmap is already underway.

These items exist today and will be updated as new deliveries replace intention with proof.

Published

Nu! Carnaval 2026

Case study for an offline-first PWA with maps, weather, and synchronization.

In progress

Mapa dos Rolezinhos

Application using interactive maps, Firebase, and local event curation.

In progress

Drift Invaders

Python experiment with a planned path toward automation, data, and ML.

Published

Bilingual resume

Technical resume in Portuguese and English, also available as PDF.

Roadmap policy

Direction, not a rigid promise.

The plan will be reviewed when projects, experience, and opportunities produce better evidence. Technologies may change; the commitment remains focused on fundamentals, delivery, and verifiable learning.