A little atmosphere. A lot of engineering.

Welcome to my corner
of the internet.

Explore the projects, the systems, and the thinking behind the work. Take a look around.

By choosing Agree & enter, you consent to first-party analytics: your network IP, device/browser details, approximate location when available, visit activity, performance, and name/email when you submit a contact form. Seth receives private daily reports to understand how this portfolio is used.

What is collected & your choices

After you agree, this site measures active viewing time, sections and case studies viewed, scroll depth, resume/link clicks, contact-form action counts, and available loading/interaction performance. Only name and email from submitted contact forms are included; message contents, passwords, and payment fields are excluded.

Browser details include device category, browser and operating-system family, language, timezone, screen/viewport size, touch support, available processor/memory and network estimates, motion/color preferences, and referring domain. To fill missing location details in private reports, your network IP may be sent to IPWHOIS over HTTPS. Its location result is cached for 24 hours. Location may include approximate country, region, city, postal code, continent, timezone, latitude and longitude supplied by Cloudflare; no GPS or street address is requested.

The server records your network IP after agreement. Names and emails appear only when you submit them through a contact form, and are not verified identities. No identity lookup, fingerprinting, cross-site profiles, passwords, full referrer URLs, or query strings are stored.

A random browser identifier and your consent last 24 hours. Events expire after 48 hours and are removed on the next housekeeping run; reports cover the previous 24 hours. Reports already emailed to Seth remain in his private inbox until deleted. Your host and other WordPress plugins may keep separate access logs.

Analytics starts only after agreement. If you do not agree, close this tab or go back. You can withdraw through Privacy & consent below the portfolio; this stops collection and requests deletion of this browser identifier’s stored events. Browser Do Not Track and Global Privacy Control signals disable analytics.

Software Engineer Systems Architect

Seth
Rodriguez

Backend Engineering · Full-Stack · Data · Automation

I architect backend-heavy full-stack systems, APIs, data pipelines, and polished interfaces that make complex operations feel simple.

Explore

01 / About

Backend depth. Full-stack ownership.

I am a backend-focused software engineer who carries systems from data model and API design through deployment and high-craft UI/UX.

My work spans Python and Django services, REST integrations, SQL data systems, automation, Docker and Linux infrastructure, business intelligence, and responsive React and JavaScript interfaces. I focus on reliability underneath and clarity at the surface.

Through independent consulting, I have delivered full-stack applications, integrations, and automated digital systems for 20+ clients. That end-to-end ownership includes requirements, implementation, deployment, hosting, DNS, analytics, CRM integrations, performance, and the user experience.

  • Precision
  • Clarity
  • Performance
  • Ownership

02 / Technical stack

A systems toolkit from backend to interface.

Backend engineering, data, infrastructure, automation, and UI/UX—applied across production work, research, and independent systems.

01

Languages

Python · Go (Golang) · C · C++ · C# · Java · JavaScript · SQL · PHP

02

Backend & APIs

Python / Django · Go · REST APIs · PHP · .NET · service integrations

03

Data & Intelligence

MySQL · MongoDB · Power BI · DAX · data pipelines · visualization

04

Systems & DevOps

Linux · Docker · Git · DNS · SSL/TLS · cloud hosting · observability

05

UI / UX Engineering

React · HTML5 · CSS3 · responsive systems · interaction · accessibility

06

Automation & Research

CRM / SaaS · Zapier · PDF generation · OpenCV · ROS · technical SEO

03 / Featured work

Selected systems in the field.

Backend systems, data products, and polished client experiences—grounded in documented scope and measurable outcomes.

Backend platform / Data engineering

Full-Stack Reporting Engine

A React and Python/Django reporting platform that aggregated real-time data from 6+ external sources, normalized fragmented datasets through automated REST pipelines, and delivered adaptive dashboards plus consistent on-demand PDFs.

Role
Lead developer & systems architect
Stack
React · Python / Django · REST APIs · MySQL · PDF generation
Read case study
S and M Quality Roofing website project 02

Marketing system / Local growth

S & M Quality Roofing

A complete marketing engine connecting the website, brand management, social publishing, SEO/AEO, Meta, and Google Ads to increase visibility and bring in leads.

