Hands-on across marketing, e-commerce, and the code that supports it.
I'm Febin — a UAE-based e-commerce and digital marketing specialist. My work sits at the point where advertising, search, storefronts, and the underlying website all have to work together, and I've spent most of my career making sure they actually do.
I started out on the marketing side — running paid search and social campaigns — and kept bumping into the same wall: the campaign would be solid, but the landing page, the product feed, or the storefront behind it would quietly undo the work. So I picked up the web development side too, first customizing themes, then building full features, then eventually full internal tools, so I wasn't stuck waiting on someone else to fix what the data was telling me to fix.
That's the shape of my background today: enough on the marketing side to plan and run campaigns end-to-end, and enough on the development side to build or fix what those campaigns point to.
How I got here
Starting in paid search & social
Began managing day-to-day Google Ads and social campaigns for small retail and service accounts — learning the mechanics of bidding, audiences, and reporting from the ground up.
Taking on full digital operations
Moved into a role covering SEO, marketplace storefronts, and the Shopify and WordPress sites behind the campaigns — managing several brands and properties at the same time rather than a single account.
Picking up custom development
Started building internal tools and storefront features in Laravel and PHP where existing themes or plugins fell short — closing the gap between what a campaign needed and what the site could actually deliver.
Connecting marketing and development
Currently focused on running Google Ads, SEO, and marketplace operations across multiple storefronts, while building and maintaining the Shopify, WordPress, and custom-built sites they rely on.
Engineer first. Developer next. Marketer by necessity.
A computer science degree was the starting point, not digital marketing — four years learning how systems are actually built, followed by an early stretch writing code and customizing themes for other people's projects. Digital marketing came later, almost by accident: campaigns kept failing for reasons that had nothing to do with the campaign itself, and nobody else around was positioned to fix both sides.
That ordering ended up being the useful part. Most marketers learn just enough development to ask for changes; most developers learn just enough marketing to follow a brief. Coming at it from the engineering side first means campaigns, tracking, and the website behind them get planned as one system instead of being handed off between two people who don't fully understand each other's constraints.
What this approach looks like day to day.
Clear, direct communication
Plain language over jargon, and issues get flagged as soon as they're found rather than saved for a scheduled report.
Decisions backed by data
Every recommendation traces back to a number in GA4 or an ads account — not a hunch about what should be working.
Documentation, not dependency
Setups and handovers get written down, so a process doesn't quietly depend on one person remembering it.
Realistic timelines
Expectations get set early, and a blocker gets flagged the moment it appears instead of letting a deadline slip quietly.
Continuous learning
Google Ads, SEO, and Shopify all change constantly — staying current with each one is treated as part of the job, not extra credit.
Structural fixes over quick wins
A short-term number that fades in a month isn't worth chasing if it means leaving the underlying structure broken.
A few things I keep coming back to
Structure beats effort
A well-structured account or site with modest daily attention usually outperforms a messy one that gets worked twice as hard. I'd rather fix the structure first.
Channels compete for the same buyer
When a brand sells across its own site, a marketplace, and paid search at once, those channels are often quietly bidding against each other. Worth checking before blaming any one of them.
If it's repeated, it should be built
Any report or task I find myself doing manually more than a few times becomes a candidate for a small internal tool — that's usually where the custom development work starts.