Senior Sales Engineer resume example

• As workstream lead, led technical discovery with sales and customer administrators, mapping identity, data flow, and integration constraints before proposing solutions; recorded which requirements the demo would prove.
• With responsibility for the review standard, built solutions demonstrations with customer-like sample data and explicit pass/fail checks; returned unresolved technical gaps to the sales plan instead of presenting the proof of concept as production-ready.
• Agreed proof-of-concept acceptance criteria with the buyer, demonstrated the proposed integration using representative data, and recorded unsupported capabilities separately from the commercial proposal.
• Prepared technical presentations showing authentication, data flows and failure handling in the proposed integration; answered buyer questions with a reproducible demonstration and separated roadmap items from available features.
• Owned a security proof of concept using agreed customer requirements, resolving a Linux policy conflict before the technical presentation and recording test exclusions.
• Built an automation script for Windows and AWS demo setup, reducing preparation time from 75 to 30 minutes and enabling repeatable customer demonstrations.

• Documented product gaps and workarounds from 42 technical discovery calls; aligned review standards and decision owners across the participating teams. Working with partner teams, shortened the path from qualified interest to a decision.
• Updated a troubleshooting article after reproducing a reported failure, separated user actions from administrator-only steps, and checked the procedure with a colleague using a clean setup.
• Reproduced a customer issue on a clean configuration, compared the working and failing settings, and tested the proposed correction without administrator privileges. Published a troubleshooting sequence that preserved the customer’s original configuration.

• Created demonstration environments for 7 industry workflows with seeded data; aligned review standards and decision owners across the participating teams
• Configured a separate test environment with a documented network diagram, account permissions and failure scenarios; captured the logs needed to distinguish connectivity, authentication and application faults.
• Tested the recovery guide from a fresh account, checked required permissions at each step, and added rollback instructions where a configuration change could disrupt the working baseline.
• Owned the recovery rehearsal using an isolated test account, resolved a missing permission prerequisite and completed the restore without changing the working baseline.

Relevant coursework: Algorithms, operating systems, databases, computer networks

• Published an independent troubleshooting guide using annotated logs, separating connectivity, authentication and application failures and documenting the rollback decision at each step.