Technology & OperationsRitesh Kumar · Technology & Operations
I turn complex operations into systems that actually work.
I work across technology, IT and global operations. I find the problem, design the system around it, deliver it with AI-assisted development, then run it in production. Right now that means 13 markets at PERGOLUX.
- 13 markets
- Internal systems
- IT operations
- AI-assisted delivery
€267M
Revenue supported
€64M+
Paid media governed
55,000+
Assets shipped
13
Active markets
13
Internal apps on one platform
Profile
An operator who ended up owning the technology.
I studied Computer Science, then spent eight years in creative and global operations. The messy, high-volume kind, across thirteen markets and every timezone that implies. That is where the systems thinking came from. You cannot run production at that scale without learning exactly where it breaks.
The bigger the operation got, the less the answer was more people. It was better systems. Internal tools instead of spreadsheets. Automation instead of chasing. One login instead of nine. A network that works in the warehouse as well as the office. So I started building those, and the remit grew to match: creative operations, then business systems, then technology and IT.
I am not a software engineer and I do not claim to be. What I do is understand an operational problem properly, decide what the system has to do about it, direct the build with AI coding tools, check the result against reality, and then run it. Business context plus the ability to actually ship and operate the thing. That combination is the work.
- Based in
- Berlin, Germany
- Currently
- Senior Creative Marketing Manager (Global)
- PERGOLUX GmbH · Global creative operations, technology and IT
- How I deliver
- I decide what the system has to do and which rules it has to hold to. AI coding tools write the implementation while I direct it. Then I test the output against real data and run whatever ships. The judgement and the ownership are mine. The code is one mechanism.
Method
How the systems actually get made.
Every system on this page came out of the same five steps. The interesting part is not step three.
01
Find the real problem
I am usually already running the broken process, so the problem never arrives as a requirements document. It is the thing that went wrong last Tuesday, plus the reason it is going to happen again.
02
Design the system
What should it do, what should it refuse to do, and which rules hold it together. Get this wrong and no amount of good code saves it. It is judgement, not typing.
03
Implement with AI assistance
The rules become a working tool through AI coding tools. I direct the build and make the trade-off calls. I am not hand-writing the code and I do not pretend otherwise.
04
Test against reality
Run it on real data and go looking for the answers that are wrong. Every rule in every system I have built is there because something specific broke first.
05
Operate it
Ship it, own it, fix it at 8am when it breaks, keep it running once the novelty is gone. Side projects skip this part. Businesses need exactly this part.
I decide what the system has to do and which rules it has to hold to. AI coding tools write the implementation while I direct it. Then I test the output against real data and run whatever ships. The judgement and the ownership are mine. The code is one mechanism.
What I build
Systems in production, not slideware.
Six areas of work, and the systems they turned into. All live right now, in front of real users.
Technology Operations
Business Systems
Workflow Automation
AI-Assisted Delivery
Global Operations
Creative Operations
The App Kit & Playbook
The template, toolkit and written playbook every new internal application starts from. Access rules, deployment, safety checks, a go-live guide. The road, not the buildings on it.
The standard other teams build on
Internal system, not publicUGC Rights Tracking
Tracks how long influencer content can legally be used and warns the responsible person before the rights expire. Turned a real compliance exposure into something that runs on its own. Part of CreativeOS.
CreativeOS module · automated rights tracking
Internal system, not publicHTML Viewer
Turns a generated HTML file into a clean, mobile-friendly link that stays put, so nobody downloads a raw file and fights with it. Small, and used constantly.
Internal tool · live in production
Internal system, not publicDelivery under pressure
The work the systems ship.
Two launches I ran end to end. The live ads are public, so the work can be checked rather than taken on trust.
Flagship Launch
Series 4 Launch
The biggest product launch, live in 13 markets at once, on a fixed deadline, with half-finished source material to work from. I found the gaps early, pulled production and localisation onto one plan, and brought in external CGI at a price I negotiated to protect the date. It landed on time.
New Category
Awnings Launch
A brand new product category across several markets, with no process for it yet. I designed the delivery workflow from intake through production to each local version, then ran it.
Career trajectory
Creative execution to technology ownership, in eight years.
Official titles stay as they are. What changed underneath them is the scope: from producing assets, to running global delivery, to owning the systems and the IT the operation runs on. Open any role for the actual remit.
PERGOLUX GmbH
Germany / Global
Senior Creative Marketing Manager (Global)
Mar 2026 – PresentThe title is a creative one. The remit is technology and operations. I run global creative delivery across 13 markets, and I own the internal systems and the IT infrastructure that work runs on.
Global Creative Marketing Manager
Aug 2025 – Mar 2026Global delivery across 13 markets. This is where the job stopped being campaign management and started being workflow design.
Junior Creative Marketing Manager
Aug 2024 – Jul 2025High-volume production across markets. A ground-level view of which parts of a creative operation break, and why.
E-commerce & Marketing Manager
IMbesharam.com
A contract role fixing a fragmented operation. Three functions, no shared cadence, aggressive timelines.
Working Student – Product Photographer
Zalando
Inside one of Europe's largest e-commerce operations, which is where I learned what a genuinely industrialised production system looks like up close.
Digital Marketing Manager
AADS Pvt. Ltd.
Four years owning an integrated digital function end to end, and building the team that ran it.
Toolkit
What I use to deliver.
Technologies and systems I work with to get outcomes shipped and kept running. Not a claim to senior engineering depth in every line of it.
AI-Assisted Development
CLAUDE CODE · CHATGPT · CODEX · CLAUDE API · LLM AGENT DESIGN
Applications & Automation
NEXT.JS · REACT · TYPESCRIPT · TAILWIND · SUPABASE · POSTGRES · INNGEST
Cloud & Delivery
CLOUDFLARE · VERCEL · GITHUB ACTIONS · SEMGREP · TRIVY
IT & Access
SSO · RBAC · MFA · APPLE MDM · UNIFI NETWORKING · REDIS
Creative Systems
FIGMA · CANVA · PICS.IO DAM · PHOTOSHOP · PREMIERE PRO · AFTER EFFECTS · DAVINCI RESOLVE
Operations
GOOGLE WORKSPACE · TICKETING · NATIVE KANBAN · DOCS & RUNBOOKS
Academic foundation
Where the systems thinking started.
A Computer Science degree is why technical conversations are not a translation exercise. The MBA is why they end in a business decision.
Master of Business Administration
Marketing Management
Berlin School of Business and Innovation • Berlin, Germany
Thesis: Investigating 'The Impact of Social Media Influencers on Brand Perception'
Bachelor of Technology
Computer Science and Engineering
GITAM University • Visakhapatnam, India
The reason technical conversations are not a translation exercise for me. It is where the systems thinking and the structured problem solving started. It is not a claim to current engineering practice.
Establish Connection.
For technology operations, business systems, IT and automation roles. Or a focused conversation about turning an operational mess into something that runs.