The Role
You'll be the primary engineer behind Parqlet — owning the backend, the database, the mobile app, and the infrastructure that ties them together. This is a senior, autonomous role: you'll set the technical direction, decide what to build next, and ship it. If you like owning a whole product end-to-end rather than a narrow slice, this is that job.
The core functionality is done. Your job is to keep it stable and correct as our first building goes live, then build the next wave from the roadmap:
Rewards exchange — residents redeem credits for gift cards and local business perks
Garage camera integration — license plate recognition so buildings automatically verify every vehicle in the garage is authorized
Revenue share with buildings — a model where the platform pays for itself as the building's parking pool grows
Multi-building scale — onboarding new buildings, each in its own isolated environment
What you'll own
The API & business logic — booking flows (auto-assign, holds, broadcast/offer, approvals), the credit/wallet system, and the rules that keep them correct.
Payments — Stripe integration end-to-end: PaymentIntents, webhooks, idempotency, subscriptions/invoices, and the reconciliation and safeguards that make sure no one is ever double-charged or under-credited.
The database — PostgreSQL schema design, migrations, data integrity, and query performance. You're comfortable owning schema changes and migration tooling in production.
The mobile app — a React Native / Expo app: features, releases through EAS to TestFlight and the App Store, and the native integrations (Stripe, push notifications).
Infra & reliability — CI/CD, deploys, observability, and hardening the system so incidents are rare and quick to resolve.
BuildingLink data integration — syncing resident and unit data from the building's management system via FTPS file exchange, keeping our database current with move-ins, move-outs, and spot assignments.
Our stack
Backend: Node.js, TypeScript, Hono, Drizzle ORM, PostgreSQL
Payments & services: Stripe, Firebase Cloud Messaging (push), object storage (MinIO/S3-compatible)
Mobile: React Native, Expo (expo-router), EAS builds, native Stripe SDK
Infra: Docker, GitHub Actions CI/CD, migration-driven schema management
Auth: OTP + JWT
You don't need to have used every one of these, but you should be genuinely strong on the backend/database side and able to move confidently across the whole stack.
What we're looking for
5+ years building and running production full-stack systems, with real depth on the backend and databases (SQL schema design, migrations, transactions, avoiding race conditions).
Hands-on experience with payments (Stripe or similar) — you understand webhooks, idempotency, and why correctness with money is non-negotiable.
Solid TypeScript/Node and comfort in a React Native / mobile release workflow (or a track record that shows you'll pick it up fast).
Strong instincts for security (authorization, data protection) and reliability (observability, safe migrations, graceful failure).
Excellent written communication — you keep work visible, flag risks early, and write clear PRs and updates without being asked.
How we work — and who thrives here
AI-accelerated by default. We'll provide you a Claude subscription (Claude Code) and tools like CodeRabbit for automated reviews. We expect you to lean on them heavily to ship faster and with higher quality — and to review the AI's work critically. You direct the tools, catch what they miss, and make sure the codebase stays clean and coherent as it grows. AI writes a lot of the code; you own its quality.
We run on Loom videos and written updates — you should be comfortable recording a quick walkthrough instead of scheduling a meeting. Sync calls happen in the afternoon (CET).
Total ownership. You're trusted to be accountable for outcomes.
Productivity and quality, together. We move fast, but we don't ship sloppiness into a payments product. Tests, code review, clean migrations, and thoughtful design are how we go fast sustainably.
Communicate proactively. Clear and frequent communication is what makes it work — status, tradeoffs, and "here's what I'm about to do" over silence.
