You asked for both. I have been both since 2008.
Elite full-stack engineer. Elite creative-tool expert. Most people reach that pairing by adding design to engineering. I arrived the other way. Design was the professional practice first, over 200 logos and identity systems before the first production system, and the engineering was built on top of the craft. Designer, engineer, product, business, founder, in that order.
This is one of very few postings I have read and thought: that is the job. The interest runs both ways, so I built this the way I work. Evidence first, in the open, including the line I don't clear.
Four jobs, one person. The posting asks for two of them in the same body; these are the other two that came with it.
Photoshop and Illustrator were the profession before code was. Identity marks, campaigns and collateral, hands-on.
, sole-engineered and live. 247 commits, roughly 96k lines, about six dollars a month to run.
Co-founded a studio and grew it to 22. Founded and still own a restaurant brand, capital and all.
Ten client geographies, Zürich to California. Remote-first since 2020, and moving for the right seat.
Your four gates, answered.
The posting sets four and says: not three out of four. Here is exactly where each one stands. Three clear with evidence you can check. One does not.
Three of four, plainly. This is the line I don't clear. What I do have: hard rooms won, including a live unscripted AI demo that changed a client's whole technology bet, and sustained public on-camera work in the French series. Neither is the same as commanding a Fortune 100 boardroom. It is also the one gap on this list I am most interested in closing. The demo instinct is there. The stage reps are not.
The craft predates the code.
Years of identity and print work came before engineering became the main thing. It is why the interface work starts in Figma rather than in components, and why the design judgement on a client project is mine to give.
No interaction to explain the idea, no second screen, no copy to lean on. The whole character of a business has to survive a signboard, a package and a phone screen at once.
Illustrator and Photoshop, by hand. Dairyland Bangladesh, East Bengal Closet and 's own mark, drawn to hold on signage, on packaging and on a phone screen.
See the marks, roughly two years as design lead. Brand, campaign, social and print collateral through the COVID delivery era, produced hands-on rather than art directed at a distance.
See the campaign workAxis. A field-operations platform designed around a worker-first permission model, with live dispatch, minute-by-minute trail replay and evidence-gated task completion.
See the interface. An entire brand produced generatively on a multi-model node canvas, running two sections down this page.
See the brand, sole-engineered and live, with its interface and design system produced entirely through Claude Design and Claude Code over MCP rather than in a drawing tool. This site runs a Gemma 4 E2B model entirely in the visitor's browser, and every fit page on it is a bespoke component set designed to that company's brand.
See WiregentHands on the file, not directing someone else's. The images live on the case studies, where they carry captions and context. This page carries the claim and the address.
And the pipelines are already built.
The posting asks for hands-on experience building multi-step automated workflows: ComfyUI, n8n, or similar. n8n is named verbatim in nine years of delivery, orchestrating workflows and pipelines for internal developer productivity and platform integrations.
In August 2026 Adobe added Google's Gemini Omni Flash to Firefly, where it joins models from Kling AI, Luma AI, OpenAI and Runway. Choosing per job is the product decision, and it is the one this pipeline makes six times over.
Multi-model node workflows on canvas boards, driving content generation end to end. Seedance, Kling, Minimax, Veo and Nano Banana wired as nodes, producing plate blueprints and campaign assets for a restaurant that did not exist yet.
A brand, produced on a node canvas.
The posting lists Firefly Creative Production and Workflow Builder as things to ramp into. This is the same shape, already running: a multi-model generative pipeline on canvas boards that produced an entire restaurant brand before the kitchen existed. Every stage below shipped.
A single board carrying the whole visual argument for a Southeast Asian fusion concept that did not exist yet.
A board, not a deck. Direction you can point at beats direction that has to be read.
Hyper-realistic plate layouts generated as direct blueprints, not mood boards.
6 modelsModel choice is an engineering decision with a cost curve and a quality curve attached. Six models, each doing the one job it wins at.
The generated image became the spec the kitchen cooked against.
Zero R&D food wasteA render is only worth something if a kitchen can cook it. A human closes this loop, which is the difference between a pipeline and a demo.
Commercial photography and videography replaced outright.
$10,000+ savedThis is where the pipeline stops being a craft exercise and becomes a line on a budget.
: founded, designed and launched by one person, now finalising a flagship in Dhanmondi, Dhaka.
4 pop-up runsOwned, not delivered. The risk, the capital and the reputation were mine, which is a different kind of accountability from shipping someone else's roadmap.
What the record actually shows.
Three claims from this page, each with the number that backs it.
went from scaffold to working platform in eight days, with the test files growing faster than the code they cover.
's entire brand came out of a multi-model generative pipeline before the kitchen existed.
Compliance moved from a retrofit at the end of a build to a constraint at the start of one, across five platforms.
The stack this seat actually needs.
Grouped the way the posting is written rather than as an inventory. Every line is something the work above depended on.
What you need.
The posting’s own list, line by line, with the evidence against each one.
Eighteen years of professional delivery, and both halves of this posting have been running the whole time. Design practice from 2008. UNDP in 2015. from 2017, on a title track from UX Engineer to Principal Software Engineer to Principal Staff to Engineering Manager to CIO. The pattern the line asks for: ran six years as a Zürich client before Loopcloud acquired it, 's ERP is still run by the client with support as recently as 2024, and 's patient records remain in active use at Bangladesh's largest public medical university.
RampCounted as software-only years it is nine. Counted as the creative-and-engineering pairing this posting is actually built around, it is eighteen.
Eighteen years across the Adobe stack and its successors. Photoshop and Illustrator professionally from 2008, producing over 200 logos and identity systems. Adobe XD as product design became the bridge into interfaces, then Figma, where the ownership sits at system level: Elobooks was designed in Figma end to end, and lists me as Lead Architect and Figma Designer. is the newest end of that lineage and used no Figma at all, its interface and design system produced with Claude Design and Claude Code over MCP, driven by the Claude Code harness with taste verification in the loop. Hundreds of UI components and 60+ applications and websites delivered across ERP, audio, health, hospitality and fintech, for audiences in different regions where the demographic actually changed the design. 's own logo, brand and business cards are mine.
n8n is named verbatim in nine years of delivery, orchestrating workflows and pipelines for internal developer productivity and platform integrations alongside GitHub Actions CI/CD that delivered 4x faster time-to-market. The current version is generative and directly on-thesis: multi-model node workflows on canvas boards, using Seedance, Kling, Minimax, Veo, Nano Banana and Seedream, that produced the entire brand and replaced over $10,000 of commercial photography and videography.
's 2020 remote-first migration: 50% productivity boost, 100% satisfaction boost, never reversed, and it held at 22 engineers. The GitHub Actions CI/CD standard behind that same four-fold time-to-market gain, which is a 75% cut in cycle time. And compliance-by-design across five portfolio platforms, where HIPAA, GDPR and WCAG 2 moved from a retrofit at the end of a build to a constraint at the start of one.
RampThese are company-wide changes at a 22-person studio, not a 30,000-person one. The practice that changed was the one I was running.
Fractured stacks, named: arrived from a London agency on a two-page handover and became a four-platform migration with 2,605 lead records moved onto client-owned accounts. Resistant rooms, named: the live AI demo that moved Cannella & Partner Solutions AG to bet early on AI, launching in January 2025. Repeat adoption, named: , six years and an acquisition, and taken from zero to production with Vipps payments.
RampAt-scale here means enterprise engagements and national platforms, not Fortune 100 marketing organisations. Adobe's scale is a genuine step up.
Both halves are public on the same site and have been for years. Creative: the campaign work, the Dairyland and East Bengal Closet identity marks, and a bespoke component set designed to each company's brand. Engineering: , sole-engineered and live at roughly 96k lines, and this portfolio itself running a Gemma 4 E2B model entirely in the visitor's browser on WebGPU with no prompt leaving the device.
The case studies are the strong half. Every project on this site is written up with architecture decisions, trade-offs and the things that did not work. The public shipping log runs continuously, and the French-learning series on YouTube and Instagram is sustained, on-camera public work.
RampNo conference talks. That is the softest part of this application after the Fortune 100 room.
: 247 commits and roughly 96k lines to date, sole engineer, deployed and operated for about six dollars a month across Cloudflare Workers, a single Fly.io machine and Neon Postgres. The eight-day build sprint in July 2026 ran 195 commits with source files going from 101 to 222 and test files from 17 to 47.
Nine years of it. Engineering Manager 2022 to 2024 and CIO 2024 to 2026 at , but the delivery model throughout was influence across client organisations that did not report to me. 's team hired and led from zero to production, Skytracks Canada engineered alongside the client's own CTO, and 22 engineers grown inside a studio where the work is always someone else's roadmap.
Firefly itself is not new to me: I used it during the beta, inside Photoshop. What I have not used is the surface this line actually names, which is Firefly Services as an API, Creative Production and Workflow Builder, and Brand Intelligence.
RampWhat transfers is the shape rather than the product. Node-to-node creative orchestration is the part I am strongest at: n8n has been in the stack for years, and multi-model generative pipelines already run in production for brand work. I have hands-on time with the first version of Gemini Omni through AI Studio, which is the same class of model Firefly now exposes. The ramp here is an API surface, not a concept.
Healthcare is real and deep. Health: the HIPAA-compliant patient-data pipeline and EHR integration across a multi-specialist clinical platform, aligned to Bangladesh Digital Health standards alongside a Ministry-level rollout, with 3,242 patients, 13,340 schedules, 64 doctors and 7 centers. 's paediatric nephrology records at Bangladesh's largest public medical university. Media and Entertainment via , and . Financial Services via 's Vipps and financing integrations.
RampMLR review specifically, meaning medical, legal and regulatory sign-off on marketing creative, is not something I have run. The adjacent muscle is regulated-delivery discipline: HIPAA, GDPR and WCAG 2 shipped as constraints across five organisations.
Cloud-agnostic across AWS (EC2, ECS, Lambda including container images as an early adopter, EventBridge, DynamoDB, SQS/SNS, CloudFormation with SAML-based provisioning in production, IAM and WAF) and GCP Cloud Run, with cost-aware architecture as a habit: ffmpeg conversion placed in Mumbai for compute cost, client endpoints in California for latency, egress modelled against competitor clouds. runs live across Cloudflare Workers, Fly.io and Neon Postgres for about six dollars a month.
The record, in numbers.
Ten geographies. Named accounts.
The posting asks for a pattern across accounts rather than one win. These are the ones that can be named.
The tools changed. The *eye* didn't.
Eighteen years of picking tools up and putting them down: Illustrator, XD, Figma, Midjourney, Nano Banana. The software kept moving. What carried across was the judgement about what belongs on the page, and a habit of being early. Midjourney in 2022 when prompt engineering had no name. Container images on Lambda before that was common. Gemini Omni through AI Studio before the API shipped. The early adoption is not a hobby; it is what keeps the professional work current.
Design becomes the professional practice, on real client work with real deadlines. Over 200 logos drawn, of which roughly 50 are good and 10 are excellent.
Product design becomes the bridge from marks into interfaces. The question stops being what it looks like and starts being what happens when someone taps it.
Ownership moves up to the system. Elobooks was designed in Figma end to end and lists me as Lead Architect and Figma Designer; used no Figma at all, produced with Claude Design and Claude Code over MCP. Hundreds of UI components, 60+ applications and sites.
Early prompt engineering, well before it had a name. Iterating composition, object placement and infographic structure to find out what the model could actually be directed to do.
Generative production and agentic design loops. A whole restaurant brand out of a node canvas, and this page designed through one.
Two of my colour themes are published on Adobe Color. Making swatches was the habit that taught me a palette holds a brand together more reliably than any single mark does.
What I bring past the checklist is the founder version of all of it. I have sat on both sides of the table: designing the thing, building the thing, and then carrying the commercial consequence of whether it worked. Empty canvas to production deployment, across ten geographies and audiences whose demographics genuinely changed the design. High agency, ownership by default, and comfortable in the room where the decision actually gets made.
Questions? I have answers.
The ones a panel would actually open with.
Both, and the two numbers answer different questions. Design has been the professional practice since 2008, so eighteen years of creative-and-engineering work is literally true, and it is true on exactly the axis this posting cares about, since you are asking for one person who is both. Counted as software-only years it is nine, eleven if you start at UNDP in 2015. All three numbers are on the page.
Figma is the current daily tool and has been for years. The heavy Photoshop and Illustrator practice was the professional craft before engineering took over, with the last sustained client run through . The creative work never stopped, it moved. Today it is multi-model generative production on node canvases, which is how the whole brand was made.
Connected-car service automation for a Hyundai programme, a Norwegian payments integration taken to production, and a six-year Swiss engagement that ended in an acquisition. Enterprise rooms with real consequences, and a smaller table than the one you are describing. The room-winning evidence I would point at is : a live AI demo that convinced Cannella & Partner Solutions to bet early on AI, and the product launched in January 2025.
None. Firefly Creative Production and Workflow Builder are multi-step generative pipelines on a canvas, and I run those. Seedance, Kling, Minimax, Veo and Nano Banana wired as nodes, producing a real brand for a real business I own. The ramp is your API surface and your guardrails.
is 247 commits and about 96k lines with exactly one engineer on it, built in the last few months. The title track at went UX Engineer, Principal Engineer, Principal Staff, Engineering Manager, CIO, and I stepped out of the operating role in August 2026 specifically to be hands-on again. Influence without headcount is also the model I already know. A studio never owns the roadmap, so direction has always had to be earned.
Remote-first in 2020 with 50% productivity and 100% satisfaction gains, compliance moved from retrofit to constraint across five platforms, CI/CD that took cycle time down 75%. Those are all the same move: change the constraint early, while changing it is still cheap. The blast radius was 22 people; the move is the same at 30,000.
Because there is genuine interest on both sides of this. If the speaking requirement is a hard day-one floor, this is a clean no. If the four gates carry different weights in practice, and most postings written this hard do, then the case is that you have someone who is genuinely both halves of this role, who has already run the pipeline shape you are asking about, and whose portfolio for both sides is public before you ask for it.
San Jose or New York both work, and I am open to relocating for this. I have delivered for California and New York clients from the beginning, ten client geographies so far, and I have been remote-first since 2020, so the interim is a solved problem. The practical route into a US seat is the part I would want to work out with your team early.
Going in first, then being asked back.
ran six years as a Zürich client before Loopcloud acquired it, with continuing as the technical team. 's ERP is still run by the client. 's records are still in active use.
See the full recordDid the customer get real value, and did they come back.
That is the posting's line, and it is the one part I did not have to think about. Nine years of client delivery is nine years of being asked back. Adobe is the rare company where the two halves of what I do stop being a strange combination and start being the job description.
San Jose or New York both work, and I am open to relocating to the US for this. I have delivered for California and New York clients from the beginning, ten client geographies so far, and I have been remote-first since 2020.
Stack on this pageFigma · Prototyping · Webflow · Design Systems · Brand Design · Adobe Illustrator / Photoshop / Premiere · Generative Content · Agentic AI Design · Taste-of-design loops (Claude + agy) · Agentic Development · Agentic Workflow · LLM Integration · MCP · A2A