Skills
Capabilities, and what backs them
A skill on its own is a claim. Each one here links to the work that demonstrates it, which is the difference between a list and an argument.
- Skills
- 36Skills
- Backed by evidence
- 35Backed by evidence
- Evidence links
- 88Evidence links
AI
AI infrastructure
Multi provider platforms, provider abstraction, and the operational side of running language models in production.
Evidence
AI evaluation
Assessing generated code, architecture, security reasoning, and prompt quality for technical correctness.
Deep learning and computer vision
Training and evaluating vision and multimodal models, and explaining what they decided.
Agentic AI systems
Autonomous reasoning pipelines, tool use, and retrieval augmented generation.
Evidence
AI security and safety
Securing AI systems, responsible deployment, and the ethics that has to sit alongside it.
Cloud
AWS
S3 for the object storage behind the enterprise platforms, and EC2 for the machines they run on.
Evidence
Google Cloud Storage
One of the interchangeable backends behind the regulatory platform's storage layer.
Evidence
Cloudinary
Media storage and delivery across the enterprise products.
Evidence
Architecture
Distributed systems
Event processing, microservices, and system design for platforms that stay up.
API design
REST and gRPC interfaces built to be used by people other than their author.
Practice
ESG and sustainability reporting
Carbon accounting under the GHG Protocol and ISO 14064-1, and the reporting workflows built on top of it.
Evidence
Regulatory technology
Compliance systems for government and international bodies, where the rules are the specification.
Evidence
Languages
Go
Backend services, distributed systems, and platform engineering.
Python
AI systems, security tooling, and backend services.
Solidity
Production smart contracts, upgradeable patterns, and ERC standards.
Noir
Zero knowledge circuits, where the work is expressed as constraints rather than as statements.
Evidence
TypeScript
Typed frontends and the client libraries that talk to them.
JavaScript
SQL
Evidence
Bash
Operational scripting and the remote command surface behind SSH driven tooling.
Evidence
Lua
Server side scripting inside Redis, where a scan or a mutation has to run as one atomic step.
Evidence
Arduino
Microcontroller programming, and the embedded end of the hardware and software boundary.
Infrastructure
Infrastructure automation
Discovering, configuring, and verifying Linux servers over SSH, across nine platform families.
Object storage
A storage layer written against the idea rather than a vendor, so local disk, MinIO, S3, and a cloud bucket are a setting rather than a rewrite.
Evidence
Docker
Containerised services, reproducible builds, and CI through GitHub Actions.
Blockchain and protocol
Protocol architecture
DEX design, liquidity systems, order books, intent based architectures, and account abstraction.
Zero knowledge proofs
Circuits, commitments, nullifiers, and proving a fact without disclosing what makes it true.
EVM internals
Bytecode level analysis, cross chain infrastructure, and multi chain systems.
Evidence
Security
Smart contract auditing
Vulnerability research, exploit development, and formal verification against deployed contracts.
Protocol security
Threat modelling, attack surface assessment, and security controls at the protocol layer.
Security automation
Continuous monitoring, threat intelligence, and automated analysis rather than one off reviews.
Frameworks
FastAPI
The framework behind the enterprise AI platforms, the document intelligence layer, and the container tooling.
Django
The framework the freelance work started on in 2020, and still what the first deepfake detection system runs on.
Evidence
Operations
Monitoring and observability
Knowing what a production system is doing before someone reports that it is not.
Databases
PostgreSQL
Relational modelling, constraints that enforce rules the application cannot forget, and full text and vector search in the same database.
MongoDB
Document modelling for records whose shape is set by the framework being analysed rather than by a schema, across both async and synchronous drivers.