Full-stack TypeScript Engineer | Product-minded systems builder

I build production-ready TypeScript systems for teams that need one engineer who can own the full stack.

Frontend, backend, database, auth, integrations, internal tools, and deployment - built with clean architecture, strong ownership, and enough pragmatism to actually ship.

Review selected workDownload resumeContact
GitHubLinkedIn

What I Can Own

The roles that fit me best need a hands-on engineer who can move across product, frontend, backend, data, integrations, and release work without losing the system view.

Full-stack product and platform work

I am strongest where a team needs someone who can understand the product flow, design the data and API boundaries, build the UI, integrate services, and keep the delivery path practical.

Best fit

TypeScript-heavy products, dashboards, internal tools, integrations, CMS/backoffice workflows, and product-platform systems.

Start a conversation

3+ years professional engineering

Full-stack engineering experience at Abra Technologies, plus technical leadership and zero-to-one platform ownership at The Atheist Line.

Full-stack ownership

Next.js, React, Node.js, PostgreSQL, tRPC, Drizzle, Supabase, Cloudflare, auth, integrations, internal tooling, and deployment workflows.

Shipped systems, not toy demos

CRM workflows, CMS/backoffice tooling, creator operations, microservices automation, portfolio infrastructure, and reusable UI/component systems.

Best fit

Teams that need a hands-on engineer who can move across product, frontend, backend, data, and operational workflows without creating architecture debt.

Abra Technologies: reusable UI, Storybook, component testing.The Atheist Line: technical direction, tooling, production readiness.Snow HQ: RBAC-aware CRM and type-safe APIs.ClipWhisperer: queue-driven media automation architecture.

Selected Work

A focused set of systems that show how I think about product flow, architecture, implementation, and production readiness.

Portfolio Platform

Live system

Problem

A portfolio needs a public proof surface plus private tools for content, career data, and technical case studies.

What it proves to a hiring team

Shows ability to build and operate a production portfolio platform: public i18n site, authenticated CMS/backoffice, content workflows, and deployment.

What I built

This public i18n site with authenticated CMS/backoffice, content APIs, and deployment path.

Architecture

Public i18n site plus RBAC-protected admin CMS, Postgres-backed content APIs, and modular homepage composition.

My role

Sole builder: architecture, implementation, content workflows, and deployment.

Proof

This website and its supporting private CMS/backoffice.

Private repository - system architecture and implementation decisions are documented.

Stack

Next.jsTypeScripttRPCDrizzleSupabaseNextAuth

Socially

Private build / release-readiness case study

Problem

Creator operations need publishing, analytics, and workflow coordination without fragmented tooling.

What it proves to a hiring team

Shows product/platform planning for creator operations: cross-platform workflows, Supabase-backed data models, Cloudflare deployment boundaries, and release readiness.

What I built

A creator operations platform direction with mobile frontend, backend boundaries, auth, and integration-ready data models.

Architecture

Product architecture and release-readiness plan for a creator operations platform; public demo is not available yet.

My role

End-to-end technical direction across product architecture, implementation, and release readiness.

Proof

Architecture and release-readiness case study. Public demo is not available yet.

Private repository - release-readiness case study available.

Stack

React NativeTypeScriptSupabaseCloudflare

ClipWhisperer

Architecture walkthrough available

Problem

Manual video generation pipelines are slow, fragile, and hard to scale across processing, storage, and delivery.

What it proves to a hiring team

Shows backend/platform thinking: queue-driven orchestration, media-processing boundaries, service separation, and cloud-integrated processing.

What I built

A production-oriented video automation platform with queue-driven orchestration and media-processing boundaries.

Architecture

Hub-based orchestration with queue-driven jobs, service separation, and cloud-integrated processing steps.

My role

Platform design and hands-on implementation across orchestration, media processing, and service boundaries.

Proof

Production-oriented microservices structure with clear ownership boundaries. Public demo is not available.

Private repository - architecture walkthrough available.

Stack

Node.jsTypeScriptSupabaseAWSFFmpeg

Snow HQ

Private build / architecture walkthrough

Problem

