匠人学院 JR Academy
OpenAI Select PartnerClaude Certified Services Partner

FORWARD DEPLOYED ENGINEER

FDE Three-MonthIndividual Mentorship

Understand a business. Own a project. Deliver an AI system that runs.

For people with technical or enterprise project experience. Work with a mentor on business discovery, requirements and agentic AI, building work you can demonstrate, evaluate and hand over.

5 places each month · Enquire about this month

LightmanJoe 韭神Jason
Lightman · Joe 韭神 · Jason

Mentors and times subject to availability

12 weeksA plan around your goals
1:190 minutes each week
A complete projectDiscovery to handover
A$33,000Three-month mentorship fee · AUD
Professionals discussing business workflows and an AI system at a studio desk
Business discovery to system delivery
90 minutes weekly

One to one, on your project

Scenario illustration

BUSINESS × ENGINEERING × DELIVERY

FDE work starts with understanding the business.

Forward Deployed Engineers work closely with customers, translate ambiguous problems into technical solutions and help systems get adopted. Business, engineering and collaboration come together.

01

Business discovery

Find the right business problem

Understand goals, processes, data and constraints across organisations and departments.

Practise workflow interviews, problem framing and prioritisation.

02

Stakeholder management

Align people and manage requirements

Clarify expectations with business, engineering and decision makers. Challenge requirements and negotiate scope.

Practise discovery meetings, proposals, change and trade-offs.

03

Hands-on AI engineering

Build agentic AI hands-on

Use Python, LLMs, tools and APIs to build a reliable, controlled workflow.

Practise architecture, implementation, evaluation and approval.

04

Ownership & delivery

Own the work and deliver

Clarify uncertainty, remove blockers and balance speed, quality and adoption.

Practise milestones, risk communication, acceptance and handover.

WHO THIS IS FOR

Connect your existing experience to end-to-end delivery.

Discuss your background and goals before starting. Scope and pace are adapted to your skills and available time.

01

Software / data / AI engineers

Your starting pointYou already code, develop features or build prototypes.

Mentoring focusAdd business judgement, customer communication and delivery.

02

Consultants / solutions engineers / architects

Your starting pointYou have customer, solution design or integration experience.

Mentoring focusDevelop hands-on agentic AI implementation and evaluation.

03

Technical founders / product leaders

Your starting pointYou know business problems and are willing to build.

Mentoring focusPractise a structured path from ambiguity to working systems.

YOUR 12-WEEK JOURNEY

Three months, with concrete work each week.

This is the standard progression. Agree personal goals, scope and acceptance criteria at the start, then adapt to real progress.

Scenario illustration

01

MONTH ONE

Discover the business and scope the right problem.

Month-end goal: explain the business problem, stakeholders and boundaries, with an actionable plan.

Week 01

Assess your starting point

You work on
Review experience, target roles and available materials; choose a feasible project.
With your mentor
Identify gaps and agree working arrangements, milestones and scope.
What you keepPersonal plan and project brief

Week 02

Map processes and stakeholders

You work on
Prepare and conduct interviews, or role-play where access is unavailable.
With your mentor
Challenge assumptions about pain points, data, permissions and conflicting needs.
What you keepWorkflow and stakeholder maps

Week 03

Clarify and prioritise requirements

You work on
Separate requests and constraints; explain what to prioritise, defer or change.
With your mentor
Handle simulated customer objections and review value and acceptance.
What you keepRequirements, scope and acceptance criteria

Week 04

Propose the architecture and plan

You work on
Map system boundaries, core flow, dependencies and delivery sequence.
With your mentor
Review agent placement, architecture, risks and human control.
What you keepArchitecture draft and delivery plan
02

MONTH TWO

Build the core working system.

Month-end goal: a runnable core flow with documented decisions and evaluation.

Week 05

Build the first end-to-end flow

You work on
Connect inputs, processing and outputs in the minimum useful workflow.
With your mentor
Review interfaces, structure, data contracts and scope.
What you keepRunnable first version

Week 06

Integrate knowledge and tools

You work on
Implement retrieval, tool calls or APIs; label any simulated integrations.
With your mentor
Review tool boundaries, source references, state and errors.
What you keepIntegrated workflow and interface notes

