Software Engineer, Applied AI Engineering

Linked In is your professional network. Facebook and Instagram are your social networks.

Ruxlo is your home's network.

Your home. Your neighborhood. Your town.

Ruxlo benefits everyone involved in real estate. Builders, architects, contractors and realtors do work that is quickly forgotten. A lawn sign stays up for a month or two, and after that no one knows who did the work. We're replacing that with one durable digital record attached to the parcel itself. Work is recorded by the professional who did it and confirmed by the owner who paid for it.

When the house sells, the record stays. Think Carfax for homes.

Around the property is your neighborhood, where you can comfortably connect and communicate with neighbors through the Ruxlo app, see other property profiles and ask about the contractors your neighbors used. Further out is your town, where you choose the notifications you want, such as recycling, bulk waste pickup, farmers markets or any other event the town sponsors.

Underneath all of it, is our database of 150 million properties, users can leverage AI natural language search to get the information they are looking for quickly. We're backed by an experienced SaaS founder and CEO who bootstrapped and exited a Gov Tech SaaS company in early 2026. We've assembled a fantastic team and have a unique opportunity to help define a category at the intersection of AI, data and real estate, the largest asset class in the country.

We're hiring a Staff Software Engineer, Applied AI. You'll set the technical strategy for how Ruxlo builds AI into the product, from a single well-designed LLM call to long-running autonomous agents, and you'll be the technical anchor for applied AI across teams.

The range is the point. One week you're tuning natural language search over property records or extracting structured data from a scanned receipt. The next you're designing an agent that runs in the background for hours, calls dozens of tools, pauses for a human approval, and resumes exactly where it left off after a failure.

Some of these agents act on a user's behalf. A homeowner might ask an agent to request quotes from contractors your neighbors used, file a receipt and warranty, or follow up until a contractor confirms a job. A contractor might hand an agent the import of their work history. These agents carry a user's authority, so they ask before anything consequential, stay inside what that user is allowed to do, and leave a record the user can review.

You know when a prompt is enough, when retrieval is needed, and when only an agent will do. The engineer who succeeds here ships all three to production, measures them honestly, keeps their cost in check, and leaves behind a platform other engineers build on.

The patterns for production agents are still being invented, and you'll be setting direction without a playbook to lean on. If that sounds like the appeal rather than the warning, we should talk.

• Own the architecture of Ruxlo's AI systems end to end: model access and routing, retrieval, prompt and tool layers, agent runtime, evaluation and cost
• Ship LLM-powered product features, including natural language search, summarization, structured extraction and classification over property, ownership and contractor records.
• Ship autonomous background agents that verify, reconcile and enrich records and keep them fresh.
• Ship agents that act on a user's behalf, such as requesting quotes, following up with contractors, importing work history and filing documents, with the user's consent at each consequential step.
• Design durable, long-running agent workflows on a durable-execution engine such as Temporal, with retries, timeouts, idempotent tool calls and safe resume after…