Deployment Strategy Lead (People Manager)
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have Benefits and Pay separate. Benefits could include equity, 401k, etc. Pay could be salary range. We need to preserve all substantive info. So we need to extract details: About the role: Could be summary from "What This Role Is" and maybe "About The Company"? But "About the role" heading should contain description of the role, not company. The posting has "What This Role Is" describing Deployment Strategy Leads. So we can put that under About the role. Responsibilities: "What You Will Do" plus maybe "How We Work" and "What Success Looks Like"? Those are more about expectations and success. Could treat as Responsibilities. Requirements/Qualifications/Skills: "What We Look For" plus maybe "Who Thrives Here", "You May Be a Fit If", "Who May Struggle Here". Those are more about fit. Could split: Requirements (hard requirements), Qualifications (preferred), Skills (maybe technical). But we need to avoid filler. We'll try to map. We need to preserve all substantive info, not invent. So we need to include all points from those sections. Let's extract bullet points. From "What This Role Is": Deployment Strategy Leads own the people and the quality bar behind ValonOS deployments. You are a specialist in a deployment domain, and you build, coach, and hold accountable a team of 3-10 people. Deployment Strategists across the entire customer journey — from contract signature through go-live through adoption. You are part manager, part deployment operator, part quality control. The team's outcomes are your outcomes. The job is not to manage from a dashboard. You stay close enough to the work to catch problems before they become client-facing, and close enough to your people to know when they need a stretch, a course correction, or to be unblocked. From "Why Valon": description of company, but maybe not needed for role. Could be omitted as not role-specific? Might be considered company info, but we might keep under About the role? The instruction: About the role section likely includes role description; company info maybe not needed. But we must preserve ALL substantive information; do not invent or summarize away detail. However we can omit boilerplate like navigation, legal, EEO. Company description is substantive but not role-specific; still part of posting. Should we include? The instruction says preserve ALL substantive information; but we are to output only HTML fragment with sections. We could include a section "About the Company" but not in allowed headings list. The allowed headings are limited to those listed. We cannot add other headings. So we must fit company info into existing sections, maybe under About the role? But that might be stretching. However we could include a brief paragraph under About the role that includes company context as it's relevant to role. The instruction: "Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." It doesn't forbid including company info in About the role. So we can include company description there. Thus About the role will contain both company description and role description. Responsibilities: "What You Will Do" plus maybe "How We Work" and "What Success Looks Like". Let's extract. What You Will Do: - A client recently described what we do as “open-heart surgery while the patient is still walking around running their business.” That is accurate. Your team is handed multi-decade-old operations processing hundreds of thousands of loans, with a reputation, a regulator, and a P&L on the line — and you have to make sure every deployment lands without anything breaking. - A Deployment Strategy Lead: - Owns a deployment domain end-to-end: builds specialist depth in a particular product surface, client function, or operational workflow, and is the standard-bearer for quality in that domain across every deployment it touches. - Manages and coaches 5-10 Deployment Strategists: runs the learning loop, sharpens their judgment on ambiguous problems, and knows when to let someone run and when to step in. - Stays accountable for the full customer journey, not just launch day: contract to go-live to adoption. A deployment that goes live but doesn't stick is not a win. - Stays close enough to the work to catch quality problems early — reviewing configurations, sitting in on client conversations, reading the data, not just the status updates. - Raises the bar on the team's craft: better decisions, faster learning loops, stronger client trust, sharper ICs. - Translates upward and outward: to senior client leaders who have been doing this for 25 years, to Valon's product and engineering teams, and to your own reports who need clarity, not just direction. - Builds and extends DeploymentOS, our internal knowledge layer, so the next Deployment Strategist to hit a given problem doesn't have to solve it from scratch. How We Work: - You own the outcome, not the org chart. This is the anti-consulting, anti-middle-management role. Your team's deployments working is what you're measured on, not headcount or process. - Our contracts are performance-based, so when your team's deployments work, Valon wins. - You figure it out. There will be incomplete data, undocumented legacy behavior, tense client tradeoffs, and unclear ownership — both in the deployments and in the team problems. The job is to create clarity anyway. - You build alignment, but you do not hide behind consensus. You synthesize, recommend, commit, and defend the decision with evidence, and you coach your team to do the same. - Code and data beat decks. A working query, a real workflow, a shipped change, or a clear operating decision wins over prettier slides — for you and for the people you manage. - AI fluency is how the work gets done, not a nice-to-have. Your team uses coding agents, builds custom skills, and develops DeploymentOS. Part of your job is making sure that fluency keeps compounding across your pod. - You are writing the playbook, not executing one. Every framework we use was built by someone figuring it out for the first time. You are responsible for the next versions, and for making sure your team's hard-won lessons don't die with the individual deployment. What Success Looks Like: - You are succeeding here if senior leaders trust your domain and your team with ambiguous, high-stakes problems and feel the work is in safe hands. - Means: - Your deployments consistently land on time, on quality, and stick past go-live into real adoption. - Your Deployment Strategists get sharper because of you — clearer decisions, faster learning loops, better client trust, stronger individual judgment. - You can walk into a domain problem you don't fully understand, build a working model quickly, and know which of your reports to point at it and how to support them. - You move fast without becoming sloppy, and you keep your team moving fast without letting quality slip. - You can hold a room of senior client leaders and still go low-level enough to debug a workflow, query, data pipeline, or operating edge case yourself when it matters. - You know the difference between coaching someone through ambiguity and rescuing them from it, and you choose deliberately. We can combine these as responsibilities. Requirements/Qualifications/Skills: From "What We Look For", "Who Thrives Here", "You May Be a Fit If", "Who May Struggle Here", plus maybe "Location and travel" (though that's more schedule). Let's extract. What We Look For: - A track record of managing teams (3+ direct reports) inside operating roles, strategy consulting, banking, investing, or other high-stakes, ambiguous environments. - Deep comfort owning a specific domain — a product surface, client function, or workflow — and building real expertise there. - Strong analytical and quantitative horsepower, with the ability to decompose ambiguous problems yourself and coach others to do the same. - Practical comfort with technical tools. You don't need to be a professional engineer, but you should be able to use SQL, Python, or AI tools to check your team's work and answer questions yourself when needed. - Demonstrated AI fluency — evidence you've taught yourself to work with coding agents, build small tools, or restructure workflows around AI, and that you can pass that fluency on. - Clear, calibrated communication with technical and non-technical stakeholders, including senior client leaders. - Ownership maturity for both outcomes and people: you can move quickly, make decisions with incomplete information, coach through mistakes, and stay accountable when the answer changes. - Nice to have: prior experience as a Deployment Strategist or in a similar end-to-end deployment/implementation ownership role; background in financial services, healthcare, government, infrastructure, or another regulated, operationally intense industry. Who Thrives Here: - This role is for people who have built or scaled a team inside a high-stakes, ambiguous environment — not just managed one that was already running smoothly. - We are especially excited by people with experience managing 3+ direct reports who also want to stay close to the actual work: former Deployment Strategists ready to lead, consultants or bankers who've managed teams and want to own outcomes instead of recommendations, and operators from other intense environments who know how to build a team's judgment, not just its headcount. You May Be a Fit If: - You are restless around ambiguity, in the work and in managing people through it. - You have taught yourself new tools because the work demanded it, and you expect the same of your team. - You are comfortable being both a manager and extremely low-level in the same day. - You can communicate clearly with executives, operators, engineers, clients, and your own reports without changing the substance of your thinking. - You care about building a durable team and body of work, not just being near an interesting problem. Who May Struggle Here: - Probably not the right role if: - You are looking for a management lane focused on process and reporting rather than deployment outcomes and client adoption. - You prefer overseeing from a distance over staying close enough to the work to catch quality problems yourself. - You are uncomfortable with technical ambiguity, data messiness, or the tools (SQL, Python, AI agents