The people behind Carpathian

A small team, which means the people listed here are the ones who scope the work, write the code, run the infrastructure, and answer when something needs attention. Each profile goes into what that person works on and how they got here.

How the team is put together

The team is deliberately small. The person who scopes a project is the person who builds it, and the engineer who provisioned a server is the one who answers when it needs attention. That is a structural choice rather than a stage the company is passing through.

Backgrounds vary more than the titles suggest. Cloud architecture and machine learning sit alongside military cyber warfare, a decade of vulnerability management and incident response, operations and community work, and fifteen years of software consulting. The spread is what makes internal review worth doing, because the person checking a security model is rarely the person who drew it.

Disciplines on the team
  • Cloud architecture
    Platform architecture, multi-tenant systems, and the hybrid cloud environments customer workloads run on
  • Security
    Vulnerability management, incident response, and the review a system goes through before it reaches production
  • AI engineering
    Model hosting, retrieval, and the AI features that get built into customer applications
  • Operations and delivery
    Project structure, team support, and the processes that keep work moving between the people doing it