Back End Developer

Company Description TheFamSync transforms Smart TVs into family coordination dashboards, offering enhanced visibility into family schedules, tasks, and plans. By unifying family calendars, task lists, meal planning, and real-time availability updates, this platform reduces the mental load of household coordination. FamSync integrates seamlessly with Google, iCloud, and Outlook for synced calendars, while also offering features like shared task reminders and live status updates. When idle, it displays a visually appealing ambient photo mode. Our mission is to simplify family life by enhancing communication and organization in a seamless, user-friendly way.

Role Description We're looking for a

Backend Engineer

who wants full ownership of TellySynco's server-side infrastructure — from real-time sync and APIs to AI/agent services and payments. You won't be slotting into a team of 20 backend engineers; you'll be

the

backend engineer, making foundational architecture decisions that will scale with the product. This is a high-autonomy, high-impact role where your work directly powers what families see on their TV every morning.

What You will Own:

Real-Time Sync Engine Design and build the real-time data sync layer that keeps family calendars, tasks, and notifications in sync across 4–6 devices with sub-3-second latency Implement conflict resolution for simultaneous edits (e.g., two family members updating the same event) Build offline-first reconciliation so the app works seamlessly even with intermittent connectivity API Architecture Design and maintain RESTful (or GraphQL) APIs serving iOS, tvOS, iPadOS, and future Android clients Integrate with Google Calendar API, Microsoft Graph (Outlook), and Apple EventKit via server-side orchestration Build the OAuth 2.0 authentication flows for third-party calendar providers AI & Agent Services Build and deploy server-side AI pipelines for intelligent calendar parsing, smart suggestions, and agent-based task orchestration Integrate with LLM APIs and orchestration frameworks for agentic AI features Complement on-device CoreML/Vision processing with server-side NLP for complex document understanding Infrastructure & DevOps Own the Firebase ecosystem: Firestore/Realtime Database, Cloud Functions, Firebase Auth, FCM (push notifications) Set up CI/CD pipelines, monitoring, alerting, and logging Manage the Python AI microservice deployment (Cloud Run or equivalent) Payments & Subscriptions Integrate RevenueCat server-side webhooks for subscription management Handle entitlement verification, receipt validation, and subscription lifecycle events

What We are Looking For:

Must-Have (Critical) 3–6+ years

of backend engineering experience Node.js / TypeScript

— strong proficiency building production APIs with Express, Fastify, or similar frameworks Firebase

— hands-on experience with Firestore or Realtime Database, Cloud Functions, Firebase Auth, and FCM Real-time systems

— experience with WebSocket, Server-Sent Events, or Firebase's real-time sync. You understand push vs. pull, connection management, and data consistency API design

— RESTful API design, versioning, error handling, rate limiting. Bonus for GraphQL experience Authentication & security

— OAuth 2.0 flows, JWT, secure token management, role-based access control

Strong-to-Have (High Value) Python

— comfortable building and deploying Python services for AI/ML workloads (FastAPI, Flask, or Cloud Run) AI/LLM integration

— experience calling LLM APIs, building agent workflows, or working with frameworks like LangChain, LlamaIndex, or CrewAI Cloud infrastructure

— GCP (Cloud Run, Cloud Functions, Pub/Sub) or AWS equivalent. Terraform/IaC experience is a plus Third-party API integration

— Google Calendar API, Microsoft Graph, or similar complex REST APIs with OAuth

Nice-to-Have (Bonus) Mobile backend experience

— prior work building backends specifically for iOS/Android consumer apps Subscription/payments

— RevenueCat, Stripe, or App Store/Play Store server-side receipt validation Event-driven architecture

— Pub/Sub, message queues, event sourcing patterns Cross-platform considerations

— experience serving both iOS and Android clients from a single backend, handling platform-specific push notification logic (APNs vs. FCM)