Ciprian Gheorghite

• Integrated third-party services into high-traffic storefronts: payment gateways, OMS platforms and SEO tracking, including the error handling and reconciliation that keeps them reliable in production.
• Profiled and optimised back-end code and site performance, and handled bug fixing and regression assessment on custom implementations after release.
• First-line on-call responder for production incidents across multiple client projects, diagnosing and fixing live failures under time pressure.
• Mentored junior developers joining the company through onboarding, code review and regular feedback.
• Designed and maintained complex, multi-layered business logic and data models for high-traffic eCommerce brands across several industries.
• Led cartridge construction projects, keeping implementations modular and consistent with platform best practice.
• Worked with front-end teams and directly with clients in Agile/Scrum delivery.

JavaScript · Node.js · SFCC (SFRA · SiteGenesis) · OCAPI · ISML · XML · Git

• Built and run a multi-tenant web application on its own domain: a public marketing site and a members-only app served from one codebase, with the host resolved at the edge before any page renders.
• Sign-in is Discord OAuth gated on membership of a specific server; each member stores an encrypted third-party API key, and the admin panel reports which keys are still readable instead of failing silently.
• Pages read from a daily snapshot rather than calling the third-party API at render time, so the product stays up when the upstream is down, and a weekly check flags changes to their markup before a user hits them.
• Moved the whole application off a personal site onto its own domain behind a permanent redirect, keeping the same database and the same signed-in users throughout.
• Around twenty people use it weekly; I own the deployment, the migrations and the incident response.

Next.js · TypeScript · Prisma · PostgreSQL · Discord OAuth · Edge middleware · Vercel · Cloudflare

• Designed and run a production Next.js application on Postgres, with each area behind its own session instead of one shared login, so a credential that opens the blog admin cannot open the private workspace.
• Designed the data model with Prisma; own deployment, migrations and incident response.
• Alongside it, a set of smaller applications built deliberately on different stacks: Fastify services behind Next.js front ends, Postgres with PostGIS for location queries, Expo for mobile, everything containerised and self-hosted.

Next.js · TypeScript · React · PostgreSQL · Prisma · Tailwind CSS · Vercel · Fastify · PostGIS · Expo · Docker

• Designed a conversational agent with a tool registry, so the model calls real tools (web search, Discord administration, media playback, a game API) rather than only replying.
• Specified a tiered permission model for tool calls (read-only, state-changing, destructive), opt-in per tier and written to an audit log, so an agent cannot quietly take an action nobody sanctioned.
• Multi-provider by design: a hosted model with automatic fallback when quota runs out, and a local model over the network for summarisation work that does not need a frontier model.
• Built a news aggregator that filters by meaning rather than keywords using local embeddings, routes matches to per-topic channels, and guarantees each item is delivered once.
• Self-hosted the supporting services (search, translation, Postgres, reverse proxy) under Docker Compose, so the whole system runs without external API keys.

TypeScript · Node.js · LLM tool-calling · Ollama · Embeddings · PostgreSQL · Docker · discord.js

• Designed and shipped the launch site for an idle-economy game on its own domain, where the waitlist is itself a game mechanic: every confirmed signup deals one point of damage to a community world boss, counted live on the page.
• Made confirmation the thing that counts, not the signup: an unconfirmed address contributes nothing, so a public counter that anyone can push cannot be inflated.
• Structured the game as a portable engine with no I/O, so the same rules can run server-side for the browser client now and be bundled into standalone Android and Steam clients later; web client and backend stay detached over HTTP.

Next.js · React · TypeScript · Vercel