Founding Backend Architect (Python/PostgreSQL)

We're a freight brokerage in NJ building a self-hosted, AI-first platform to replace our legacy CRM/TMS.

The AI compute infrastructure and data foundation are already in place. We need the architect who turns it into a production operating system.

This is a systems architecture role, not a feature dev role. If your primary strength is writing features or following tickets, this is not the role.

You will be responsible for: designing and deploying a PostgreSQL schema for complex freight operations across 30+ entities. Building Python service layers integrating multiple REST APIs. Wiring locally-hosted LLM inference into business workflows. Structuring systems that involve document ingestion, email processing, and asynchronous event-driven pipelines. Defining backend patterns for reliability and maintainability across a multi-million record environment.

The entire stack is self-hosted on custom-built server hardware. Database, application layer, AI inference — all of it. No cloud dependencies. No API rate limits. No monthly GPU bills. No vendor lock-in. You have direct access to the metal, you deploy on your terms, and the only ceiling on what you can run is the hardware itself.

If you've ever wanted to build a production platform without a cloud provider standing between you and your infrastructure, this is that role.

You are the first technical hire. You report directly to the owner, who is directly involved in this hire and in daily collaboration on the build. Architectural decisions are yours to make. AI coding tools and low-code UI frameworks are part of the workflow — your time goes to data models, service orchestration, and API plumbing, not hand-building screens.

Stack: Python, PostgreSQL, FastAPI, Docker, Neo4j, Linux, vLLM. Preferred: freight/TMS domain, Microsoft Graph API, CRM migration experience.

1-week paid onsite onboarding in NJ, then fully remote. Equity conversation open once mutual fit is established.

To apply, send: (1) your resume, (2) a brief writeup of a system you designed end-to-end — not code, but the architecture decisions you made and why, (3) a short note on why this role interests you.