General Responsibilities

• Work with the sales team to win deals
• Build and present demos to the client
• Demos need not be built as needed, they can be prepared already in advance and repeatedly demonstrated to different clients
• Running live demos in front of the audience are favored over pre-recorded ones
• Depending on the case, letting the audience test out the demo is also allowed but guidance must be provided
• Answer technical questions and explain technicalities of the product or solution to non-technical stakeholders during presentations
• Learn more about the customer’s current process and translate pain points / objectives into technical requirements
• Be a consultant to guide the customer on their current situation and how they can be helped by Senti’s products or solutions
• Scope the solution to address the customer requirements
• Plan timelines and resources based on the gathered requirements
• Design a cloud architecture diagram to turn over to the development team
• Decide on the best technology / component to use for implementation
• Provide different options based on cost, efficiency, or infrastructure of the client
• Make cost estimates on the build based on the estimate usage / parameters of the customer
• Write technical parts in RFP (Request for Proposal) / Proposal
• Fill in functionalities, compliances, and cost estimates in RFI (Request for Information) or RFQ (Request for Quotation)
• Create documentation for implemented POCs
• Evangelize about Senti’s products and previous use cases in events (e.g. webinars)

Must-have

• Excellent communication skills and presentation skills
  • Especially explaining highly-complex systems in simple terms to non-technical audiences
  • Also explaining general needs from non-technical stakeholders to the Engineering team
  • Can act as a bridge between the client/Sales team and the Engineering team
  • Curiosity
  • Knows how to ask the right questions to dig deeper on the customer’s use case
  • Can mentally picture the current situation of the customer
  • Stays updated with the newest cloud technologies
  • Strong problem-solving skills
  • Can envision an “ecosystem” of products/solutions that help alleviate customer’s pains
  • Can identify which implementation or technologies will work best for the client and their current infrastructure, regardless of cloud platform
  • Comfort with external meetings
  • Especially the majority of a CE’s day is devoted to meetings
  • Adaptability
  • Must know how to deal with changes (not only in terms of solution architecture, but also other parts of the entire project such as timelines and direction)
  • Technical know-how
  • Familiarity with designing Cloud Architecture
  • Familiarity with Microservices
  • Familiarity with cloud security concepts

Good to have
Know-how

• Degree in Computer Science, Information Technology, Engineering, or related field - OR experience with sales or marketing in the Software industry (especially in Artificial Intelligence)
• Familiarity with telephony concepts (e.g. VoIP)

Building demos

• Familiarity with developing on Cloud services, especially Google Cloud Platform
• Familiarity with communications APIs such as Twilio
• Previous experience with chatbot or voicebot development and conversation design

Typical schedule of Customer Engineers

• Meet with the Sales team on Mondays 9 AM
• Sync-up with co-CE(s) after Sales meeting if necessary, ideally mornings
• CEs are each other’s accountability partner, so this is the opportunity to share what has been done, what should be done, and what is currently being done
• Rants on work slumps/demotivation phases are ????
• Asking for support on a task is ????
• Meetings are usually from 11 AM to 12 NN and 1 PM to 5 PM
• Meetings may be online or face-to-face
• Free time slots are devoted to building demos/POCs, work breakdown structure (WBS/timeline), cloud cost estimates, proposals, and various documentation

Extra free time may be devoted to upskilling and attending various events