New opportunity

Staff Engineer - AI Engineering

GE Vernova · Niskayuna, United States

About this role

GE Vernova seeks a Staff Engineer - AI Engineering in Niskayuna, New York, to develop and improve LLM prompts for business use cases and help integrate LLM solutions into applications.

Responsibilities

  • Work with domain experts to translate business needs into prompts; develop, test, and refine prompts for accurate, relevant outputs.
  • Collaborate with software developers on integration into new or existing applications. Help build a scalable prompt-engineering framework that supports reuse and knowledge sharing across business units.
  • Gather and analyze user feedback, document processes and outcomes, and track LLM advances to inform tool and platform decisions.

Required qualification: A master’s degree in Computer Science, AI/ML, Engineering, Mathematics, or a related field, with at least 5 years of relevant experience.

Ideal candidate characteristics: A related PhD; prompt-engineering experience and familiarity with OpenAI GPT models or Hugging Face; proficiency in Python or another AI/ML programming language; experience with frameworks such as PyTorch and libraries such as Pandas and NumPy; prior NLP or machine-learning project experience; familiarity with Git; and an understanding of traditional industry operations and challenges. The posting also seeks problem-solving, attention to detail, communication with non-technical stakeholders, teamwork, and adaptability.

Applicants must be legally authorized to work in the United States. Relocation assistance is provided. The stated U.S. pay range is $98,400–$164,000, with geographic differentials of 110%, 120%, or 130% in certain areas and eligibility for a discretionary annual bonus. Listed benefits include health coverage, retirement savings with company contributions, tuition and adoption assistance, paid parental leave, 12 paid holidays, and permissive time off.

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

Skills for this role

Prompt engineeringLarge language modelsOpenAI GPT modelsHugging FacePythonPyTorchPandasNumPyNatural language processingMachine learningGitStakeholder communicationProblem-solvingDocumentation

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

  • Translate business needs into prompts

    The posting calls for collaboration with domain experts to turn business needs into clear LLM prompts. Prepare an example of how you would clarify a use case with non-technical stakeholders before designing a prompt.

  • Test and improve output quality

    The role develops and refines prompts for accurate, relevant outputs and analyzes user feedback. Prepare to explain how you would evaluate results, identify failures, and use feedback to guide revisions.

  • Integrate LLM solutions into applications

    The posting specifies close work with software developers on new or existing applications. Prepare to discuss how you would coordinate prompt changes with application development and testing.

  • Build reusable practices across business units

    The role contributes to a scalable prompt-engineering framework and documents processes, best practices, and outcomes. Prepare to describe how you would make prompt work understandable and reusable by other teams.

  • Inform tool and platform decisions

    The posting asks this engineer to track LLM advances and contribute to strategic tool and platform choices. Prepare to explain how you would compare options against a defined use case without treating novelty alone as a benefit.

Likely challenges to think through

  • Balancing tailored prompts with reuse

    A likely challenge, not a confirmed employer problem, is that prompts tailored to one domain may be hard to reuse across business units. Prepare an approach that separates shared patterns from use-case-specific context and records where each applies.

  • Judging quality across varied use cases

    Because the role covers varied use cases and user feedback, a plausible difficulty is deciding what counts as an accurate, relevant answer for each audience. Prepare to explain how you would agree on evaluation criteria with domain experts and investigate conflicting feedback.

  • Adopting new LLM capabilities without disrupting applications

    Tracking LLM advances while supporting application integration creates a possible trade-off between improvement and stability. Prepare to describe how you would compare a proposed tool or prompt change with the current approach and coordinate testing before adoption.

03

Practice your answers

Technical practice

How would you translate a domain expert’s business need into an LLM prompt?

What to coverThe role calls for working with domain experts to turn business needs into prompts. Suggested preparation: Explain how you would clarify the intended task, required context, output expectations, and what an unacceptable answer would look like before drafting.

