Solutions Engineer

The AE always runs discovery, always runs the first demo, always owns pricing and the close. You never join a first call. You join when a technical evaluator is joining the next meeting, when the solution needs custom architecture, when a proof of concept needs building, or when an integration question has stumped the AE twice. If a deal arrives without a completed discovery brief, you send it back. This role is a weapon the AEs deploy, not a crutch they lean on.

First 30 days: you can run our standard demo solo and have shadowed every active enterprise deal.

First 90 days: you own the technical calls on live deals and have shipped the first three playbooks in the pattern library.

Year one: you own the technical motion on every enterprise deal, the pattern library covers our top ten deployment types, and the founders have not run a scoping call in six months.

You have been an SE, Solutions Consultant, or senior Implementation Engineer in staffing technology, ATS ecosystems, or CCaaS and business telephony. You do not write production code, but you read API docs fluently, test endpoints without an engineer, and can debug an integration live on a call. You have built or configured AI agents or IVR flows, you can run a technical demo solo under hostile questioning, and you write documentation people actually use. You explain architecture in plain English to a business owner and hold your own with their IT team in the same meeting. You get genuine satisfaction from making the deal work, not from being the hero of the room.

You need a solved problem handed to you with a runbook.

You want to stay behind the scenes. This role is customer facing every week.

You see documentation as someone else's job.

You cannot travel to shows and customer sites.

The technical motion that closes our biggest deals currently lives in two founders' heads. You are the person who scales it, owns it, and builds the playbook that everyone after you runs.