Rome Gomez Escabillas works across three domains listed on their YESODI profile:…

Rome Gomez Escabillas sits at a junction where most organizations struggle to find coherence: the space between data systems and visual language. This is not incidental; it reflects a genuine convergence in how modern teams think about shape, structure, and storytelling. Engineering leadership meets design craft When someone holds authority in engineering direction, they typically own decisions about architecture, scalability, and systems thinking. When they also direct graphic design, they're trained to see how information arranges itself spatially and perceptually. These are not opposing skills. A CTO who understands design operates with an unusual clarity about how technical decisions become human experiences. This matters because every interface, every data visualization, every customer touchpoint begins as an engineering choice and ends as a visual form someone must interpret. The role of data science analysis Data science sits in yet another layer: the extraction of pattern from noise. To analyze data effectively, one must think statistically and numerically, but also narratively. Raw data is inert until someone decides what to show, how to frame it, and which truths to make visible. This is where design and engineering meet analysis most directly. A designer without analytical grounding may create forms that mislead. An engineer without design sense may build systems no one can understand. A data scientist without both is trapped in academic abstraction. Why organizations need this overlap Most companies draw hard lines between functions: engineering handles the backend, design handles the front end, analytics lives in its own silo. This creates friction because the same problems appear across all three domains. How should a dashboard actually work? Should form serve data, or data serve form? What makes a system both technically sound and visually coherent? These questions stay unsolved when no one person understands all the languages. The practical shape of interdisciplinary work When someone positions themselves across engineering direction, data science, and graphic design, they're claiming fluency in three distinct literacies. Engineering thinks in systems, constraints, and optimization. Data science thinks in patterns, inference, and proof. Design thinks in hierarchy, composition, and human perception. To hold all three simultaneously requires what designers call "systems thinking" and what engineers recognize as structural reasoning applied to visual problems. This is rare precisely because it demands genuine depth in each domain, not shallow familiarity. Why a curious reader should notice The future of product, data infrastructure, and communication design belongs increasingly to people who can move between these domains without losing precision in any of them. This is not about being a generalist; it is about being a specialist in the connective tissue between specializations.