Languages
PROJECTS — Fortran/OpenMP numerics, Go microservices, TypeScript SDK & widgets.
Capabilities
A breakdown of technologies, frameworks, and domains I work with, referenced against the production systems, data pipelines, and research projects where they were used.
01 / Capability map
PROJECTS — Fortran/OpenMP numerics, Go microservices, TypeScript SDK & widgets.
REFERENCE — rules engine evaluating eligibility under peak event traffic.
REFERENCE — embeddable wallet widget and public developer SDK.
REFERENCE — on-device cryptographic signing, multi-tenant data isolation.
CERTIFIED — C100DBA, MongoDB Certified DBA Associate.
REFERENCE — serverless ETL pipelines on AWS, containerised models in production.
CONTEXT — self-hosted and self-provisioned; see self-directed work below.
REFERENCE — embedded multi-chain wallet released as open source.
REFERENCE — out-of-core processing of ~2 TB ocean datasets, LSTM failure prediction in production.
REFERENCE — generating and post-processing an ensemble of ~20k scenarios.
REFERENCE — re-engineered particle core with OpenMP parallelisation.
CONTEXT — running models on constrained hardware, and wiring local and hosted APIs into a single agent harness.
02 / Self-directed work
Proxmox for LXC provisioning, Terraform for declarative infrastructure as code, a self-hosted mesh VPN with WireGuard and Headscale, and dynamic DNS automated via the Cloudflare API. Maintaining this platform provides hands-on familiarity with Linux networking and the operational layers underneath production application services.
Running local inference with llama.cpp, evaluating quantization tradeoffs for resource-constrained deployment, and developing agent harnesses that integrate self-hosted models with cloud APIs for automated development workflows.
03 / Where this fits
01
Production microservices, REST and gRPC APIs, and data pipelines — taking full responsibility from architecture through CI/CD and day-2 operations with clear interfaces and clean operational ownership.
02
Simulation, modelling, and geospatial data platforms where mathematical accuracy is essential and software engineering standards ensure reproducible, verifiable results.
03
Comfortable working with ambiguous requirements, investigating legacy codebases, and seeing systems through from initial architecture to daily operational maintenance.
04
Based in Santander, Spain, working hours that overlap European and American teams, with disciplined asynchronous written communication habits.
04 / Contact
Open to discussing backend engineering roles, scientific computing projects, and distributed systems challenges. Feel free to reach out via email or LinkedIn.