Aligne/ETRM Platform Support Engineer
for section headings (e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Preserve all substantive info. Remove boilerplate (cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions). Include a section ONLY when posting has real, specific content for it — never emit heading followed by filler/placeholder text. Prefer few substantive sections over many thin ones. We need to decide which sections to include. The posting includes: location, visa sponsorship, job description, responsibilities (list), qualifications (required skills, preferred), benefits (salary range, 401k, vacation, holidays, sick days, personal days, health insurance, etc.). Also maybe "About the role" could be the introductory paragraph describing role. Could combine location and visa sponsorship into a short
maybe under "About the role". But we must not create sections with filler. We need sections: maybe "About the role", "Responsibilities", "Qualifications", "Benefits". Pay is part of benefits (salary range). Schedule: location mentions hybrid – at least 3 days onsite/week, first 3 months 5 days a week. That's schedule info. Could include a "Schedule" section. But we need to avoid filler. The posting does give schedule specifics, so we can include Schedule section. We must not create Pay section separately if we include salary in Benefits. But we could still have Pay section if we want, but they said prefer few substantive sections. So we can include salary within Benefits. Thus sections: About the role (intro paragraph summarizing role and location/visa), Responsibilities (list), Qualifications (list of required skills and preferred), Benefits (salary, 401k, vacation, holidays, sick/personal days, health insurance, voluntary STD/LTD, commuter benefits). Possibly also "Schedule" separate? But schedule info is location/hybrid. Could be part of About the role. But they said use headings for Schedule if we have content. We have content: hybrid – at least 3 days onsite/week, first 3 months 5 days a week. That's specific. So we could make a Schedule section. But we need to avoid too many thin sections. However schedule is substantive. Could combine with About the role? Might be okay to have About the role include location and schedule. But they gave examples of headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. They didn't forbid combining. But they said prefer a few substantive sections over many thin ones. So maybe we can have About the role (including location, schedule, visa sponsorship), Responsibilities, Qualifications, Benefits. That's four sections. We must not include "Requirements" separate if we have Qualifications covering required skills. Could also have Skills but we can incorporate into Qualifications. Thus output:
About the role
... paragraph containing location, visa sponsorship, role description.
Responsibilities
- ... each responsibility.
Qualifications
- ... required skills
- ... preferred experience Benefits
- ... benefits
- . Qualifications: Required Skills list as bullet points. List: - FIS Aligne / ETRM - Commodity/Energy Trading & Trade Lifecycle - Production/Application Support – L2/L3 - SQL, Oracle, Unix/Linux, Shell Scripting - Batch Processing / Control-M / Autosys - REST/SOAP APIs, XML/JSON, SFTP - Market Data, Risk, P&L, Valuation, Settlements - ServiceNow / ITIL - Incident, Problem, Change & Release Management - Root Cause Analysis and troubleshooting - Strong communication and stakeholder-management skill Preferred: Experience supporting energy/commodity trading environments, physical and financial commodities, EOD/EOM processing, application upgrades, automation using Python/Shell, and vendor management. We could combine required and preferred in same list with a note, or separate subheadings? But we only have Qualifications section; we can include both required and preferred as bullet points, maybe mark preferred with "(Preferred)". Simpler: list required bullets, then a separate bullet for preferred. Benefits: list: - Competitive salary between USD $110,000 - US$140,000 - 401(k) retirement plan with company matching - 15 days of paid vacation per year at hire and up to 27 according to seniority (annual untaken vacation days are cashed out) - 8
Talan is an international group that supports its clients in their end-to-end Data & AI transformation by combining management consulting with technological expertise. With over 6,000 employees across five continents, Talan accelerates clients' transformations through long-term partnerships, creating measurable and sustainable impact. The company’s value proposition is built on a structured innovation ecosystem: 2,500 Data & AI experts, proprietary solutions built on advanced models, and an applied research, experimental development, and innovation laboratory. In the Americas, multidisciplinary teams bring over 30 years of experience helping business leaders across key industries achieve measurable performance and strong ROI, designing, building, and scaling solutions that enable companies to grow more efficiently.
Location: Houston, Texas (Hybrid – at least 3 days onsite/week; for the first 3 months of onboarding, the client may require 5 days onsite/week). Visa sponsorship is offered under specific treaty‑based U.S. work visas (TN and E‑2 for eligible Canadian, Mexican, and French citizens); other visa types (e.g., H‑1B) are not supported.
The role is for a US Energy – Aligne/ETRM Specialist consultant supporting a client in the power and energy industry. The consultant will play a key role in supporting the transition from Aligne to Orchestrade, providing day‑to‑day production and operational support throughout the implementation. As a functional and technical subject‑matter expert for the FIS Aligne Energy Trading and Risk Management (ETRM) platform, the consultant will act as the primary liaison between frontend commercial trading desks, middle‑office risk management, backend financial accounting, and internal IT delivery teams. Responsibilities include day‑to‑day production support, system configuration, functional specifications mapping, and driving critical platform transformations or version upgrades.
That may be too much but okay. Now Responsibilities: list each bullet from "Key Responsibilities". Need to preserve all. Let's extract them: - Provide 24×7 production support, incident triage, troubleshooting, escalation, and resolution in accordance with SLAs. - Support the complete commodity trade lifecycle, including trade capture, amendments, positions, scheduling, nominations, confirmations, settlements, invoicing, risk, valuation, and P&L. - Troubleshoot FIS Aligne application issues, configuration problems, data discrepancies, workflow errors, batch failures, and application performance issues. - Use SQL/Oracle to investigate trades, positions, transactions, reference data, settlements, and production data issues. - Perform Unix/Linux troubleshooting, log analysis, process monitoring, shell scripting, and file-system investigation. - Monitor and troubleshoot EOD/EOM batch jobs, Control-M/Autosys processes, scheduled tasks, and dependent workflows. - Support integrations using REST/SOAP APIs, XML/JSON, SFTP, messaging, and file-based interfaces between ETRM and downstream/upstream systems. - Investigate market-data, pricing, curve, position, valuation, MTM, and P&L discrepancies. - Perform root-cause analysis (RCA), problem management, incident reviews, and implement permanent corrective actions. - Coordinate with traders, risk, scheduling, settlements, accounting, developers, DBAs, infrastructure teams, and FIS/vendor support. - Manage ServiceNow incidents, problems, changes, releases, and production deployments following ITIL/change-management processes. - Support application upgrades, patches, releases, testing, and production validation. - Create technical documentation, knowledge articles, support procedures, and provide user/vendor communication. We'll put each as