Role
Web development & delivery
Scope
Brand · SEO / AEO · Social · Paid ads
Read case study
Lesthetique Medspa website and social presence project 03

Commerce / Connected operations

Lesthetique Medspa

A complete storefront with cart, checkout, customer accounts, database and finance workflows, and an NDA-protected custom reporting engine.

Role
Website delivery
Scope
Storefront · Accounts · Operations
Read case study
Aerial media created for Salais Auto Group 04

Media system / Local visibility

Salais Auto Group

Licensed Part 107 aerial production delivered in formats for short-form content, local marketing, and Google Business Profile use.

Role
Technical production
Scope
Drone · Multi-format delivery
Read case study

Further into the work

Software / Data platformFull-Stack Reporting Engine

Software / Data platform

Full-Stack Reporting Engine

From fragmented data to a shared answer.

A full-stack reporting platform that brings external data, historical analysis, interactive dashboards, and on-demand documents into one workflow.

Illustrative dashboard using synthetic data. Original production records are not displayed.
Illustrative dashboard using synthetic data. Original production records are not displayed.

01 / Context

The starting point

Reporting depended on assembling records from separate sources. Different data shapes made comparison difficult and recurring document preparation added manual work.

02 / Ownership

What I owned

Lead developer and systems architect. Owned the React interface, Python/Django integration layer, REST pipelines, MySQL schemas, and PDF generation.

03 / Delivery

What came together

  1. 01

    Integrated data from more than six external REST sources

  2. 02

    Normalized records into a common MySQL reporting model

  3. 03

    Built interactive React visualizations with custom filters and two years of history

  4. 04

    Added consistent PDF generation from the reporting dataset

Conceptual architecture based on the project scope; not a production system export.
Conceptual architecture based on the project scope; not a production system export.

04 / Approach

The design decision

Keep integration and normalization concerns below the presentation layer so dashboards and documents share a dependable reporting model.

≈50%estimated reduction in reporting effort

The outcome

Approximately 50% less manual reporting effort, based on the operational estimate recorded in the résumé. The same data can be explored interactively and delivered as a document.

Source: September 2026 résumé; operational estimate, not an independent benchmark.
Client feedback · proposed wording

“Having the dashboard and report in one workflow makes recurring reporting much easier to manage.”

Proposed stakeholder feedback · editorial draft

Written from the supplied project scope and positive feedback reported by Seth. This is proposed wording, not a verbatim client quotation.

  • React
  • Python / Django
  • REST APIs
  • MySQL
  • PDF generation
Discuss a reporting system
Client work / Marketing systemsS&M Quality Roofing

Client work / Marketing systems

S&M Quality Roofing

A local brand with a connected growth engine.

A website, search presence, social content, and paid advertising system built to help an El Paso roofing business become easier to find and contact.

Website presentation from the existing portfolio media library.
Website presentation from the existing portfolio media library.

01 / Context

The starting point

A local service business needs a consistent presence wherever customers discover it: search, social media, advertising, and the website. Those channels need to lead to a clear next step.

02 / Ownership

What I owned

Owned website delivery, brand management, social publishing, SEO and AEO, Facebook/Meta optimization, Google Ads, and the lead-generation experience.

03 / Delivery

What came together

  1. 01

    Built a service-led website with clear estimate and contact paths

  2. 02

    Aligned brand presentation and social-media publishing

  3. 03

    Improved search and answer-oriented content for local discovery

  4. 04

    Connected Facebook/Meta and Google Ads activity to the marketing presence

Conceptual architecture based on the project scope; not a production system export.
Conceptual architecture based on the project scope; not a production system export.

04 / Approach

The design decision

Make each channel reinforce the same service story and direct interested visitors toward an inquiry, with consistent messaging throughout.

Connectedbrand, discovery, and lead generation

The outcome

The completed marketing engine brought in leads and increased public visibility through coordinated social content, brand management, search optimization, and advertising.

Qualitative project outcome supplied by Seth Rodriguez. No numerical lead or revenue claim is made.
Client feedback · proposed wording

“Our website, social presence, and advertising finally feel connected. The work gave our roofing business a clearer presence and helped bring in inquiries.”

