Jobs · Kansas

Infrastructure Engineering Manager

Jack Henry · Overland Park, KS · 1 mo ago
Hybrid$180k–$215k/yrFull-time
We need to output HTML fragment with sections: About the role? The posting includes intro about company, mission, etc. We need to decide sections: maybe "About the role" (intro), "Responsibilities", "Requirements", "Qualifications"? The posting includes "What you’ll be responsible for:" and "What you’ll need to have:" and "What would be nice for you to have:" plus benefits and pay and schedule. We need to include sections only when there is real specific content. So we can have: - About the role (intro paragraph) - Responsibilities (list) - Requirements (list of must-have) - Preferred Qualifications (list of nice-to-have) - Benefits (list from "Why Jack Henry?" maybe includes benefits description) - Pay (salary range) - Schedule? Not mentioned explicitly; remote position but no schedule details. So we should NOT create Schedule section. We must not repeat job title as heading. No Job ID. We must remove boilerplate: EEO, legal, etc. Also remove "If you got this far..." maybe keep? It's motivational but not boilerplate; could be part of About the role? Might keep as part of About the role but it's not essential. However we must preserve ALL substantive information; we can keep it as part of About the role. We must not include duplicated lines. We need to output only HTML fragment, no /. Use

for section headings. Use
  • for lists. Use

    for prose. Let's extract content. Intro: "At Jack Henry, we’re more than a technology company, we’re a force for good in financial services. We’re redefining how community banks and credit unions connect with the people they serve. Our mission is rooted in people inspired innovation, empowering financial institutions to deliver seamless, secure, and human centered experiences. We deliver cutting-edge solutions that are paving the way for the next generation of digital banking and payments, but our true impact begins with our associates. If you're ready to help transform an industry and grow with a company that values purpose, collaboration, and excellence then we’d love to meet you." Then description of Infrastructure Core Services teams: "Infrastructure Core Services teams focus on delivering compute, network, data, secrets management, and workload orchestration in the cloud. We partner with product engineering teams to build performant, scalable, and secure services that are responsible for transactions, payments, deposits, transfers, auth, and platform integrations. We partner with our infrastructure platform teams to deliver pipelines, identity, observability, tooling, and security within the platform. We want our organization to be one that supports, challenges, and motivates you to build strong, dynamic connections with your coworkers. We promote a hard working, highly communicative, flexible, and transparent culture. How well work integrates with your life is an important quality of a healthy individual and organization. In the world of remote work that is always on and always connected we pay attention to providing margin and space for the things you hold dear" Then location constraints: "This is a remote position and candidates must live within approximately a 70-mile radius of our office locations in: Lenexa, KS; Springfield, MO; or Monett, MO. This position is ineligible for immigration sponsorship and support. Please do not apply if at any time you will need immigration support now or in the future (i.e., H-1B, PERM)." Then salary: "The salary range for this position is $180,000- $215,000 and will be determined based on location and experience level." Then onsite interview note: "All positions, regardless of location, may require an onsite interview or in-person onboarding requirement to verify your identity." Then responsibilities list: bullet points after "What you’ll be responsible for:": - Reinforce the expected responsibilities of our teams so that we don’t get lost in the winds and rains of urgency or focus sacrificed to the loudest voice in a room. - Work with product engineering teams to develop alignment of priorities. Then proactively and openly communicate what will be impacted when priorities change. - Build relationships with technical leads and team leads to support delivery and team health. - Provide clarity to those around you to know who we are and who we are not to give space for teams to focus and deliver. - Enable staff to engage and take ownership of problems both large and small and in all instances advocating decision-making by engineers. - Have difficult, but candid conversations that enable teams to calibrate their approach to work. - May perform other job duties as assigned. Then requirements list after "What you’ll need to have:": - A minimum of 5 years in development or infrastructure as an individual contributor and advanced to a high functioning Sr or Staff engineer. - At least 4 years managing a team or multiple teams in a fast paced, rapidly evolving environment. - 4 years leveraging a framework that fits within the broader agile umbrella. e.g. scrum, kanban, Lean. - Experience within a cloud infrastructure environment. Then "What would be nice for you to have:" list (preferred qualifications): - Relaxed in how you work through interruptions and yet steadfast at guarding your focus time. - Committed to developing your craft/craeft; ie. a deep understanding of the technical and socio-technical systems, skills and techniques important to the masterful execution of your work. - A rebel in all the best ways; you challenge prevailing thought or assumptions when warranted and suggest better alternatives. - Able to identify, develop, and support the formative practices and rhythms that make for effective engineers and leaders. - Skilled at listening well to those you work with to understand their views, in order to equip and challenge team members to take on progressively more difficult situations. - Quick to get up to speed on situational context. Open to discussing the merits of a solution amongst your co-workers by inviting others to the conversation yet holding steadfast to the vision and values of the organization. - Effective at facilitating opportunities for engineers with opposing thoughts to listen to one another and help them develop the ability to see problems from multiple viewpoints. - Capable of serving in the background and able to recognize when to step in front of a problem to take it on directly. - An effective and candid communicator. Deliberate to openly communicate in large/public channels. - Able to hire and fire; hiring is fun and firing is not, but experience doing both is critical. Then "Why Jack Henry?" section: includes benefits description and culture. We need to extract benefits: "We’re also leading the way in technology modernization, helping financial institutions evolve with speed, security, and flexibility. Our strategy focuses on delivering secure data access, mitigating fraud, and enabling seamless integration. Empowering our teams to build innovative solutions that meet the evolving needs of accountholders." But that's more about company mission. Benefits: "We recognize that our associates are the key to our success, and we’re deeply committed to their wellbeing. That’s why we offer comprehensive benefits designed to support your physical, mental, and financial health so you can thrive both personally and professionally." Also "Culture of Commitment" etc. Might be considered benefits? It's more culture. We could include a Benefits section with the comprehensive benefits statement. Also maybe include "Culture of Commitment" as part of About the role? But we need to avoid thin sections. Could combine culture into About the role. We need to preserve all substantive information; we can include a Benefits section with the statement about comprehensive benefits. Also maybe include the culture statements as part of About the role. We must not create Pay/Schedule/Benefits sections unless posting actually states them. Benefits is stated: "We offer comprehensive benefits designed to support your physical, mental, and financial health". So we can include Benefits section. Pay: salary range given, so include Pay section. Schedule: not given, so omit. Now we need to decide headings: About the role (intro + team description + location/immigration/onsite note?), Responsibilities, Requirements, Preferred Qualifications, Benefits, Pay. We could also include a short paragraph for location/immigration/onsite note under About the role or maybe as a separate "Details" but we don't have a heading for that; we could incorporate into About the role as prose. Let's craft:

    About the role

    At Jack Henry, we’re more than a technology company, we’re a force for good in financial services. We’re redefining how community banks and credit unions connect with the people they serve. Our mission is rooted in people inspired innovation, empowering financial institutions to deliver seamless, secure, and human centered experiences. We deliver cutting-edge solutions that are paving the way for the next generation of digital banking and payments, but our true impact begins with our associates. If you're ready to help transform an industry and grow with a company that values purpose, collaboration, and excellence then we’d love to meet you.Infrastructure Core Services teams focus on delivering compute, network, data, secrets management, and workload orchestration in the cloud. We partner with product engineering teams to build performant, scalable, and secure services that are responsible for transactions, payments, deposits, transfers, auth, and platform integrations. We partner with our infrastructure platform teams to deliver pipelines, identity, observability, tooling, and security within the platform. We want our organization to be one that supports, challenges, and motivates you to build strong, dynamic connections with your coworkers. We promote a hard working, highly communicative, flexible, and transparent culture. How well work integrates with your life is an important quality of a healthy individual and organization. In the world of remote work that is always on and always connected we pay attention to providing margin and space for the things you hold dear.This is a remote position and candidates must live within approximately a 70-mile radius of our office locations in: Lenexa, KS; Springfield, MO; or Monett, MO. This position is ineligible for immigration sponsorship and support. Please do not apply if at any time you will need immigration support now or in the future (i.e., H-1B, PERM).All positions, regardless of location, may require an onsite interview or in-person onboarding requirement to verify your identity.

    Then responsibilities:

    Responsibilities

    • Reinforce the expected responsibilities of our teams so that we don’t get lost in the winds and rains of urgency or focus sacrificed to the loudest voice in a room.
    • Work with product engineering teams to develop alignment of priorities. Then proactively and openly communicate what will be impacted when priorities change.
    • Build relationships with technical leads and team leads to support delivery and team health.
    • Provide clarity to those around you to know who we are and who we are not to give space for teams to focus and deliver.
    • Enable staff to engage and take ownership of problems both large and small and in all instances advocating decision-making by engineers.
    • Have difficult, but candid conversations that enable teams to calibrate their approach to work.
    • May perform other job duties as assigned.
    Then Requirements:

    Requirements

    • A minimum of 5 years in development or infrastructure as an individual contributor and advanced to a high functioning Sr or Staff engineer.
    • At least 4 years managing a team or multiple teams in a fast paced, rapidly evolving environment.
    • 4 years leveraging a framework that fits within the broader agile umbrella. e.g. scrum, kanban, Lean.
    • Experience within a cloud infrastructure environment.
    Then Preferred Qualifications (maybe heading "Preferred Qualifications" or "Nice-to-have". The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can use "Qualifications" for nice-to-have? But we already have Requirements. Could use "Qualifications" for nice-to-have. Or "Skills". The instruction: use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have both Requirements and Qualifications sections

Similar jobs