Pickle is the first bespoke personal AI — built inside iMessage, the most natural interface consumers already live in.
You tell Pickle what you need, and it builds a mini-app for you on the fly. A fitness coach, a medication tracker, a quantum physics tutor — whatever you need. Every app shares one continuous memory, so your workout app knows what you ate in your cooking app.
Over time, Pickle understands your personal story more deeply and starts changing your life proactively — by messaging you first.
To try it out, join the waitlist at the link above.
We're looking for a Founding Frontend Engineer who can own every consumer-facing surface of Pickle — the landing site, the webapp, the mobile web shell, and the browser extension.
This is not a "just do frontend" role. It is the opposite. It is for a full-stack engineer who has shipped a complete consumer product end-to-end: backend, deploy, database, observability, the whole thing, and has chosen frontend as the layer they want to spend the next decade of their career on. Not because backend is hard for them, but because they believe the frontend is where consumer products are actually won or lost.
What we mean by "won or lost" is specific. A 3D memory graph that has to stay smooth while rendering many glowing nodes with custom shaders and per-frame level-of-detail budgeting. A landing page where every image has to be delivered in the right format, at the right size, for the visitor's device and network, before their eye reaches it. A mobile web surface that has to feel as responsive as a native app on a three-year-old Android over a slow network.
If you treat frontend as systems engineering rather than component assembly, keep reading.
<aside>
The full consumer product surface
Own the entire UI layer of Pickle across three surfaces that share one codebase: the landing site at pickle.ai, the desktop webapp, and the mobile web shell. All of them ship from a single React 19 + TypeScript + Vite codebase under strict feature-slice rules enforced through ESLint and explicit dependency conventions.
You'll also pick up the browser extension (a separate submodule) and own the authentication bridge that hands off state between the extension and the webapp.
</aside>
<aside>
The interactive 3D memory space
The marquee piece of our webapp is a 3D memory graph — built on React Three Fiber and Three.js — where each memory is a glowing sphere with custom shaders, custom node materials, distance- and proximity-based detail management, and a real frame budget. It has its own render loop, camera controls, keyboard and pointer input, and animation states for spawn, focus, and exit transitions.
You'll own its future: shader work, lighting passes, camera systems, interaction models, and the frame budget. When a user pans across their own life in 3D and it feels like magic rather than a tech demo, that is you.
</aside>
<aside>
Asset pipeline, performance, and delivery
Every image on our landing site runs through a Sharp build pipeline that generates AVIF and WebP variants at multiple widths, uploads them to a versioned S3/CDN path, and generates an asset manifest the app consumes directly. The system cut asset weight by 95% in measured production. Videos ship with browser-specific codec fallbacks. Above-the-fold loading behavior is engineered rather than left to defaults.
You'll own this delivery layer: build scripts, CDN strategy, caching and update behavior, multi-device and multi-network testing, and the performance bar we hold ourselves to.
</aside>