arXivDaily arXiv每日学术速递 周一至周五更新
arXiv 2602.19353cs.SE
收藏

设计并实现一个全面的研究软件工程师职业阶梯:来自普林斯顿大学的案例研究

Designing and Implementing a Comprehensive Research Software Engineer Career Ladder: A Case Study from Princeton University

Princeton University(普林斯顿大学)

Ian A. Cosden, Elizabeth Holtz, Joel U. Bretheim

AI总结:

本研究针对普林斯顿大学RSEs需求激增的问题,设计并实施了涵盖助理至主任级别的全面职业阶梯,通过明确的指导原则和能力框架提升招聘效率与晋升路径清晰度。

摘要:

研究软件工程师(RSEs)已成为计算研究和学术领域不可或缺的角色。在高等教育中RSEs的快速崛起以及大学在新技术角色创建和采纳方面的缓慢趋势,意味着缺乏能够认可技术精通、学术影响和领导力成长的结构化职业路径。针对普林斯顿大学对RSEs的巨大需求以及致力于将RSE团队至少扩大一倍的资金支持,普林斯顿被迫制定如何协调定义职位描述的策略,以匹配快速招聘的RSE职位,同时保持足够的灵活性以认可每个职位的独特性质。本案例研究描述了我们设计和实现的一个涵盖助理至主任级别的全面RSE职业阶梯,包括并行的团队领导和管理轨道。我们概述了指导原则、能力框架、人力资源(HR)协调以及实施过程,包括与外部顾问的合作以及利用市场基准映射到标准职位分级框架。我们分享了早期的经验教训和成果,包括提高了招聘效率、更清晰的晋升路径以及员工的积极反响。

英文摘要:

Research Software Engineers (RSEs) have become indispensable to computational research and scholarship. The fast rise of RSEs in higher education and the trend of universities to be slow creating or adopting models for new technology roles means a lack of structured career pathways that recognize technical mastery, scholarly impact, and leadership growth. In response to an immense demand for RSEs at Princeton University, and dedicated funding to grow the RSE group at least two-fold, Princeton was forced to strategize how to cohesively define job descriptions to match the rapid hiring of RSE positions but with enough flexibility to recognize the unique nature of each individual position. This case study describes our design and implementation of a comprehensive RSE career ladder spanning Associate through Principal levels, with parallel team-lead and managerial tracks. We outline the guiding principles, competency framework, Human Resources (HR) alignment, and implementation process, including engagement with external consultants and mapping to a standard job leveling framework utilizing market benchmarks. We share early lessons learned and outcomes including improved hiring efficiency, clearer promotion pathways, and positive reception among staff.

机构、总结、中文摘要均由AI分析而来,可能存在错误,请以论文正文为准。

↑