Workshop materials

Download the materials.

Pay once, download the PDF as soon as the payment is confirmed.

You are taken to a secure Duitku payment page. The download link appears on the status page once the payment is received — keep that page.

Quest-based learning path

Forward Deployed Engineer.

Translate user problems into integrated solutions that can be tested and operated.

The quest platform requires a password. Need access? Request access from Rakitala.

Skills you will practice

From understanding a problem to proving a result.

The work starts with understanding a problem, before choosing a model. This path connects discovery, integration, deployment, and handover so the systems you build can actually be used.

01

Understand the problem and constraints

Map workflows, users, data, and success criteria. Decide where AI helps and where conventional software is a better fit.

02

Build an integrated solution

Prototype, connect APIs and data, and handle authentication, validation, and errors. Test assumptions through user feedback.

03

Prepare for real use

Plan deployment, observability, documentation, and handover. Explain technical trade-offs and measure results against the original need.

Before you start

Bring these foundations.

For software and product professionals who want to connect business needs with technical implementation alongside users.

  • Experience building a small application in Python or JavaScript/TypeScript.
  • An understanding of HTTP, JSON, REST APIs, databases, Git, and basic authentication.
  • Willingness to write clarification questions, explain trade-offs, and read English briefs and technical documentation.

Equipment and access

Prepare a laptop, editor, Git, a Python or Node.js runtime, and Docker when required. Some integrations need sandbox accounts or system access. Example data does not replace permission to use a client system.

Path practitioner

Frederik Sakspari (Rico)

Meet the Rakitala team
Quest sequence

Build capability, one challenge at a time.

Each quest has a purpose and several briefs ordered to add skills and complexity gradually. Expand each section to see its focus and the work you can produce.

F01Scope the right system6 briefs

Turn a vague AI request into a bounded plan with explicit acceptance criteria.

Skill focus

  • Discovery
  • Scoping
  • Acceptance criteria

Suggested work product

A requirements brief, clarification questions, and a phased implementation plan.

Open quest F01
F02Connect the business systems6 briefs

Move from one unreliable integration to a coordinated workflow across business tools.

Skill focus

  • APIs
  • CRM
  • Idempotency

Suggested work product

A working integration with error, duplicate-request, and recovery tests.

Open quest F02
F03Knowledge that stays current7 briefs

Build from reliable document ingestion to a cited assistant that handles changing information.

Skill focus

  • RAG
  • Ingestion
  • Citations

Suggested work product

A document pipeline and cited RAG demo with index-refresh checks.

Open quest F03
F04Automation with human control6 briefs

Connect tools while keeping validation, approvals, and consequential actions visible.

Skill focus

  • Workflows
  • Approvals
  • Validation

Suggested work product

A workflow with approval checkpoints, input validation, and failure scenarios.

Open quest F04
F05Build a tenant-aware workspace6 briefs

Keep AI features useful while protecting roles, client boundaries, and sensitive documents.

Skill focus

  • RBAC
  • Multi-tenancy
  • Data boundaries

Suggested work product

An access matrix and workspace with user or tenant isolation tests.

Open quest F05
F06From repository to reliable release6 briefs

Take existing AI applications through integration, secure deployment, and end-to-end acceptance.

Skill focus

  • Deployment
  • Security
  • Release checks

Suggested work product

A deployment, smoke-test results, environment configuration, and rollback guide.

Open quest F06
F07Make the system usable after handover6 briefs

Help a team understand its workflow, operate it day to day, and keep it healthy.

Skill focus

  • Handover
  • Training
  • Operations

Suggested work product

An operating guide, handover demo, and maintenance checklist.

Open quest F07

Briefs are independent cases, not one continuous project commissioned by a single client. The connection is the skill you practice. A brief can appear in another path with a different focus; difficulty is guidance, not a promised completion time.

Examples from the quest collection

Problems you will work through.

These examples are part of this path’s practice sequence. Read the full briefs on the platform to check scope, acceptance criteria, and material requirements.

F02

CRM AI Assistant Optimization

Repair an integration boundary and handle timeouts and API errors so the user workflow can continue.

Explore in the quest
F03

Custom RAG Application & AI Support Chatbot Development

Connect documents and retrieval to an application that answers from relevant context.

Explore in the quest
F06

Container App DevOps Pipeline Setup

Define the environment and acceptance checks, then automate a verifiable container application release.

Explore in the quest
How you learn

Read. Build. Test. Explain.

  1. 01

    Choose a starting point

    Read the quest’s purpose and prerequisites. Follow the sequence or start where it fits your experience.

  2. 02

    Check the brief and materials

    Understand the expected result, effort estimate, and required access. Use synthetic materials when supplied and record your assumptions.

  3. 03

    Build and gather evidence

    Implement a solution, run checks, and keep code, configurations, or experiment results that someone else can inspect.

  4. 04

    Reflect and move forward

    Compare your result with the brief, document limitations, and mark your practice progress before taking on the next challenge.

Evidence of your skills

Produce work others can examine.

Use this list to guide your documentation. The final deliverables for each assignment still follow the brief you choose.

  • A discovery document with problem scope, assumptions, and acceptance criteria.
  • An application or workflow with data integration, validation, and error handling.
  • A deployment tested through a user journey, with configuration and rollback instructions.
  • A demo and handover guide covering daily use and maintenance.

Tools follow the problem.

Applications & APIs

Python, FastAPI, TypeScript

Data & workflows

PostgreSQL, REST APIs, n8n or Make

Delivery & operations

Git, Docker, GitHub Actions

Not every tool is used in every quest. Choose according to requirements, compatibility, costs, and access constraints.

Practical details

Plan your learning with clarity.

Does every solution have to use AI?

No. You need to decide whether AI serves the user’s need. Some problems are better addressed with API integrations, deterministic rules, or workflow improvements. Explain technical choices through the requirements and constraints of each case.

How long does the path take?

There is no uniform duration for seven quests. Brief estimates assume a working developer allocating 10 hours per week per person. Total person-hours, team size, experience, and material availability affect elapsed time. Use individual brief estimates to plan a realistic schedule.

What is available now, and what does it cost?

The quest and brief collection is available through a password-protected platform. Contact [email protected] to request access and discuss your learning needs. Program fees, class schedules, and mentoring arrangements have not been announced. APIs, cloud services, or GPUs used for practice may have separate costs.

Are all client materials included?

Not necessarily. Check each brief: some need data, code, accounts, or devices that are not supplied. Available synthetic packs are labeled “with synthetic data” and serve as practice substitutes. They do not provide access to client systems or guarantee that every dependency is covered.

Will AI automatically review my work?

Not on the shared platform yet. Private submissions and Rakitala-provided AI reviews are planned for a later stage. Current completion marks are self-reported practice progress in your browser, not a passing grade or certification of proficiency.

Are these paid jobs assigned to me?

Briefs are practice cases, not work assignments or payment promises. Estimated budget figures come from collected listing amounts; they are neither program fees nor promised earnings. Use the English learning adaptation and check its assumptions and limitations.

Do I have to follow the entire sequence?

The order helps build skills gradually. If you already meet the prerequisites, choose the quest most relevant to you. Some briefs appear across paths because deployment, evaluation, and inference decisions are connected.

Start with a challenge that fits you.

Explore the practice path, or discuss your experience, goals, and access needs with the Rakitala team.

The quest platform requires a password. Need access? Request access from Rakitala.

Contact

Let’s talk about your idea.

Tell us about your learning needs, engineering challenges, or a collaboration you would like to explore with Rakitala.