About / Engineering practice

I build software from the system boundary inward.

I’m Jose Carlos Arce Camet, a Computer Engineering student at The University of Texas Rio Grande Valley.

Profile / 2026
School
UTRGV
Degree
Bachelor of Science in Computer Engineering
Expected
Fall 2027
Location
McAllen, Texas
Languages
English / Spanish

A consistent process across very different products.

My projects span AI applications, audio analysis, personal finance, recruiting workflows, and interaction-heavy frontend systems. Although the products look different, my process is consistent: understand the problem, model the data and trust boundaries, build the complete workflow, test the risky behavior, and refine the interface until the product feels intentional.

I’m especially interested in full-stack product engineering and the point where technical architecture becomes visible to the user—through reliability, speed, accessibility, clear states, and thoughtful interaction.

I use AI-assisted development tools as accelerators while owning the requirements, architecture, product decisions, review, verification, testing, and understanding of the final implementation.

I’m currently pursuing software-engineering internships, junior frontend and full-stack roles, remote or hybrid technical opportunities, and selected freelance projects.

Email Jose
01Areas of focus

Engineering across the product boundary.

01

AI application engineering

Explicit orchestration and bounded context instead of opaque behavior.

02

Full-stack development

Complete workflows across interface, API, persistence, and ownership boundaries.

03

Frontend engineering

Interfaces built around complex state, clarity, and accessible interaction.

04

Security and reliability

Authorization, validation, and failure modes treated as product concerns.

05

Testing and delivery

Risk-focused verification from pure logic through real-browser behavior.

02 / Working principles

How I make product decisions.

  1. 01

    Model the system before styling the screen.

  2. 02

    Treat user ownership as a backend responsibility.

  3. 03

    Make uncertain behavior inspectable.

  4. 04

    Use design to clarify—not obscure—the product.

03 / Contact

Open to the next useful problem.

Seeking software engineering, full-stack, and AI application opportunities.

josecarlos.arce@outlook.comView résuméGitHub (opens in a new tab)LinkedIn (opens in a new tab)