iambogdan v3 preview

Why a v3

Same engineer. New site.

This site stays up until v3 is ready. v3 is a rebuild, not a reskin.

  1. A new design. Layout, colour, type and copy, all from scratch.

  2. Every state, tested. Each component has a Storybook story for every state, run in a real browser.

  3. Accessibility, enforced. Every story must pass an automated accessibility check (axe), or the tests fail.

The v3 home page design: a midnight-blue page with the headline “I build the app. And the agents inside it.”, the word “agents” in lime, next to an isometric stack of three layers labelled Sites, Agent and Data.

Work in progress Isometric art and logo subject to change.

The v3 home page · design v2.2
BA AI Engineer & Full-Stack TypeScript Developer

Curriculum Vitae

The long version

Newest first: web design, front-end, WordPress, performance, TypeScript, full-stack, and now agents that run on live customer traffic. Most of it is one long run — from designing pages, to building the systems behind them.

18 yr 11 mo since the first paid web work, in 2008
2 yr 7 mo of it shipping production LLM systems
9 roles, from web design to AI engineering
  1. 2026 → now

    AI Engineer & Full-Stack Developer

    Current

    Independent

    2026 — Present 4 mo self-employed · remote

    Two products of my own, built end to end and live on Railway, and a new version of my own site.

    • bifa (app.bifa.dev). A kanban where AI agents work on the board next to people. Agents are a kind of person in the schema, and Claude files, moves and comments on cards through bifa's own MCP server, signing in through bifa itself. REST API, Google sign-in, one organisation per person. Private beta, by invitation. In daily use: 23 projects and 350+ cards, this CV's included.
    • DefineProcesses (defineprocesses.com). Processes that humans and AI agents follow by the same rules: sections, tasks and subtasks become reusable templates, with an AI copilot (Mastra + CopilotKit). Multi-org, on Neon with row-level security, with per-org Stripe subscriptions on four plans. Private alpha.
    • iambogdan.com: an Astro 7 site and an Electron desktop admin, both in daily use. v3 in progress, built for AEO/GEO: site and admin on one component library; design system in public beta at ds.iambogdan.com.
    • MCP
    • Mastra
    • CopilotKit
    • Next.js 16 App Router
    • Drizzle
    • Neon (RLS, Auth, Data API)
    • Better Auth
    • Stripe
    • Turborepo
    • Electron
    • Railway
    • SEO / AEO / GEO
  2. 2024 → 2026

    AI Engineer & Full-Stack Developer

    AirTreks

    2024 — 2026 2 yr 7 mo United States · remote

    Production LLM systems end-to-end — the agents, the automation behind them, and the analytics that show what they changed. Built the AI chat channel from zero into a live revenue line.

    • A support agent that builds while it talks. The interface changes as the conversation goes — trips appear in front of the customer, and they can edit them mid-chat or by hand.
    • Two agents, split by intent. A cold lead and an existing customer need different conversations, so they get different agents behind the same chat surface.
    • A brain both agents read from. Versioned skill bundles plus pgvector retrieval over Q&A and internal knowledge, pulled live mid-conversation — and past conversations are ingested and analysed, so an objection that came up once feeds the next answer. Human agents can push in what matters.
    • Automation that survives a crash. Instant customer emails, alerts to a human agent on conversion, and the trip written straight into the sales CRM and published as a route on the front end — on idempotent steps, exactly-once email, and a distributed lock that releases itself.
    • Measurement, and a way to ask it questions. Typed PostHog events across every funnel, wired into the brain over MCP — so “what happened in that conversation” and “what did the funnel do last week” are both questions you can ask from Claude.
    • AEO/GEO — Schema.org on every page type, machine-readable endpoints, a named AI-crawler policy, and a frozen prompt panel that measures whether assistants cite the site.
    • Mastra
    • Vercel AI SDK v6
    • Generative UI
    • MCP
    • pgvector RAG
    • Next.js 16 App Router
    • Neon + Postgres
    • Drizzle
    • Workflow DevKit
    • Supabase
    • PostHog
    • AEO / GEO
    • TypeScript (strict)

    See the project

  3. 2023 → 2024

    Full-Stack Developer

    AirTreks

    2023 — 2024 1 yr United States · remote

    Moved the content layer off headless WordPress onto Sanity, and wired the sales CRM to the site: a trip created in the AirTreks trip-planner app published itself as a route on the front end, through Firebase Functions and the CRM's own APIs. Replaced Hotjar with PostHog — the event tracking everything after this was measured on.

    • TypeScript
    • Next.js
    • Supabase
    • Firebase Functions
    • Sanity
    • PostHog
  4. 2020 → 2023

    TypeScript Developer

    AirTreks

    2020 — 2023 3 yr United States · remote

    Replaced the public sites on both AirTreks and BootsnAll: WordPress stopped serving pages and became a headless CMS behind Gatsby and Next.js front ends, over GraphQL.

    • TypeScript
    • Gatsby
    • Next.js
    • GraphQL
    • Headless WordPress
  5. 2014 → 2020

    Front-End & WordPress Developer

    AirTreks

    2014 — 2020 6 yr United States · remote

    WordPress front-end development, and the web-performance optimisation of the WordPress stack itself.

    • WordPress
    • Front-End
    • Web Performance Optimisation
  6. 2012 → 2014

    UI/UX Designer & Front-End Developer

    BootsnAll Travel Network

    2012 — 2014 2 yr United States · remote

    • UI / UX
    • Front-End
    • WordPress
  7. 2010 → 2012

    Web Designer

    BootsnAll Travel Network

    2010 — 2012 2 yr United States · remote

    Designing web interfaces and implementing them on the front end.

  8. 2009 → 2010

    Web Design

    Code 932

    2009 — 2010 1 yr

  9. 2008 → 2009

    Web Designer

    Red Studio Iași

    2008 — 2009 1 yr Iași, Romania

