RelationalAI - Solution Engineer

• You thrive in ambiguity and move with intent. You're motivated by deep understanding and meaningful impact. • Owner, not participant. You take full accountability for the outcome, not your slice of it. When something is broken and it's nobody's job, it becomes yours. • Owner, not participant. • You build. Your instinct in the face of a hard problem is to open an editor, not a deck. You'd rather show a working prototype on real data than a diagram of one. • You build. • High conviction, low ego. You argue hard for what you believe, you're direct about what's wrong, and you change your mind quickly when the evidence turns. You challenge ideas without making it personal - people leave arguments with you feeling sharper, not smaller. • High conviction, low ego. • Rigorous. You root-cause things. You can explain both why it broke and why your fix works. Surface symptoms don't satisfy you. • Rigorous. • Fast in unfamiliar territory. Dropped into a codebase, a domain, or a data model you've never seen, you're useful within days. "I only do backend" and "that's not my job" are phrases you don't use. • Fast in unfamiliar territory. • High tolerance for friction. Enterprise environments are messy - broken data, VDI access, security reviews, politics. You route around it and keep shipping. • High tolerance for friction. • Impact-driven. You want the thing you built to still be running, and still be load-bearing, two years from now. • Impact-driven. • What This Role Is Not • We'd rather be blunt than waste your time: • It is not demo-and-handoff pre-sales. You don't disappear after the POC; you're there when it goes to production. • It is not staff augmentation. You own outcomes, not hours or ticket queues. • It is not advisory. We deliver working software, not recommendations. • It is not a support role. You deploy new things; you don't maintain someone else's legacy. • 5+ years building and shipping production software, at least some of it inside customer or partner environments • Demonstrated end-to-end ownership: you have personally taken something from an ambiguous problem statement to running in production, and you can walk us through the whole arc, including what went wrong • Strong SQL and deep familiarity with cloud data platforms (Snowflake, BigQuery, Databricks, Redshift) • Strong programming ability - Python primarily; comfort with declarative or logic-style languages is a real advantage • Comfortable reading unfamiliar source code, interpreting stack traces, and debugging systems you didn't write • Able to hold your own with both a VP of Supply Chain and a staff data engineer, in the same meeting • Comfortable operating in high-autonomy, high-velocity, low-instruction environments • Built analytical, decision, or reasoning applications that reached production and stayed there • Experience with optimization, constraint solving, rule engines, graph algorithms, or ML on structured data • Semantic modelling, data pipelines, and governance in real enterprise settings • Track record of upstream contribution - features, tools, or abstractions you built for one customer that became standard for everyone • Prior experience in enterprise technology, AI, or analytics platforms • How We Hire • How We Hire • Our loop is designed to test the job, not trivia. Expect a technical screen; a session where you navigate and extend a system you've never seen before; a problem-decomposition session on a realistic customer scenario; and a conversation about ownership with the hiring manager. We're looking for how you think when you don't know the answer. • The Solution Engineer position offers a base salary range of $170,000 to $200,000, along with equity and comprehensive benefits. Please note that this range serves as a guideline; actual total compensation may vary based on factors such as experience, skill set, qualifications, and geographic location.