Computer Engineering · UTRGV · McAllen, Texas
I’m Jose Carlos Arce Camet, a Computer Engineering student building complete software products across AI, audio, finance, workflow systems, and interaction-heavy frontend experiences.
My work combines technical architecture, secure user-owned data, accessibility, testing, and original product design.
Seeking software engineering, full-stack, and AI application opportunities.
Each project isolates a different kind of risk—from AI context and audio validation to financial correctness, workflow modeling, and keyboard interaction.
Exact financial logic
Exact money calculations, accessible analytics, and user-owned financial data.
An authenticated finance workspace for transactions, monthly budgets, cash-flow analytics, filtering, and defensive CSV export.
AI orchestration
Inspectable personal AI with approved memory and selective response evaluation.
A full-stack AI workspace combining mode-specific conversations, approval-gated memory, document workflows, tasks, saved insights, and inspectable execution decisions.
Audio processing
Explainable audio recognition with secure full-stack workflows.
An experimental audio-recognition application that analyzes microphone or uploaded clips, ranks an original catalog, and explains confidence through signal and score diagnostics.
Business workflow modeling
A private recruiting pipeline for applications, follow-ups, and interview milestones.
A Supabase-backed job-search workspace for managing opportunities, recruiter context, deadlines, activity history, and pipeline analytics.
Accessible interaction
Accessible local chess built on a replayable move-log architecture.
A local two-player chess interface with complete legal-move integration, SAN history, keyboard interaction, responsive geometry, and original SVG pieces.
Capabilities are grouped by engineering responsibility, not presented as a wall of logos.
Explicit orchestration and bounded context instead of opaque behavior.
Complete workflows across interface, API, persistence, and ownership boundaries.
Interfaces built around complex state, clarity, and accessible interaction.
Authorization, validation, and failure modes treated as product concerns.
Risk-focused verification from pure logic through real-browser behavior.
Model the system before styling the screen.
Treat user ownership as a backend responsibility.
Make uncertain behavior inspectable.
Use design to clarify—not obscure—the product.
I’m a Computer Engineering student at UTRGV with a software-focused project portfolio spanning AI systems, browser audio, finance tools, operational dashboards, and accessible interfaces.
I’m especially interested in full-stack product engineering: translating an idea into a working system, defining its data and trust boundaries, and refining the experience until it feels deliberate.
More about my processI’m open to software-engineering internships, junior development opportunities, remote or hybrid technical work, and selected freelance projects.