Side projects: websites for clients such as SOS Hydration, with Shopify as a headless CMS and Next.js.

FAQ

What working with me actually looks like

Twelve years at one employer, a Romanian timezone and a part-time offer all raise the same handful of objections. Here they are, answered before you have to ask.

You spent twelve years at one company. Can you still adapt?

The company stayed the same; the work didn't. Nine roles since 2008 — web design, front-end, WordPress, performance, TypeScript, full-stack, and then production LLM systems — each one a deliberate move, not a promotion I waited for. I've also built websites for other clients on the side, such as SOS Hydration's, so the parallel-client muscle isn't theoretical.

Then I left. Since August 2026 I've been independent, building two products of my own end to end — bifa and DefineProcesses — with nobody to hand the hard parts to. That's adapting as a daily job rather than an interview answer.

Are you available, and for how much?

Yes — part-time, remote, and taking on work now. Days are booked into the calendar in advance rather than pulled ad hoc, which is what makes part-time actually work for both sides.

How many days, and from when, is the first thing worth agreeing rather than the last. Tell me what the work needs and I'll tell you what I can commit to.

How do you work day to day?

Everything goes through a tracker — Linear, Jira, whatever you already use. Chat is for talking, not for assigning; work that only exists in a Slack thread tends to get lost or silently doubled.

If the priorities aren't obvious, I'll tell you what I'd do first and why — most of the time the ordering comes from the numbers rather than from an opinion. I'll also tell you what each item costs in days, so the trade-off is visible. The call stays yours.

You're in Romania. Is the time difference a problem?

Full working-day overlap with the EU and the UK, plus the US East Coast morning. Twelve years of remote work with a US company happened across exactly this gap.

Async is the default, and features are where it pays off: give me a feature with the scope agreed up front and I'll break it into tasks, work through it and come back with something you can look at — no check-in every few hours. Live calls on your tool of choice when a decision is genuinely faster spoken than written.

Do you just write code, or do you make product decisions too?

Both, and the second one is usually where the money is. A large part of the last decade was conversion work, funnels, SEO and UX on a site that had to sell — measuring a flow, changing one thing, and checking whether the number moved. I'm most useful when I'm allowed to argue with the brief, not just implement it.

What don't you do?

Native mobile, data science and ML training, and heavy DevOps or infrastructure architecture. I also don't take on work where the outcome depends on budget or channels I don't control; I own what I can actually move.

Design is a different case: I started as a designer and I still design, but in code rather than in Figma — sketches and flows up front, then the interface built directly. If you want polished Figma files handed over to someone else, that's not me.

A CV is a list of places. The systems are the actual claim — what was built, what it moved, and which numbers survived being checked.

See the projects Start a conversation