Nick walking above a misty mountain lake in British Columbia

Nick Sevostiyanov

BCIT graduate. Software developer.

I’ve been working with computers my whole life. Now I build AI agents, web apps and the servers they run on.

Scroll to explore

About

About me.

BCIT Computer Information Technology, class of 2026. I write code, run servers and fix what’s broken.

Last role: founding engineer at Anticipation Labs, where I took a browser agent from 73.3% to 95.6% on a fixed test set. Now I’m building Peltify, an app for tracking what you watch, read, hear and play and sending picks to friends. I also run a home server and make leather goods.

Technical range

Skills & tools.

How I use it

I work across the complete agent loop: Playwright and Chrome CDP for control, DOM, screenshot and accessibility-tree context for perception, set-of-marks scanning for grounding, and ReAct-style planning for the next action.

Changes are evaluated on fixed episodes with paired seeds, exact McNemar tests, per-arm cost tracking and a pre-committed rule to revert anything without a positive pooled result.

Evidence in the work

  • Moved a fixed 45-episode MiniWoB++ regression set from 33/45 to 43/45 through seven paired experiments.
  • Kept three general-mechanism wins and cleanly reverted four candidates; every retained change received a regression test.
  • Established a fixed-slice WebVoyager baseline and rejected all three architecture candidates when they missed the non-regression gate.

How I use it

I build vertically: interface components, server routes, authentication, relational data, integrations and deployment are treated as one product path rather than disconnected specialties.

Recent work includes Next.js and React interfaces, Node.js REST APIs, Python agent services, MySQL and PostgreSQL data, Clerk authentication, Twilio messaging and webhook-based integrations.

Representative delivery

  • Designed a frozen versioned API so web and iOS surfaces could consume one backend through fail-closed adapters.
  • Rebuilt a responsive dashboard design system across two themes and two breakpoints while its 291-test suite remained green.
  • Built Bridge2AI’s import, schema, prompt and dual-output pipeline end to end for an external industry client.

How I use it

I trace failures across boundaries rather than stopping at the visible symptom: browser state, extension behavior, WebSocket transport, service routing, operating system and deployment environment.

For browser automation, that means controlling the user’s logged-in Chrome through a Manifest V3 extension and CDP while preserving focus, isolating per-job state and failing honestly when the surface is unavailable.

Representative delivery

  • Diagnosed transport races, WebSocket fragmentation, hardcoded surface routing and focus-stealing extension behavior.
  • Restored background automation with up to three concurrent jobs and a dedicated tab per job.
  • Configured and worked across Railway, Vercel, Supabase, Clerk, Twilio and Expo/EAS production services.

How I use it

I work with data as a product constraint: explicit schemas, traceable imports, scoped queries, truthful missing values, retrieval budgets and operational backups.

The range spans application databases and pipelines through self-hosted storage, private networking and routine administration.

Representative delivery

  • Imported spreadsheet and CSV data into MySQL, then translated natural-language questions into SQL for Bridge2AI.
  • Worked with PostgreSQL through Supabase, SQLite plus embedding retrieval, and a Neo4j-backed memory visualization.
  • Deployed and maintain TrueNAS with ZFS storage and snapshots, file sharing and Tailscale remote access.

How I use it

Ariadne Leather joined physical craft with the full operating path around it: workshop tooling, product photography, catalog management, hosting, orders, shipping and customer communication.

I use OpenSCAD for practical workshop templates and jigs, and I treat the storefront as an operated system rather than a decorative web project.

Representative delivery

  • Built and administered a WordPress and WooCommerce storefront with MySQL, payments and self-managed hosting.
  • Integrated Canada Post live rates, SMTP delivery, automated receipts and review workflows.
  • Handled product photography, fulfilment, support and the physical leatherwork behind the catalog.

Portfolio

Selected work.

Things I’ve built. Open one for the details.

Product idea

Discovery with a human reason behind it.

Peltify starts with personal curation. A person organizes the culture they care about, then receives suggestions that explain why a title may fit instead of presenting an unexplained recommendation score.

The social loop

The central action is deliberate friend-to-friend sharing: choose one recommendation, add human context and “Pelt” it to someone. The product is designed around a meaningful pick rather than an endless public feed.

Current boundary

The Next.js and React concept currently uses seeded sample data. It is a validation artifact for testing the information structure, curation flow and explanation model—not a claim of a launched recommendation engine.

What I am evaluating

  • Whether explainability makes suggestions more useful.
  • How much structure curation needs before it becomes work.
  • Whether deliberate one-to-one sharing feels meaningfully different from a feed.

Input pipeline

Turn client spreadsheets into queryable data.

The importer accepted .xlsx and .csv datasets, mapped them into a MySQL schema and established the structured context used by the language-model prompt pipeline.

Query path

A natural-language question was translated into SQL through the Claude API. Results could be returned as a human-readable table or raw JSON, allowing both conversational use and downstream integration.

Delivery scope

  • Schema design and data import.
  • Prompt pipeline and SQL generation.
  • Table and JSON output modes.
  • Twilio querying for remote access.
  • 99-test Vitest suite.

Relevance

This was an industry-sponsored BCIT project for an external client, so the work included requirements translation and iterative delivery—not only a classroom demonstration of an API.

Visit

Open the Workforce Scheduling Engine card on the client's throughput page to see this work described.

Visit Bridge2AI

The complete system

Craft, commerce and operations in one project.

I built the storefront around the physical work: a self-managed WordPress and WooCommerce platform backed by MySQL, product photography and the practical realities of cataloging, fulfilment and support.

Commerce operations

  • Payments and order handling.
  • Canada Post live shipping rates.
  • SMTP delivery, automated receipts and review workflows.
  • Hosting, database administration and customer communication.

Workshop tooling

OpenSCAD provides a repeatable way to design templates and workshop aids around real leathercraft tasks, connecting software with physical iteration rather than treating them as separate interests.

The workflow

SMS intake → validated job → draft form → timestamped receipts.

A solo, clean-room prototype built in zero-dependency Node with ES modules, a deterministic agent loop, a pluggable portal driver and node:test. It modeled regulated paperwork without connecting to a live portal or sending real messages.

Safety by construction

  • A plan ending in submit halts at a deterministic gate and returns a refusal receipt.
  • Field mapping is fail-closed: one unresolvable value means no fill, rather than a misleading partial draft.
  • Approvals are single-use, expiring and replay-safe; webhook signatures reject tampering.

Verification

The final gate held 120/120 tests, including a fixed 32-scenario fixture suite that asserts its own count. Five deliberate regressions were mutation-tested and each failed the intended fixture. The system was re-verified on August 1, 2026.

Explicit scope

The statutory bar was fenced in three separately tested layers. The work used a mock portal and mock transport only: no live submissions, live SMS sends or users.

Public document

Resume

If the document preview does not load, open the PDF.

Nick_Sevostiyanov_Resume_Public.pdfPDF document · public copy · private phone and email removed

Contact

Want to
reach out?

For work, collaboration or a straightforward question, send me an email.