Observer · Entry
№ 001 — 2026

Teresa
Tran.
Design Engineer.

Full-stack · Systems · Interface
Open to work
LocationCalifornia
ModeRemote-friendly
Currently Observing

Areas where humans compensate for a system

Field notes
ExploringInformation architecture, worldbuilding
ReadingThe Timeless Way of Building, Braiding Sweetgrass
BuildingA field atlas for the edible garden
Thinking aboutHow to represent living systems in an interface
About — 02

Background &
Approach

My path into design engineering has a specific origin point. On a small team building an application from the ground up, I was the only one interested in designing the interface. I obsessed over layout, user flows, color palettes, and typography to make something genuinely pleasing and easy to navigate. It worked.

My background spans the visual and performing arts, biological sciences, and a long habit of paying attention to how things fit together — how a space feels, the choreography and tempos behind and translations between systems, the difference between a form that feels considered and one that clearly wasn't. Design language, like spoken language, can be purposeful, decorative, or haphazardly put together. I aim for intentional.

This direction is deliberate. Time away from the industry gave me space to pay attention differently — traveling, observing systems and interfaces without the pressure of building them, sitting with grief. Loss has a way of clarifying what's worth doing and when. This was worth doing, and now was when. I want to make things and experiences that make someone's life a little easier, and ideally more enjoyable — because what's living if it can't be enjoyed?

Field record
Ingeniarius designatus
Experience
    10 years engineering · currently full-stack
Education
    M.S. Computer Science · CSU Fullerton
    B.S. Neuroscience · UCLA
Habitat
    Visual systems, natural systems, and language systems
Behaviour
    Names things carefully; mentally models systems
Interests
    Design systems; DX, information architecture
Status
    Always learning
collected · june 2026
ref. field-001
Skills — 03

Toolkit &
Capabilities

Languages
PythonSCRIPTINGFLUENT
TypeScriptTS · JSFLUENT
SQLSEASONED
GoLEARNING
Frontend & Design
ReactNEXT.JSFLUENT
Design SysTOKENS · DSFLUENT
HTML & CSSFLUENT
FigmaPROTOTYPINGSEASONED
MotionANIMATIONLEARNING
Infrastructure
CI / CDGH ACTIONSSEASONED
DockerCONTAINERSSEASONED
KubernetesORCHESTRATIONSEASONED
AWSCLOUD INFRASEASONED
PostgreSQLSCHEMA · QUERIESSEASONED
RedisCACHINGSEASONED
Work — 04

Selected
Projects

Observations ongoing
001Field Atlas — Portfolio
Pivoting toward design engineering with no public body of work to point to yet, I arrived at a question worth designing around: what is the purpose of a portfolio if you can't show what you've worked on? If I can't show you what I've done, I might as well show you how I think. My answer? The Field Atlas.
Next.jsTailwind v4TypeScriptSVGMotion
Open entry →
002
Field entry pending · in progress