GO-GENIE · Proposed interview plan
A practical first 90 days
How I could learn the business, take on agreed work and improve one useful part of the operation. This is a proposed plan to discuss and shape with the team.
01 / Meet Alvin
I know the work. I build around it.
I’m Alvin Foo Dun Zhi, an AI Forward Deployed Engineer and business founder. I started building AI and CRM tools to take repetitive work off my hands in my own business.
AI Native Builder & Business Founder. Decade in B2B/B2C Sales, Digital Marketing & Growth.
- Founder and Managing Partner of Apply Singapore PR LLP; registered on 28 May 2019.
- Through Apply AI, I turn customer needs into useful software, demonstrations and practical plans.
This is a starting point for our conversation. We would agree the actual role and responsibilities together.

02 / Relevant work
Software I use to do the work.
I built and use Apply PR’s CRM and preparation portal every day. Client records, documents, unanswered questions and review progress stay together, so I can see what needs doing next.
I built JARVIS AI to help AI agents pick up work without starting over. It uses Obsidian notes to carry forward current instructions, business context and progress I have checked.
- I decide what the system needs to do, direct Codex-assisted development, check the changes and improve it through daily use.
- The system uses React/TypeScript, Python and Google Drive/Sheets.
- I can show a demonstration with private details removed, explain the business problem and walk through how I check the result.
03 / Start with questions
Show me the work that needs attention.
I would start by asking the people who use and maintain the systems to show me their everyday work.
- Which tasks matter most to customers and the day-to-day operation?
- Which software and connections between systems would I look after?
- How does the team handle support, updates, access and problems that need senior help?
- What already works well, and where would a change save the team the most trouble?
These are questions for the team, rather than assumptions about GO-GENIE. Their systems, priorities and agreed responsibilities would shape the plan.
04 / Proposed days 1–30
Learn the business. Keep the work moving.
In the first month, I would learn how the work gets done and help keep the agreed operations running.
- Map the customer journey, current IT and AI systems, and how they depend on or connect to one another.
- Agree what I am responsible for, what I can access, who reviews my work and who to call when I need help.
- Watch how the team handles support and software updates; review monitoring, backups, recovery steps and known issues with the people responsible.
- Record how the work performs today, then agree one small improvement worth exploring.
The first milestone: a map the team has checked, clear responsibilities and one agreed next step.

Days 1–30Learn
05 / Proposed days 31–60
Take on the work. Let the team check it.
I would begin handling agreed tasks while an experienced team member observes and reviews my work.
- Practise support and software-update tasks with a reviewer before taking responsibility for them.
- Keep decisions, fixes and unanswered questions easy for the team to find.
- Build one small, clearly agreed improvement around a real user problem.
- Show the result, test the affected work and demonstrate how to recover or undo the change before release.
Before changing a live system, we would agree the work, what a good result looks like and who can approve its release.

Days 31–60Build with review
06 / Proposed days 61–90
Show what improved. Make it easy to keep using.
I would review the change with the people using it and compare the result with what we measured at the start.
- Show what improved, what did not and what we still need to understand.
- Write clear instructions: how to run it, who looks after it and how to get help or recover from a problem.
- Improve the workflow using actual feedback.
- Recommend what to tackle next, explaining its likely value, effort and what it depends on.
We would agree the measures and targets together, then check the results against the starting point.

Days 61–90Measure & hand over
07 / Let’s discuss
What would you want me to take on first?
I would like to understand what a useful first 90 days means for GO-GENIE. I can show a working system with private details removed and explain how I turn an everyday problem into software that can be checked and used.
- What would make this hire a success for you?
- Which responsibilities need attention first?
- Who would I work with, and how would we agree the work and review progress?
Let’s shape the plan around the actual role and what the team needs.
Use the arrows or keyboard ← →. Present simplifies the view; Esc returns. Print includes every slide.
Ask me to walk you through this ↗