arrow_back Back to home
Erik Beltran
code

About Me

Full Stack Developer with business vision. I don't just write code, I design complete solutions.

My Story

I started programming in 2022 during my university studies. From the beginning, I was more interested in the "why" than the "how". It wasn't enough for me to make something work, I wanted to understand the structure behind it. In September 2024, I joined Printpack Medical as an intern. I thought I would do small tasks, support existing projects. Instead, I ended up designing complete systems from scratch. First The Encyclopedia (technical documentation), then SO.FI (the prototype that demonstrated the value of a centralized platform), and finally ORBE, an enterprise platform for 17 plants and over 3,200 employees. Those 14 months taught me that I can take an ambiguous problem, understand the business needs, and build something that actually works. Not just code that compiles, but systems that people use.

Where I'm Going

I'm looking for roles where I can combine technical depth with strategic thinking. I'm interested in being involved in architecture decisions, understanding the business behind the product, and working on problems that require more than just implementing features. My long-term goal is to build my own tech products. That's why I'm so interested in both the technical and business side: because eventually I want to apply all of this to create something of my own.

format_quote

"Code matters, but the foundation matters more."

My Vision

I don't think in terms of features or tickets. I think in terms of complete systems, long-term scalability, and how each technical decision affects the business. When I face a problem, I don't look for the fastest solution. I look for the solution that will still work in 5 years, that will be easy to maintain, and that can grow with business needs.

How I Solve Problems

visibility
1.

Visualize the System

I draw the data model and flows before writing code. If I can't visualize it, I don't build it.

timeline
2.

Think Long-Term

What happens when we have 10x users? I design for scale from the start.

balance
3.

Evaluate Trade-offs

Speed vs. maintainability. Simplicity vs. flexibility. I always consider both sides.

build
4.

Build Step by Step

Database first, then backend, then frontend. Each layer validated before the next.

What I Bring to the Table

architecture

Technical Decisions

Technology choices, system architecture, design patterns.

palette

Design Decisions

Design systems, reusable components, functional UX.

trending_up

Business Vision

Software exists to solve business problems. Every feature must justify its value.

group

Autonomous Work

I can take an ambiguous problem and turn it into a solution without constant supervision.

Education

B.Eng. in Multiplatform Software Development & Management

Universidad Tecnológica de Tijuana (UTT)

TSU obtained 2024. Returning April 2026.

Languages

Native Spanish. B2 English (ITEP).

Certifications

Mendix Rapid Developer

Availability

Remote, hybrid, or relocation. Immediate start.

Contact

location_on

Location

Tijuana, Baja California, Mexico

phone