Skip to content

Software Engineer · Data Engineering and Applied AI

Felipe Duenas

I build software that enlivens data for intelligent decisions.

I'm a software engineer who works on data. At AWS I build the pipelines behind a capacity-planning platform for data centers, and the AI assistant that answers questions from them. Most of my work is the part underneath: getting messy data into a shape software can actually use, which turns out to be what makes the AI on top of it correct rather than merely fluent.

Statistics & Data Science, UCLA '27 · SF Bay Area | Los Angeles

Portrait photograph

Work

What I've built

Each card is the plain version. Open one for the full engineering account, including what broke and what I'd do differently.

sources →pipelines →warehouse →models →agents →answers
Amazon Web Services June 2026 — Present

Making 3,000 dashboards answerable by an AI agent

AWS's capacity teams keep their operating knowledge in 3,000 dashboards that only a person could read. I made them readable by software, so an AI assistant can answer questions from them.

3,000+
Tableau workbooks in the pipeline
85%
Increase in queryable data
  • Python
  • AWS Step Functions
  • AWS Lambda
  • +4
Amazon Web Services 2026

Dashboards from a sentence, in 3 minutes

Building a dashboard used to take a specialist four days. Now a planner describes what they want and gets a working one in about three minutes.

4 days → 3 min
Median time to a working view
10k → 300
Model output tokens per rendered view
  • Python
  • Strands Agents
  • Bedrock AgentCore
  • +6
UCLA Trustworthy AI Lab Jan 2026 — May 2026

An agent for data science, not just the SQL

A research tool that takes a plain question and a data file, then does the analysis itself: writes the code, runs it, and hands back charts and a table.

65%
Execution accuracy on the BIRD benchmark
18% → 5%
Agent failure rate, after re-architecting context
  • Python
  • PostgreSQL
  • Supabase
  • +6
Amazon Web Services Jun 2025 — Sep 2025

Forecasting data center power: $400K in avoided rack spend

Data centers were reserving far more electrical power than they actually used. A better forecast freed 21% of that headroom, so AWS did not have to buy racks it already had room for.

1.9%
Forecast MAPE, against a 6.3% baseline
21%
Usable capacity released, same power envelope
  • Python
  • AWS Glue
  • Redshift
  • +7

Experience

Where I've worked

  1. June 2026 — Present

    Now

    Software Engineer Intern

    Amazon Web Services · Data Platform · Seattle, WA

    • The org's operational knowledge lived in 3,000+ Tableau dashboards that no software could read. I built the pipeline that turned them into something an AI agent can answer from for our internal supply chain automation platform (serving 5,000+ users). 85% more of the org's data became reachable, and the accuracy gain traced to the data, not the prompt.
    • Then the other direction: tooling that builds a dashboard from a prompt, so a planner gets one in three minutes as a self-serve request instead of waiting four days on a BI engineer's build cycle. The page is constructed in code rather than typed by the model, which took output cost from 10k tokens to a few hundred and means every cell traces to a real row.
  2. Jan 2026 — May 2026

    Backend & Data Engineer Intern

    UCLA Trustworthy AI Lab · Agentic Data Science · Los Angeles, CA

    • Built the tool-calling layer for the Lab's agentic data science platform, which turns a plain-language ask and a raw file into runnable Python, charts, and an exportable table. Achieved a 65% execution accuracy on BIRD, 8 points above GPT-4o.
    • The agent worked due to the data architecture upstream, with an ingestion pipeline that infers schema and column types from any CSV, JSON, or Parquet, and a Postgres event log recording every response and failure. Querying that log and acting on the findings is what cut the failure rate from 18% to 5%.
  3. Jun 2025 — Sep 2025

    Business Intelligence Engineer Intern

    Amazon Web Services · Arlington, VA

    • Planners at government sites were coordinating builds around power numbers padded by buffers on top of buffers. An XGBoost forecast, blended with a Random Forest and fed peak events as their own signal, cut error from a 6.3% baseline to 1.9% MAPE: tight enough to recalculate the planned values and release 21% more usable capacity inside the same power envelope. This led to roughly $400K of rack spend avoided across 33 AZs.
    • Underneath it, the data work: Glue loading 500M+ daily telemetry events into Redshift, dbt modeling them into incremental marts, one capacity-planning layer in place of the seven sources my team was reading by hand, and a Bedrock text-to-SQL interface over it. Weekly reporting went from six hours to thirty minutes.
  4. Jun 2024 — Sep 2024

    Data Analyst Intern

    Acer · San Jose, CA

    • 30+ years of records were scattered across siloed systems, so I created a single data model in PostgreSQL that helped increase data accessibility by 125% for Acer's legal team.
    • I helped cut report preparation time for General Counsel by creating automated Tableau dashboards, and I elevated licensing discrepencies through analyzing trends from merger and financial docs.

Education

Expected March 2027

University of California, Los Angeles

B.S. Statistics & Data Science · Minor in Data Engineering

Lab

Code you can read

The work above is internal, so none of it is open. These are smaller things I built on my own time, and the repos are public.

Toolkit

What I reach for

Things I've actually shipped with, not everything I've ever opened.

Languages
PythonSQLJavaRBash
Cloud
AWSGCPRedshiftSnowflakeS3LambdaBedrock
Data platform
AirflowdbtSparkDockerTerraformCDK
Applied AI
ClaudeStrands AgentsMCPRAGRetrieval evaluationVector databases
Modeling
scikit-learnPyTorchForecastingAnomaly detectionNLP

Contact

Don't hesitate to reach out. Students, professionals, or people who want to talk about shooting data centers into space.