Proposed S&M Quality Roofing testimonial · editorial draft

Written from the supplied project scope and positive feedback reported by Seth. This is proposed wording, not a verbatim client quotation.

  • WordPress
  • HTML / CSS / JS / PHP
  • SEO / AEO
  • Meta
  • Google Ads
Client work / Commerce + operationsLesthetique Medspa

Client work / Commerce + operations

Lesthetique Medspa

A polished storefront. A connected operation.

A customer-facing web experience supported by commerce, accounts, data management, finance workflows, and a custom reporting system.

Public-facing website presentation from the existing portfolio. It does not show confidential back-office systems.
Public-facing website presentation from the existing portfolio. It does not show confidential back-office systems.

01 / Context

The starting point

The digital storefront needed to present a premium brand while supporting the practical steps behind shopping, customer accounts, and day-to-day operations.

02 / Ownership

What I owned

Delivered the storefront website, cart and checkout integration, login/account management, database management, finance-related workflows, and a custom reporting engine.

03 / Delivery

What came together

  1. 01

    Created a coherent storefront and customer journey

  2. 02

    Integrated cart, checkout, and account-management experiences

  3. 03

    Connected data and finance-related operational workflows

  4. 04

    Developed custom reporting within an NDA-protected scope

Conceptual architecture based on the project scope; not a production system export.
Conceptual architecture based on the project scope; not a production system export.

04 / Approach

The design decision

Connect the customer experience to the operational work behind it while maintaining a clear boundary around confidential reporting capabilities.

End to endcustomer experience through operations

The outcome

A complete storefront supported by connected account, data, and operational capabilities. Reporting details remain confidential under an NDA.

Scope supplied by Seth Rodriguez. Internal screens, customer data, financial details, and reporting logic are withheld.
Client feedback · proposed wording

“The storefront feels cohesive and professional, and the connected account and operational workflows make the experience much more complete.”

Proposed Lesthetique Medspa testimonial · editorial draft

Written from the supplied project scope and positive feedback reported by Seth. This is proposed wording, not a verbatim client quotation.

  • Storefront development
  • Commerce integration
  • Account management
  • Database workflows
  • Custom reporting
Client work / Aerial mediaSalais Auto Group

Client work / Aerial media

Salais Auto Group

A different perspective on local visibility.

FAA-licensed drone production and professional editing turned aerial footage into polished assets for local marketing and digital discovery.

Original aerial photograph delivered for Salais Auto Group, from the existing portfolio library.
Original aerial photograph delivered for Salais Auto Group, from the existing portfolio library.

01 / Context

The starting point

A dealership's physical presence is difficult to communicate through ordinary listings. Aerial media creates a broader view of the location and a stronger visual impression.

02 / Ownership

What I owned

Owned licensed aerial production, professional editing, and preparation of media for short-form content, local marketing, and Google Business Profile use.

03 / Delivery

What came together

  1. 01

    Captured aerial footage through FAA-licensed drone operations

  2. 02

    Professionally edited the footage into finished marketing media

  3. 03

    Prepared formats for short-form and local marketing channels

  4. 04

    Delivered location-focused visuals with a consistent presentation

Conceptual architecture based on the project scope; not a production system export.
Conceptual architecture based on the project scope; not a production system export.

04 / Approach

The design decision

Start with the real location and create finished assets suited to the channels where prospective customers encounter the business.

≈20%traffic increase reported by project owner

The outcome

The project owner reports an approximately 20% increase in traffic associated with the delivered work. The traffic channel and comparison period were not specified.

User-supplied result; channel, time period, and independent attribution are not available.
Client feedback · proposed wording

“The aerial footage gave our location a strong new perspective. The finished edits looked professional and were ready to use across our marketing.”

Proposed Salais Auto Group testimonial · editorial draft

Written from the supplied project scope and positive feedback reported by Seth. This is proposed wording, not a verbatim client quotation.

  • FAA-licensed drone production
  • Professional editing
  • Multi-format delivery
  • Local marketing
Experience / Systems + automationMountain Star Roofing Systems

Experience / Systems + automation

Mountain Star Roofing Systems

Less reporting overhead. More operational clarity.

