Skip to content

Profile

Santiago Gómez

Full-Stack Software Engineer

I build reliable products by turning complexity into clear, practical solutions.

  • Meta
  • Stackline
  • Adaptive

6+ years in software engineering

Experience

Where I’ve worked.

I’ve built software for traders, linguistic engineers, shoppers, and the teams supporting them.

  1. Stackline

    -

    Full-Stack Software Engineer

    At Brandclub, I rebuilt the shopper onboarding flow after browser navigation and persisted account state had become tightly coupled, making it predictable across refreshes, direct links, and returning sessions. I later took primary engineering ownership of the internal admin replacement, redesigning it with Client Services around the work they actually needed to do and moving sensitive operations behind an internal network boundary.

    Ask about this role

    Technologies

    • React
    • TypeScript
    • Node.js
    • Elasticsearch
    • GraphQL
  2. Meta

    -

    Software Engineer

    At Meta, I built internal tooling for linguistic engineers working in Assistant Studio. I automated documentation from published data, then drove much of the design and implementation of a structured authoring workflow that let engineers make a change once, validate it, and compile the roughly seven device-specific files they previously maintained by hand.

    Ask about this role

    Technologies

    • React
    • Hack
    • Python
  3. Adaptive Financial Consulting

    -

    Web Application Developer

    At LTX, I built trader-facing and Client Services software around dense, fast-moving market and operational data, later becoming the primary or sole frontend engineer for substantial parts of the Client Services product. At Bank of America, I helped build a shared component system and desktop applications for traders, giving multiple applications a common UI foundation that client engineers could reuse and extend.

    Ask about this role

    Technologies

    • React
    • TypeScript
    • Storybook
    • RxJS
    • OpenFin

Projects

Selected work.

A few projects where the interesting part was the tradeoff, not just the implementation.

Personal / Independent / 2026

Blind Journal

End-to-end encrypted journal

A private journal designed so the server can authenticate users and store entries without needing access to their plaintext.

Figure 001Product screen
Blind Journal sign-in page explaining its end-to-end encrypted privacy model
Live Blind Journal sign-in and privacy explanation.
My role
Designed and built the product, including the encryption model, client-side key handling, and the privacy UX around sign-in and recovery.
Key decision
Keep decryption capability on the client and separate account authentication from the ability to decrypt journal content.
Result
Shipped a live, localized journal whose server stores encrypted entries without needing plaintext access.

Approach

How I work.

These are the habits I keep coming back to when the implementation gets messy or the real problem is still unclear.

  1. Start with the real job

    If someone asks for a workaround, I want to understand what they are actually trying to accomplish before I preserve the workaround.

  2. Keep the system understandable

    I prefer explicit data flow and boundaries over abstractions that save a few lines but make behavior harder to trace.

  3. Follow the problem

    If a bug or feature crosses the UI, API, data, or deployment boundary, I keep going until I understand the whole path.

  4. Change my mind when the evidence changes

    I prototype, measure, and revisit decisions when the implementation proves that a tradeoff is not worth it.

Ask AI

Want to go deeper?

Ask about the work, the decisions behind it, or anything you want to understand better.

Dig into what I owned, how I approached a problem, the tradeoffs I considered, and what I learned along the way.

Open Ask AI

Try a question

I review these chats to see how the assistant is performing and where it can improve. With that in mind, please don't share any sensitive information.

Contact / Direct

Let's talk.

If you think my background fits what your team is building, I’d like to hear from you.