Microsoft
Microsoft5 open roles

Senior Software Engineer - CoreAI, Durable Task Scheduler (Forward Deployed)

$120–235kRedmond, WAOn-siteSeniorFull-time

Posted 7 days ago

The role in short

Embed with customers to design, build, and deploy production-grade durable workflows and AI agents using Durable Task Scheduler and Azure services.

We’re entering a new era defined by the power of AI to transform how organizations operate and innovate. At Microsoft, we’re building the next generation of AI-powered platforms and production-grade solutions that help customers solve complex challenges and create meaningful business impact. Durable Task Scheduler (DTS) is a fully managed Azure service that lets developers write reliable, stateful, distributed workflows and durable AI agents in code that reads like ordinary async programming, backed by checkpointing with automatic replay, transparent retries, fan-out/fan-in parallelism, durable timers, durable entities, and human-in-the-loop steps.

As a Senior Software Engineer - CoreAI on the Durable Task Scheduler team, you’ll work at the intersection of durable execution and real-world customer outcomes. Embedded directly with customers, you’ll partner closely with stakeholders to understand their most critical workflow, orchestration, and AI agent challenges, and rapidly design, build, and deploy DTS-powered solutions that move from concept to production.

Working in small, cross-functional teams alongside engineers, product managers, and domain experts, you’ll own the end-to-end delivery of production-grade applications, durable workflows, and AI agent systems built on DTS and the Durable Task SDKs (.NET, Python, Java, JavaScript/TypeScript, and Go). You’ll apply modern engineering practices and AI-enabled engineering practices across the development lifecycle to help customers accelerate decision making, improve operations, and unlock new opportunities, and you’ll bring what you learn in the field back to the product team to shape the service, SDKs, and developer experience.

Microsoft’s mission is to empower every person and every organization on the planet to achieve more. As employees, we come together with a growth mindset, innovate to empower others, and collaborate to realize our shared goals. Each day we build on our values of respect, integrity, and accountability to create a culture of inclusion where everyone can thrive at work and beyond.

Responsibilities

  • Partner directly with customers and stakeholders to understand business challenges, define success criteria, and translate needs into durable workflow and orchestration solutions built on Durable Task Scheduler.
  • Design, build, test, deploy, and operate secure, reliable, and scalable production-grade software systems and services using DTS, Azure Durable Functions, and the Durable Task SDKs, applying AI and data capabilities where appropriate.
  • Rapidly move from concept to prototype to production, iterating alongside customers to deliver measurable business outcomes.
  • Build durable, stateful, and observable AI agents and agentic workflows, including with the Microsoft Agent Framework, that connect customer systems, data, and AI capabilities into reliable end-to-end solutions.
  • Help customers adopt durable execution patterns (fan-out/fan-in, durable timers, durable entities, human-in-the-loop, retries, and compensation) and migrate existing workflow or job-scheduling workloads onto DTS.
  • Integrate customer solutions with Azure Functions, Azure Container Apps, and Kubernetes/KEDA for hosting, scaling, and deployment.
  • Apply engineering best practices including code reviews, automated testing, CI/CD, observability (OpenTelemetry, distributed tracing, and the DTS dashboard), documentation, and security-first development.
  • Drive end-to-end ownership of customer solutions, monitoring performance, reliability, quality, and maintainability, and continuously improving deployed systems after release.
  • Collaborate across engineering, product management, design, and customer teams to solve complex distributed-systems problems such as concurrency, idempotency, state management, and failure recovery.
  • Contribute reusable components, samples, reference implementations, and best practices that can be leveraged across customer engagements and the open-source community.
  • Share insights and learnings from customer deployments to help improve the DTS service, SDKs, developer experience, and broader Microsoft platforms and engineering practices.
  • Foster a culture of learning, inclusion, innovation, and continuous improvement while contributing to the growth of the broader FDE community.
  • Embody our culture and values.

Qualifications

Required/Minimum Qualifications:

  • Bachelor's Degree in Computer Science or related technical field AND 4+ years technical engineering experience with coding in languages including, but not limited to, C, C++, C#, Java, JavaScript, or Python
    • OR equivalent experience

Other Requirements:

Ability to meet Microsoft, customer and/or government security screening requirements are required for this role. These requirements include, but are not limited to the following specialized security screenings:

  • Microsoft Cloud Background Check: This position will be required to pass the Microsoft Cloud background check upon hire/transfer and every two years thereafter.

Preferred/Additional Qualifications:

  • Bachelor’s Degree (or currently pursuing) in Computer Science or related technical field AND 5+ year(s) technical engineering experience with coding in languages including, but not limited to, C, C++, C#, Java, JavaScript.
  • Experience through coursework, projects, internships, or employment building software, data, cloud, or AI-enabled solutions.
  • Interest in working directly with customers and supporting solutions from early concept through deployment and ongoing improvement.
  • Familiarity with AI or machine learning concepts, cloud platforms, data pipelines, application development, or deploying technical solutions.
  • Familiarity with durable execution, workflow orchestration, or job-scheduling systems (for example, Azure Durable Functions, the Durable Task Framework, Temporal, or AWS Step Functions).
  • Exposure to building on Azure Functions, Azure Container Apps, or Kubernetes, or to AI agent frameworks (for example, the Microsoft Agent Framework, Pydantic, or Langchain).
  • Demonstrated ability to collaborate with technical and non-technical stakeholders, learn in ambiguous environments, and communicate clearly.

