Founding Sales Engineer

se Revel is built by Sales Engineers for Sales Engineers, so the person who sells it should be one. As Founding Sales Engineer you run POCs of se Revel using se Revel: you build the demo environments, write the technical win plans, and prove the product to SE teams who know exactly what a bad POC tool looks like. Nearly all our customers come from SEs telling other SEs, which means your evaluations are our marketing, and every gap you hit in a live one is a gap you get to fix in the product.

• Run technical evaluations of se Revel end to end: scope the use cases, set up the workspace and customer portal, drive the POC to a decision
• Build and maintain demo environments and realistic POC data that show use-case intelligence, AI coaching and customer portals doing real work
• Write a technical win plan for each evaluation: success criteria, integration path, risks, and what has to be true for the prospect to say yes
• Get our integrations working in the prospect's environment, starting with Salesforce, Slack and Gong, and the rest of the list (Jira, Confluence, Microsoft Teams, Product Board) when the deal needs them
• Feed what you see in the field back into the product: reproducible bugs, missing capabilities, and where the workflow does not match how SEs actually work
• Turn what you learn into the POC playbook, templates and enablement material that whoever comes after you will run with
• Take what a lost evaluation taught you to the founders, with specifics, and push for the fix

• Several years as a Sales Engineer or Solutions Engineer at a B2B software company, running POCs and POVs yourself, not just overseeing them
• Hands-on with SaaS integrations: you have connected products to Salesforce, Slack or similar via APIs, webhooks or admin consoles, and can debug when it breaks
• Comfortable owning the technical side of a deal from first call to close, with an AE or without one
• Clear, direct writing: you can turn a messy evaluation into a one-page win plan a buyer will actually read
• Able to work without a playbook: remote, small team, decisions made before the process exists

• Admin or integration-side experience with Gong, Jira, Confluence or Product Board
• You have led an SE team and know what SE leadership needs to see in POC data
• Basic scripting or SQL to build demo data and answer questions without waiting for engineering
• You have been an early hire before and know what it is like to build the playbook instead of inheriting one