Week 07

Add permissions and human approval

You work on
Handle confirmation, missing permissions, timeouts and failure paths.
With your mentor
Challenge risky assumptions and check audit and fallback.
What you keepControlled workflow and risk log

Week 08

Evaluate and iterate

You work on
Build representative and failure cases, record results and address issues.
With your mentor
Review metrics, coverage and trade-offs; practise a requirement change.
What you keepEvaluation set, report and change log
03

MONTH THREE

Validate, hand over and explain your contribution.

Month-end goal: work you can open, evidence you can inspect and an accurate project narrative.

Week 09

Review against acceptance criteria

You work on
Close gaps in reliability, cost, access and limitations.
With your mentor
Separate measurements and estimates; narrow remaining scope.
What you keepAcceptance checklist and complete version

Week 10

Prepare the demo and handover

You work on
Document configuration, operation, maintenance and rollback.
With your mentor
Assess whether another person can run and maintain it.
What you keepWorking demo and handover documentation

Week 11

Build the career case study

You work on
Explain the problem, responsibility, decisions and results.
With your mentor
First project defence or mock interview; revise a targeted resume.
What you keepCase study, resume revision and feedback

Week 12

Demonstrate and plan next steps

You work on
Present the project, answer business and technical questions, and explain limitations.
With your mentor
Second defence or mock interview; agree further development.
What you keepDelivery pack, feedback and next-step plan

HOW WE WORK TOGETHER

Bring real work. Leave with a clear next step.

Mentors guide and review. You own implementation and follow-through. Agree what to deliver, who can help and how to address blockers.

01 / BEFORE

Share progress and blockers

Bring current work, decisions and questions to make each session specific.

02 / 90-MINUTE 1:1

Work through decisions together

Review requirements, architecture or code; practise customer conversations and prioritise.

03 / AFTER

Implement, review and iterate

Complete agreed work, submit it for feedback and track unresolved issues.

12 × 90 minutes

Individual guidance

Normally weekly; dates confirmed together.

One review each week

Asynchronous feedback

Review agreed documents, architecture, code or delivery material.

Weekday support

Project questions

Generally respond within two working days; complex topics move into sessions.

1 resume + 2 rehearsals

Career communication

Targeted resume revision and mock interviews / project defences within the 12 sessions.

YOUR MENTOR TEAM

Lightman, Joe and Jason. Scheduled around availability and project needs.

Each session pairs one mentor with one learner. Confirm the first phase before starting; any change includes progress, decision and feedback handover.

01 / MENTORLightman

JR Academy founder

Lightman

Startup practice, full-stack development and product design.
02 / MENTORJoe 韭神

Former Googler SDE · Block SDE

Joe 韭神

Software engineering, cross-team collaboration and career mentoring.
03 / MENTORJason

AI Engineer VIP mentor

Jason

AI engineering projects and one-to-one technical guidance.

A named mentor is not guaranteed throughout. All three do not attend every session together.

WHAT YOU BUILD & KEEP

Show your capability through specific work.

Work towards the agreed scope and compile a demonstrable, inspectable delivery pack. Record unfinished work and limitations accurately.

01

A runnable AI project

Open and operate the agreed core flow in a demo or local environment.

02

Business and requirement decisions

Problem, stakeholders, priorities, scope, acceptance and change.

03

Code and technical documentation

Architecture, interfaces, configuration and implementation trade-offs.

04

Evaluation and handover evidence

Results, failure cases, cost boundaries, limitations and operating steps.

05

A project case study

Context, responsibility, solution and outcomes, redacted where necessary.

06

Career communication materials

Resume, project narrative, defence feedback and development plan.

OPEN THE EXAMPLE

Open a complete example. See what delivery contains.

Outcomes for case company Harbour Supply, showing the content and depth of the project deliverables.

HARBOUR SUPPLY / DELIVERY PACK

Outcome: support triage and reply approval

Read the complete problem, stakeholders, trade-offs, architecture, acceptance and handover.

01 / Problem and scope

Case company Harbour Supply receives delivery, damage and refund requests. This system classifies requests, references policy, drafts replies and queues approval. It does not send email, issue refunds or change orders.

02 / Stakeholders and trade-offs

