Solution Engineer

Job description

Mercura ( YC W25 ) helps the companies that build the real world move at software speed, automating the back-office work that runs the $12 trillion industry behind every hospital, school, and power plant. We started with one of their biggest bottlenecks - turning messy technical requests into accurate quotes - and grew to $2M ARR in our first year . With a team of 16, we're now targeting $10M by the end of 2026 as well as our expansion into the US. About the role This is a technical role at the center of how we win enterprise deals. Our customers are technical suppliers: industrial, careful with their buying decisions, and often disappointed by software before. They don't decide based on a pitch. They decide when they see Mercura take one of their own messy quote requests and return a correct quote, on their data. That is hard to do well. Real requests are unstructured, product catalogs are complex, and quotes run through ERP systems that every customer configures differently. A standard demo rarely survives the first real edge case. So most enterprise deals come down to one question: can someone make Mercura work, credibly, inside this specific customer's setup? If this sounds exciting, this role is for you. Your responsibilities You own the technical side of every major deal, from the first demo to a signed customer. Understand the customer's reality. Get into the customer’s actual workflows and identify the case that best shows what Mercura can do for them. Lead the technical conversation. Join sales conversations and be the credible counterpart on integrations, data, security, and architecture. Resolve the concerns that stand between the customer and a buying decision. Build the proof. Set up demos and proof-of-concepts on the customer's real data that you prepared and structured. Build prototypes for new features, and make customers feel that Mercura works in their own context rather than an idealized one. Feed insights back to the team. You're often the first to see why a deal stalls. Judge whether a customer request is demo-only, a quick customer-specific build, or something that needs core product and engineering - and translate that into clear, prioritized input for the team. Who we're looking for Native-level communication in German: You can explain clearly, present well to senior stakeholders, and stay composed when a demo is tested in real time.…