New opportunity

Applied AI Engineer

Percepta · New York City, United States

About this role

Percepta is hiring an Applied AI Engineer to work directly with customer executives, operators, and technical teams to define and deliver production-grade AI agents and workflows. The company embeds with customers in critical industries, including healthcare, manufacturing, and energy, to turn applied AI into measurable business value. This is a full-time, on-site role in New York City.

Responsibilities

  • Collaborate with customer stakeholders on long-term AI strategy and transformation roadmaps, then identify and prioritize high-leverage applications.
  • Rapidly design, build, and deploy AI products for real users and data, rather than prototypes or laboratory projects.
  • Incorporate lessons from customer engagements into Mosaic, Percepta’s in-house toolkit for deploying agentic workflows, by contributing features, patterns, and abstractions.

What Percepta seeks:

  • Enthusiasm for bringing AI into critical institutions; collaborative idea generation, initiative, and ownership.
  • Ability to ship code quickly in ambiguous environments while balancing speed and quality, understand customer pain points, and iterate directly with end users. No specific years of experience or education requirement is stated.

Bonus qualifications:

  • Hands-on experience with LLM tooling such as LangGraph, Mastra, or Agents SDK, or with production LLM-powered systems involving tool use, RAG pipelines, multi-step agents, or human-in-the-loop workflows.
  • Technical foundations in Python or TypeScript, cloud deployment on AWS, GCP, or Azure, and DevOps tooling; startup or founding-engineer experience.

The stated base salary range is $150K–$400K per year, with equity offered. The specific offer depends on experience, technical skills, and location.

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

Skills for this role

AI agentsAgentic workflowsMosaicLarge language modelsLangGraphMastraAgents SDKRAGTool useHuman-in-the-loop systemsPythonTypeScriptAWSGCPAzureDevOpsCloud deploymentAI strategyCustomer collaboration

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

  • Turn AI strategy into measurable use cases

    The role works with customer executives, operators, and technical teams on transformation roadmaps, then prioritizes applications that connect the long-term vision to business value.

  • Ship production AI agents and workflows

    Percepta emphasizes rapidly building and deploying products for real users and real data, rather than prototypes or laboratory projects.

  • Own delivery with customers

    The posting calls for initiative in ambiguous environments, understanding customer pain points, and iterating directly with end users to deliver useful outcomes.

  • Improve Mosaic from field lessons

    Applied AI Engineers are expected to turn lessons from customer engagements into features, patterns, and abstractions in Percepta’s agentic-workflow toolkit.

Likely challenges to think through

  • Balance shipping speed with production quality

    Likely preparation challenge: rapid delivery in messy environments can conflict with the reliability needed for real users and data. Prepare a concrete example of how you decided what to ship first, what to validate, and when to slow down.

  • Align different customer perspectives

    Likely preparation challenge: executives, operators, and technical teams may define value and feasibility differently. Prepare to explain how you would surface those differences and choose a use case with a measurable outcome.

  • Separate reusable patterns from customer-specific work

    Likely preparation challenge: a solution tailored to one engagement may not belong in Mosaic as-is. Prepare to describe how you would identify a repeatable pattern without making the immediate customer delivery wait for a broad abstraction.

03

Practice your answers

Technical practice

How would you turn a customer's long-term AI vision into an engineering roadmap?

What to coverSuggested preparation: explain how you would learn the goals of executives, operators, and technical teams, then identify dependencies and near-term deliverables. Distinguish a strategic aspiration from an application that can be shipped and measured.

How would you prioritize AI applications for a customer?

What to coverSuggested preparation: compare potential business value, user pain, data readiness, implementation effort, and operational risk. Explain what evidence would justify building one application first and what outcome would show it worked.

How would you design a production agent that uses tools across multiple steps?

What to coverSuggested preparation: describe how the agent would choose tools, manage intermediate results, and handle failed or unexpected tool responses. Discuss when a constrained workflow may be preferable to a more autonomous agent; tool use and multi-step agents are listed as bonus experience.

When would you use a RAG pipeline, and how would you evaluate it?

What to coverSuggested preparation: explain when retrieving customer information is useful, how you would assess retrieval quality and answer grounding, and how you would handle missing or conflicting information. RAG is listed as bonus experience, not a stated requirement for every project.

Where would you place human review in an AI workflow?

What to coverSuggested preparation: identify decisions that warrant approval or escalation and explain the trade-off between oversight and workflow speed. Describe how users would see enough context to make a decision; human-in-the-loop workflows are listed as bonus experience.

How would you judge whether a shipped AI workflow succeeds?

What to coverSuggested preparation: separate technical measures, such as task quality and failure rates, from adoption and measurable customer outcomes. Explain how you would test with real users and data rather than treating a working prototype as proof of production value.

How would you investigate an agent that performs well in tests but fails for end users?

What to coverSuggested preparation: walk through reproducing failures and checking inputs, retrieval, tool responses, and workflow steps. Explain how findings from operators or end users would guide a fix and how you would check for regressions.

What would you consider before deploying an LLM-powered workflow to the cloud?

What to coverSuggested preparation: discuss reliability, access to customer data, monitoring, and recovery when a dependency fails, alongside the pressure to ship quickly. Cloud deployment and DevOps tooling are bonus qualifications; no particular provider or deployment method is required.

How would you turn a customer-specific solution into a reusable Mosaic capability?