CRM workflows need tenant separation, permissions, dashboards, and maintainable full-stack delivery.

What it proves to a hiring team

Shows full-stack product execution: tenant-aware CRM workflows, RBAC-aware data modeling, type-safe APIs, and dashboard UI.

What I built

A multi-tenant CRM with RBAC-aware data modeling, typed APIs, and dashboard flows.

Architecture

Type-safe APIs, tenant-aware data modeling, RBAC, and dashboard-oriented workflows.

My role

Full-stack implementation across frontend, backend, and database layers.

Proof

Private build with architecture and implementation notes available. Public demo is not available.

Private repository - architecture walkthrough available.

Stack

Next.jstRPCPostgreSQLDrizzle ORM

Experience

Professional work and technical leadership context, written plainly so the role shape is easy to evaluate.

Abra Technologies

Full Stack Engineer, 2024-2025

Worked on the early development of an internal government data platform, reusable UI systems, Storybook-backed component workflows, component testing, and frontend architecture foundations.

The Atheist Line

Technical Lead, 2025-Present

Volunteer technical leadership role for a 17-person organization. I serve as the primary technical owner for public-facing and internal systems, content workflows, tooling, integrations, CI/CD, analytics foundations, and production readiness.

Menora Mivtachim

Business Rules Configuration Specialist, 2023-2024

Configured insurance product logic and internal business rules with a focus on correctness, consistency, and operational reliability.

Technical Strengths

The strengths I want hiring teams to evaluate first.

Full-stack TypeScript delivery

Next.js, React, Node.js, tRPC/REST APIs, PostgreSQL, Drizzle, Supabase, auth, and deployment workflows.

Review full-stack proof

Frontend systems that stay maintainable

Reusable UI components, responsive product screens, Storybook-backed workflows, component testing, and clean feature composition.

Review frontend proof

Backend, data, and integrations

API boundaries, relational data modeling, permissions, queue-driven workflows, media processing, and service ownership.

Review backend proof

Internal tools and operational workflows

CMS/backoffice systems, dashboards, admin panels, automation opportunities, and tools that reduce fragmented manual work.

Review systems proof

Resume, GitHub, and Case Studies

The fastest links for reviewing my work, background, and implementation history.

Resume

Full experience, skills, education, and project history in one place.

Open resume

Snow HQ case study

Multi-tenant CRM with tRPC, PostgreSQL, Drizzle, RBAC-aware modeling, and dashboard flows.

View case study

ClipWhisperer architecture

Queue-driven video automation platform with service boundaries and cloud processing.

View architecture notes

Portfolio platform

Public i18n site plus authenticated CMS/backoffice, content APIs, and modular homepage composition.

View system notes

GitHub

Code, experiments, project repositories, and implementation history.

Open GitHub

LinkedIn

Professional profile and fastest recruiter-friendly contact path.

Open LinkedIn

Common Questions

Can you own work end to end?

Yes. My strongest lane is full-stack ownership across frontend, backend, data modeling, integrations, deployment, and operational workflows.

Are you senior?

Not by title. I have 3+ years of hands-on professional engineering experience across 2024-2026 and counting, and I back that with strong ownership, modern stack fluency, clear communication, and production-minded delivery.

Where do you fit best?

Teams building TypeScript-heavy products, dashboards, internal tools, integrations, CMS/backoffice workflows, or product-platform systems that need someone comfortable across the stack.

What should I review first?

Start with Snow HQ for full-stack product execution, ClipWhisperer for backend/platform architecture, the Portfolio Platform for CMS/backoffice ownership, and the resume for work history.

What makes you different from another TypeScript developer?

I am not only focused on screens or isolated tickets. I care about the system: product flow, data model, API boundaries, operational workflow, maintainability, and how the thing gets shipped.

How should a recruiter contact you?

LinkedIn or email are best. Send the role, stack, team context, and what kind of ownership the position requires.

Contact

I am best suited for teams building product-facing systems, internal tools, dashboards, integrations, CMS/backoffice workflows, and TypeScript-heavy web platforms.

For selected technical/project conversations, send a short brief with scope, timeline, and current technical constraints.