Sr Lead SW Support Engineer
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use - for any list of duties/requirements/benefits, and
for prose. 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. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences.
We need to parse the posting.
Key content:
- About Northern Trust (company description) – could be "About the role"? Actually "About Northern Trust" is company overview. Could be under "About the role"? The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content to those headings.
We have sections:
- Description - WHO WE ARE (company overview)
- WHY US (culture)
- Role (description of role)
- Principal Responsibilities (list)
- Skills / Experience (list)
- Salary Range (Pay)
- Benefits description (Benefits)
- Work Authorization (maybe part of Requirements)
- Working with Us (culture again)
- Reasonable Accommodation (maybe not needed)
We need to include only sections with real content.
We need to avoid duplication.
We need to produce HTML with
headings and appropriate content.
We need to include Pay section because salary range is given.
Benefits section: they describe comprehensive benefits package.
Schedule: Not mentioned explicitly; there is mention of 7x24 availability, on-call after hours, weekend support. That could be schedule info. The posting says: "7x24 availability in a Service Delivery/Production Delivery Client Centric environment". Also "Critical incident may require weekend and/or after hours support." and "Responsible to attend on-call, after office hours including weekend to support High and Critical production issues." So schedule info exists: 7x24 availability, on-call, weekend. So we can include a Schedule section.
We need to avoid filler like "commensurate with experience". Not present.
We need to remove boilerplate: cookie/navigation/legal/EEO etc. There's some about work authorization repeated; we can keep once.
We need to preserve all substantive info.
Let's extract substantive content:
Company overview (Northern Trust description):
- As a global leader in innovative wealth management, asset servicing, asset management and banking services, Northern Trust (Nasdaq: NTRS) is proud to guide the world’s most successful individuals, families, corporations and institutions.
- Since 1889, we have aligned our efforts with our three guiding Principles That Endure: Service, Expertise, and Integrity.
- Together, they reflect the three cornerstones of business conduct which we strive to instill in our employees, whom we call partners, and to provide to our clients and the communities we serve worldwide.
- With more than 135 years of financial experience and over 24,000 partners, we serve the world’s most sophisticated clients using leading technology and exceptional service.
- This is a Production Support role, and the candidate we hire must have prior /current SW Production Support experience.
- *****This is a highly visible role and will have CIO visibility and oversight.*******
- 7x24 availability in a Service Delivery/Production Delivery Client Centric environment
Then "Description - WHO WE ARE" repeats similar but slightly different numbers: 130 years, nearly 20,000 partners. We need to preserve all substantive info; we can combine but not duplicate. We'll include both? Might be duplicate but we can keep unique info: mention 130 years, nearly 20,000 partners, metamorphosis, Agile, cloud, analytics, microservices, Digital design systems.
WHY US: flexible and collaborative work culture, strong history of financial strength and stability, movement encouraged, senior leaders accessible, pride in strengthening communities, talented driven energetic people changing face, speed, influence, focus to positively change client experience, people are greatest wealth, desire to work in fast-paced Agile inclusive environment values teamwork, problem-solving, deadline management, communication, attention to detail, continuous improvement.
Role: This role will support our Wealth Management business, product, operations, partners and clients. As a support lead you will collaborate with Application Development teams to implement business solution through agile practice and manage production issues. The ideal candidates will possess excellent leadership and communication skills coupled with a solid understanding of modern cloud technologies preferably in the financial sector. Critical incident may require weekend and/or after hours support.
Principal Responsibilities: list bullet points.
Skills / Experience: list requirements.
Salary Range: $99,600 - 169,200 USD. Note: "Salary range is a good faith estimate of base pay."
Benefits: Northern Trust provides a comprehensive benefits package including retirement benefits (401k and pension), health and welfare benefits (medical, dental, vision, spending accounts and disability), paid time off, parental and caregiver leave, life & accident insurance, and other voluntary and well-being benefits. Northern Trust also provides a discretionary bonus program that may include an equity component.
Work Authorization: Applicants must be authorized to work in the U.S. without the need for employment-based visa sponsorship now or in the future. Northern Trust will not sponsor applicants for U.S. work visa status for this opportunity (no sponsorship is available for H-1B, L-1, TN, O-1, E-3, H-1B1, F-1, J-1, OPT, CPT or any other employment-based visa). This appears twice; we can keep once.
Working with Us: similar to WHY US but includes inclusive workplace, philanthropy, etc.
Reasonable Accommodation: statement about adjustments; we could include maybe under a generic section? Not in headings list; we could omit as not required.
We need to decide sections: About the role (maybe combine company overview and role description?), Responsibilities, Requirements (or Qualifications), Skills, Benefits, Pay, Schedule.
We have both Requirements and Skills; maybe combine as Requirements (including experience, authorization) and Skills (technical). But we can have both.
We need to avoid thin sections; prefer few substantive sections.
Potential sections:
- About the role (company overview + role description)
- Responsibilities (Principal Responsibilities)
- Requirements (Work authorization, experience years, etc.)
- Skills (technical skills list)
- Benefits
- Pay
- Schedule (7x24 availability, on-call, weekend)
We need to ensure we don't repeat info.
Let's extract each.
About the role: combine company overview and role description.
Company overview: we have two versions; we can merge key points: global leader in wealth management, asset servicing, asset management, banking; guiding principles Service, Expertise, Integrity; >135 years experience, over 24,000 partners; also mention 130 years, nearly 20,000 partners (maybe just keep higher numbers). Also mention metamorphosis, Agile, cloud, analytics, microservices, digital design systems.
Role description: support Wealth Management business, product, operations, partners and clients; as support lead collaborate with Application Development teams to implement business solution through agile practice and manage production issues; ideal candidates possess excellent leadership and communication skills plus solid understanding of modern cloud technologies preferably in financial sector; critical incident may require weekend/after hours support.
We'll produce a paragraph.
Responsibilities: list bullet points from Principal Responsibilities.
Let's extract bullet points:
- Lead production stability effort by preventing production issue and improve production stability.
- Familiar with ITIL Process and Project methodologies.
- Assist and drive Change /Incident/Problem Management process and Project releases
- Identify measures to improve applications stability and availability, sustain and improve cost efficiencies and productivity gains.
- Provide leadership and guidance to junior staff, fostering an environment that encourages employee participation, teamwork, and communication
- Consult with business unit partners to determine the most effective computer utilization to solve business problems or address business needs.
- Help direct systems projects, including project planning, management status reporting, systems specifications and implementation
- Help ensure compliance with all audit requirements including change control procedures and data security
- Manage and coordinate with onsite and offshore NT partners to Support applications and drive continuous improvement efforts.
- Coordinate with various teams, including offshore staff, and raise support ticket for all issues, analyze root cause and assist in efficient resolution of production issues.
- Responsible to attend on-call, after office hours including weekend to support High and Critical production issues.
We need to keep as - .
Requirements: include work authorization, experience years, maybe education? Not given. Also mention "Applicants must be authorized to work in the U.S. without the need for employment-based visa sponsorship now or in the future. Northern Trust will not sponsor applicants for U.S. work visa status for this opportunity (no sponsorship is available for H-1B, L-1, TN, O-1, E-3, H-1B1, F-1, J-1, OPT, CPT or any other employment-based visa)." Also mention "5-8 plus years of application development /Support experience using modern technical frameworks and architecture, including experience collaborating with external technology teams." Also "Must have prior work experience supporting business applications on Java and database technologies." Also "Good to have past experience under DevOpps or SRE role." Also "Understanding of the Secure Software Development Lifecycle (SSDLC) and/or other methodologies" Also "Experience working on projects in an Agile/XP environment." Also "Experience using at least some of the following technologies: Java, J2EE, Pivotal Cloud Foundry, AZure, Cloud Computing (IaaS, PaaS and SaaS), RESTful interfaces, GIT, Gradle, Maven, NPM, Spring (Spring Batch and Spring Boot), Bootstrap, CSS3, HTML4, React.js, Node.js/JavaScript, Oracle PL/SQL, Data Bricks, NEO4J,DOTNET" Also "Strong communication and interpersonal skills, along with a solid technical background are essential as is the ability to multitask in a fast paced environment. The ideal candidate can explain technical issues in layman’s terms and translate business needs to technology teams and back." Also "Strong leadership and team player to work as part of a global support team, cross training and supporting multiple critical client facing applications." Also "Experience working effectively with diverse groups around the world, including IT management, technology staff, business partners, consultants, vendors and clients"
We could split Requirements (authorization, years, experience) and Skills (technical list, soft skills). But we have both headings allowed.
Let's make:
- Requirements: work authorization, 5-8+ years experience, prior Java/database experience, Agile/XP, DevOps/SRE optional, SSDLC understanding, ability to multitask, leadership, communication, global teamwork.
- Skills: list of technologies (Java, J2EE, etc.) plus maybe soft skills? But we already have communication etc. Might duplicate. We'll keep skills as technical list.
Better: Requirements: authorization, years, core experience (Java/database, Agile, etc.). Skills: specific tech list.
Let's extract core experience: "5-8 plus years of application development /Support experience using
for prose. 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. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences. We need to parse the posting. Key content: - About Northern Trust (company description) – could be "About the role"? Actually "About Northern Trust" is company overview. Could be under "About the role"? The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content to those headings. We have sections: - Description - WHO WE ARE (company overview) - WHY US (culture) - Role (description of role) - Principal Responsibilities (list) - Skills / Experience (list) - Salary Range (Pay) - Benefits description (Benefits) - Work Authorization (maybe part of Requirements) - Working with Us (culture again) - Reasonable Accommodation (maybe not needed) We need to include only sections with real content. We need to avoid duplication. We need to produce HTML with