Job Title: Founding Engineer Company Name: Inferal Job Url: https://www.linkedin.com/jobs/view/4372942345/?eBP=NOT_ELIGIBLE_FOR_CHARGING&trk=flagship3_search_srp_jobs&refId=a%2BwyKlLIcW5EL3brblpd3g%3D%3D&trackingId=63ARQgeLH1zNavFbHdD93g%3D%3D Job Description: Inferal (prev. Omnigres) Founding Engineer San Francisco Bay Area · 1 day ago · 64 people clicked apply Promoted by hirer · Responses managed off LinkedIn Remote Full-time Apply Save Your profile was shared with the job poster. Undo Did you apply? Let us know, and we’ll help you track your application. Yes No Use AI to assess how you fit Get AI-powered advice on this job and more exclusive features with Premium. Try Premium for PKR0 Show match details Tailor my resume Help me stand out About the job Palantir charges $10M to connect the dots. There's a layer missing from the data stack. Most people don't notice because they've been working around it for so long it doesn't feel like a gap anymore. It feels normal. Your database stores facts. Your application code reacts to requests. Between those two things, there's a question nobody answers well: what should happen right now, given everything the system knows? Today, the answer is scattered across cron jobs, event handlers, polling loops, and message queues. Dozens of ad hoc mechanisms pretending to be one coherent system. They sort of work. Until they don't. And when they don't, it goes one of two ways: silence, where the thing that should have happened simply doesn't, or a cascading failure, where one missed condition tears through everything downstream. What we're building A system that watches everything your business knows and acts the moment conditions align. Not a workflow you define. Not a query you run. Continuous evaluation against streaming facts, where agents activate with full context already assembled. Every decision traceable. Every inference with provenance. Think of it as the missing layer between your database and your agents. Where we are Early stage. Paying customers, revenue, hard problems we haven't solved yet. The roadmap changes as we learn. You'll shape the product, not just build what's specced. Who we're looking for Someone who can hold database internals and agent orchestration in the same mental model. You've worked close to metal: graph engines, distributed scheduling, storage systems. You also know what it takes to make AI agents reliable in production, not just in demos . Rust, Python, and whatever else the problem demands. You're comfortable when the map is incomplete and the next step isn't obvious. That's where the interesting work lives. Please note that at this moment, we're NOT looking for dedicated AI/ML engineers; using AI/ML is just a part of our routine. We care more about what you've built than where you went to school. More about how you think through a problem than which languages are on your resume. Attitude first, then belief, then skill. Skills can be learned. Attitude can't. Not ready to apply yet? Join the Software Internals Discord, a community where people dig into the kinds of problems listed above.