Use an existing open support req for an Arabic-speaking Middle East support hire - a new role, not a like-for-like backfill
Situation
On 10/23 in #human-resources Greg questioned a support hire. Peter approved it (good because Bjorn is good), told HR it is fine to use the existing open req, and told Greg the hire will not do the previous holder job: he will support the Middle East deployments first and foremost, as Arabic-speaking support.
Reasoning
Core42 and the Grenoble pursuit made the Middle East the heaviest support load, with the team on 5am calls daily; a local Arabic-speaking hire makes those motions repeatable at lower cost. Reusing an existing req avoids a new headcount debate; naming the role prevents it being treated as a backfill. Peter deferred to Bjorn on the go-to-market need and owned the role definition.
Additional Context
Confirmed by Peter. Posted 10/23 just before the prior reflection and not logged then.
Observed Evidence
No Greg. This is to support Middle East deployments. / Arabic speaking support. / It is fine to use the existing req.
Confidence Breakdown
Reasoning Depth Analysis
Related Context
slack
he will not be doing the previous holder job. He will be supporting the middle east first and foremost.
Outcome
No outcome recorded yet.
Decision ID: 952313bd-212b-40ab-a1ac-6c4a8614a402