What to coverSuggested preparation: identify which features, patterns, or abstractions could serve other engagements without obscuring customer-specific needs. Explain how you would decide whether a repeated need merits a toolkit change rather than another one-off implementation.

How would you keep implementation quality high while shipping quickly?

What to coverSuggested preparation: describe which tests, reviews, and operational checks you would retain under time pressure and where you could simplify scope instead. Python or TypeScript foundations are listed as a bonus, so focus on sound engineering choices rather than assuming a mandated language.

Behavioural practice

Tell me about a time you took ownership of an ambiguous problem without waiting for an assignment.

What to coverSuggested practice: give the situation, the next step you chose, and how you communicated that decision to others. State the result and what you changed when new information emerged.

Describe a time you aligned people with different goals around a technical direction.

What to coverSuggested practice: identify the stakeholders and their competing concerns, then explain the actions you took to reach a decision. Give the result, including how you kept people informed rather than working in a silo.

Tell me about a time direct feedback from users changed what you built.

What to coverSuggested practice: describe the user's pain point, how you learned about it, and the change you made. Explain the observed result without substituting shipped features for user outcomes.

Describe a time you had to balance delivery speed against quality.

What to coverSuggested practice: set out the deadline or uncertainty, the risk you weighed, and where you chose to move quickly or slow down. Give the result and explain what made the trade-off appropriate.

Tell me about a time you gave candid feedback while sustaining a collaborative relationship.

What to coverSuggested practice: describe the situation, the specific feedback or decision you communicated, and how you treated the other person. Explain the result and what the example shows about working with urgency and kindness.

02

Sharpen your knowledge

Topics to prepare

  • AI strategy and use-case prioritization

    Posting: The role helps customers define transformation roadmaps and prioritize applications with measurable business value. Exercise: For a hypothetical manufacturing customer, rank three AI use cases by expected value, feasibility, and time to delivery; explain the trade-offs.

  • Production-grade agents and workflows

    Posting: Engineers ship AI agents and workflows for real users and data, not laboratory prototypes. Exercise: Diagram an agent workflow and identify where it needs error handling, user feedback, and a way to judge whether it delivers the intended outcome.

  • Speed, quality, and ownership

    Posting: Engineers are expected to ship quickly in messy environments, balance speed with quality, and decide what to do next. Exercise: Given an ambiguous customer request, outline a first release, what you would defer, and what evidence would make you slow down.

  • Reusable patterns for Mosaic

    Posting: Engineers turn lessons from customer engagements into features, patterns, and abstractions for Mosaic, Percepta’s in-house agentic-workflow toolkit. Exercise: Compare two hypothetical customer workflows and sketch one reusable pattern without assuming access to Mosaic’s internals.

  • LLM workflow design options

    Posting: Tool use, RAG, multi-step agents, and human-in-the-loop workflows appear as bonus experience, not core requirements. Exercise: For one customer task, explain when each approach would or would not help; treat this as optional preparation.

Skills to revise

  • Elicit and validate customer needs

    Posting: The role works directly with executives, operators, technical teams, and end users. Exercise: Draft distinct questions for each group, then turn their answers into a concise problem statement and a measurable success criterion.

  • Build and iterate a small workflow

    Posting: Engineers rapidly build, deploy, and improve AI solutions used in the wild. Exercise: As practice, implement a narrow agent workflow using sample data, walk through an end-user task, and revise it based on a documented failure.

  • Explain a production delivery plan

    Posting: Deployment is central to the role; Python or TypeScript, AWS, GCP, Azure, and DevOps tooling are listed as bonus foundations. Exercise: Using a language and cloud platform named in the posting, outline how you would deploy, observe, and update a small workflow. This is optional practice, not a specified stack.

  • Turn engagement lessons into product changes

    Posting: Engineers contribute features, patterns, and abstractions to Mosaic. Exercise: Write a short proposal based on a hypothetical recurring workflow problem: describe the shared need, the proposed abstraction, and what should remain customer-specific.

04

Your preparation checklist

  • Map a customer problem to business value

    The role involves shaping AI roadmaps and prioritizing high-leverage applications. Prepare a one-page hypothetical use-case brief for a critical industry, with stakeholder needs, a prioritization rationale, and a proposed measure of value.

  • Practice a stakeholder discovery conversation

    The role works with customer executives, operators, and technical teams. Draft distinct questions for each group about the workflow, user pain points, available data, and what a useful outcome would look like.

  • Prepare a production project walkthrough

    If you have a relevant project, outline the user problem, your decisions and contributions, deployment, iteration with users, and observed results. Distinguish measured outcomes from expectations; Percepta emphasizes shipped systems over prototypes.

  • Work through an agent design exercise

    Sketch a hypothetical AI workflow using real users and data: inputs, tool use or retrieval where justified, human review, deployment considerations, and how you would evaluate and improve it. These are design choices to discuss, not stated requirements for every project.

  • Show how you balance speed and quality

    Prepare a specific example, if available, of shipping amid ambiguity. Explain what you prioritized, what you checked before release, what you deferred, and how feedback changed the next iteration.

  • Identify a reusable product pattern

    Percepta says engineers carry lessons from customer work into Mosaic. From your walkthrough or design exercise, describe one feature, pattern, or abstraction that might be reusable, and what evidence would justify adding it to a shared toolkit.

  • Bring focused questions for Percepta

    Ask how teams choose customer use cases, measure value after deployment, gather end-user feedback, and decide when an engagement lesson belongs in Mosaic. Include a question about how engineering, product, and research collaborate while embedded with customers.

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…