30-60-90 day plan for sales engineers
On this page
- What does a sales engineer need to be able to do by day 90?
- The 30-60-90 day plan
- How should product and demo certification work?
- How should a new sales engineer run a proof of concept?
- Which security documents will a new sales engineer handle?
- Which numbers should a new sales engineer track?
- What does "on track" look like at day 30, 60 and 90?
- A filled example
- How should a hiring manager use this plan in the final interview?
- What should the manager ask at the 30, 60 and 90-day check-ins?
- Common mistakes
- Adapting the plan
- Questions people ask
A 30-60-90 day plan for a new sales engineer should get them certified on the product and the standard demo in the first 30 days, running discovery and demos alone with account executives by day 60, and owning a scoped proof of concept and the technical side of their deals by day 90. The plan is built around the work only a sales engineer does: demos tailored to what discovery found, proofs of concept with written success criteria, and accurate answers to technical and security questions. Security answers become customer commitments, so the plan teaches the approved answer library before the first questionnaire arrives.
This plan is for a sales engineering manager or VP of sales onboarding a sales engineer, also called a solutions engineer, solutions consultant or pre-sales engineer. The account executive they partner with ramps on the 30-60-90 day plan for account executives, and the leader above both is covered in the 30-60-90 day plan for VPs of sales.
What does a sales engineer need to be able to do by day 90?
- Explain the product's architecture in the buyer's terms: how it deploys, integrates, authenticates users and handles data.
- Run technical discovery alongside the AE: current systems, integration points, security requirements, who decides technically.
- Deliver demos that show the buyer's own use cases, not a tour of every feature.
- Scope and run a proof of concept with success criteria the buyer signed up to before it started.
- Answer technical and security questions accurately, from the approved library, and know when to bring in product or security.
- Hand over to implementation with what was promised, what was tested and what the customer still expects.
The 30-60-90 day plan
30-60-90 day plan — [Name], Sales Engineer, [segment / region]
Reports to: [SE manager] Start date: [date]
Paired AEs: [names] Product areas: [list]
Demo environment: [tool / tenant] Security answers: [library owner]
DAYS 1-30 — Learn and certify
Goals:
- Complete the internal product certification and any admin or
technical courses the product team requires
- Build your own demo environment with realistic data
- Shadow [N] discovery calls, [N] demos and one live proof of concept
- Read the last [N] won and lost technical evaluations and the
reasons recorded
- Learn the security answer library: SOC 2 report access, policies,
certifications, who approves new answers
Deliverables by day 30:
- Product certification passed
- Standard demo delivered to the SE manager and an AE (demo
certification), with written feedback
DAYS 31-60 — Run deals with support
Goals:
- Run discovery and demos alone on [N] deals, with the SE manager
reviewing recordings
- Answer technical questions and draft questionnaire responses
from the library; route new questions to product or security
- Build one tailored demo for a priority use case in your segment
- Agree with each paired AE how you split discovery and follow-up
Deliverables by day 60:
- [N] demos delivered alone, with AE feedback
- One scoped proof of concept plan with signed success criteria
DAYS 61-90 — Own the technical win
Goals:
- Run a proof of concept to its success criteria and close it out
with a written result
- Own the technical side of your deals in forecast reviews
- Hand one closed deal to implementation with a written summary
- Send product feedback from lost and won deals to product managers
Deliverables by day 90:
- POC completed with a written outcome
- Handoff document accepted by the implementation lead
Check-ins: weekly with the SE manager; day 30, 60 and 90 reviews.How should product and demo certification work?
Certification turns "ramped" into something both the new hire and the manager can check. The timings below are examples; set them to the product's complexity.
| Certification | What the sales engineer shows | Who signs off | Example timing (example only) |
|---|---|---|---|
| Product knowledge | Passes the internal product course and can explain architecture, integrations and data handling | SE manager or product enablement | Week 2-3 |
| Standard demo | Delivers the core demo to a panel playing the buyer, handles objections and questions | SE manager and an AE | Week 4 |
| Discovery | Runs a recorded technical discovery that surfaces requirements, systems and decision process | SE manager, from the recording | Week 6 |
| Proof of concept | Scopes a POC with success criteria, timeline and buyer resources | SE manager before the buyer sees it | Week 8 |
| Vendor certifications | Holds any partner or platform certifications the product requires for implementation work | The issuing vendor | As the role requires |
How should a new sales engineer run a proof of concept?
A proof of concept without written success criteria tends to grow until it becomes free consulting. Before agreeing to one, the sales engineer and the AE should write down:
- The decision it supports: what the buyer will decide if the POC succeeds, and by when.
- Success criteria: three to five tests the buyer agrees in writing, each with a pass condition.
- Scope and time box: which use cases, which data, which integrations, and an end date.
- Buyer resources: named technical contacts, access to systems and test data.
- The close-out: a results meeting on a set date, with the result written against each criterion.
The SE manager should review the first POC plan before the buyer sees it. A buyer who will not agree success criteria is telling the team something about the deal.
Which security documents will a new sales engineer handle?
Buyers' security teams usually ask for evidence early in an enterprise deal. A new sales engineer should know which of these the company has, how to share them, and who approves answers, as of October 2026:
- SOC 2 report. An independent CPA firm's report on the company's controls against the AICPA's Trust Services Criteria for security, availability, processing integrity, confidentiality and privacy. Learn the report period, which criteria it covers, and the company's rules for sharing it.
- ISO/IEC 27001. The international standard for information security management systems; the current edition is ISO/IEC 27001:2022, amended in 2024. Know whether the company is certified, the certificate's scope and which entities it covers.
- CSA CAIQ. The Cloud Security Alliance's Consensus Assessments Initiative Questionnaire (version 4.1) is a set of yes-or-no questions about a cloud provider's controls, mapped to CSA's Cloud Controls Matrix. Some companies publish a completed CAIQ that answers many buyer questions in advance.
Every answer to a questionnaire can end up in the contract. Draft from the approved library, mark anything new for the security team, and never promise a certification, feature or configuration that does not exist. If the company sells into hiring or HR teams, the guide to SOC 2 for recruiting software shows how buyers in that market read the report.
Which numbers should a new sales engineer track?
| Measure | What it shows | Example standard (example only) |
|---|---|---|
| Certifications passed on schedule | Whether the ramp is on track | Product and demo certification by day 30 |
| Demos delivered alone | Independence and capacity | A small number by day 60, growing by day 90 |
| AE and manager feedback on recorded calls | Quality of discovery and demos | Reviewed every two weeks |
| POCs with signed success criteria | Discipline in technical evaluations | Every POC from day 60 onward |
| Turnaround on technical questions and questionnaires | Whether deals wait on the SE | Agreed with the SE manager by day 30 |
Technical win rate matters later, but in the first 90 days the sample is too small to judge one person by it.
What does "on track" look like at day 30, 60 and 90?
| Checkpoint | On track | Worth a direct conversation |
|---|---|---|
| Day 30 | Product and demo certification passed; own demo environment working; has shadowed a live POC | Still demoing from someone else's environment; certification slipping |
| Day 60 | Running discovery and demos alone; questionnaire drafts accurate and routed correctly | Feature tours instead of tailored demos; new security answers improvised |
| Day 90 | One POC closed against written criteria; clean handoff to implementation | A POC with no end date; implementation surprised by what was promised |
A filled example
Sales engineer: Arjun Mehta (invented), previously an implementation consultant, joining a data integration software company's mid-market team.
Day 30: Passed product certification in week three and the demo certification on his second attempt, after feedback that he spent too long on setup screens. Built a demo tenant with sample retail data.
Day 60: Ran discovery and demos alone on five deals. Drafted two security questionnaires from the library and routed four new questions to the security team instead of answering them himself.
Day 90: Ran a three-week POC against four written criteria; three passed and the fourth led to a scoped product request. The deal closed, and the implementation lead accepted his handoff document without a follow-up meeting.
How should a hiring manager use this plan in the final interview?
For sales engineers, pair a short 30-60-90 day plan with a mock discovery and demo: give every finalist the same fictional buyer brief and fifteen minutes of discovery before they demo something they know well. The guide on how to evaluate a 30-60-90 day plan in an interview covers the brief and rubric. A strong plan names certification, the demo environment, POC discipline and security answers; a weak one is an AE's plan with "learn the product" added. Questions that test it:
- "A buyer asks whether we support a feature you are not sure about. What do you say on the call?"
- "The AE wants a POC to start next week, but the buyer will not agree success criteria. What do you do?"
- "Tell me about a demo you changed because of something you learned in discovery."
The technical aptitude interview questions and the interview guide for sales roles cover the two halves of the job.
What should the manager ask at the 30, 60 and 90-day check-ins?
- Day 30: Which part of the product would you least like to be asked about tomorrow?
- Day 60: Which AE do you work with best, and what is different with the others?
- Day 90: What did lost deals teach you that product should hear?
Common mistakes
- Feature tours. Demos that show everything prove the product is big, not that it fits.
- Unbounded POCs. Without criteria and an end date, a POC becomes free consulting.
- Improvised security answers. They turn into contract terms nobody can meet.
- Skipping the handoff. Implementation inherits promises it did not know about.
Adapting the plan
- Enterprise: longer certification, more stakeholders, formal RFPs; extend the POC milestone toward day 120 if cycles are long.
- Product-led or high-velocity sales: fewer POCs, more short technical calls; measure turnaround and conversion after technical calls.
- Partner or channel sales engineers: add certifying partners' engineers and joint demos.
The general structure for any role is in the 30-60-90 day plan template for new hires.
Questions people ask
What should a sales engineer accomplish in the first 30 days?
Pass the internal product certification, build a working demo environment, deliver the standard demo to the sales engineering manager, and shadow discovery calls, demos and a proof of concept with experienced colleagues. By day 30 they should also know where the approved answers for security questionnaires live and who owns them.
When should a new sales engineer run demos alone?
After they have passed a demo certification: delivering the standard demo to a panel, usually the sales engineering manager and an account executive, who play the buyer and ask hard questions. In the plan on this page that certification comes around day 30, and solo demos start in days 31-60 on smaller or earlier-stage deals.
How do you measure a sales engineer's first 90 days?
By certification milestones passed on time, demos delivered alone with good AE and buyer feedback, at least one proof of concept scoped with written success criteria, and turnaround on technical questions and questionnaires. Technical win rate is useful later but too small a sample in the first 90 days to judge one person.
Should sales engineers answer security questionnaires themselves?
They should draft answers from the company's approved library and route anything new to the security team. Answers about SOC 2 reports, ISO/IEC 27001 certification or the CSA's CAIQ become commitments to the customer, so a new sales engineer should never improvise them.