Adrien Murillo
Let’s discuss your project.
An objective, a constraint, some context: a few lines are enough to begin scoping the conversation.
Optional · 3 questionsHelp me prepare my message
Answers stay on this page. Nothing is saved or sent automatically.
Before we talk
Practical questions.
Who will I work with?
With Adrien Murillo, an independent engineer and trainer. I am your point of contact for scoping the need, carrying out the work and handing over agreed deliverables.
Can an engagement cover several areas?
Yes. A platform may need risk work, technical controls and training. Scoping identifies priorities, dependencies and what belongs in the engagement.
What should I prepare for the first conversation?
The expected outcome, the system or team concerned and the main constraint. A few lines are enough. Sensitive documents and any access requirements are addressed later within an appropriate framework.
What deliverables can I expect?
Depending on the engagement: risk documentation, control evidence, code, procedures, tests or training material. Deliverables, verification criteria and handover responsibilities are agreed before the work begins.
Are GitHub projects client engagements?
No. Case studies describe my professional experience. The GitHub catalogue contains public tools and demonstrators, with provenance and limits. AI security is documented there without claiming client references.
How is training prepared?
Starting with the audience, prerequisites and situations the team needs to handle. The program defines objectives, exercises, a debrief and material. The proposed workshops are a starting point for scoping.
When can an engagement start?
Schedule and terms are confirmed after discussing scope. The form starts that conversation. It does not reserve a slot or initiate an engagement.