Power Markets Analyst
Job description
About the role
This role guides commercial decision support for renewable energy infrastructure through advanced market analytics. The position sits within Commercial Operations and connects market expertise with engineering to improve storage optimization platforms.
Software engineers turn product ideas into working code. Engineers work in small teams, review each other's work, and ship in small batches. Most teams follow agile practices such as sprints and daily standups. Engineers also write tests, fix bugs, and improve performance. The field values clear communication as much as technical skill. Engineers spend part of every week on planning, code review, and debugging, not just writing new code. The ability to explain a technical decision in plain words separates strong engineers from the rest.
Key facts
What you'll do
This informs internal stakeholders and external customers with data-driven market insights.
Partnership with engineering identifies and prioritizes performance improvements on a per-ISO basis. Market insights are translated into actionable product and model guidance that shapes optimization efforts.
Reports include performance recaps, market condition analysis, and strategic commentary for decision use.
These tools enable faster, more reliable assessments of market and congestion conditions.
Collaboration with the policy team navigates regulatory and market design changes within target ISO markets. This keeps analytics aligned with evolving rules and participation requirements.
Requirements
Five or more years of experience in wholesale power markets is mandatory, with hands-on exposure to market operations, energy trading, storage dispatch, or market analytics. This background must come from an IPP, utility, trading firm, ISO/RTO, or energy software company.
Deep knowledge of at least one organized electricity market is required, covering MISO, SPP, CAISO, NYISO, or PJM. Understanding of market structure, bidding rules, settlement mechanics, and storage-specific participation requirements must be current.
Comfort with large time series datasets and settlement data is necessary for effective analysis. Proficiency in Python, SQL, or equivalent analytical tooling is strongly preferred, and building analytics tools from scratch is an advantage.
Complex market dynamics must be translated into clear, data-backed narratives for both technical and non-technical audiences. This role is customer-facing, though it does not own direct customer relationships.
Self-direction and analytical rigor define the work style, as the role sets its own research agenda. Finding signals in noisy data and communicating what matters is essential.
Practical notes
The role may require travel within the listed locations.
Typical interview steps
Hiring for engineering roles usually starts with a recruiter screen, followed by one or two technical rounds. Candidates often solve a coding problem, discuss past projects, and answer system design questions. Some loops include a take-home task. Final rounds typically cover team fit and give candidates a chance to ask questions. Interviewers look for how you break down an unfamiliar problem, not just whether you reach the answer. Practicing a few problems aloud and reviewing your own past projects are the best preparation.
Good to know
The role uses modeling platforms to support energy companies in development, financing, and operation of renewable infrastructure. Core tools include analytics and monitoring software for market signals and settlement data. Success depends on interpreting market rules and translating them into actionable insights.
Career growth
Engineering careers usually progress from individual contributor to senior, staff, and principal levels. Some engineers move into management and lead teams of five to twenty people. Others stay on the technical track. Growth follows demonstrated impact, not tenure alone. A typical engineering ladder has clear levels with defined expectations for scope, quality, and mentorship. Moving up usually requires owning outcomes end to end rather than completing assigned tickets.