The code making your money and the code scaring your engineers
is usually the same code. That's where I work.
Forward deployed and product engineering aren't a pivot for me - they're newer names for how I've worked since the start. Requirements-first, full lifecycle, in the room with the people who'll use the thing. What's new is the tooling: RAG pipelines, agentic workflows, and building against foundation model APIs.
That's covered e-commerce, retail, higher education, legal, startups and agencies, across 25+ engagements. I'm hands-on, and I get involved beyond the code - helping teams understand complex systems, reduce risk, and make better decisions when the trade-offs aren't obvious.
The problems are rarely industry-specific. They come down to systems that have grown faster than the people maintaining them.
| monthly infrastructure spend |
saved through automation on a single project |
peak checkout response time |
mentored across teams |
Owning the why, not just the how. Scoping what to build in the room with the people who'll use it, rather than from a spec handed down by someone else.
Integration across systems. Connecting client products to in-house APIs and platforms, and the reverse, so both sides hold up in production.
Training and enablement. Teaching the people who inherit the system, not handing it over and moving on.
Ongoing maintenance. Staying accountable after ship - support, fixes and iteration, not one-time delivery.
I've also shipped the unglamorous end of this: stopping a six-figure stock exploit, moving 10,000+ products off spreadsheets, and designing a 30+ table schema in 18 days.
I develop the way I deploy - containerised, terminal-first, on an immutable base - so what runs on my machine isn't a special case.
I built systems for years before AI tooling existed, which is why I can use it well now. Retrieval pipelines, agentic tooling, and API integration against foundation models, plus the evaluation and guardrail work that keeps them usable once real people are on them.
| Languages |        |
| Frameworks |        |
| Data |      |
| Infra |           |
| APIs & payments |       |
| Observability |     |
Full tech list - everything I've worked with, including the old stuff
Languages - PHP, Python, Rust, Node.js, JavaScript, TypeScript, Bash, Perl, BASIC, Turbo Pascal, Progress 4GL, SQL
Backend frameworks & runtimes - Laravel, Lumen, Laravel Octane, FrankenPHP, Swoole, Symfony, FastAPI, CodeIgniter, CakePHP, Yii, Ruby on Rails
Frontend & templating - React, Next.js, Vue.js, Livewire, Alpine.js, Tailwind CSS, GraphQL, HTML, CSS, SCSS, Bootstrap, Zurb Foundation 6, jQuery, Twig, Liquid
CMS & e-commerce - Drupal 6, Drupal 7, Drupal 8, Drupal Commerce, WordPress, WooCommerce, Shopify, TerminalFour
Databases & caching - PostgreSQL, MySQL, MariaDB, SQLite, Microsoft Access, Redis, Apache Solr, phpMyAdmin, database design and optimisation, multi-tenant schema design, PII separation
DevOps & infrastructure - Docker, Podman, Caddy, AWS, Azure, DigitalOcean, Cloudflare, Vercel, Jenkins, BuddyWorks, Nginx, Apache, RabbitMQ, Linux, Fedora, Debian, Windows, Rackspace, tmux
AI & LLM tooling - Claude Code, Anthropic API, OpenAI API, Ollama, MCP, Laravel Boost, RAG pipelines, agentic workflows, local model hosting
Tooling, QA & monitoring - Git, GitHub, Bitbucket, Composer, Xdebug, PHPUnit, XHProf, Postman, Swagger / OpenAPI, Jira, Sentry, Datadog
Payments, APIs & integrations - Stripe, PayPal, Klarna, WorldPay, JWT, LaunchDarkly, Zapier, Microsoft Dynamics CRM, FormStack, Campaign Monitor, SendGrid, Mailchimp, Google Analytics, Google Ads, Facebook API, TextLocal SMS, Postcode Anywhere, Call Credit API
Data formats - JSON, YAML, XML
Methods & delivery - OOP, SOLID, MVC, microservices, REST, multi-tenant architecture, security hardening, payment API security, PII-aware data modelling, Agile, Scrum, Kanban, CI/CD, unit / integration / UAT / browser testing, architecture, technical leadership, documentation, training, SEO, accessibility, reverse engineering
GIAC Security Essentials (GSEC) and GIAC Foundational Cybersecurity Technologies (GFACT).
I've hardened payment flows, caught address-bypass and stock exploits before they cost money, and built PII handling in from the start rather than retrofitting it.
PHP from Zero - designed, built and shipped on my own. No team, no brief, no external deadline. It teaches beginners PHP with clear explanations and practical examples. Proof I can scope, build and ship a complete thing end to end.
I own the code. Claude decided I didn't. - Claude Code found a ToS file in my own repo, then decided I wasn't licensed to use my own API.
You've been a polyglot this whole time. - Ask most engineers what they do and you'll get a framework back.
My GitHub was a graveyard. So I deleted 30+ repos. - I started on GitHub in 2010. Last week I went through every single repo.
More at amarjit.uk and dev.to/byamarjit.
Most of my work lives in private client repos. What's public here is the smaller stuff.
Sometimes the fastest fix is someone from outside - no history with the codebase,
no stake in past decisions. LinkedIn is the best place to reach me.