New opportunity

AI Engineer

Paces · Brooklyn, United States

About this role

Paces is hiring an AI Engineer to automate work involved in developing renewable infrastructure and power projects. Its platform uses agentic AI for early-stage due diligence and supports siting, interconnection, and permitting for renewable energy and data center developers, real estate firms, EV charging companies, and others. The engineer will work with power and permitting experts on the software engineering team.

Responsibilities

  • Build AI agents that automate human-driven work and develop automation that enables new modeling capabilities.
  • Own end-to-end features, iterating with industry experts; scale the platform to support growing traffic.
  • Collaborate with the product team on the roadmap.

Requirements

  • 4+ years of experience building data-intensive software. The page's role summary separately lists 3+ years of experience.
  • Experience deploying AI agents in production and familiarity with Agent SDK, Messages API, and LangGraph.
  • Proficiency in Python and SQL, with comfort working across backend systems, ETL, databases, and infrastructure.
  • Strong problem-solving skills; ability to work independently and with a team, navigate ambiguity, and make progress without complete specifications.

Preferred

Experience at a fast-paced, high-growth startup; with geospatial data and platforms; or with energy grid modeling or utility companies.

The role is hybrid, with approximately three days per week in the Williamsburg, Brooklyn office. The listing specifies US citizen/visa only. Annual compensation is $150K–$190K, with equity, 401(k) matching, health, dental and vision insurance, paid company holidays, and PTO.

For full details about this role, click “Apply on company site” to view the employer’s original posting.

Skills for this role

AI agentsAgent SDKMessages APILangGraphPythonSQLETLBackend developmentDatabasesInfrastructureGeospatial dataEnergy grid modelingProblem solvingCollaboration

Your skill match

Checking your profile…

YOUR NEXT STEP

Get interview-ready for this role

A focused preparation guide, built around this job’s responsibilities and requirements.

✦ AI-generated guide
Preparation suggestions, not the employer’s actual interview questions. Always check the original posting for current requirements.
01

Understand the role

What matters most

  • Automate due diligence with production AI agents

    Paces says its agentic AI automates early-stage due diligence and asks this engineer to automate human-driven work. The role requires production deployment experience and familiarity with Agent SDK, Messages API, and LangGraph.

  • Build data-intensive automation for modeling

    The role calls for automation that enables new modeling capabilities, plus work across Python, SQL, backend systems, ETL, databases, and infrastructure. Geospatial data and energy grid modeling are listed as bonus experience, not requirements.

  • Own features with domain and product partners

    The engineer will own projects end to end, iterate with power and permitting experts, and collaborate with product on the roadmap. Learning the domain and making progress without complete specifications are explicit expectations.

  • Scale the platform as traffic grows

    Scaling the platform and system for growing traffic is a stated responsibility alongside building new agent-driven features.

Likely challenges to think through

  • Choosing where agents should defer to experts

    Preparation hypothesis: automating diligence while working with power and permitting experts may require deciding which outputs need expert review. Prepare to explain how you would validate an agent's results and handle uncertainty without assuming every step can be automated.

  • Making useful models from complex inputs

    Preparation hypothesis: new modeling capabilities across siting, interconnection, and permitting may involve difficult data integration and domain assumptions. Prepare an approach to checking input quality, documenting assumptions, and testing outputs with industry experts; the posting does not specify particular datasets or models.

  • Balancing delivery speed with system growth

    Preparation hypothesis: end-to-end ownership, incomplete specifications, and growing traffic could put rapid iteration at odds with reliability. Prepare to describe how you would scope an initial feature, agree on success criteria with product and experts, and identify what to measure before scaling it.

03

Practice your answers

Technical practice

How would you design an AI agent to automate part of early-stage power-project due diligence?

What to coverSuggested preparation: Describe how you would define the human task, identify required inputs, and decide which steps can be automated versus reviewed by an expert. Discuss how you would make the agent’s outputs traceable and handle missing or conflicting information.