How would you structure and refine a prompt for accurate, relevant output?

What to coverThe posting explicitly calls for developing, testing, and refining prompts. Suggested preparation: Discuss clear instructions, appropriate context and output format, then explain how you would compare revisions without assuming one example proves reliability.

How would you evaluate prompts across different use cases?

What to coverThe stated goals are accuracy and relevance across varied use cases. Suggested preparation: Describe representative test cases, criteria agreed with domain experts, and trade-offs between a prompt that performs well on one case and one that works consistently across cases.

What would you investigate if a previously effective prompt began producing less relevant answers?

What to coverThe role includes improving prompt effectiveness. Suggested preparation: Walk through checking the inputs, prompt revisions, model or tool changes, and examples of failures before deciding whether to revise the prompt or investigate another cause.

How would you work with developers to integrate an LLM solution into an application?

What to coverThe posting calls for collaboration on new or existing applications. Suggested preparation: Describe the prompt’s inputs and outputs, how developers could test changes, and how you would handle failures or unexpected output; these are preparation topics, not stated implementation requirements.

How would you design a prompt-engineering framework for reuse across business units?

What to coverA scalable framework supporting reuse and knowledge sharing is an advertised responsibility. Suggested preparation: Discuss which prompt components could be shared, where use-case-specific variation belongs, and how to prevent a shared change from harming another use case.

How would you use user feedback to improve a prompt?

What to coverThe role includes gathering and analyzing feedback to improve effectiveness. Suggested preparation: Explain how you would group feedback by failure type, check it against test examples, and decide whether a change improves outcomes beyond the users who first reported it.

How would you compare LLM tools or platforms for a business use case?

What to coverThe posting mentions following LLM advances, contributing to tool and platform decisions, and familiarity with GPT models or Hugging Face. Suggested preparation: Compare candidates against the use case’s output quality and integration needs, making trade-offs explicit rather than assuming one tool is best.

How could Python and data-processing or ML libraries support prompt experiments?

What to coverPython or a comparable language, PyTorch, Pandas, and NumPy appear among ideal candidate characteristics, alongside NLP or ML experience. Suggested preparation: Describe a practical way to organize test inputs and inspect outputs, while distinguishing data analysis from model development and avoiding claims that a particular library is required for every task.

How would you document and track prompt changes so others can reuse the work?

What to coverThe role calls for documenting processes, best practices, and use-case outcomes; familiarity with Git is also listed as ideal. Suggested preparation: Explain what you would record about a prompt’s purpose, revisions, tests, and limitations, and how version control could help collaborators understand changes.

Behavioural practice

Tell me about a time you clarified an ambiguous request from a domain expert.

What to coverSuggested preparation: Use a real situation, your actions to establish the underlying need and explain technical choices in accessible terms, and the result. This practices the posting’s emphasis on domain collaboration and communication with non-technical stakeholders.

Describe a time you collaborated with software developers to deliver an AI or ML capability.

What to coverSuggested preparation: Give the situation, your specific contribution and coordination with developers, and the result. Focus on how you resolved an integration or ownership question rather than claiming a particular application architecture.

Tell me about a time feedback revealed a problem in something you had built.

What to coverSuggested preparation: Explain the situation, how you assessed the feedback and changed your approach, and the result. Choose an example that shows problem-solving and attention to detail, both highlighted in the posting.

Describe a time project requirements changed after work was underway.

What to coverSuggested preparation: State what changed, how you worked with the team to reprioritize or adapt, and the result. The question reflects the posting’s emphasis on teamwork and adaptability, not a stated company process.

Tell me about a time you made technical work easier for another team to reuse.

What to coverSuggested preparation: Describe the situation, what you documented or standardized, and the result for the other team. Relate the example to the advertised goal of sharing prompt-engineering knowledge across business units without implying you have done that exact work.

02

Sharpen your knowledge

