Senior Technical Program Manager
1999年成立,WordWinner 在世界赢家消费品牌下开发和运营具有竞争力的技能游戏,以现金奖励的实体品牌并与领先的 Sports Gaming Entertainment 公司 FanDuel 合作.WorldWinner 是最知名且值得信赖的技巧游戏技术平台和品牌,为想要玩到胜利的玩家提供了游戏。我们将激发人们更多的游戏带来世界。拥有超过20个挑战性的游戏,结果取决于玩家的技能而不是机会,跨越经典卡片游戏至随机喜欢的内容库,WorldWinner 有适合每个玩家的东西。支持 Platinum Equity 和战略投资者,我们正在在移动及其他领域构建我们的平台的下一个阶段。通过支持工程 SVP,你将拥有如何进入 WorldWinner 中心服务,DevOps 和数据团队的工作流程。在金融技术级,真钱游戏环境中。你将运行接入和分类,保持飞行中的所有内容的视图,清楚报告出货以及为什么,并自动化该过程的状态追踪。你还将领导一小组合同工程师涵盖中央服务和数据。这对一个工程师来说是理想的,他宁愿让整个系统运行得更好而不是再建立一个功能。这是你做出的合同角色。· 运行中心服务,DevOps 和数据的接入和分类。决定每个请求是什么,它到谁去了,何时回来。· 保持在飞行的团队之间的一种视图,以免平行工作碰撞或破坏别人的结果。· 报告出货的内容,正在推出的内容和被卡住的内容,并写说明我们为什么选择了我们的信息。· 注意当工作停止移动时,并采取行动。• 领导一个小组合同工程师在中央服务和数据中。设定优先事项,运行 1:1s 并给我们直接阅读他们如何做的事情。· 自动化连接组织。我们一些系统已经谈话彼此,我们想要更多的东西。脚本与他们的 API,所以状态自动移动而不是被追赶 · 构建我们没有的仪表板。一个地方显示了整个景观的健康和状况:应用程序,基础设施,数据以及运输内容。从实际上居住的地方收集起来。这是一个野心,而不是规范 · 使用 AI 适当。我们在工程领域广泛使用它,并希望你也可以 · 运行交付基本知识:计划,承诺,回顾
查看英文原文
Founded in 1999, WorldWinner develops and operates competitive games of skill with real cash prizes under the WorldWinner consumer brand and in partnership with leading Sports Gaming Entertainment company FanDuel under the FanDuel Faceoff name.
WorldWinner is the most recognized and trusted skill games technology platform and brand for players who want to Play to Win. We bring games to the world that inspire people to play for more. With over 20 challenging games where the outcome is dependent on player skills versus chance across a content library spanning classic card games to casual favorites to retro arcade games, WorldWinner has something for every gamer. Backed by Platinum Equity and strategic investors, we are building the next phase of our platform on mobile and beyond.
Supporting the SVP of Engineering, you’ll own how work flows into WorldWinner’s central services, DevOps and data teams in a fintech-grade, real-money gaming environment. You’ll run intake and triage, keep one view of everything in flight, report clearly on what shipped and why, and automate the status-chasing out of the process. You'll also lead a small team of contract engineers covering central services and data. It’s ideal for an engineer who’d rather make the whole system run well than build one more feature. This is a contract role.
What You'll Do
- Run intake and triage for central services, DevOps and data. Decide what each request is, who it goes to, and when it’s back
- Keep one view of what's in flight across teams, so parallel work doesn't collide or spoil someone else's results
- Report what shipped, what's rolling out and what's stuck, and write the summary that explains why we chose what we chose
- Notice when work stops moving, and do something about it
- Lead a small team of contract engineers in central services and data. Set priorities, run 1:1s and give us a straight read on how they're doing
- Automate the connective tissue. Some of our systems already talk to each other and we want a lot more of it. Script against their APIs so status moves on its own instead of being chased
- Build the dashboards we don't have. One place showing the health and status of our whole landscape: the apps, the infrastructure, the data, and what's shipping. Pulled together from wherever it actually lives. That's an ambition, not a spec
- Use AI properly. We use it heavily across engineering, and expect you to as well
- Run the delivery basics: planning, commitments, retrospectives, and a clear picture of who owns what in a release
What You'll Need
- You've written and shipped software professionally, then moved toward programs and delivery. We care that you can read code, write scripts and talk to engineers as a peer - not which languages you used
- You automate your own work - calling APIs, wiring tools together, building the report rather than asking for it
- You use AI tools seriously, and have a view on where they help and where they don't
- You've owned delivery or release reporting for a team that ships regularly
- You've led engineers before, even a small group. We're not asking for a career manager, we're asking for someone people will follow
- Good judgment about what's urgent and what's only loud
- Clear writing. Most of this job happens in writing
- Calm under pressure, and the kind of presence that makes people bring you problems early
Nice to Have But Not Necessary
- Live-service, real-money or regulated-product experience
- Mobile release management - Apple App Store, Google Play
- Administering Jira or Confluence
- Incident response and on-call practice
- AWS or another cloud provider
A Note on Applying
If you can do most of this, we'd like to hear from you. We'd rather talk to someone strong in four of these areas than someone who ticks every box.
Originally posted on Himalayas