about00
About / Houston, by way of Cameroon

Understand a system well enough that a person can move with more agency.

Engineer, founder, sometime musician. Bioengineering at Rice, production software in finance and clinical care, then OrgX and Open Becoming. What I keep coming back to is amplification: a person, a team, or a fleet of agents doing more than they could alone.

Explore my skills and tools
Hope Atina
HoustonCameroonian roots
00

Four scales

Everything I build makes something survive a handoff.

A language, a device, a community, a company. I learned the same lesson four times, each at a bigger scale.

  1. Cameroonian roots

    Meaning has to survive translation.

    The same words carry different weight depending on who is listening and what they have lived. Check the structure before you trust the surface.

  2. Rice → DermaShift → clinical production

    At the human boundary, a dropped handoff costs a person.

    Bioengineering, then healthcare systems under HIPAA. Make the risk visible, keep the rollout reversible, attach the evidence. The boundary is where the consequence lives.

  3. Figma & Chill

    Many hands on one file, nothing lost.

    A community built by making things together. Everyone kept their own strength and the thing still held. Figma platformed it.

  4. OrgX

    The decision comes back as a receipt the next run inherits.

    Memory, authority, execution, and proof for agent work. The lesson, shipped as infrastructure.

01

The root system

Multidisciplinary from the first serious problem.

HOPE spelled in glowing lights in a photograph from my high-school years
A little hope, from the high-school archives.

My Cameroonian roots were my first lesson in translation. The same thing can mean something different depending on context and history. I learned early to look at the structure before believing the surface.

Bioengineering at Rice gave that instinct rigor. With DermaShift, our team built a low-cost way to detect pressure-ulcer risk and won a national undergraduate design competition. A human need, clinicians, sensors, product design, proof. I still work that way.

Music and dance sit in the background. Timing, tension, release. A composition can be technically correct and still feel unfinished.

Hope Atina with the Rice DermaShift bioengineering team
Rice bioengineering · DermaShiftPhoto / ASME ↗
2015 / rehabilitation + assistive devices

A real person. A physical system. A device that had to earn belief.

Pressure ulcers aren't a dashboard problem. We had to understand the clinical need, build a portable device, make the economics work, and explain the evidence plainly. That's still how I want engineering to meet the world.

02

The practice

Look closely. Find the boundary. Build the fix. Leave it stronger.

A hard problem is useful once it shows you the mechanism underneath. I like working with people where disagreement sharpens the model and evidence settles the next move.

  1. 01 / human consequence

    A problem can look solved while the person living with it still pays for it.

    Start with the person. Then bring whatever disciplines the fix actually needs.

    Bioengineering stuck as a product instinct. Understand the system, build the mechanism, prove it worked.

    Rice bioengineering · DermaShift
  2. 02 / creative rhythm

    An interface can be technically correct and still feel flat.

    Compose software with timing, tension, release, and room for someone else to play.

    Music and dance stay quiet in the work. They still set the pacing.

    Music production · shared making
  3. 03 / amplify people

    People's best work gets hidden by the room, the process, or the tools.

    Set up the conditions where people make things together and can see each other's work.

    The system becomes an amplifier. A community, a product team, a fleet of agents working for one company.

    Figma and Chill · OrgX
03

The questions got harder

Each environment added a boundary I could no longer ignore.

One practice that kept growing. Not a list of unrelated jobs.

01 / Capital One · scale

Can data be trusted before it starts moving?

In regulated finance, data quality and lineage were part of the system. You didn't get to clean up after the pipeline.

Spark · Scala · Snowflake · near-real-time ETL
02 / Vessel Health · ownership

What changes when the API touches hardware and operations?

I led backend work across auth, calibration, AWS, and internal workflows. Ownership stopped ending at the code.

API architecture · hardware calibration · AWS · operations
03 / Alma · consequence

How do you move continuously when failure reaches clinical work?

HIPAA production taught me to bring privacy in early, make failure visible, keep rollouts reversible, and treat operator trust as engineering quality.

Django · Celery · PostgreSQL · Datadog
Research / MD Anderson · visualization

Can the right picture change an operational decision?

Research that turned operating-room capacity into a picture people could actually use.

React · D3.js · scientific and operational visualization
04

Collaboration is a creative technology

I started Figma and Chill because talking about design wasn't enough.

It started as an empty Clubhouse room. It grew into a global BIPOC design community where people made things together in real time. At Config 2021 we shared how it worked.

Watch the Config talk
Figma Config 2021 talk cover for Figma and ChillConnection → community → culture
Capabilities / tools / the work behind them

What I bring to the work.

Production engineering, independent products, research, and creative practice. Explore a discipline, then a tool to see how I use it.

14 highlights · 59 tools to explore

  • Product & interaction / BrainBuffet · Meridian · Alma

    React

    Compose stateful interfaces around the work: learning progress, clinical workflows, and evidence-led decisions.

    See it in the work
05

In my own words

In Hope’s own words

  • “I’m less about talk and more about action.”

    Figma Config, on starting Figma and Chill · 2021
  • “It’s not a lack of words. It’s a lack of retrievals.”

    Bessemer interview · October 2026
  • “Consistency builds up into an avalanche of momentum.”

    In conversation · April 2025
  • “I’ll just keep building. That’s how I compound.”

    On being a generalist · September 2025
  • “Style is the moat.”

    A product design discussion · September 2025
  • “Collaboration by default, not by crisis.”

    On independence and interdependence · December 2025
  • “I believe that we should have a maximalist future.”

    A portfolio reflection · December 2024
  • “It’s becoming the protagonist rather than a victim. That’s the fundamental change.”

    On agency · May 2025
  • “I want to make a racing game that will show the diversity and craziness of driving in Cameroon.”

    The first note on Chaos Riders · August 2025
  • “The diagnosis is right. The prescription is generic. The math is fake-rigorous.”

    Reviewing an AI business analysis · April 2026
  • “Make it 100x better… where is the flair, the taste, the attention to detail?”

    Reviewing the OrgX carousel engine · July 2026
  • “We could do better on visual repetition that doesn’t have accompanied significance.”

    Reviewing the OrgX carousel engine · July 2026
  • “Trains of thought, and thinking rockets.”

    On extending cognition · January 2026
  • “There is no drought. There’s only a flood and there will only be rain…”

    A voice note · May 2025
  • “I believe solutions should be accessible. Discovery should be democratized.”

    In a working session · October 2026
Now / October 2026

Building OrgX in public, and Open Becoming on paper.

Proof for AI-delivered work by day; a companion for becoming more in the margins. Open to founder collaborations and senior or staff roles where systems depth, product judgment, and AI-native execution all matter at once.