Topics to prepare

  • Prompt quality and evaluation

    The role calls for accurate, relevant LLM outputs across use cases. As a conceptual exercise, define what accuracy and relevance would mean for two different business requests, and explain how you would compare prompt revisions against those criteria.

  • Reusable prompt-engineering design

    The posting calls for a scalable framework that supports reuse and knowledge sharing across business units. Sketch which parts of a prompt should be shared and which should remain specific to a use case; this is a preparation exercise, not a prescribed GE Vernova design.

  • Application integration decisions

    The role involves working with developers to add LLM solutions to new or existing applications. Walk through the information an application would need to send and receive, and where prompt revisions could affect application behavior.

  • Feedback and tool selection

    The posting asks for user-feedback analysis and contributions to tool and platform decisions as LLM technology advances. Practice explaining how observed output problems and use-case needs would inform a prompt change versus a tool comparison.

  • Industry and stakeholder context

    Understanding traditional industry challenges and communicating with non-technical stakeholders are listed as ideal characteristics. Practice turning an illustrative operational request into a clear LLM task, while stating which domain details you would need to confirm with an expert.

Skills to revise

  • Test and refine prompts

    Draft a prompt for an illustrative business request, test it against several varied inputs, record inaccurate or irrelevant outputs, and revise it. This directly rehearses the posted prompt-development responsibility; the example request is not a claimed company project.

  • Build a small integration example

    As a suggested exercise, use Python or another AI/ML language to show how an application passes input to an LLM prompt and handles the response. The posting lists programming proficiency as ideal and explicitly calls for collaboration on application integration.

  • Analyze feedback with data libraries

    Create a small sample of fictional user comments and output ratings, then use Pandas or NumPy to group recurring issues and propose one prompt revision. These libraries are listed as examples of ideal experience; the exercise mirrors the feedback-analysis responsibility.

  • Version and document prompt changes

    Use Git to track two prompt revisions and write a short record of each change, its test results, and its intended use case. Git familiarity is listed as ideal, and the role calls for documenting processes and outcomes for a knowledge base.

  • Explain a technical trade-off plainly

    Prepare a brief explanation for a non-technical domain expert of why one tested prompt produced more relevant outputs than another, then ask a clarifying question about the business need. This rehearses the posted collaboration and communication expectations.

04

Your preparation checklist

  • Map evidence to the stated qualifications

    Prepare a one-page record of your education and relevant experience against the posted master’s degree and 5+ years requirement. Separately note any evidence for the listed ideal characteristics, without treating them as requirements.

  • Prepare a prompt-improvement walkthrough

    Choose a project you can discuss and show the business need, input constraints, prompt versions, test cases, observed accuracy or relevance, and how feedback changed the result. The role explicitly calls for developing, testing, and refining prompts.

  • Practice translating a domain need

    As a preparation exercise, draft questions for a domain expert, then turn a hypothetical business request into a prompt specification with intended outputs and evaluation criteria. Be ready to explain it to a non-technical stakeholder.

  • Sketch an application and reuse design

    Draw a small design for integrating an LLM prompt into an existing application, including how prompts could be versioned, tested, and reused across business units. Label this as your proposed approach, not GE Vernova’s architecture.

  • Gather technical examples and tradeoffs

    Prepare concise examples, where applicable, involving Python or another AI/ML language, GPT models or Hugging Face, NLP or ML work, and Git. Explain tool-selection tradeoffs; PyTorch, Pandas, and NumPy appear as ideal characteristics, not mandatory tools.

  • Show a feedback and documentation loop

    Draft a sample feedback log and a brief prompt record covering the use case, revisions, test results, and outcomes. These are preparation artifacts for the posting’s feedback-analysis and knowledge-sharing responsibilities.

  • Write targeted questions for the employer

    Ask how domain experts and developers collaborate, what defines prompt accuracy and relevance, how reuse across business units is approached, and how user feedback informs tool or platform decisions.

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…