Power BI, CRM data, automation, and production infrastructure brought reporting and recurring operational work into a more connected system.

Illustrative workflow reconstructed from résumé scope; no internal company data is displayed.
Illustrative workflow reconstructed from résumé scope; no internal company data is displayed.

01 / Context

The starting point

Executive reporting and recurring data work needed a dependable connection to operational CRM records and fewer manual handoffs.

02 / Ownership

What I owned

Systems Director, September 2025–June 2026. Owned Power BI/DAX dashboards, JobNimbus integration, Zapier and API automation, and web/communications infrastructure.

03 / Delivery

What came together

  1. 01

    Built Power BI dashboards with advanced DAX and live JobNimbus CRM data

  2. 02

    Automated recurring workflows with Zapier and custom API connectors

  3. 03

    Administered SaaS platforms, reporting tools, and operational data flows

  4. 04

    Maintained DNS, SSL/TLS, hosting, and secure email configuration

Conceptual architecture based on the project scope; not a production system export.
Conceptual architecture based on the project scope; not a production system export.

04 / Approach

The design decision

Connect reports to operational data and automate repeated handoffs, while keeping the underlying web and communication services dependable.

20+ hrsmanual work eliminated per week

The outcome

The résumé records a 50% reduction in executive reporting time, more than 20 manual hours eliminated each week, and 100% production infrastructure uptime during the stated role.

Source: September 2026 résumé. These are historical role outcomes, not future performance guarantees.
Client feedback · proposed wording

“Connecting CRM data with reporting helped reduce repetitive work and made operational information easier to use.”

Proposed stakeholder feedback · editorial draft

Written from the supplied project scope and positive feedback reported by Seth. This is proposed wording, not a verbatim client quotation.

  • Power BI / DAX
  • JobNimbus
  • Zapier
  • REST APIs
  • DNS / SSL / hosting
Research / Computer visionAutonomous Systems Research

Research / Computer vision

Autonomous Systems Research

From visual perception to a vehicle that follows the lane.

An autonomous-systems research internship exploring lane-following behavior through computer vision, simulation, and vehicle testing.

Conceptual perception-to-control diagram; this is not a recording from a research vehicle.
Conceptual perception-to-control diagram; this is not a recording from a research vehicle.

01 / Context

The starting point

A Polaris GEM e2 needed a lane-following approach that could be developed in simulation and evaluated through on-road testing.

02 / Ownership

What I owned

Autonomous Systems & Data Research Intern at Lawrence Technological University, May–August 2022. Developed and tested lane-following algorithms and co-authored a research paper.

03 / Delivery

What came together

  1. 01

    Developed lane-following algorithms in C++ and Python

  2. 02

    Used OpenCV and ROS for perception and system integration

  3. 03

    Evaluated behavior in simulation and on-road testing

  4. 04

    Co-authored a peer-reviewed paper published in MDPI Vehicles

04 / Approach

The design decision

Use simulation and physical-route testing together to evaluate lane-following behavior and establish a benchmark for later research cohorts.

95%route accuracy recorded in the résumé

The outcome

The résumé records 95% route accuracy in simulation and on-road testing, successful completion of the autonomous course, and selection as one of eight students from more than 1,000 applicants.

Source: September 2026 résumé. The full evaluation protocol and paper citation are not included in the supplied material.
Client feedback · proposed wording

“The lane-following implementation gave the research team a concrete system to evaluate in simulation and on the course.”

Proposed research feedback · editorial draft

Written from the supplied project scope and positive feedback reported by Seth. This is proposed wording, not a verbatim client quotation.

  • C++
  • Python
  • OpenCV
  • ROS
  • Polaris GEM e2
More client work
  • Avalos ConcreteSearch, growth strategy, and advertising support, focused on local discovery.
  • Maya’s Beauty SalonWebsite and digital credibility work to support a coherent customer-facing presence.

04 / Experience

Technical progression, grounded in delivery.

January 2022 — Present

Lead Digital Systems Architect

Independent Consultant · El Paso, Texas

Delivered custom full-stack applications, data integrations, and automated digital systems for 20+ clients while owning requirements, implementation, deployment, hosting, DNS, analytics, and CRM integrations.

  • Full-stack JavaScript, PHP & MySQL delivery
  • Data integrations & automation
  • Advanced UI/UX, accessibility & performance

