Skip to content

Mock Engagement

  • Primary references: the earlier topics of this track, 01 Discovery through 07 Escalation and Handoff; your own platform from the course
  • Supplementary: the role-path capstone (one mock customer, Lexa, through every part); Shostack, Threat Modeling (for the security questionnaire)
  • Prerequisites: field-engineering topics 01 to 07; for the course modules, your system at v1.0.0 (course Passes 1 to 10)
  • Estimated time: 1 to 2 weeks in course Pass 11
  • A field engineer sells and delivers a system they understand to the bottom. Running a mock engagement against a platform you built removes the guesswork: every sizing number, benchmark, and security answer can be checked.
  • Each stage has a deliverable with a check: discovery notes, a sizing, a performance report, a POC plan, a migration plan, a security questionnaire, a handoff.
  • Numbers come from your own tools: capacity from M05.1, load reports from load.01, threat model and SBOMs from craft.17 and craft.18.

Work the capstone for the role path, then run field.01 to field.07 against your own platform in course order, each graded by its rubric.


The engagement is the same for any platform; what changes is how much you can prove. With your own system, every claim in a proposal links to a test, a report, or a document you produced, which is the standard a customer’s architects will hold you to.

Key ideas:

  • Stages field.01 to field.05: discovery, qualification and sizing, performance engagement, POC and evaluation, migration plan.
  • Commercials and security (field.06): answer a security questionnaire from your threat model, SBOMs, and usage policy.
  • Escalation and handoff (field.07): hand the platform to a mock customer team using your runbooks.
ModuleTopicKindPass
field.01Discovery against your platformpractice11
field.02Qualification and sizingpractice11
field.03Performance engagementpractice11
field.04POC and evaluationpractice11
field.05Migration planpractice11
field.06Commercials and security review: answer a customer security questionnaire from your threat model and SBOMpractice11
field.07Escalation and handoff: hand the platform to a mock customer team using your runbookspractice11
#ModuleChapterKindPass
1field.01Mock engagement: discoverypractice11
2field.02Mock engagement: qualification and sizingpractice11
3field.03Mock engagement: performance engagementpractice11
4field.04Mock engagement: POC and evaluationpractice11
5field.05Mock engagement: migration planpractice11
6field.06Commercials and security reviewpractice11
7field.07Escalation and handoffpractice11
TrackConnection
Field Engineeringthe track this topic applies
Securitythe threat model and SBOMs behind the questionnaire
Incident Response and Chaosthe runbooks the handoff uses