New opportunity

AI Solutions Developer

Two Sigma · New York, United States

About this role

Two Sigma is hiring an AI Solutions Developer for its new AI Solutions team in New York. This is a hands-on engineering role focused on turning opportunities for AI augmentation into production systems across the investment management firm, rather than conducting research or managing products. Projects range from short integrations to multi-month platform builds.

Responsibilities

  • Work directly with teams to understand workflows, identify useful AI applications, and deliver systems they can rely on.
  • Design and build agent-based workflows for knowledge and analysis tasks, including orchestration, escalation, and human-agent interaction.
  • Integrate AI capabilities with existing infrastructure through MCP servers, APIs, data pipelines, and internal tools.
  • Build and maintain deployment infrastructure, monitoring, observability, and operational support for AI-powered systems.
  • Help shape the firm’s AI platform through production work across domains. Independently scope problems, make architectural decisions, and deliver results with minimal specification.

Qualifications

  • A BS in a science, technology, engineering, or mathematics field, or equivalent work experience, and at least 1 year of experience. Five to 10 years of experience and an MS are preferred.
  • Strong software engineering fundamentals and experience building dependable production systems; meaningful experience with AI tooling and agentic systems over the past 2–3 years, including an understanding of their evolution and limitations.
  • Experience building integrations, APIs, or developer tooling; comfort with ambiguity and changing contexts; and strong communication skills.

The role follows a hybrid policy with flexible in-office days and a home-office setup budget. Base pay is $165,000–$300,000; a discretionary bonus may be significant. Listed benefits include paid medical and dental premiums for employees and dependents, a 401(k) match, life and disability insurance, learning support, vacation, unlimited sick days, and caregiver leave.

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

Skills for this role

Agentic AIAI toolingAgent-based workflowsAgent orchestrationMCP serversAPIsData pipelinesDeveloper toolingSoftware engineeringSystem architectureMonitoringObservabilityAI deployment infrastructureCommunication

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

  • Find useful AI applications in real workflows

    The role embeds with teams across the firm to understand their work before building. Prepare to explain how you would identify an AI opportunity, define a useful outcome, and decide when AI is not the right solution.

  • Build agent workflows with human oversight

    The posting calls for agent-based knowledge and analysis workflows, including orchestration, escalation, and human-agent interaction. Prepare to discuss where an agent should act independently, hand off, or ask for review.

  • Connect AI to existing systems

    MCP servers, APIs, data pipelines, and internal tools are named integration areas. Prepare a concrete example of designing an integration around existing interfaces and operational constraints.

  • Own production reliability

    This is a building role delivering systems people depend on, with responsibility for deployment infrastructure, monitoring, observability, and operational support. Prepare to explain how you would detect failures and maintain a system after launch.

  • Make architectural decisions with limited specification

    The role requires autonomous scoping and architecture decisions while contributing to an AI platform through production work across domains. Prepare to show how you would choose a practical first implementation without losing sight of reuse.

Likely challenges to think through

  • Ambiguity versus delivery speed

    Likely preparation hypothesis: Partner teams may describe a workflow without a complete specification, while projects range from two-day integrations to multi-month builds. Be ready to explain how you would clarify the goal, limit scope, and deliver a useful first version.

  • Agent autonomy versus dependable outcomes

    Likely preparation hypothesis: More autonomous workflows may reduce manual work but make failures harder to catch. Prepare to describe how escalation, human review, monitoring, and knowledge of agentic tools' limitations would inform the design.

  • Local solutions versus a reusable platform

    Likely preparation hypothesis: A solution tailored to one team may be faster to ship, while platform components need to work across domains. Prepare to explain when you would build a narrow integration and when repeated production needs would justify a shared capability.

03

Practice your answers

Technical practice

How would you identify a useful AI augmentation opportunity in an existing workflow?

What to coverThe role involves understanding teams’ workflows before building. Suggested preparation (inferred): explain how you would map the task, compare an AI approach with simpler alternatives, and define what a useful result would look like.

How would you design an agent-based workflow for a knowledge or analysis task?

What to coverThe posting specifically names agent-based workflows and orchestration. Suggested preparation (inferred): describe how you would divide responsibilities, manage intermediate results, and prevent failures in one step from silently affecting the final output.

When should an agent escalate to a person, and what should that handoff contain?

What to coverEscalation and human-agent interaction are stated responsibilities. Suggested preparation (inferred): discuss triggers such as uncertainty or consequential actions, and how to give a reviewer enough context to make a decision.

How would you evaluate whether an agentic system is reliable enough for its intended use?

What to coverThe role calls for production systems people depend on and an understanding of where AI tools break down. Suggested preparation (inferred): cover representative task tests, failure analysis, and the trade-off between automation and human review.

How would you integrate an AI capability with existing services through an MCP server or API?

What to coverMCP servers, APIs, and existing infrastructure are named in the posting. Suggested preparation (inferred): explain interface boundaries, error handling, and how you would keep an integration maintainable as either side changes.

What would you consider when connecting an AI workflow to an existing data pipeline?

What to coverData-pipeline integration is an advertised responsibility. Suggested preparation (inferred): address data freshness, input quality, failure recovery, and how downstream users would know when results are incomplete.

How would you turn a working AI prototype into a dependable production system?

What to coverThe team’s stated focus is shipping systems that others rely on, not conducting research. Suggested preparation (inferred): discuss testing, predictable failure behavior, maintainability, and the trade-offs you would resolve before deployment.

