DebtBook
Solutions Engineer
Charlotte, NCmidAdded today
About this role
DebtBook seeks a Solutions Engineer to bridge sales and product teams in the public sector treasury space. You'll conduct discovery with prospects, deliver tailored product demos, and translate complex financial workflows into clear business value to support customer acquisition and account expansion.
What you'll do
- Provide presales support by partnering with Account Executives on new customer and expansion opportunities
- Conduct discovery conversations to understand prospects' processes, challenges, and technical environments
- Prepare and deliver customized product demonstrations connecting DebtBook capabilities to client needs
- Develop working proficiency across Debt, Cash, Investment, and Lease Management modules
- Serve as subject-matter resource in assigned product areas while coordinating complex multi-product demos
- Continuously deepen knowledge of treasury operations, public finance, financial reporting, and competitive landscape
What they're looking for
- Solutions engineering or presales experience
- Presentation skills for finance and technical audiences
- Treasury, banking, or public finance knowledge
- Complex business process analysis and translation
- SaaS product demonstrations and discovery techniques
- Project management and stakeholder coordination
- Financial data integrations and systems knowledge
- RFP response and value engineering
Opens the application — the Jobs AI extension fills it for you. Set up autofill
Opens the official application on the employer’s site. No login required.
DebtBook
DebtBook builds a sophisticated treasury platform designed for public sector financial management. The company is hiring software engineers to develop and maintain its Ruby on Rails and React applications.
- Website
- debtbook.com
Likely interview questions
- Walk us through your experience conducting discovery with enterprise finance customers—how do you ensure you uncover their true pain points?
- Tell us about a complex financial or technical concept you've had to explain to non-technical stakeholders. How did you approach it?