Agree the retirement plan for the legacy process large language model engineering replaces.
Engineering and Developing Large Language Models
A senior-level treatment of large language model engineering, focused on what changes outcomes.
📍 Cairo🗓️ 5 training days📚 4 modules🎓 Accredited certificate
5intensive training days
4scientific modules
8training sessions
32detailed points
Course Overview
The constraint on large language model engineering is rarely the model or the platform — it is the data and the operating discipline behind it. Technology choices around model engineering are easy to reverse on paper and expensive to reverse in practice. The programme uses small-group work so that each participant's treatment of this strand of digital and data-driven work is examined, not just described. The course gives participants a defensible structure for large language model engineering and the judgement to adapt it. Participants gain a clear basis for measuring what the wider digital and data-driven work agenda has actually achieved. Moving model engineering from written policy into daily practice is not achieved by a single decision. Field experience suggests that the barrier to better large language model engineering is rarely technical. It is designed for mixed groups, so that model engineering is examined from more than one functional angle. The final session converts the week's work on the digital and data-driven work discipline into commitments with owners and dates.
Expected Learning Outcomes
Build the internal skills to operate model engineering without permanent vendor dependency.
Document decisions about large language model engineering in a form that remains useful after the people change.
Build a concise delivery roadmap for model engineering that colleagues can follow without further explanation.
Quantify the running cost of large language model engineering — compute, licensing, and the people who keep it alive.
Reduce avoidable variation in how model engineering is carried out across teams.
Establish version control and rollback for every component of large language model engineering that reaches production.
Who Should Attend
Solution architects designing how large language model engineering fits the existing estate.
Experienced practitioners formalising an approach to model engineering that has grown up informally.
Chief information officers accountable for the investment in large language model engineering.
Information security officers reviewing the exposure created by model engineering.
Training and development staff building internal capability in large language model engineering.
Vendor and contract managers overseeing suppliers involved in model engineering.
Course Modules
Large language model engineering: monitoring, drift and operational ownership
2 sessions · 8 pointsSession 1Who owns large language model engineering once the project team disbands
- Set the metrics that will show whether large language model engineering is drifting from its intended behaviour.
- Identify every system model engineering must read from or write to.
- Set out how exceptions to large language model engineering are requested and approved.
- Verify that model engineering still performs when input volume doubles unexpectedly.
Session 2What has to be agreed before work on model engineering starts
- Decide which legacy process large language model engineering retires, and set the date.
- Agree who is on call for model engineering outside working hours.
- Plan how large language model engineering is versioned and how a bad release is rolled back.
- Reduce the variation in how model engineering is carried out between teams.
Model engineering: vendor selection and avoiding lock-in
2 sessions · 8 pointsSession 1The data question everyone skips at the start of model engineering
- Define the exit route from the supplier supporting large language model engineering.
- Remove steps in model engineering that add effort without adding assurance.
- Arrange the handover of large language model engineering so capability survives staff changes.
- Agree the smallest change to model engineering that would be visibly useful.
Session 2The paperwork for model engineering that is actually needed
- List the data sources large language model engineering consumes and confirm each has a named owner.
- Map the handovers in model engineering between functions and secure them.
- Confirm that contractual obligations around large language model engineering are understood.
- Establish what evidence demonstrates model engineering is under control.
Model engineering: measuring benefit and retiring what it replaces
2 sessions · 8 pointsSession 1Explaining model engineering to people whose jobs it changes
- Agree what will be standardised in large language model engineering and what will not.
- Record the reasoning behind each architectural choice in model engineering.
- Confirm the retention and deletion rules applied to data inside large language model engineering.
- Estimate the resource model engineering requires to run as designed.
Session 2What to measure in large language model engineering and what to ignore
- Specify the fallback path when large language model engineering is unavailable.
- Verify six months later that changes to model engineering have held.
- Classify the data in large language model engineering and apply access controls that match the classification.
- Build the competence framework that supports model engineering.
Model engineering: cost, licensing and total running expense
2 sessions · 8 pointsSession 1Reading the true cost of running model engineering
- Identify the data already collected that bears on large language model engineering.
- Assess the regulatory obligations model engineering triggers in each jurisdiction.
- Define the service level large language model engineering must meet and what happens when it is missed.
- Test the procedure for model engineering against a realistic scenario.
Session 2The pilot that actually settles the argument about model engineering
- Design the pilot for large language model engineering so that a negative result is still useful.
- Build the user briefing that explains what model engineering does and does not decide.
- Define acceptance criteria for large language model engineering in advance.
- Build the internal briefing that explains model engineering to those affected.
Choose the package that suits you
Silver Package
At least 3 people
USD1,250
- Workshop or Program Participation
- Airport Transfers
- Customized Badge
- Expert Mentorship (Private Sessions)
- Supervision & Secretarial Services
- Accredited Certificate of Participation
- Complete Training Kit
- Coffee Break
- Closing Ceremony
Gold Package
At least 3 people
USD1,850
- 5-night stay in a 5-star hotel
- Workshop or Program Participation
- Airport Transfers
- Customized Badge
- Expert Mentorship (Private Sessions)
- Supervision & Secretarial Services
- Accredited Certificate of Participation
- Complete Training Kit
- Coffee Break
- Closing Ceremony
Complete your registration
We will contact you within one business day to confirm.