Salesforce development. There's a real learning curve, but Salesforce provides really good teaching academies and certification processes.
For an enterprise company, there is no data more important or highly valued than the CRM. Also at a mature company, sale motions are already dialed in, and comp plans typically only change 1-2 times a year (more than one change a year is bad for org morale). Large overhauls can be a pain, but they're extremely infrequent and ideally scheduled well in advance.
Once the system is operating and the daily, weekly, monthly, and quarterly cadence reports are dialed in, you just need to make sure the system continues to run, and deal with any special odd projects or reporting requirements from the sales execs you're working with.
Your sale exec partners have every incentive to get their processes right the first time, and rarely change them -- change disrupts any team (not just engineers), only with sales teams, that change results in tightly trackable lost revenue.
Its not "zero work", but it fits the "2 hours of active work, then chill" requirement. You'll have a busier end of quarter, but the first 2-3 weeks of the quarter will either be crickets or greenfield work.
Edit: this role can legitimately be fun too. You're at the nerve center for how the company actually makes money, and you get to have a cross sectional view of all other functions as a result. You'll see "how the sausage is made" but you only have to report on it and build the tracking systems -- you're not on the hook for performance or output. Also, sales people know when they have a good CRM process and are some of the most grateful folks in the world to those who help them. If you do a good job for your users, you'll be getting public shoutouts every day.
For an enterprise company, there is no data more important or highly valued than the CRM. Also at a mature company, sale motions are already dialed in, and comp plans typically only change 1-2 times a year (more than one change a year is bad for org morale). Large overhauls can be a pain, but they're extremely infrequent and ideally scheduled well in advance.
Once the system is operating and the daily, weekly, monthly, and quarterly cadence reports are dialed in, you just need to make sure the system continues to run, and deal with any special odd projects or reporting requirements from the sales execs you're working with.
Your sale exec partners have every incentive to get their processes right the first time, and rarely change them -- change disrupts any team (not just engineers), only with sales teams, that change results in tightly trackable lost revenue.
Its not "zero work", but it fits the "2 hours of active work, then chill" requirement. You'll have a busier end of quarter, but the first 2-3 weeks of the quarter will either be crickets or greenfield work.
Edit: this role can legitimately be fun too. You're at the nerve center for how the company actually makes money, and you get to have a cross sectional view of all other functions as a result. You'll see "how the sausage is made" but you only have to report on it and build the tracking systems -- you're not on the hook for performance or output. Also, sales people know when they have a good CRM process and are some of the most grateful folks in the world to those who help them. If you do a good job for your users, you'll be getting public shoutouts every day.