I started from operations, which is why I design from the failure case.

I began as a Salesforce administrator at a consultancy in 2022, working across several client industries at once. That start matters: before I wrote much Apex, I spent a year watching what actually breaks in a live org — permissions nobody documented, automation layered on automation, and processes that only worked because a particular person remembered a particular step.

From there the work moved toward development and then integration. At Marakez I delivered the Salesforce integration with Oracle Fusion Accounts Receivable — and found that a custom payment-plan engine was calculating Net Present Value incorrectly, which meant the instalment schedules going out to property buyers were wrong. Correcting that taught me more than the integration did: financial logic fails plausibly, and nothing catches it except checking the arithmetic.

At Khazenly I owned the Salesforce side of warehouse and fulfilment integration end to end — the data model, the API surface, the reconciliation logic, and the interface people actually used, with AWS Lambda as the middleware between Salesforce and external delivery providers. At IBM I saw how enterprise delivery works when governance, knowledge transfer, and formal standards are not optional.

Today I am a Senior Salesforce Developer at Emaar in Dubai, where I designed and implemented the end-to-end integration with the Dubai Land Department and OQOOD systems that automates property unit registration. The constant across all of it has been the same: the interesting problems are almost never inside Salesforce. They are at the boundary, where Salesforce has to agree with something it does not control.