SlipstreamJobs tracks this role from the company's public career site. Apply directly on the employer's site.
RelationalAI is hiring a Solution Engineer to embed within customer organizations and own end-to-end outcomes for enterprise AI decision systems. You'll work directly with executives, domain experts, and data teams to identify high-impact business problems—inventory misplacement, hidden risk concentrations, fraud patterns, capacity planning—then model their world using RelationalAI's ontology, formulate reasoning problems, write PyRel code, and deploy working systems against customer data in Snowflake.
Every engagement produces two deliverables: a production decision system that changes how the customer operates, and critical feedback on platform gaps—modeling patterns you hand-rolled, constraint formulations that should be primitives, workarounds that should be APIs. You bring these insights back, argue for them, and the strongest become product roadmap items. This role exists to close the gap between what customers need and what the platform provides; if you only deliver the first deliverable, you're a consultant, not what we're hiring.
You'll operate with unusual autonomy: you decide what's worth building, when a workaround is acceptable versus technical debt, and when a customer's stated problem isn't their real problem. You're technical enough to root-cause production issues yourself rather than escalate. You own discovery, modeling, implementation, performance tuning, production hardening, and measurement—no handoffs at each stage.
You thrive in ambiguity and move with intent. You're an owner, not a participant; when something is broken and it's nobody's job, it becomes yours. Your instinct facing a hard problem is to open an editor, not a deck. You'd rather show a working prototype on real data than present a diagram. You argue hard for what you believe, stay direct about what's wrong, and change your mind quickly when evidence warrants it. You're rigorous—you root-cause things and can explain both why something broke and why your fix works.
You're fast in unfamiliar territory: dropped into a new codebase, domain, or data model, you're useful within days. You don't say "that's not my job." You have high tolerance for enterprise friction—broken data, VDI access, security reviews, politics—and route around it to keep shipping. You're impact-driven: you want the systems you build to still be running and load-bearing two years later.
This is not demo-and-handoff pre-sales, staff augmentation, or advisory work. You deliver working software that stays in production.