Software Engineering IC4 - The typical base pay range for this role across the U.S. is USD $119,800 - $234,700 per year. There is a different range applicable to specific work locations, within the San Francisco Bay area and New York City metropolitan area, and the base pay range for this role in those locations is USD $160,200 - $261,000 per year.

Certain roles may be eligible for benefits and other compensation. Find additional benefits and pay information here:
https://careers.microsoft.com/us/en/us-corporate-pay

This position will be open for a minimum of 5 days, with applications accepted on an ongoing basis until the position is filled.

Microsoft is an equal opportunity employer. All qualified applicants will receive consideration for employment without regard to age, ancestry, citizenship, color, family or medical care leave, gender identity or expression, genetic information, immigration status, marital status, medical condition, national origin, physical or mental disability, political affiliation, protected veteran or military status, race, ethnicity, religion, sex (including pregnancy), sexual orientation, or any other characteristic protected by applicable local laws, regulations and ordinances. If you need assistance with religious accommodations and/or a reasonable accommodation due to a disability during the application process.

Prep for this interview

5 questions likely to come up at Microsoft, each matched to a line in this posting.

  1. 1LLMs, RAG and agents
    They wrote: “Build durable, stateful, and observable AI agents and agentic workflows, including with the Microsoft Agent Framework, that connect customer systems, data, and AI capabilities into reliable end-to-end solutions.”

    The model gives a confident wrong answer to an important customer. What now?

    How to answer

    Why they ask: Tests how you handle trust, on top of the technical fix.

    1. Tell the customer the same day what you know and when they'll hear more
    2. Reproduce it and find the cause (bad retrieval, missing data, prompt, model)
    3. Add the case to the test set so it can't come back unnoticed
    4. Add a guard where it matters: citations, confidence checks, human review

    Tip: Own it with the customer first, then show the change that stops it happening again.

  2. 2Cloud, deployment and security
    They wrote: “Integrate customer solutions with Azure Functions, Azure Container Apps, and Kubernetes/KEDA for hosting, scaling, and deployment.”

    How would you debug a deployment that works in staging but fails at the customer's site?

    How to answer

    Why they ask: Customer environments differ in ways you can't see. This tests method under pressure.

    1. Compare versions, config and environment variables
    2. Check network rules, proxies and certificates (common in enterprise)
    3. Look at resource limits and permissions
    4. Add the missing check to your install steps afterwards

    Tip: List the usual suspects and how you'd check each without full access.

  3. 3Discovery and scoping
    They wrote: “Partner directly with customers and stakeholders to understand business challenges, define success criteria, and translate needs into durable workflow and orchestration solutions built on Durable Task Scheduler.”

    A customer says “we want AI in our claims process.” What do you ask in the first meeting?

    How to answer

    Why they ask: Most FDE work starts this vague. They want to hear you find the real problem before you pick a tool.

    1. Map the current process: who touches a claim, in what order, with which systems
    2. Find the slowest or most error-prone step and ask what it costs them
    3. Agree on one measurable goal (for example time per claim, or error rate)
    4. Ask what data you can access, and who signs off on security

    Tip: Ask about the work, not the technology. Who does it today, how long it takes, what a mistake costs, and how they'd know it got better.

  4. 4Data and SQL
    They wrote: “Familiarity with AI or machine learning concepts, cloud platforms, data pipelines, application development, or deploying technical solutions.”

    How would you design a daily pipeline that feeds customer data into our product?

    How to answer

    Why they ask: Tests basic data engineering: scheduling, failures, re-runs and monitoring.

    1. Extract with timestamps or change tracking, not full dumps, when possible
    2. Transform in steps you can re-run without creating duplicates
    3. Validate row counts and key fields before loading
    4. Alert a person on failure, with enough detail to fix it

    Tip: Make re-running safe (same input, same result) and say how you'd know it failed.

  5. 5Ownership and working with customers
    They wrote: “Drive end-to-end ownership of customer solutions, monitoring performance, reliability, quality, and maintainability, and continuously improving deployed systems after release.”

    Tell me about something you shipped that broke in production.

    How to answer

    Why they ask: Everyone has broken production. They want to hear you own it and change something afterwards.

    1. What broke and who it affected
    2. How you found out and what you did in the first hour
    3. The root cause, said plainly
    4. What you changed so it can't happen the same way again

    Tip: Pick a real one with a cost. Spend most of the answer on what you changed.

Not the one? Get the next one by email

New roles land here every day. Pick what you want to hear about.

FDE Info

Want the job, not just the posting? Learn how FDEs work.

FDE Info is our free weekly newsletter for forward deployed engineers: tools, field notes from real deployments, and how FDE teams hire and pay.

Free. One email a week. Unsubscribe in one click.

More at Microsoft

Similar roles at other companies

Microsoft

$120–235k · On-site

Apply