September 2025 — June 2026

Systems Director

Mountain Star Roofing Systems · El Paso, Texas

Architected Power BI and DAX systems using live JobNimbus CRM data, automated reporting with custom API connectors, and administered the organization’s production web and communications infrastructure.

  • 50% lower executive reporting latency
  • 20+ manual hours eliminated weekly
  • 100% production infrastructure uptime

May 2022 — August 2022

Autonomous Systems & Data Research Intern

Lawrence Technological University · Southfield, Michigan

Engineered and tested lane-following algorithms in C++ and Python with OpenCV and ROS for a Polaris GEM e2. The work achieved 95% route accuracy across simulation and real-road environments and contributed to a peer-reviewed MDPI Vehicles paper.

  • 1 of 8 selected from 1,000+ applicants
  • C++ · Python · OpenCV · ROS
  • Autonomous course completion & benchmarks

Education

B.S. Computer Science

The University of Texas at El Paso · Minor in Mathematics

A computer science and mathematics foundation supporting work across algorithms, backend systems, data engineering, automation, and human-centered software interfaces.

05 / Engineering approach

From ambiguity to a system that holds up.

  1. 01

    Understand

    Find the real constraint behind the request.

  2. 02

    Model

    Make the system, tradeoffs, and interfaces explicit.

  3. 03

    Build

    Ship a simple, observable foundation first.

  4. 04

    Measure

    Test behavior, performance, and usefulness.

  5. 05

    Refine

    Remove friction and automate repetition.

  6. 06

    Ship

    Document the system and own the outcome.

How this portfolio is engineered
01 / Rendering

Stable scene, adaptive atmosphere

The Japanese night artwork anchors a WebGL water surface, curved sakura geometry, and interactive systems. A responsive image preserves the composition before enhancement and in Static mode.

02 / Interaction

Progressive by design

Semantic HTML remains usable before enhancement. Motion, dialogs, scroll-linked indicators, and advanced CSS activate only when the browser and visitor preferences support them.

03 / Access

Control without compromise

Keyboard navigation, visible focus, live form status, and Full, Reduced, or Static effects modes keep the interface expressive without making animation a requirement.

04 / Constraint

Performance is part of the UI

The scene adapts its rendering resolution, shares repeated geometry, pauses when hidden, and provides a complete static fallback. Content and controls remain ordinary, accessible HTML.

06 / Contact

Have a difficult problem worth solving?

Tell me what you are building, where it is stuck, or what a better system needs to accomplish.

Open to software engineering opportunities and thoughtful collaborations.

Message received.

Thanks for reaching out. I’ll respond as soon as I can.

System 01 / Case study

Full-Stack Reporting Engine

Project scope + illustrative artifacts

Follow one reporting request from fragmented external sources to a normalized, decision-ready dashboard and consistent on-demand PDF. Select a stage to inspect the engineering responsibility behind it.

Reporting pipeline: sources, ingestion, normalization, storage, interface and delivery. Use the six stage buttons below to explore each step.
REQUEST / JOURNEY

Select a stage to inspect an artifact. Drag sideways to rotate; swipe vertically to scroll.

01 / SOURCES

Fragmented operational data

More than six external REST sources supplied differently shaped records, inconsistent identifiers, and separate update schedules.

Constraint
External schemas and availability were outside application control.
Decision
Treat each source as an explicit adapter boundary before data enters the reporting model.
Failure behavior
Keep a source-specific failure observable instead of allowing one integration to invalidate the complete reporting path.
01 / SourcesOpen artifact ↗
Illustrative map of six REST sources feeding an adapter layer
Source boundary mapIllustrative architecture based on project scope. No production credentials or records are displayed.What I owned Integration of more than six REST sources into the reporting platform.
OwnershipLead developer & systems architect
Historical windowTwo years of analysis
Measured directionApproximately 50% less reporting effort
OutputAdaptive dashboards + on-demand PDFs

The reporting-effort figure is an estimated operational reduction from documented project scope, not a synthetic benchmark.

SELECTED WORK / IN DETAIL