About
Tilak Raj
Salesforce developer & DevOps engineer, working where delivery automation meets AI.
Bio
I've been building software professionally since 2015. I started out at Lumen and have since worked across product companies, consultancies and global system integrators — LeaseWorks, Deloitte, NTT DATA, Quess Corp, Brillio, and today Confluent. Along the way my focus settled on the Salesforce Platform and the engineering discipline around it: clean Apex, solid integrations, and delivery pipelines that make releases boring.
More recently that work has grown to include AI — Python automation and agentic, LLM-powered workflows wired into CI/CD, with evals to keep them honest. I care about software that stays simple to reason about as it grows, and I write about what I learn here.
Professional journey
A winding path from where it started, in 2015, to where I am now.
What I do
- Salesforce development — Apex, Lightning Web Components, Flows, triggers and trigger frameworks, SOQL performance, and platform events. Code that is testable, readable, and respects governor limits.
- Integrations — REST and SOAP APIs, named credentials, platform events and middleware patterns to connect Salesforce with the systems around it.
- DevOps & CI/CD — source-driven development with Salesforce CLI and scratch orgs, Git branching workflows, and CI/CD pipelines (GitHub Actions / Azure DevOps) that run automated Apex tests, PMD static analysis and release tooling such as Gearset and Copado on every change.
- AI & agentic workflows — building LLM-powered and agentic automations: retrieval, tool-calling, and multi-step agents that do real work, wired into existing systems and kept honest with evals and guardrails.
- Python & automation — Python for glue code, data tasks, small CLIs and the scripts that hold a pipeline together, from local dev to production.
- Org health — paying down technical debt, untangling unmaintainable automation, and turning change sets into a real, reviewable delivery pipeline.
How I work
- Small changes, reviewed, and shipped often.
- Tests are part of “done” — not a follow-up ticket.
- Automate the repetitive parts of a release so people do the interesting parts.
- Write it down, so the next person (often future me) doesn't start from zero.
About this blog
This site is my engineering journal — Salesforce architecture and Apex patterns, DevOps and CI/CD, Python tooling, and experiments with agentic AI and LLMs, plus the debugging stories in between. Writing a problem down forces clarity, and if a post saves someone else an afternoon, even better. New posts land on a near-daily basis; the blog page is the fastest way to keep up.
Looking to work together?
I'm always keen to connect with like-minded people who need a hand with Salesforce development, DevOps & CI/CD, or AI automation — a build, a rescue, a pipeline, an integration, an agentic workflow, or a second pair of eyes on a review. If you have professional work along those lines, let's talk.
Elsewhere
GitHub LinkedIn X Facebook Stack Overflow DEV Community RSS feed Email