Appendix F. End-to-End Cases: BDM and Backend
Coverage map
| Chapter | BDM B2B SaaS payments | Backend Engineer |
|---|---|---|
| 2. Role and criteria | Role brief: partner revenue, discovery, enterprise negotiations | Role brief: API reliability, backend design, responsibility for keeping the system running in production |
| 4. Screening | Check B2B SaaS, deals, and motivation for the payments domain | Check the stack, production-support experience, and motivation for reliability |
| 5. Interview | Role-play scenario: a conversation with a CFO/partner | System design / work sample |
| 6. Assessment | Scorecard: discovery, negotiations, funnel judgment | Scorecard: API design, code quality, incident-driven thinking |
| 8. Levels | Level anchors for Sales/BDM | Level anchors for Engineering |
| 9. Decision | Decision log for offer, pause, or decline | Decision log for offer, pause, or decline |
| 11. Offer | Counteroffer risk and compensation expectations | Competing-offer risk and role-level risk |
| 12. Preboarding | Hand over partnership and client context | Hand over system context, access, and the first-week plan |
| 13-14. Analytics and economics | Impact on the partnership funnel and commercial capacity | Impact on the roadmap, reliability, and incident backlog |
| 15-16. Pipeline and rhythm | Return to contact for similar GTM roles | Return to contact for similar backend/platform roles |
Compact case: Business Development Manager B2B SaaS payments
| Stage | Artifact |
|---|---|
| Role | We need a BDM who opens partner channels for a B2B SaaS payments company and runs complex negotiations. |
| Screening | Check B2B SaaS, payment/fintech exposure, enterprise discovery, and motivation for long cycles. |
| Interview | Role-play scenario: the candidate explains a payment solution to a partner and handles a CFO objection. |
| Assessment | Criteria: discovery, commercial thinking, negotiations, follow-up reliability, and domain learnability. |
| Decision | An offer is possible if the mandatory criteria are confirmed by at least two signals and the hiring manager accepts the onboarding risks. |
Compact case: Backend Engineer
| Stage | Artifact |
|---|---|
| Role | We need an engineer who maintains a reliable backend and API and is responsible for keeping the system running in production. |
| Screening | Check the stack, production experience, incident analysis, and motivation for quality and support. |
| Interview | System design / work sample: design an API and discuss fault tolerance. |
| Assessment | Criteria: backend design, code quality, observability, ownership, and collaboration. |
| Decision | An offer is possible if a strong technical signal is confirmed, the role level is aligned, and the onboarding plan covers the domain context. |
