Full-Stack Developer - Next.js & Python at Pavago —

About The Role

Full-Stack Developer – Next.js & Python

Position Type: Full-Time, Remote

Working Hours: U.S Business Hours

About the Role

We are looking for an experienced Full-Stack Developer to build and maintain production web applications across a modern frontend, backend, database, and cloud stack.

This is a hands-on development role for someone who can own a slice of the product across both UI and API. You’ll work with Next.js, React, TypeScript, Python, FastAPI, relational and graph databases, multi-service architecture, real-time functionality, and Azure infrastructure.

What You’ll Own

Frontend Development

Build production web applications using Next.js 16 with App Router, React 19, and strict TypeScript.
Work with server/client boundaries and data-fetching using TanStack Query or equivalent.
Build interfaces using Tailwind CSS v4, shadcn/ui + Radix, Zustand, React Hook Form + Zod, and AG Grid Enterprise.
Work with Framer Motion and Socket.IO.
Write frontend tests using Vitest + Testing Library.
Build end-to-end tests using Playwright.

Backend Development

Build and maintain backend services using Python 3.13 and FastAPI.
Work with Pydantic v2, SQLAlchemy 2 / SQLModel, Alembic, Celery, Redis, and uv.
Work with typed schemas, async I/O, authentication, and background jobs.
Work within a multi-service codebase using HTTP between services, Redis, and workers.

Database & Data

Work with relational modeling and migrations using SQLAlchemy/Alembic or equivalent.
Work with Azure SQL (MSSQL) and PostgreSQL.
Work with Neo4j for family / heirship graphs.
Work with PostgreSQL + pgvector.
Work with MongoDB for logs.

Cloud & Operations

Work with Azure services including Blob, Identity, Key Vault, SQL, and Container Registry.
Work with Docker Compose.
Work with Prometheus / Grafana.
Work with pnpm workspaces + Turborepo.

Advanced Features & Integrations

Work with graph databases or non-trivial graph UIs such as trees, canvases, XYFlow/D3/canvas.
Work with complex data UIs including AG Grid, maps, PDF viewers, and rich text using Tiptap.
Work with real-time technologies such as Socket.IO / WebRTC or telephony platforms such as Telnyx or similar.
Work with LLM/RAG features including embeddings, pgvector, and tool-using assistants.
Work with chatbot services; you do not need to be an ML engineer.

Required Experience & Skills

6+ years shipping production web apps.
3+ years as the person who owns a slice across UI and API.
Strong TypeScript and React experience.
Comfortable with App Router, server/client boundaries, and data-fetching using TanStack Query or equivalent.
Strong Python and FastAPI experience, or Django/Flask at a similar depth.
Experience with typed schemas, async I/O, authentication, and background jobs.
Strong relational modeling and migration experience using SQLAlchemy/Alembic or equivalent.
Experience with MSSQL or PostgreSQL.
Experience in a multi-service codebase with HTTP between services, Redis, and workers, not only a single monolith.
Tests as a habit: unit/integration on the backend and component tests on the frontend.
Clear written communication.
Ability to leave the next engineer a module they can change without a walkthrough.

Strongly Preferred

Graph databases such as Neo4j or non-trivial graph UI using trees, canvases, XYFlow/D3/canvas.
Azure experience with SQL, Blob, Key Vault, or a comparable cloud.
Experience with complex data UIs such as AG Grid, maps, PDF viewers, or rich text using Tiptap.
Real-time experience with Socket.IO / WebRTC or telephony with Telnyx or similar.
LLM/RAG experience including embeddings, pgvector, and tool-using assistants.

Nice-to-Haves We Actually Use

WebRTC calling.
DocuSign / PKCS#7 signing.
GEDCOM.
Google Maps.
Campaign/inbox graph models.
Prometheus metrics.

What Makes You a Strong Fit

You have extensive experience shipping production web applications and owning a slice across both UI and API.
You’re comfortable working across TypeScript/React and Python/FastAPI.
You can confidently reason about relational modeling, migrations, and multi-service architecture.
You’re comfortable working with Redis, workers, and HTTP communication between services.
You treat testing as part of development rather than something to add later.
You communicate clearly in writing.
You leave the next engineer with a module they can change without a walkthrough.

What Success Looks Like

You can independently own a slice of the product across UI and API.
Production features are supported by appropriate backend and frontend tests.
Relational models and migrations are reliable and maintainable.
Multi-service communication, Redis, and workers operate effectively.
Complex data UIs and graph-based functionality are implemented effectively where required.
Real-time, cloud, and third-party integrations work reliably.
Your code is clear enough for the next engineer to understand and modify without a walkthrough.