How would you choose between Agent SDK, Messages API, and LangGraph for an agent workflow?

What to coverThe posting asks for familiarity with all three, but does not specify how Paces uses them. Suggested preparation: Explain the capabilities you would compare, such as workflow control, integrations, observability, and operational complexity, rather than assuming a particular stack.

How would you evaluate and troubleshoot an AI agent deployed in production?

What to coverSuggested preparation: Discuss testing against representative tasks, monitoring failures and output quality, and tracing a bad result through inputs and agent steps. Explain when you would revise the workflow, add a safeguard, or route a case to human review.

How would you build an ETL pipeline for data-intensive project-development software?

What to coverSuggested preparation: Cover validation, changing source data, repeatable processing, and how downstream features would know which data they used. Explain trade-offs between processing speed, data quality, and maintainability without assuming a particular data source.

How would you use Python and SQL to diagnose a slow data-backed feature?

What to coverSuggested preparation: Explain how you would locate the bottleneck across application code, queries, and database access before changing anything. Discuss query plans, data volume, and the trade-off between a targeted fix and a broader redesign.

How would you scale an end-to-end feature as platform traffic grows?

What to coverThe role explicitly includes backend, database, infrastructure, and scaling work. Suggested preparation: Describe how you would measure the constraint, protect reliability during a rollout, and choose improvements based on observed load rather than assuming a specific architecture.

How would you validate automation intended to enable a new modeling capability?

What to coverSuggested preparation: Define the model’s intended decision or output with domain experts, then compare automated results with appropriate reference cases. Discuss how you would expose uncertainty and decide when the capability is ready for use.

How would you translate siting, interconnection, or permitting expertise into software requirements?

What to coverPaces says engineers work closely with power and permitting experts on features for these workflows. Suggested preparation: Explain how you would map a current decision process, clarify exceptions, and confirm that the resulting feature preserves important expert judgment.

If a feature used geospatial data, what data-quality and engineering issues would you examine?

What to coverGeospatial experience is a bonus, not a stated requirement. Suggested preparation: Discuss location accuracy, coordinate-system consistency, data freshness, and how errors could affect a siting-related result.

If automation touched energy-grid modeling, how would you establish its boundaries?

What to coverEnergy-grid modeling or utility experience is listed as a bonus; the posting does not define a specific model. Suggested preparation: Explain how you would agree on inputs, assumptions, validation cases, and points requiring expert review before relying on an automated result.

Behavioural practice

Tell me about a time you made progress without complete specifications.

What to coverSuggested preparation: Use a real situation, the questions you resolved or assumptions you made, and the actions you took to unblock the work. State the result, including anything you had to revise when more information became available.

Tell me about a time you iterated on a feature with a domain expert.

What to coverSuggested preparation: Describe the situation, how you elicited the expert’s reasoning, and what you changed after feedback. Give the result without claiming expertise or outcomes you cannot substantiate.

Tell me about a time you helped a product team make a roadmap trade-off.

What to coverSuggested preparation: Set out the competing needs, your technical input, and how the decision was made. Explain the result and what you learned about balancing delivery with longer-term work.

Tell me about a time you took ownership of an end-to-end feature.

What to coverSuggested preparation: Identify the situation, your responsibilities across implementation and release, and how you coordinated with others. Describe the result and how you addressed any issue discovered after delivery.

Tell me about a time you responded to a production reliability problem with a team.

What to coverSuggested preparation: Describe the impact, your specific diagnostic and coordination actions, and the observed result. Include a follow-up change or lesson if there was one, without presenting a hypothetical incident as personal experience.

02

Sharpen your knowledge

