Skip to content
← Courses & learning pathways

LOCKEDIN / FORWARD-DEPLOYED ENGINEERING 101

Understand it.
Then build it.

You can be an experienced engineer and still be new to agents. Start with what each thing is and how it helps a person do useful work. Explore 58 original introductions across software, agents, cloud, security and delivery. Start here without a model key; each topic connects to deeper instruction and practice.

A place to start.

Choose a short reading route, or look up a concept below.

  1. 101UnderstandPlain language, visual walkthrough, vocabulary
  2. 102Build with guidanceOriginal lessons, examples and knowledge checks
  3. 103Practise and explainRunnable labs, failure cases and handover

Guided 101 · Concept 4 of 8

Understand agents

Leave route

Put the model inside an application that can execute permitted actions and check the result.

See the 8-concept route

For engineers who know software but are new to AI applications. Open the related definitions whenever a term is unfamiliar.

  1. 01The modelStart with what produces the text. Separate the model from the application using it.
  2. 02TokensSee the units a model reads and produces before reasoning about its input limits.
  3. 03ContextDecide what information reaches the model for this particular request.
  4. 04The agent loopYou are here
  5. 05WorkflowsSeparate a fixed sequence from a model-selected next action before choosing a framework.
  6. 06LangChainSee how a framework assembles the model, tools and application-controlled context.
  7. 07LangGraphMake the steps and shared state explicit when work needs to branch, wait or resume.
  8. 08MCPConnect capabilities through a shared protocol while keeping permission checks in the application and server.

Bookmark this page to return to this concept. The number shows your place in the reading route; it is not an assessment result.

101 / LEARNING STUDIO

An application built around an AI model

What is an AI agent?

An AI agent is software that uses an AI model to choose some of the steps needed to complete a task. It can call tools, inspect their results and decide what to do next within limits set by the application. The model is one component; the agent also needs code, tools and rules about when to stop.

Why it matters in the field

An FDE needs to decide when model-driven choices help a real task and when a predictable sequence is enough. An agent is useful only if it improves the work and stays within its allowed scope.

UNDERSTAND THE SYSTEM

An agent chooses an action, then reads the result

An agent is an application that lets a model choose its next action within limits. The application runs tools; the model does not reach into your systems by itself.

01 / EXPLORE THE PARTSTap a part to explain it
Direction of information or workReturn / feedback

WHAT THIS PART DOES

Your goal

A person asks for a useful outcome: find the delivery date for order 104.

CONNECTED TO
  • Give the task: Model
Read the connections in plain English
  1. 01
    Your goal → Model

    The goal and tool descriptions become part of the model's input.

  2. 02
    Model → Application checks

    The model proposes lookup_order with order_id 104. A proposal is not permission.

  3. 03
    Application checks → Order lookup

    Trusted code authorizes the caller and runs the lookup within its configured limits.

  4. 04
    Order lookup → Model

    The tool result joins the context. The model can answer or propose another permitted action.

  5. 05
    Model → Answer or stop

    The application checks the result and ends the loop; a budget limit can also force a stop.

Check your understanding: What changes if the model asks to cancel the order?

Nothing is cancelled by the model's words alone. A write tool would need to exist, pass authorization and satisfy the application's confirmation policy. A read-only agent should reject that action.

1 of 5 · Get the ideaUse the buttons or swipe across the lesson.