Cross-functional Collaboration

Connecting people, context, and decisions across different parts of a project.

  • Working with developers
  • Working with UI/design contributors
  • Aligning product and implementation
  • Coordinating with business stakeholders
  • Giving and receiving implementation feedback
  • Making dependencies visible
  • Maintaining shared context
  • Turning conversations into documented decisions

A significant part of my work happens between roles rather than inside a single discipline. I work with technical and non-technical teammates to clarify decisions, surface dependencies, review outcomes, and keep work moving.

Systems, Documentation & Operations

Creating enough structure for complex work to remain understandable and executable.

  • Project structure
  • Task breakdown
  • Ownership and priorities
  • Decision logs
  • Documentation systems
  • Source-of-truth thinking
  • Roadmap and milestone tracking
  • QA workflows
  • Release/readiness tracking
  • Operational follow-through

I care about reducing information loss between a decision and its execution. I use documentation, task structure, ownership, dependencies, and clear sources of truth to make projects easier to operate and revisit.

Analytical & Scientific Thinking

A physics background shapes how I approach complex and uncertain problems.

  • Quantitative reasoning
  • Mathematical problem solving
  • Breaking complex systems into smaller components
  • Working with assumptions and constraints
  • Comparing competing explanations
  • Identifying inconsistencies
  • Evidence-oriented reasoning
  • Computational thinking

Studying physics has trained me to be comfortable with abstraction, uncertainty, mathematical reasoning, and systems with many interacting variables. My computer science minor is extending that foundation toward algorithms and computation.

AI-assisted Work

Using AI as a tool for analysis, research, implementation, and operational leverage.

  • Structured research with AI
  • Comparing options and trade-offs
  • Drafting and reviewing documentation
  • Codebase exploration
  • Implementation assistance
  • QA assistance
  • Information synthesis
  • Building repeatable AI-assisted workflows

I use AI extensively, but not as a substitute for ownership or judgment. I use it to increase the amount of context I can process, test alternatives faster, assist implementation, and make repetitive work more systematic.

TOOLS I WORK WITH

Product & Knowledge

  • NotionProduct context, tasks, decisions, roadmaps and documentation.
  • FigmaUI review, flows and design-development communication.

Development & Delivery

  • GitHubCode, version history and development collaboration.
  • VercelDeployment and release verification.

AI

  • ChatGPT / CodexResearch, analysis, implementation support, QA and structured workflows.

CURRENTLY DEVELOPING

Areas I’m actively building toward through university study, projects, and independent learning.

Algorithms & Computer Science

Building a stronger formal foundation through my Computer Science minor.

Quantum Computing

Exploring the intersection of quantum physics, computation and algorithms.

Machine Learning

Developing the mathematical and computational foundations needed to use ML more rigorously.

Research Practice

Working toward a more formal research trajectory connecting physics and computation.