You've seen what I build.
Here's how I got there.
Two parallel tracks, professional and academic, running simultaneously.
My Journey
Two tracks, one developer
Professional
Academic
Professional
Software Developer Intern
Faster Solutions, Duluth MNJun 2019 to Aug 2019
The gap between knowing how to code and writing code that ships is wider than any classroom suggests. This summer closed it.
Frontend Developer
Arroyo ConsultingFeb 2022 to Oct 2022
First real team, first real deadline pressure. Worked on TimeTracker, an internal hour-logging platform, and discovered that clean requirements are a luxury, not a given.
Full-Stack Developer
Magneto GlobalNov 2022 to Aug 2024
Nearly two years on Colombia's leading HR platform. Real traffic, real teams, real tradeoffs. Where best practices stopped being theory and started being survival.
Web Developer
Cafeto Software, Client: ProsNov 2024 to Feb 2026
Joined a mature UI library powering airline SaaS products. The kind of codebase that teaches you more than a greenfield ever could. Refactoring, migrating, and learning how good teams handle technical debt.
Academic
A.S. Computer Technology
Lake Superior CollegeJan 2017 to May 2019
Two years in Minnesota. Studying in English, thinking in systems, learning to work in rooms where nobody looked like me. The foundation everything else is built on.
Platzi Master Bootcamp
PlatziJan 2021 to Sep 2021
Nine months going deep into React, Redux, GraphQL, and enough architecture thinking to know why the choices matter. The year that reframed how I approach a problem.
Técnico Profesional en Sistemas
TeincoFeb 2022 to Sep 2023
Formal grounding in systems and software development. The academic layer that gives the hands-on experience somewhere to anchor.
B.S. Software Engineering
UNINPAHU UniversityFeb 2024 to Present
6th semester. The part of engineering school where the theory starts connecting to everything you've already shipped. AgroTech, an IoT agriculture system, got university recognition in the first semester.
Active
Recognition
Beyond the job description
How I Work
Process, not just craft
bash — sebastian@bccloudsolutions ~
// process.flow
01
Understand
Map functional and non-functional requirements. Ask what the business actually needs, not just what was written in the ticket.
02
Design
Define the contract before the code. Data flow, component boundaries, API shape. On paper first.
03
Build
Iterative and incremental. Small PRs, atomic commits, continuous feedback from the team and the backlog.
04
Deliver
Code review, QA handoff, sprint demo. Delivery is a team event, not a solo push to main.
05
Improve
Retrospective thinking applied beyond the ceremony. What slowed us down, what can be automated, what should be documented.
sebastian.config.ts
| 1 | const sebastian = { |
| 2 | // Know the domain |
| 3 | types: "rules, constraints, edge cases first", |
| 4 | |
| 5 | // Design the contract |
| 6 | api: "API and props before implementation", |
| 7 | |
| 8 | // Ship incrementally |
| 9 | webVitals: "small PRs, fast feedback, no big bangs", |
| 10 | |
| 11 | // Leave it better |
| 12 | testing: "refactor, document, then close the ticket", |
| 13 | |
| 14 | anyType: false, // non-negotiable |
| 15 | }; |