How would you monitor and troubleshoot a deployed AI-powered workflow?

What to coverMonitoring, observability, and operational support are explicit duties. Suggested preparation (inferred): describe what you would observe across the workflow, how you would isolate a failure, and how findings would inform a fix.

How would your deployment approach differ for a short integration and a multi-month platform build?

What to coverThe posting says projects can range from a two-day integration to a multi-month build. Suggested preparation (inferred): compare the minimum safeguards needed to ship quickly with the deployment and maintenance choices justified by a longer-lived system.

How would you decide whether a solution belongs in a shared AI platform?

What to coverThe role contributes to the platform through production work across diverse domains. Suggested preparation (inferred): explain how you would distinguish a reusable pattern from a domain-specific need, including the costs of premature abstraction.

Behavioural practice

Tell me about a time you understood another team’s problem before proposing a solution.

What to coverWorking directly with partner teams and understanding their problems are central to the role. Suggested preparation (inferred): use a real situation, the questions and actions you took to clarify the workflow, and the resulting decision or outcome.

Describe a project you scoped and delivered with little initial specification.

What to coverThe posting calls for autonomy in scoping, architecture, and delivery. Suggested preparation (inferred): give the situation, how you bounded the problem and made decisions, and the result.

Tell me about a time you switched between projects or unfamiliar domains.

What to coverRapid context-switching across projects, domains, and partner teams is explicitly mentioned. Suggested preparation (inferred): describe the situation, how you learned what mattered and managed competing demands, and what happened.

Describe a production issue you helped resolve in a system others depended on.

What to coverThe role includes operational support for dependable production systems. Suggested preparation (inferred): explain the situation, your diagnostic and communication actions, and the result, including what changed afterward.

Tell me about a time you had to explain an architectural trade-off to collaborators.

What to coverArchitectural decisions and strong communication are stated expectations. Suggested preparation (inferred): present the situation, how you made the options and consequences understandable, and the decision or result.

02

Sharpen your knowledge

Topics to prepare

  • Agentic AI capabilities and limitations

    Suggested revision exercise: Compare two approaches to a knowledge or analysis task, noting where an agent helps, where it can fail, and when human review is preferable. The posting explicitly seeks experience with AI tooling and agentic systems, including how they have evolved and where they break down.

  • Orchestration, escalation, and human-agent interaction

    Suggested revision exercise: Diagram an agent workflow with decision points, escalation conditions, and a handoff to a person. These patterns are explicitly named in the role’s knowledge and analysis work.

  • Production reliability and operations

    Suggested revision exercise: Walk through how an AI-powered system would be deployed, monitored, diagnosed after a failure, and supported. The role calls for dependable production systems, deployment infrastructure, monitoring, and observability.

  • Integration and architecture decisions

    Suggested revision exercise: Sketch how an AI capability could connect to an existing API, data pipeline, or MCP server; explain the boundaries and trade-offs. The posting names those integrations and expects autonomous architectural decisions.

  • Scoping ambiguous workflow problems

    Suggested revision exercise: Take a loosely stated workflow problem and outline questions, a bounded first deliverable, and criteria for deciding whether AI augmentation is useful. The role involves understanding partner teams’ problems and delivering with minimal specification.

Skills to revise

  • Build an agent workflow

    Suggested hands-on exercise: Implement a small knowledge-task workflow with orchestration, a defined escalation path, and a human handoff; demonstrate what happens when a step fails. Designing and building such workflows is an explicit responsibility.

  • Create an infrastructure integration

    Suggested hands-on exercise: Build a small integration that exposes a capability through an API or MCP server and connects it to a data flow; explain the interface and failure handling. The posting calls for integrations with existing infrastructure.

  • Add operational visibility

    Suggested hands-on exercise: Instrument a practice AI service so you can observe a request, detect a failure, and explain how you would investigate it. Monitoring, observability, and operational support are explicit duties.

  • Communicate a scoped solution

    Suggested hands-on exercise: Role-play a workflow-discovery conversation, then write a short implementation scope with assumptions, architectural choices, and open questions. Direct collaboration, communication, and independent scoping are central to the role.

04

Your preparation checklist

  • Map a workflow from problem to opportunity

    The role involves working directly with teams to understand workflows before building. Prepare a short discovery plan with questions about users, existing steps, failure points, and where AI augmentation would be useful.

  • Prepare a production-system walkthrough

    Choose a real system you helped build, if available, and outline the problem, your decisions, reliability measures, outcome, and what you would change. Be precise about your contribution.

  • Sketch an agent-based workflow

    For a hypothetical knowledge or analysis task, draw the agent steps, orchestration, human review, and escalation paths. Explain where agentic tooling may fail and how the design handles that uncertainty.

  • Explain an integration design

    Prepare a small design showing how an AI capability could connect to existing tools through an API, MCP server, or data pipeline. Identify interface boundaries, data flow, and failure handling as proposed choices, not known firm architecture.

  • Plan for production operations

    Extend the design with deployment, monitoring, observability, and operational support. Specify what you would measure and how a team would detect, investigate, and respond to failures.

  • Gather evidence for the stated qualifications

    Make a factual inventory of relevant software engineering, AI tooling, agentic-system, and integration work, including dates and your specific role. Prepare to discuss how the tools have evolved and where they break down.

  • Draft questions about scope and platform decisions

    Ask how the new AI Solutions team chooses projects, balances short integrations with longer builds, and turns lessons from production work into platform decisions. These questions reflect the advertised scope without assuming a particular process.

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…