Jobs · Analyst · Texas

Trade Support / Business Analyst - US Power Market

Talan · Houston, TX · 1 mo ago
On-siteAnalystFull-time
We need to output HTML fragment with sections for headings: About the role? Not present. Responsibilities, Qualifications, Benefits, Pay, Schedule? Pay is present: salary range. Schedule: location mentions hybrid schedule: at least 3 days onsite/week, first 1-3 months 5 days a week. That's schedule info. So we can include Schedule section. Benefits section present. Pay section present. Responsibilities present. Qualifications present. About the role maybe not needed; we could include a brief intro paragraph before sections? The instruction: Use

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. Thus we need sections: Responsibilities, Qualifications, Benefits, Pay, Schedule. Possibly also "About the role"? Not needed; we can include a short paragraph about the company? The posting includes description about Talan at top. That's substantive info about the company and role context. Could be placed as a

    before sections, not as a heading. That's allowed. We should not create a heading for it unless we have a section like "About the role". The instruction says we can use About the role as a heading example, but we should only include if posting has real specific content. The posting does have a paragraph about Talan and the role context. That could be considered "About the role". But it's more about the company. However we could still include an

    About the role

    with that paragraph. That seems okay. But we must ensure not to create filler. The paragraph is substantive. So we can include About the role. We must not include Visa Sponsorship? That's minor metadata; we could fold into a short

    maybe under About the role or separate? The instruction says fold minor metadata into a short

    or drop it. Visa sponsorship is specific info; maybe we should keep it as a short paragraph under About the role or separate? It's not a heading; we can include it as a

    after the About the role paragraph. We must remove EEO boilerplate line: "All your information will be kept confidential according to EEO guidelines." That's boilerplate; remove. We must remove duplicated lines: there is "Qualifications Qualifications". We'll keep only one. We need to preserve all substantive info: responsibilities list, qualifications list, benefits list, pay range, schedule details. Let's extract: About Talan: first paragraph: "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, we accelerate our clients' transformations through long-term partnerships, creating measurable and sustainable impact. Our 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 Americas, our 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." Then location and visa: "Location: Houston (Hybrid – at least 3 days onsite/week but for the first 1-3 months, will be asked to come in 5 days a week for on-boarding) Visa Sponsorship: We offer sponsorship under specific treaty-based U.S. work visas, including TN and E-2 (for eligible Canadian, Mexican, and French citizens). We do not support or transfer other visa types (e.g., H-1B)." Then description: "This is a business-facing role with strong Front Office and technology responsibilities. The successful candidate will bring deep practical knowledge of US/North American Power Markets and will work closely with traders, quants, developers, QA, and senior technical teams to support business processes, system functionality, trade lifecycle, and production operations. Strong subject matter expertise in US Power Markets is a critical requirement for this position. Candidates must understand how US power trading operates, including the underlying trading and operational processes, products, positions, pricing, PnL, settlements, and the interaction between Front Office users and ETRM/trading platforms." Then Responsibilities heading: "Key Responsibilities" then bullet list. Let's capture responsibilities bullet points: - Serve as a US Power Markets Subject Matter Expert (SME) for the Front Office and technology teams. - Work directly with traders and business stakeholders to understand US Power trading workflows, products, processes, and business requirements. - Analyze and document business processes across the trade lifecycle, from trade capture through position management, pricing, PnL, End-of-Day, and downstream processes. - Translate Front Office requirements into clear business requirements, functional specifications, user stories, and acceptance criteria. - Identify gaps between existing business processes and Orchestrade functionality and work with stakeholders to define appropriate solutions. - Support requirements gathering, process mapping, impact analysis, testing, and implementation activities. - Act as the primary business/functional interface between Power Trading, Operations, QA, Development, and Infrastructure teams. Qualifications: "Qualifications" repeated; we need list: - 5+ years of experience as a Business Analyst, Trade Support, Application Support, or Front Office Analyst within US/North America Power & Energy (PJM, ERCOT, MISO, CAISO, NYISO, ISO-NE, SPP) - Strong understanding of Power trading processes, trade lifecycle, positions, pricing, and PnL. - Strong SQL and Linux/Unix skills. - Experience with an ETRM platform such as Openlink Endur, Allegro, ION Aspect, TriplePoint, RightAngle or Proprietary Custom ETRM system. - Strong communication skills and ability to work directly with traders and technical teams. - Nice to Have: Orchestrade implementation or Go-Live experience We could separate Nice to Have as separate bullet maybe under Qualifications or Skills. But we can keep as bullet with note. Benefits: list: - Competitive salary between USD $120,000 - US$160,000 (but that's Pay) - 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 paid holidays + 5 sick days + 2 personal days per year - Company health, dental, and vision insurance plans + FSA - Voluntary STD and LTD - Commuter/transit benefits Pay: salary range. Schedule: hybrid schedule details. We need to avoid duplication: salary appears both in Benefits and Pay; we should only include Pay section for salary, and Benefits section for other benefits (excluding salary). So we will move salary to Pay section. Thus Benefits section will exclude salary line. Now construct HTML: We'll start with a

    for the company intro paragraph(s). Then maybe a

    for location and visa sponsorship (minor metadata). Then

    About the role

    with a paragraph summarizing role description (the paragraph after location). Or we could incorporate that into About the role. Let's structure:

    Talan is an international group ... (the long paragraph).

    Location: Houston (Hybrid – at least 3 days onsite/week but for the first 1-3 months, will be asked to come in 5 days a week for on-boarding). Visa Sponsorship: We offer sponsorship under specific treaty-based U.S. work visas, including TN and E-2 (for eligible Canadian, Mexican, and French citizens). We do not support or transfer other visa types (e.g., H-1B).

    About the role

    This is a business-facing role with strong Front Office and technology responsibilities. The successful candidate will bring deep practical knowledge of US/North American Power Markets and will work closely with traders, quants, developers, QA, and senior technical teams to support business processes, system functionality, trade lifecycle, and production operations. Strong subject matter expertise in US Power Markets is a critical requirement for this position. Candidates must understand how US power trading operates, including the underlying trading and operational processes, products, positions, pricing, PnL, settlements, and the interaction between Front Office users and ETRM/trading platforms.

    Responsibilities

    • Serve as a US Power Markets Subject Matter Expert (SME) for the Front Office and technology teams.
    • Work directly with traders and business stakeholders to understand US Power trading workflows, products, processes, and business requirements.
    • Analyze and document business processes across the trade lifecycle, from trade capture through position management, pricing, PnL, End-of-Day, and downstream processes.
    • Translate Front Office requirements into clear business requirements, functional specifications, user stories, and acceptance criteria.
    • Identify gaps between existing business processes and Orchestrade functionality and work with stakeholders to define appropriate solutions.
    • Support requirements gathering, process mapping, impact analysis, testing, and implementation activities.
    • Act as the primary business/functional interface between Power Trading, Operations, QA, Development, and Infrastructure teams.

    Qualifications

    • 5+ years of experience as a Business Analyst, Trade Support, Application Support, or Front Office Analyst within US/North America Power & Energy (PJM, ERCOT, MISO, CAISO, NYISO, ISO-NE, SPP)
    • Strong understanding of Power trading processes, trade lifecycle, positions, pricing, and PnL.
    • Strong SQL and Linux/Unix skills.
    • Experience with an ETRM platform such as Openlink Endur, Allegro, ION Aspect, TriplePoint, RightAngle or Proprietary Custom ETRM system.
    • Strong communication skills and ability to work directly with traders and technical teams.
    • Nice to Have: Orchestrade implementation or Go-Live experience

    Benefits

    • 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 paid holidays + 5 sick days + 2 personal days per year
    • Company health, dental, and vision insurance plans + FSA
    • Voluntary STD and LTD
    • Commuter/transit benefits

    Pay

    Competitive salary between USD $120,000 - US$160,000

    Schedule

    Hybrid – at least 3 days onsite/week; for the first 1-3 months, required to be onsite 5 days a week for on‑boarding.

    Check for any leftover boilerplate: removed EEO line.

Similar jobs

Power Markets Analyst

FactSetLakewood, CO· 1 wk ago
Marketing$65k–$80k/yrapply on factset.wd108.myworkdayjobs.com

Power Trading Analyst

Leeward Renewable EnergyDallas, TX· 4 mo ago
Financeapply on leewardenergy.wd1.myworkdayjobs.com