Topics to prepare

  • Production AI-agent design

    Posting: Production deployment of AI agents is required, along with familiarity with Agent SDK, Messages API, and LangGraph. Suggested exercise: diagram an agent that completes a due-diligence task, marking where it handles errors, records outcomes, and passes uncertain results to an expert.

  • Data-intensive system design

    Posting: The role requires experience with data-intensive software and spans backend systems, ETL, databases, and infrastructure. Suggested exercise: sketch how project data moves from ingestion to a user-facing feature; identify likely bottlenecks and data-quality checks.

  • Scaling end-to-end features

    Posting: The engineer will own features and scale the platform for growing traffic. Suggested exercise: walk through a feature design, then explain what you would measure and change as usage increases.

  • Power-development workflow

    Posting: Paces automates early-stage due diligence and supports siting, interconnection, and permitting, working with power and permitting experts. Suggested exercise: outline these stages and list questions you would ask an expert before automating one task; detailed domain expertise is not stated as a requirement.

  • Geospatial and grid-modeling context

    Posting: Geospatial experience and energy grid modeling or utility experience are bonus points, not requirements. Optional exercise: explain how location data or grid constraints might affect a siting decision, clearly separating assumptions from facts you would need to verify.

Skills to revise

  • Implement an agent workflow

    Posting: Building and deploying AI agents is central to the role. Suggested hands-on exercise: implement a small Python agent for a mock due-diligence task using one of the named interfaces or frameworks—Agent SDK, Messages API, or LangGraph—and test an unsuccessful or ambiguous result.

  • Query and transform project data

    Posting: Python, SQL, ETL, and databases are explicit requirements. Suggested hands-on exercise: clean a small mock project dataset in Python, load it into a database, and write SQL queries that flag missing fields and summarize records.

  • Build a backend feature with a scaling check

    Posting: Backend and infrastructure comfort, feature ownership, and scaling are explicit. Suggested hands-on exercise: expose the mock dataset through a small backend feature, measure its behavior under increased requests, and explain one improvement; no particular infrastructure tool is specified.

  • Turn ambiguous input into an iteration plan

    Posting: The engineer will work with industry experts and product, and must progress without complete specifications. Suggested hands-on exercise: draft a one-page feature plan from a vague permitting-automation request, stating assumptions, expert questions, a first deliverable, and how feedback would change it.

04

Your preparation checklist

  • Prepare a production-agent walkthrough

    The role requires experience deploying AI agents in production and familiarity with Agent SDK, Messages API, and LangGraph. Prepare one example showing your architecture, deployment decisions, failure handling, and measured results; distinguish tools you used from those you only know.

  • Document a data-intensive feature

    The posting calls for Python, SQL, and work across backend systems, ETL, databases, and infrastructure. Prepare a diagram and concise account of a feature you built, including data flow, your ownership, and performance or reliability tradeoffs.

  • Practice an early-stage diligence design exercise

    Paces says its agentic AI supports early-stage due diligence for siting, interconnection, and permitting. As interview practice, sketch a hypothetical workflow with inputs, agent actions, expert review points, and ways to check uncertain outputs; do not assume this is Paces’s implementation.

  • Prepare a scaling discussion

    The role includes scaling the platform for growing traffic. Bring a concrete example of a bottleneck you investigated, the evidence you used, the change you made, and the resulting tradeoffs.

  • Rehearse an ambiguous-project story

    The engineer will own end-to-end features, iterate with power and permitting experts, and collaborate with product on the roadmap. Prepare a story showing how you clarified an incomplete specification, made progress independently, incorporated specialist feedback, and adjusted priorities.

  • Draft focused questions for Paces

    Ask which due-diligence tasks most need automation, how industry experts review agent outputs, and where scaling is most pressing. You can also clarify the listing’s 4+ years requirement versus the separate 3+ years role summary.

AI-generated from the job information · Prepared Sep 30, 2026 (UTC)Useful preparation, not a guarantee of eligibility or an offer.

Availability last checked: Nov 4, 2026. Status can change after a check; confirm on the employer’s website. Report an issue · Our checking policy

KEEP EXPLORING

Similar AI jobs

Related skills and specializations in United States. Matched to this role, not your profile.

Explore more jobs
Finding similar opportunities…