What Infotech does
Infotech Solutions builds Microsoft-native governance software for regulated organisations. The platform combines security, governance, assurance, evidence and controlled execution.
PEOPLE · ONBOARDING
David's 90-Day Onboarding
Start date 28 September 2026 · Reports to Kgaogelo Madileng · Remote · Lagos
INF-NG-0002Learn the company.
Learn the company.
Build safely. Deliver evidence.
This workspace turns your first 90 days into a clear operating plan. Complete work in sequence, keep evidence with each deliverable, and use Wednesday and Friday reviews to unblock decisions.
90-DAY REVIEW0%
0 of 30 onboarding actions completeWed + Fricore collaboration cadence
START HERE
Your Infotech map
One platform, three products
AI & Data Governance OS, Cloud Security & Resilience OS, and Fiscal Governance & Accountability OS share reusable platform services while remaining independently licensed products.
Human-authorised execution
The OS detects and controls. AI investigates and explains. People authorise. Approved automation executes. Evidence records the outcome. AI does not recommend remediation.
Secure engineering first
Your first 90 days focus on secure engineering delivery, access discipline, DevSecOps, identity/cloud controls, documentation and reliable team cadence.
SIGNED REVIEW FRAMEWORK
What the 90 days build toward
30%Secure engineering delivery
20%Security & access discipline
15%Code quality & DevSecOps
15%Identity & cloud controls
10%Documentation & operational readiness
10%Team cadence & communication
DELIVERY MILESTONE
Microsoft OS delivery · 30 November 2026
FIRST 60 DAYS = PRODUCTIVE DELIVERY
Onboarding while shipping
Your onboarding runs alongside Infotech's OS delivery commitment. Company orientation, manuals and enablement remain required, but from Week 1 your engineering work should contribute directly to getting the OS securely deployable, testable and demonstrable by the end of November.
30NOV
Cloud Security + DevSecOps
Own bounded work across deployment engineering, infrastructure automation, security controls and release readiness. Core product architecture and product ownership remain outside this lane unless specifically assigned.
Build together, own clear lanes
Core product implementation remains with the product engineering lane. David focuses on cloud deployment, DevSecOps, infrastructure automation, security engineering and release readiness. Architecture authority, product direction and acceptance remain with the Managing Director.
Stabilise + prove ownership
After the November milestone, use the final month to resolve deployment and security debt, improve automation, complete runbooks and demonstrate independent ownership of the assigned engineering lane.
Secure engineering environment
GitHub and Azure access, local development environment, repository understanding, branch/PR workflow and CI baseline.
Deployment foundation
Containerisation, Azure Container Apps deployment structure, environment configuration, infrastructure-as-code baseline and dev/test deployment.
DevSecOps pipeline
GitHub Actions plus code, dependency, container and IaC security checks, secrets controls and controlled deployment gates.
Azure security implementation
Support approved Entra integration, workload identities/RBAC, secrets handling, logging, monitoring and assigned cloud security configuration.
Release hardening
Deployment testing, security findings, pipeline fixes, documentation, reproducible deployment and release evidence.
Microsoft OS milestone
Support a technically deployable, security-controlled OS build with repeatable deployment evidence for the agreed milestone.
Stabilisation
Fix defects, improve automation, close documentation gaps, complete runbooks and address technical debt discovered during delivery.
Evidence-based review
Demonstrate engineering artefacts and outcomes produced for Infotech, mapped to the signed KPI categories and agreed role scope.
November definition of done for David's lane: working Azure deployment path; Container Apps configuration aligned to approved architecture; assigned infrastructure-as-code; controlled GitHub CI/CD; automated code/dependency/container/IaC checks; approved secrets handling; least-privilege workload identity/RBAC; logging and deployment observability; reproducible build/deploy/release documentation; and deployment/control evidence with open items clearly recorded.
90-DAY PLAN
Progress saves on this deviceFour delivery phases
KNOWLEDGE
Company manuals & reading path
▣
Company Handbook
About Infotech, how we work, organisation and roles, communication standards.
READ IN DAYS 1–7⌘
Engineering Handbook
Development workflow, GitHub standards, DevSecOps, environments, releases and change.
READ IN DAYS 1–14◈
Security Handbook
Access control, secrets, secure development, incidents, evidence and documentation.
READ BEFORE PRIVILEGED ACCESS△
Architecture Library
Approved architecture, ADRs and technical standards. Access only to material approved for your current task.
PROGRESSIVE ACCESSInternal architecture and customer information are provided on a least-privilege, task-specific basis. Do not copy confidential material into unapproved AI or code-assistant services.
TOOLS
Company tools
GUARDRAILS
Non-negotiables from day one
Use approved company systems and unique credentials with MFA.
Access is progressive and least-privilege. GitHub/Azure access is provisioned for the task at hand.
Never place confidential code, architecture, credentials or customer information into unapproved AI/code assistants.
Declare pre-existing code/tools and follow open-source review and licensing requirements.
Report suspected compromise, access issues and security incidents immediately.
Do not make unreviewed production changes or represent Infotech to customers beyond your authorised scope.