Support owns response quality, the warehouse checks shipment and damage facts, and finance controls refunds. A request to close all tickets automatically is narrowed to draft creation and human review because model output cannot establish logistics facts or refund authority.

Requirements and control matrix
RequirementAllowed system behaviourBoundary
RQ-01 Delivery enquiryClassify and draft a tracking enquiry responseDo not infer arrival dates without carrier records
RQ-02 Damage reportRequest photos and route to support and warehouseDo not assign fault or promise replacement
RQ-03 Refund requestCollect order, reason and item conditionAn authorised person makes the refund decision
RQ-04 Reply approvalPresent evidence and draft for reviewApproval and sending are separate; nothing is sent here

03 / Architecture

A Python API validates fields and access. An LLM proposes a category and retrieves versioned policy. A structured validator checks evidence and required fields. Missing evidence and financial decisions go to human review. Logs record sources, category, approver and state.

Data and control flow
  1. Ticket input
  2. Field and access checks
  3. Classification + policy retrieval
  4. Structured validation
  5. Human review queue

The model proposes; deterministic validation checks structure and evidence; authorised people decide. Missing evidence or retrieval failure routes to a person rather than continuing automatically.

04 / Acceptance review

The three deterministic cases below include category, policy, next action and draft. Damage and refunds remain under human control. None are sent. This is a structural check, not measured model accuracy, latency or business benefit.

Inspectable acceptance items
InputDelivery requirementExisting outcome
HS-1042 Delivery enquiryNo delivery promise without tracking evidenceCategory, D-01 reference and a verification draft
HS-1043 Damage reportCollect evidence before confirming a remedyCategory, D-02 reference and photo request draft
HS-1044 Refund requestAn authorised person must review the refundCategory, R-01 reference and information request draft

These items inspect the completeness of authored examples. Real model accuracy, latency and business improvements have not been measured; no production performance is claimed.

05 / Cost and operation

Token usage, throughput and cloud costs have not been measured. A real integration needs least privilege, redaction, vendor approval, timeouts and fallback.

06 / Handover and release conditions

Handover covers API contracts, policy versions, evaluation cases, configuration and review procedures. Before production, the business must confirm policies and access, evaluate authorised representative data and test failure and rollback paths. This is not production acceptance evidence.

BEFORE YOU START

Know what to expect.

Is this for complete beginners?

It is primarily for people with technical or enterprise delivery experience. Basic programming, APIs, Git and English technical reading are recommended. Discuss suitability first; prerequisite study may be recommended.

Do I need startup experience or a real client?

Startup experience is helpful, not required. Use authorised business materials where available, otherwise clearly labelled simulations. Real clients, enterprise access and production deployment are not included by default.

How much time do I need?

Allow around 8–12 hours of independent project work beyond the weekly 90-minute session. Effort varies with skills and complexity. You own the implementation; mentors guide and review.

Can I choose a specific mentor?

Lightman, Joe and Jason are scheduled according to availability and project needs. Confirm arrangements before starting. A particular mentor is not guaranteed throughout, and all three do not attend together.

Is a completed project guaranteed?

Agree a feasible scope and milestones at the start. Completion depends on skills, effort, complexity, data and access. Record finished work, limitations and outstanding tasks honestly.

Who covers software, models and cloud costs?

Any third-party tools, model APIs and cloud resources are discussed before use. Joining does not automatically enable paid resources.

Does this guarantee a job or salary?

No employment, interview, offer or salary is guaranteed. The service provides the agreed guidance, review and support. Hiring outcomes depend on individual circumstances and the market.

Can we talk before I decide?

Yes. Discuss your background, goals, project and availability before agreeing suitability, mentor schedules, service terms and start date.

LET’S TALK

Bring your experience and goals. Discuss a practical path forward.

Limited to 5 places each month. Contact us to confirm current availability and discuss your goals, project direction and mentor schedule.

  • Current role and technical foundation
  • Projects and your responsibilities
  • Where you want to progress
  • Weekly time available
Discuss 1:1 FDE mentorshipWeChat and other contact options

hello@jiangren.com.au

JR Academy

No employment, interview, offer or salary guarantee. Start date, mentor availability and service arrangements require confirmation.