Summary for Recruiters
Principal/Senior Software Engineer (Full‑stack with a strong Frontend & Platform focus). I join product teams and deliver new features, measurable improvements to performance, reliability, and developer experience improvements. Comfortable moving between hands‑on delivery and light technical leadership.
- Location/timezone: UK (GMT/BST)
- Engagements: audits, scoped delivery projects, or fractional/staff‑aug (part‑time)
- Sectors: buildtech, fintech, crypto, SaaS, e‑commerce, logistics/operations, and more
What I’m good at
- Frontend architecture and performance: React, TypeScript, route‑level code‑splitting, design systems, Core Web Vitals hygiene
- Full‑stack pragmatism: .NET/C# APIs, Ruby on Rails background, REST/JSON APIs, Docker‑based environments
- Developer experience (DX): testing strategy, CI reliability, build tooling, documentation and diagrams (Mermaid)
- Team enablement: code reviews, raising code quality, levelling up standards without slowing delivery
Recent/representative work
- Senior Full‑stack Engineer at Sterling DCS (employee): building React + TypeScript apps with MUI over .NET APIs in Docker; code reviews across frontend and backend; documentation with Mermaid sequence/flow diagrams; working in agile sprints with stakeholders.
- Open source: authored Ruby gems jekyll‑esm (ESM modules for Jekyll), jekyll‑webpack (Webpack integration for Jekyll), rokaki (search filter helpers), and the npm package vorm‑validations.
Ways I can help (scoped offers)
- Performance tune‑ups: code audit, prioritized fixes, DX optimisation to improve delivery and prevent regressions.
- Frontend platform upgrades: TypeScript hardening, testing optimisation, CI stabilization, component library hygiene, documentation.
- Full‑stack feature delivery: implement an end‑to‑end slice across React/TypeScript and .NET API, with tests and clear handover.
Core tools and tech
- Languages: TypeScript/JavaScript, C#/.NET, Ruby (Rails)
- Frontend: React, Redux, MUI; experience with Angular, Vue, React Native, Elm
- Platform/Tooling: Docker, Git/GitHub, CI, JetBrains Rider, Vim
- Collaboration: Jira, Confluence; Trello, Gitub, diagrams and docs with Markdown + Mermaid
How I work
- Diagnose → prioritize → implement → test & measure → release. I follow the pareto principal (80/20 rule) as a rule of thumb when building complex features.
References & code
If this sounds useful for your team, feel free to get in touch to discuss scope and availability.