Sarma Portfolio
A hire-me page backed by 25 public GitHub repos with real commit history, dependabot-verified security patches, and a live zero-knowledge AI chat product he built and shipped solo.
Location
Hemel Hempstead, Hertfordshire, United Kingdom
Skills
Notable
- 25 public GitHub repositories under sarmakska, with real multi-month commit histories, dependabot security patching, and open issues/PRs on the flagship repo
- sarmalink — a live, shipped BYOK AI chat product with client-side AES-256-GCM/PBKDF2 encryption and 17-provider failover, running in production at ai.sarmalinux.com
- SarmaLink-AI — an OpenAI-compatible multi-provider LLM gateway with 36-engine failover across 7 providers, MIT-licensed, 7 GitHub stars, 3 forks
What makes it work
A breakdown of the choices that make this portfolio stand out.
Every claim on the page links to checkable evidence
Each capability row ends in "Evidence:" followed by a specific GitHub repo, product page, or blog post — not a generic "see my work" link. Following github.com/sarmakska/Sarmalink-ai confirms the claims directly: 67 commits, a real commit log going back through 2026, dependabot-authored dependency bumps with green "Verified" badges, 5 open issues, 5 open PRs, a CONTRIBUTING.md and SECURITY.md. This is what an actively maintained open-source project looks like, not a portfolio repo created for show.
Self-scored capability matrix instead of a skills cloud
Instead of a wall of unranked tech-logo badges, the page scores eight capability areas out of 5 and says outright "not maxed across the board, because that would not be true." That single sentence does more credibility work than any amount of superlative copy — it reads as an engineer being honest about depth versus breadth rather than a marketer inflating a resume.
A live, working product as the flagship proof point
sarmalink at ai.sarmalinux.com is presented as the "densest piece of evidence... because you can open it in a browser right now" rather than a screenshot or a demo video. Client-side AES-256-GCM encryption with PBKDF2 at 600,000 iterations and multi-provider failover across seventeen LLM providers are specific, checkable technical claims, not vague "built an AI app" language.
Explicit, unglamorous constraints on what he wants
The page spends real space on "PAYE only, not contract, not Inside IR35" and "United Kingdom only" — details that filter out mismatched recruiters rather than casting the widest possible net. Combined with a personal blog that includes F1 write-ups and a Samsung phone review alongside the engineering essays, the whole site reads like an actual person's corner of the internet rather than an agency funnel dressed up as a portfolio.
What AI Agent Architects can take from this
Specific, actionable tips to apply to your own portfolio — no generic advice.
Link every capability claim to a specific piece of evidence — a repo, a PR, a whitepaper — instead of a generic "portfolio" or "GitHub" link at the top of the page. Specificity is what makes a claim checkable.
State a self-assessed limitation somewhere on the page ("not maxed across the board, because that would not be true"). One honest caveat does more for credibility than ten more superlatives.
If you have a live product, lead with the URL to the running thing, not a screenshot. A hiring manager who can click through in ten seconds trusts the rest of the page more.
Say plainly what kind of role and work arrangement you will and won't take (contract vs. permanent, location, seniority). It reads as confidence, not as narrowing your options.
Keep non-engineering personality on the site (hobbies, opinions, reviews) alongside the professional content — it is one of the more reliable signals that a site is a real person's and not a template.
More AI Agent Architect portfolios
Ready to build your portfolio?
Follow the AI Agent Architect roadmap — skills, projects, and timeline to get hired.