Career journal for
Solutions Engineers
SE work is the technical proof that closed the deal. The POC is gone by the next sales cycle and the demo is already deprecated by the next product release.
Bloomly is the career journal built for the moments the work actually happens, not the night before the review.
A captured day for a Solutions Engineer
- 01
9am: ran the technical demo for Stripe's CTO; cleared the throughput concern.
- 02
1pm: scoping a custom POC for a strategic-accounts target.
- 03
3pm: post-call debrief with Alex (AE); aligned on what to bring next.
- 04
5pm: shipped a product-feedback memo to PM on a recurring customer ask.
What a Solutions Engineer captures
- Deals where technical win was the decider
- Custom demos and POCs that landed
- Integrations shipped post-sale
- AE partnerships that scaled
- Technical-feedback loops to product
Supported 23 deals (19 closed-won, $4.8M ARR). 83% win rate on supported deals vs 67% team baseline. Built 4 POCs from scratch.
Promotion rubric, mapped to capture
- Deals supported and wonCaptured automatically through dated entries, auto-tagged against this dimension, and surfaced in your generated Performance Report and Period Recap.
- Technical-win momentsCaptured automatically through dated entries, auto-tagged against this dimension, and surfaced in your generated Performance Report and Period Recap.
- Customer integrationsCaptured automatically through dated entries, auto-tagged against this dimension, and surfaced in your generated Performance Report and Period Recap.
- AE partnershipCaptured automatically through dated entries, auto-tagged against this dimension, and surfaced in your generated Performance Report and Period Recap.
Related templates for Solutions Engineers
You don't write the solutions engineer review. Bloomly does.
Built the 5-day POC for Plaid. Proved out our latency at their scale (3.4M events/day, p99 under 80ms). Deal closed. Thirty seconds in the moment. The full review writes itself from a year of those.