Job Url: https://www.linkedin.com/jobs/search/?currentJobId=4366892904&distance=25.0&f_AL=true&f_TPR=r20000&f_WT=2&geoId=103644278&keywords=software%20engineer&origin=JOB_SEARCH_PAGE_JOB_FILTER&start=175 Job Description: Founding Engineer REALLM Realty · United States (Remote) Easy Apply Save Save Founding Engineer at REALLM Realty Show more options Your profile is missing required qualifications Show match details Help me update my profile BETA Is this information helpful? Get personalized tips to stand out to hirers Find jobs where you’re a top applicant and tailor your resume with the help of AI. Try Premium for PKR0 Meet the hiring team George Humphreys 3rd CTO | AI for Real Estate Job poster Message About the job # Founding Engineer @ Maira **Location:** Remote (US) or Hybrid (SF Bay Area) **Stage:** Pre-seed / Early **Team Size:** 2 founders --- ## 🏠 What is Maira? Maira is an AI assistant built specifically for real estate agents. We're not building another chatbot...we're building a system that actually understands the agent's world - their contacts, their listings, their calendar, their relationships - and can _take action_ on their behalf. When an agent says *"follow up with John about the Elm Street property,"* Maira knows who John is, what their relationship history looks like, what stage the property is at, and what the right next action is. Then it executes—drafting emails, scheduling showings, updating CRMs—with the agent in the loop on high-stakes actions. We're two technical founders building the first real AI teammate for the $50B real estate brokerage industry. --- ## 🔧 The Role We're looking for our first engineering hire—a **founding engineer** who will shape the technical foundation of Maira alongside us. This is not a role where you'll be assigned tickets. You'll be expected to own entire product surfaces end-to-end: from understanding the user problem, to designing the architecture, to shipping and operating the solution in production. **You will:** - Act as a technical owner: making architecture calls, setting standards, and deciding what not to build - Build AI orchestration systems that reason, plan, and execute multi-step workflows - Design preference learning models that adapt to user behavior - Create multi-step wizards and data collection flows that produce intelligent outputs - Debug production issues at odd hours **In your first 90 days, you might:** - Ship an improvement to our context engine that makes agent responses 2x more relevant - Build a new tool integration (e.g., MLS data, calendar sync) end-to-end - Design and implement a new user-facing feature from scratch - Establish patterns and conventions that define how we build software --- ## 💻 Our Stack - **TypeScript** everywhere (frontend, backend, shared packages) - **Next.js** (App Router, API routes) - **PostgreSQL** with Drizzle ORM - **LLM integrations** (OpenAI, Anthropic, Vercel AI SDK) - **pnpm monorepo** with shared packages - **Vitest** for testing - **Docker** for local development We care less about specific framework experience and more about your ability to learn quickly and make good decisions. --- ## 🎯 What We're Looking For ### Required - **Strong fundamentals.** You understand data structures, systems design, and can debug hairy async issues without hand-holding. - **Full-stack fluency.** You can build a database schema, an API, and a frontend in the same afternoon—and know when each layer needs attention. - **Bias toward shipping.** You'd rather ship something imperfect and iterate than architect forever. But you also know when to slow down and design. - **Clear technical communication.** You can explain your decisions in writing. You document your tradeoffs. You write runbooks. - **High agency.** You don't wait to be told what to do. You see problems and fix them. You proactively identify risks and surface them. - **Comfort with ambiguity.** Requirements will be incomplete. You'll need to make judgment calls, ship, and adjust. ### Bonus - Experience building AI/ML systems in production - Familiarity with real estate, proptech, or adjacent industries - Previous startup experience (especially as an early engineer) - Open source contributions or notable side projects --- ## 🚀 Why Join Now? ### The opportunity - **Equity that matters.** As a founding engineer, you'll have meaningful ownership in what we're building. - **Outsized impact.** Every line of code you write will directly shape the product and the company. - **Technical depth.** You'll work on genuinely hard problems: AI orchestration, preference modeling, context-aware systems. - **Learn at startup speed.** You'll wear many hats and grow faster than you would at a larger company. ### The reality Let's be honest about what this is: - **We're tiny.** Two founders and you. There's no HR, no corporate ladder, no dedicated QA team. - **Compensation is startup-level.** We'll pay fairly, but we can't compete with FAANG cash comp. The bet is on equity. - **You'll work hard.** This isn't a 9-5. We're building something from zero, and that takes intensity and commitment. - **Things will break.** We're moving fast. You'll ship bugs. You'll fix them. You'll learn. - **Ambiguity is constant.** We're still figuring out parts of the product. You'll need to be comfortable making decisions with incomplete information. If that scares you, that's okay—this role isn't for everyone. If it excites you, keep reading. --- ## 📋 How We Evaluate We believe in evaluating engineers the way they'll actually work—not through leetcode puzzles. Our process: 1. **Quick intro call** (30 min) – Get to know each other, gut check on fit 2. **Technical challenge** (8-12 hours, async) – Build a real feature in a repo we provide. We're evaluating: - Does it work? - Is the architecture clean? - Are the tradeoffs documented? - Can we run and debug it from your docs? 3. **Technical deep-dive** (60 min) – Walk us through your solution. Defend your decisions. Discuss alternatives. 4. **Founder chat** (45 min) – Alignment on values, working style, and what we're building We respect your time. The challenge is designed to be completable over a weekend, and we give you flexibility on timing. --- ## 🧠 What Kind of Problems You'll Solve Here's a taste of the technical challenges at Maira: **Context Engine Design** When a user says "follow up with John about the Elm Street listing," how do you parse that prompt, query the database for relevant entities (contacts, properties, interactions), and build a context snapshot—all before the LLM even starts planning? **Multi-Step Orchestration** How do you break a user request into discrete steps, execute them with dependency awareness, persist state for resumability, and gate high-risk actions (like sending emails) behind approval—while continuing to execute independent steps? **Preference Learning** How do you learn a user's preferences from their behavior (swipes, clicks, engagement) and score new items against those preferences? How do you explain why something scored high or low? **Explainable Outputs** Real estate is high-stakes. When we suggest a price range for a home, we need to show our work: which comparables we used, what adjustments we made, why. How do you make AI outputs defensible? --- ## 📩 How to Apply Apply through LinkedIn or send an email to **[team@trymaira.com]** with: 1. A brief note on why Maira interests you 2. Your resume or LinkedIn 3. (Optional) Links to projects, GitHub, or anything that shows how you build No cover letter template. No formality. Just tell us who you are and what you're looking for. --- ## FAQs **Do I need AI/ML experience?** Helpful but not required. We care more about strong engineering fundamentals and the ability to learn new domains quickly. **Is this remote?** Yes, we're remote-first with optional in-person time in the SF Bay Area. **What's the interview timeline?** We move fast. Typically 2-3 weeks from first call to offer. **Can I see the technical challenge beforehand?** We'll share it after the intro call. It involves building a real feature (AI orchestration, preference modeling, or a guided wizard flow) in a TypeScript/Next.js/Postgres stack. **What if I'm still in school or recently graduated?** We don't filter on credentials. If you can build, you can build. --- ## Experience TypeScript Next.js PostgreSQL Full-Stack Development Distributed Systems AI / LLM Systems Early-Stage Startups --- *Last updated: January 2026*