You land once.I make it spread.
Paris · On-site · Full time
Dust's 70%+ weekly active number is defended after the signature — by whoever builds the sticky use case, wins the security room, and turns usage into roadmap. That has been my seat for a decade, held under founder titles: co-founding , scaling it to 22 product and engineering professionals, and staying the hands-on technical partner for clients across nine geographies. I build the exact category Dust sells — multi-agent systems in production — and I'm relocating to Paris on purpose.
Certified & shipped with
Aptitude. Attitude. Agency.
Dust's own hiring dimensions, mapped honestly — practitioner depth, receipts over adjectives, and a decade of finding the problem before anyone scoped it.
Aptitude
He builds the exact category Dust sells: daily agent-led development (Claude-led, Gemini second) and multi-agent systems in production — on Google's A2A, 's autonomous deal pipeline, the CMS behind CI/CD gates. Product expertise starts from practitioner depth, not a slide deck.
Attitude
Gaps named first, receipts over adjectives. A 900+-day public French streak for consistency; GDPR, HIPAA and WCAG 2 designed in across five client organisations; clients kept for years because the software kept earning its place.
Agency
Co-founded in 2017 and scaled it to 22 while staying in the repo. Nobody scoped the six AI-native products he shipped in the last year — during the World's Largest Hackathon, at Milan AI Week 2026 — he found the problems and built.
Ask Fauzul's AI
What you're hiring for, running.
Dust wants its first post-sales Solutions Engineer to be the technical partner for existing Enterprise customers — deep product expertise, advanced implementations, workshops for security and compliance evaluators, and a voice-of-customer channel back to product. Here is the point-by-point mapping of a decade of customer-embedded delivery onto that seat, with the real ramps marked honestly.
How long do Enterprise clients actually keep him?
Jamahook: six years, through to the 2026 Loopcloud acquisition. EKAGRA: two years seven months and counting.
The technical partner customers keep
Post-signature relationships measured in years — the seat this role formalizes.
4+ years in a combination of technical and customer-facing roles (e.g. software engineering, solutions architect, implementation engineer).
A decade of both at once. Fauzul co-founded in 2017 and held the technical and the customer-facing seat simultaneously — UX Engineer to Principal Engineer to Engineering Manager to CIO — while personally owning client relationships across London, Zurich, Oslo, Dubai, Florida, Montreal and Laval. The work was implementation engineering by any name: embedding in 's codebase to pair-code a Vipps payment integration, architecting 's clinical platform, building 's federated OIDC identity and instance-level RBAC.
Strong relationship-building skills with ability to establish yourself as a trusted technical advisor
His client relationships are measured in years, not quarters: six years with through to its Loopcloud acquisition; four years with and SkyTracks working directly with the client's technical CTO; two years seven months and counting with . Trusted-advisor status came the same way every time — being the person who understood both the architecture and the business, and who said 'no' with evidence when it mattered.
Effective multitasking and prioritization skills under pressure and in ambiguous situations across a wide variety of tasks.
Founder triage was the job: as 's CIO he ran parallel client books across nine geographies and five time zones — a HIPAA clinical platform, a GDPR/VAT music-commerce checkout, a Norwegian fintech integration, all live at once. Prioritization under ambiguity is what a product engineering venture firm sells; he did it for eight-plus years without dropping a client.
What does 'scrappy' look like in the field?
Weeks inside EKAGRA's diabetes and wound-care clinics, watching doctors under pressure — then fixing what actually stalled adoption.
Implementations that stick
Scrappy in the field, rigorous in the repo — use cases that survive first contact.
An action-oriented and organized self-starter mindset who isn’t afraid to get scrappy to solve customer issues.
Receipts rather than adjectives: over the last year he solo-shipped six AI-native products — built during the World's Largest Hackathon and submitted to Y Combinator, at Milan AI Week 2026 (results pending), , the CMS, and . Nobody scoped or unblocked these. Scrappy in the field looks like the weeks he spent inside 's diabetes and wound-care clinics, watching doctors use the software under pressure and fixing what actually stalled adoption.
A strong work ethic and commitment to excellence.
The public receipt is a 900+-day daily French streak — not missed once, taught in public on YouTube. The professional receipt is retention: grew with for six years until Loopcloud acquired it in 2026, with continuing as the technical team; is two years seven months in and counting. Excellence at was operationalized, not proclaimed — CI/CD release gates and compliance checklists as the condition for shipping fast.
A deep interest in understanding customer needs and the desire to become an expert on Dust’s product.
The customer-needs half is a decade deep: clinic-floor observation at became product direction; client-side auth friction became 's OIDC backbone. The Dust-product half is the honest ramp — he hasn't operated Dust in production yet. What de-risks it: he is a daily practitioner of the exact category (agents connected to real data and tools), and Dust's core is open source.
How would he open a security review?
From the evaluators' risk register — GDPR, HIPAA and OIDC/RBAC receipts first, the live product second, slides never.
Evaluators won, usage measured
Security rooms, cross-functional pods, and adoption debates that run on numbers.
Demonstrated ability to work collaboratively with cross-functional teams to achieve shared goals.
's delivery pods were cross-functional by construction — design, engineering, product and a commercial counterpart per account, with Fauzul as the technical lead who kept them aligned. He has spent years pairing with client engineers in their repos while reporting outcomes to their executives, which is precisely the Customer Success + Product & Engineering triangulation this role describes.
A data-driven mindset that can interpret customer feedback and behavior.
Adoption at is measured in usage, not sentiment: 2,212 new patients and 9,650 schedules onboarded in 2026. His pilots are instrumented so rollout debates run on numbers, and his agent work ships with evaluation harnesses that score outputs before go-live (, ). Usage patterns became roadmap at every client — the voice-of-customer loop this JD names is how he has always steered product.
A passion for technology, problem-solving, and a commitment to your customers’ success.
He builds daily and learns in public: agent-led development every working day, hackathon builds shipped to real deadlines (, ), certifications earned rather than claimed — Anthropic's Claude Code 101 and Introduction to Agent Skills, and the Google × Kaggle 5-Day AI Agents Intensive. Customer success is the through-line of the whole career: only got paid when the client's product worked.
Which agents has he shipped to production?
VisaPros on Google's A2A, Wiregent's autonomous founder/investor pipeline, and a Claude-powered CMS behind CI/CD gates.
The agent stack behind the claims
High technical aptitude, demonstrated in the category Dust operates.
High technical aptitude, with an ability to work directly with engineers as well as business stakeholders. Experience with APIs, web development, and writing scripts to build internal tools is a plus. Familiarity with LLMs like GPT-4, Claude, Mistral or Gemini is highly desirable.
Production depth, not familiarity: TypeScript/Node.js and React at ten years of shipping; REST, GraphQL and webhook integrations across Stripe, Vipps and third-party SaaS; internal tools built and open-sourced (). On LLMs he goes past 'familiarity' — his production AI is Claude-led with Gemini a genuine second, running in a client's live stack () and across multi-agent builds on A2A and MCP. The altitude switching is proven: architecture to VPs and C-suite in the morning, pairing with staff engineers in the afternoon.
He hasn't operated Dust itself in production yet — product expertise is day-one work, not a day-one fact.
Weeks — the platform is open sourceHe is a daily practitioner of the category Dust sells (agents connected to real company data and tools), and Dust's core is public at dust-tt/dust. His pattern on deep new systems is weeks-to-production: A2A and MCP went from zero to shipped builds within weeks. Step one is rebuilding his own workflows on Dust so he arrives at customer scenarios as a power user, not a reseller.
The vendor-side post-sales SE title is new — his post-sales muscle was built on the buyer's and agency side.
2–4 weeksThe buyer's side is an asset here: as 's CIO he was the customer's technical partner after every signature — the one accountable for adoption, renewals and expansion in practice. He knows first-hand every objection an Enterprise team raises after the honeymoon, because for a decade he was the person absorbing them.
Professional French is in progress — working fluency is real but building.
Ongoing daily — publicly verifiableThe practice is genuine and unbroken: a 900+-day daily French streak, with A2 grammar explainers taught publicly on YouTube. Dust's working language is English and the role's Enterprise customers span geographies; his French trajectory adds Paris-office depth rather than gating day-one effectiveness.
Ask Fauzul's AI
'We land once, and spread.' The spread is my job description — I have held it for a decade under founder titles.
From his recommended response · Solutions Engineer Post-Sales
See how it works, post-signature.
For — a Dhaka-based export house serving global importers — Fauzul replaced the traditional CMS with an agentic one. The owners edit their live site in plain English; Claude authors a pull request; CI/CD verifies and ships it to production. It is the closest thing to a Dust deployment he could have built himself: non-technical operators running their real business surface through an agent connected to their actual content and tools, with governance designed in — which is why adoption survived first contact with reality.
A 26-year-old export house that runs its web presence by talking to an agent
Land — earn the technical room
Discovery with engineers and business stakeholders together: map the architecture, the data, the tools, the risk posture. A decade of altitude-switching between C-suite and staff engineers means the trusted-advisor seat is earned in the first meetings.
Build — the use case that sticks
Lead the advanced implementation personally: integrations, custom workflows, agents wired to the customer's real systems — the Vipps integration inside 's repo, the agentic CMS at . Sticky means load-bearing, not impressive.
Adopt — win evaluators, measure usage
Run the security and compliance workshops from their risk register (GDPR, HIPAA, OIDC/RBAC across five orgs), then instrument adoption so retention and expansion debates run on numbers — the way 's 2026 usage is counted, not narrated.
Compound — playbook and product loop
Champion usage patterns and objections back to Product & Engineering, and codify what worked so each deployment beats the last. 's delivery playbook, written while scaling to 22 engineers (52+ professionals total FT & contract), is the first-hire deliverable beyond any single account.
Objections, answered first.
Candid answers to the hard objections — why a founder wants a post-sales seat, what he will and won't claim about operating Dust itself, how he'd run a security-team workshop, and the honest state of his French.
Ask Fauzul's AI
Connected capabilities.
The stack behind the claims — multi-agent systems in production, integrations and custom workflows shipped inside client environments, and the compliance surfaces (GDPR, HIPAA, OIDC/RBAC) that Enterprise evaluators actually probe.
Agentic Development · Agentic Workflow · LLM Integration · MCP · A2A · Google ADK · Prompt Engineering · Prompt Caching · Computer Use · Eval / harness hill-climbing · Token & cost-aware context engineering · Firecrawl · Cursor · Bolt · Firebase Studio · Nano Banana · Claude Code · Claude Skills · Claude Code Subagents · Claude hooks & tools · Anthropic Claude · Google Antigravity (agy CLI) · Gemini Spark (email topic loops) · Gemini Omni (first version, via AI Studio) · On-device Gemma 4 E2B (this site chat · WebGPU + MediaPipe) · Kimi via OpenRouter (NewScriber) · Gemini TTS via Azure (NewScriber)
Multi-agent systems in production (A2A · MCP) · Claude in production (Claude-led, Gemini second) · n8n agentic workflows · RAG & retrieval · Prompt engineering & agent evals · LLM integration
Client communication · Requirements gathering · Specifications management · Enterprise problem identification · Solution architecture · Technical scoping · Delivery management · Stakeholder alignment · Executive communication
REST / GraphQL / Webhooks · Stripe · Vipps · third-party SaaS · TypeScript / Node.js · Python (AI & data) · Postgres · Docker & serverless · GitHub Actions (CI/CD)
OAuth2 · OIDC · RBAC · JWT · Auth0 · Multi-tenancy · Magic-link · Passport · HIPAA · GDPR / VAT · WCAG 2 · Auditability
React · Angular · Next.js · Astro · Redux · RxJS · Tailwind · Web Audio · WebGPU · Storybook · TanStack Query · TanStack Start
Ask Fauzul's AI
What I bring that the job description doesn't ask for.
The post-sales SE spec is the floor, not the ceiling. Four things I'd bring into the room on top of it — each one a compounding advantage for a first hire building the function.
Demos and onboarding that feel like the product, not a slide deck.
I came up as a UX Engineer before I was a founder — I bridge Figma to React with pixel precision, draw my own SVG assets, and build the micro-interactions that make a technical demo land. When a customer's evaluators watch me configure an agent live, the craft of how it looks and moves is doing quiet work on the deal.
I don't just do the job — I build the people who'll scale it.
As the first post-sales SE, the org is the second deliverable. I've coached engineers into senior roles abroad — alumni now lead at organisations in Norway (2), Canada, Germany, plus two leading local Bangladeshi tech companies — and wrote 's onboarding and delivery rituals from scratch. Hiring, ramping and levelling the next SEs is a muscle, not a someday.
Enterprise fluency across nine geographies and five time zones.
A decade delivering for clients in London, Zurich, Oslo, Dubai, Florida, Montreal and Laval means I read a room in Paris, a security review in Zurich and a procurement call in the US as the same job in different accents. Dust's customers are international; cross-cultural enterprise judgment is not something I'll be learning on the job.
The discipline shows up daily, in public, whether anyone's watching.
A 900+-day unbroken French streak, A2 grammar taught on YouTube, six AI-native products shipped solo in the last year, hackathons entered on real deadlines. The same daily consistency I point at French is what makes a first-hire actually write the playbook instead of promising to — and it's now pointed at Paris.
[ The first post-sales SE hire ]
Your customers aren’t just buying agents. They’re running them. So am I.
Intentional about Paris — a 900+-day daily French streak (public, unbroken, ongoing) and a deliberate EU/EEA relocation plan; Dust's relocation package (€10k) and visa sponsorship make the landing straightforward. Office-first is a preference, not a concession: the highest-leverage moments of a decade of delivery happened physically inside customer environments.
— Relocating to Paris · 994-day daily French streak, unbroken →