Software Engineer – API and Platform

Description

About
East Daley Analytics

East Daley Analytics drives transparency in energy markets. We specialize in identifying, understanding, and monitoring operational risk across the oil and gas value chain, on the principle that no one should be surprised by an energy market event.

Anyone can gather energy data; our work is telling clients the "so what" of it. We track and forecast throughput and capacity across more than 1,200 midstream assets operated by 26 major midstream companies across crude oil, natural gas, NGLs, and the capital markets that finance them. That research reaches investors, operators, and business leaders through Energy Data Studio®, our analytics portal.

The Opportunity

We are always seeking ways to provide a cutting-edge and technologically advanced experience for our clients. This role executes this premise through the construction of an API over our data, and a live interactive front end in our customer portal that consumes it. The API is the center of the work: the contract our own pages depend on, the surface our customers’ tooling will call, and the layer that has to serve dashboard queries at extract speed.

This offering is also going to be queried by AI agents, not only by users in our front-end experience. That means a constrained, introspectable query surface an agent can reason about safely. It is a genuinely interesting design problem, and we are thrilled by the opportunity to make it come to life.

What
You’ll
Own

The API and the query layer. A versioned API our own pages and our customers’ tooling can depend on: resource endpoints, cursor pagination, sparse field selection, and filtering that does not fall apart as query complexity grows. You will own this contract, its versioning, and ensuring strong uptime.

Supporting the front end. Our customer-facing dashboards are moving from generated static pages to a live, interactive product including charts, maps, filtering, cross-chart interaction. A dedicated front-end engineer will own that work. Your job is to make sure the API gives them everything they need, and to be comfortable enough in the front-end codebase to read it, debug against it, and assist when it matters.

Running it in production. These dashboards are the products served to customers outside our network using the API. You will help stand up and operate what that requires: edge caching and protection, request authentication against our existing identity provider, rate limiting, observability good enough to tell you in which layer a slow request actually spent its time, and deployment that does not require a maintenance window.

Collaborate with the Data Team on SQL foundations. You will work closely with the Data Team as they optimize the database layer feeding the product. This includes stored procedures, the semantic view layer, and the filter architecture that keeps a wide multi-select query fast.

What Success Looks Like

In the first 6 months:

• The API is something others can build on without asking you how it works: versioned, documented, self-describing, and stable enough that a new dashboard page or an agent-driven query tool can be built against it independently.
• The migration is in place. Dashboards in the customer portal are live pages served by our own API, at response times equal to or better than the legacy versions they replaced.
• The aggregation problem is solved structurally. The large tables that cannot be queried live today are served from pre-aggregated stores, refreshed off the request path on a cadence matched to how fresh each one needs to be.
• The schema shared by the entire pipeline from database to HTML is enforced, changes to it are additive and coordinated, and drift at that seam is not a recurring defect.

Requirements

Minimum Qualifications

• 3+ years of professional software engineering experience.
• Designed and
  operated
  an
  API
  other teams consumed. Resource modeling, cursor pagination, sparse fieldsets, versioning, deprecation without breaking live clients.
• Maintained a schema
  across language boundaries. Additive evolution, versioned change, no rename-and-redeploy-everything.
• Golden-file and snapshot testing over generated output
  , plus the instinct for when a green suite is lying to you: silent skips, vacuous assertions, mocked-out logic.
• Daily AI-assisted development to increase production velocity and QA/QC abilities.
• End-to-end ownership. Ambiguous request ? shipped ? iterated. You can talk to an analyst who knows exactly what they need to see without knowing how it gets built.
• Bachelor's
  in CS or a related
  technical field, or equivalent experience.

Preferred Qualifications

• Agent-facing API design: MCP servers, OpenAPI-driven tool generation, runtime schema introspection.
• JSON query DSL ? parameterized SQL. Selector-based filter/sort/aggregate, no caller-supplied SQL text.
• SQL Server at scale: clustered and non clustered column store, indexed views, incremental rollup tables, read routing, execution-plan tuning.
• Public-facing service: CDN, WAF, JWT/OIDC…