[marcus0x62]

Being an SE is the definition of an always-on job. The stress is (or, can be,) different than what an account manager faces, but the same underlying dynamic is the same: you're only ever as good as your last quarter and you can never achieve "enough".

Beyond the mental aspects, SEs are frequently inserted, either officially or unofficially, in all manner of customer support processes like case escalation, managing beta software builds, arbitrating between the customer and professional services engineers, etc.

[nunez]

This is true (from what I've observed; you've been in the game longer than me!), but AEs are literally responsible for bringing in the business [0], whereas SEs are chiefly responsible for the technical win. I think the latter is way easier from how I've seen AEs operate.

You're also right in that we get inserted into these wedge functions, but I haven't seen any of that bleed into my personal life like deals tend to do to AEs.

[0] BDRs are LITERALLY responsible for pipe, so this isn't entirely true. However, many AEs are hired for their Rolodex, so to speak, and when they miss their forecasts, blaming BDR doesn't go very far.

[pmarreck]

> frequently inserted, either officially or unofficially, in all manner of customer support processes like case escalation, managing beta software builds, arbitrating between the customer and professional services engineers, etc.

other than managing beta software builds, a lot of this stuff seems to be less impactful to the bottom line (of the business, and thus potentially to your salary) than just supporting the sales cycle from the technical side would be. I could see that happening though if there simply wasn't a constant stream of SE work to do. But I can't imagine that an hour burned on customer support, instead of an hour spent writing up how well the technical fit is to a particular customer in a big sales proposal, is making that company more money off you (and again, thus potentially impacting your salary ceiling).

[marcus0x62]

Managing beta builds is the least revenue impacting thing from that list.

These tasks impact the company bottom line (and an SEs compensation) in that unhappy customers don't buy product. Leaving your customers to fend for themselves when they ask for help - and they will ask for help - will quickly lead to an SE getting replaced, either due to their company getting kicked out of an account and replaced with a competitor, or the SE kicked out of their company and replaced with a competitor.

The general consensus is that SEs spend, on average, about 20% of their working time on "post-sales" tasks. I'm not aware of any published data in this area, but it tracks with my experience, both as an individual SE and an SE manager for 15 years.

[pmarreck]

That seems fair. Had no idea.