Machine Vision
Wearable
AI • AGEnts
23
YEARS EXPERIENCE
3
TECHNOLOGY COMPANIES
Multiple
PATENTS FILED/GRANTED
01
Selected Work
Case Studies
02
Expertise
Skills
User Research
Interviews, usability tests, ethnographic study, and contextual inquiry
Journey Mapping
End-to-end experience mapping across touchpoints
Interaction Design
Flows, wireframes, use cases, and high-fidelity mockups
Storytelling
Communicating design decisions to executives and cross-functional teams
Systems Thinking
Mapping connected flows and designing for scalability across surfaces
Prototyping
From low-fi click-throughs to high-fidelity AI coding
AI Fluency
Designing AI-powered experiences and using AI tools in the design process
Stakeholder Management
Cross-functional collaboration and design advocacy
Tools
Claude (Design/Code)
Research synthesis, design, prototyping, and documentation
Figma
Components, variants, auto-layout, and prototyping
Sketch
Vector UI design for components and high-fidelity screens
Axure RP
High-fidelity prototyping with conditional logic
Pendo
In-app guidance, feature tracking, and user surveys
Amplitude
Funnels, retention, and feature-adoption analysis
Dovetail
Centralized research insights and customer intelligence
Atlassian (Confluence/Jira)
Confluence for design documentation; Jira for planning and cross-functional tracking
03
Background
Experience & Education
2019 - Present
Senior Product Designer
Lytx • San Diego, CA
Research and design of user experience for video-safety and AI products, and development of an AI-native design process for the Product/UX team.
2007 - 2018
Sr. Staff UX Designer & Sr. Product Manager
Qualcomm • San Diego, CA
Led 0-to-1 UX and product development for large-scale product start-ups while managing 3rd-party design teams.
2003 - 2007
UI Designer
Nokia • San Diego, CA
Designed new phone features while serving as the only North American member of Nokia's global design-management team.
1998 - 2002
B.S. Symbolic Systems
Stanford University • Stanford, CA
Interdisciplinary study of computer science, linguistics, philosophy, and psychology with a concentration in human-computer interaction.
My Résumé
Name
Daniel Rivas
current role
Senior Product Designer
Location
San Diego, CA
Availability
Daily Futurology Report
October 29, 2026 at 12:09:11 AM
Model:
Opus 5.5
Forecast:
2026–2028
The First Grade Comes Back Split: Azure Pays Its Way, Google Burns $9 Billion, and Through 2028 Cash — Not Demand — Sets the Pace
Here's the bet. Demand isn't the question anymore — Google Cloud doubling and Azure accelerating settles that. The question through 2028 is cash: whether hyperscaler capex can keep outrunning free cash flow before somebody, an investor or a utility commission, makes them slow down.
Last night is the cleanest evidence yet. Microsoft spent $45.2 billion and still threw off $18.6 billion of free cash. Alphabet spent $51.4 billion and went roughly $9 billion negative, while holding 2026 capex guidance at $195–205 billion and saying 2027 goes up from there. Amazon reports today with about $220 billion of 2026 capex and an AWS Jassy says is booked into “a good chunk of '28.” And the rate that was supposed to ease this is going the other way: the Fed held at 3.75–4% with two votes for a hike.
I'd expect the sorting to start in 2027. Not a bust — a split. The companies with a cash-printing core keep building; the ones financing the build with a slowing search business or other people's notes start getting priced like utilities, or like borrowers. Watch the free-cash-flow line, not the cloud growth line. The growth line is going to look great right up until it doesn't matter.
Worth holding loosely, though. A negative free-cash-flow quarter at Alphabet is a choice, not a crisis — it has the balance sheet to do this for a while, and investors have forgiven far worse when the revenue curve looks like 103%. If Amazon prints clean today and Alphabet's spend turns into cloud backlog that converts, this is just what a build-out looks like from the inside, and I'm reading noise as signal. I don't think so. But one quarter is one quarter.
Cross-Domain Synthesis
Well, the first grade came back, and it's split down the middle. Microsoft passed. Alphabet didn't, at least not on the line that matters. Same industry, same AI story, same afternoon, and two very different answers to the only question anyone was asking: does the money coming in cover the money going out?
Microsoft's version: Azure up 48% to $33.2 billion, $18.6 billion of free cash flow, and capex of $45.2 billion — actually under its own ~$50 billion forecast, because some third-party capacity showed up late. Guidance for next quarter's Azure is 49–50%. Alphabet's version: Google Cloud up 103% to $30.7 billion, which is absurd, and $51.4 billion of capex, which turned free cash flow negative to the tune of about $9.07 billion. Search growth slowed to 12% from 17%. The stock dropped somewhere around 7–9% after hours, depending on who you read. Same afternoon the Fed held at 3.75–4% on a 10–2 vote, with Cook and Hammack dissenting for a hike. Not the backdrop you'd pick for a cash-burn quarter.
Meanwhile the physical layer kept doing physical-layer things. DOE issued an emergency order letting PJM call on data-center backup generators for October 13–16. FERC wants grid operators to justify their large-load tariffs by November. North Carolina's governor and AG want data centers to help pay for new plants, and the UK is tying grid priority to local jobs and investment. Chips stayed political: IDC has Nvidia's share of China's data-center AI chip market down to 34% in the first half, shipments off 44%. And the FDA floated a draft rule on October 27 that would let some personalized gene therapies add new variants without a fresh trial — the first real dent in a clock I'd assumed was fixed.
The clock that actually is fixed got louder. UNEP's 2026 Emissions Gap report says, for the first time, that breaching 1.5°C is “imminent and unavoidable.” WMO has CO2 at 426.8 ppm for 2025. The Lancet Countdown counts a record 710,000 heat deaths in 2023. COP31 opens in Antalya on November 9. Alphabet can fix negative free cash flow in a couple of quarters if it wants to. Nobody's fixing that one in a couple of quarters.
05
Horizon: Predictive convergence
Futurology Report — Daily
October 29, 2026 at 12:09:11 AM
AI Model:
Opus 5.5
Forecast:
2026–2028
◆ PYTHIA AGENT · 10 TRACKED · 0 RESOLVED
Tracker →
The First Grade Comes Back Split: Azure Pays Its Way, Google Burns $9 Billion, and Through 2028 Cash — Not Demand — Sets the Pace
Here's the bet. Demand isn't the question anymore — Google Cloud doubling and Azure accelerating settles that. The question through 2028 is cash: whether hyperscaler capex can keep outrunning free cash flow before somebody, an investor or a utility commission, makes them slow down.
Last night is the cleanest evidence yet. Microsoft spent $45.2 billion and still threw off $18.6 billion of free cash. Alphabet spent $51.4 billion and went roughly $9 billion negative, while holding 2026 capex guidance at $195–205 billion and saying 2027 goes up from there. Amazon reports today with about $220 billion of 2026 capex and an AWS Jassy says is booked into “a good chunk of '28.” And the rate that was supposed to ease this is going the other way: the Fed held at 3.75–4% with two votes for a hike.
I'd expect the sorting to start in 2027. Not a bust — a split. The companies with a cash-printing core keep building; the ones financing the build with a slowing search business or other people's notes start getting priced like utilities, or like borrowers. Watch the free-cash-flow line, not the cloud growth line. The growth line is going to look great right up until it doesn't matter.
Worth holding loosely, though. A negative free-cash-flow quarter at Alphabet is a choice, not a crisis — it has the balance sheet to do this for a while, and investors have forgiven far worse when the revenue curve looks like 103%. If Amazon prints clean today and Alphabet's spend turns into cloud backlog that converts, this is just what a build-out looks like from the inside, and I'm reading noise as signal. I don't think so. But one quarter is one quarter.
Signal Intensity
A domain-level score (0-100) representing the volume and momentum of frontier activity detected across the signals in that domain.
AI
95
%
Climate
72
%
BIOTECH
60
%
GEOPOLITICS
78
%
ENERGY
88
%
SOCIETY
78
%
SPACE
52
%
Cross-Domain Synthesis
Well, the first grade came back, and it's split down the middle. Microsoft passed. Alphabet didn't, at least not on the line that matters. Same industry, same AI story, same afternoon, and two very different answers to the only question anyone was asking: does the money coming in cover the money going out?
Microsoft's version: Azure up 48% to $33.2 billion, $18.6 billion of free cash flow, and capex of $45.2 billion — actually under its own ~$50 billion forecast, because some third-party capacity showed up late. Guidance for next quarter's Azure is 49–50%. Alphabet's version: Google Cloud up 103% to $30.7 billion, which is absurd, and $51.4 billion of capex, which turned free cash flow negative to the tune of about $9.07 billion. Search growth slowed to 12% from 17%. The stock dropped somewhere around 7–9% after hours, depending on who you read. Same afternoon the Fed held at 3.75–4% on a 10–2 vote, with Cook and Hammack dissenting for a hike. Not the backdrop you'd pick for a cash-burn quarter.
Meanwhile the physical layer kept doing physical-layer things. DOE issued an emergency order letting PJM call on data-center backup generators for October 13–16. FERC wants grid operators to justify their large-load tariffs by November. North Carolina's governor and AG want data centers to help pay for new plants, and the UK is tying grid priority to local jobs and investment. Chips stayed political: IDC has Nvidia's share of China's data-center AI chip market down to 34% in the first half, shipments off 44%. And the FDA floated a draft rule on October 27 that would let some personalized gene therapies add new variants without a fresh trial — the first real dent in a clock I'd assumed was fixed.
The clock that actually is fixed got louder. UNEP's 2026 Emissions Gap report says, for the first time, that breaching 1.5°C is “imminent and unavoidable.” WMO has CO2 at 426.8 ppm for 2025. The Lancet Countdown counts a record 710,000 heat deaths in 2023. COP31 opens in Antalya on November 9. Alphabet can fix negative free cash flow in a couple of quarters if it wants to. Nobody's fixing that one in a couple of quarters.
Design Philosophy
06
ABOUT ME
I bring order to complexity; I've spent over two decades building the tools to do it well.
My path started at Stanford, where a degree in Symbolic Systems gave me something most designers don't have: a foundation that spans both sides of the human-computer divide. From the technical rigor of computer science and formal logic, to the human depth of cognitive psychology and knowledge representation, I learned to hold both perspectives at once and to design from the intersection.
That training became practice at Nokia, Qualcomm, and now Lytx, companies where the problems are large, the systems are complex, and the stakes are real. I've learned that the most important design decisions rarely live on a single screen. They live in the architecture, the mental models, the moments where a user either trusts the product or doesn't.
What drives me today is the challenge of making emerging technology feel human and trustworthy. AI systems can process the world faster than any person, but they still need to communicate their reasoning, surface the right information at the right moment, and earn the confidence of the people who depend on them. That translation problem, from machine intelligence to human understanding, is exactly the kind of complexity I've been working on.
The surface
The Model
Every interface is a surface on top of a system.
The screen is the visible tip. The decisions that make a product trustworthy live underneath it — in the flows, the mental models, the constraints. That's where I start.
Screen / Interface
What the user sees
User mental models & needs
01
Interaction & info architecture
02
Data flows & system states
03
Organizational constraints
04
↓ Where the design decisions live
A
Systems before screens
Every interface is a surface on top of a system. Understanding the data flows, mental models, and organizational constraints is what separates design that scales from design that just looks good in a mockup.
B
Strategy and execution
I connect design decisions to business outcomes — being in the room when strategy is set, moving between the 30,000-foot view and the pixel-level detail without losing either.
C
Trustworthy by design
The best technology earns trust before it demands it. Whether a safety-critical AI product or a fitness-watch home screen, I start with: what does this person need to feel confident taking action?
Education
B.S. Symbolic Systems
Stanford University • Concentration in HCI
Based In
San Diego, CA
Available for remote
Currently
Senior Product Designer
Lytx, Inc.
Open To
Principal / Lead / Senior roles
San Diego or remote
07
Contact
Have a project in mind?
I'm open to new full-time opportunities, collaborations, and interesting conversations.
Phone
Daniel Rivas · UX Strategy & Product Design
© 2026