A highly experienced Software Engineer with over 10 years of experience in the industry. Skilled in software development, software engineering, mobile development, front-end and back-end development (Fullstack). Proven track record of success in leading teams, making executive technology decisions, and aligning technology with organizational goals.
- π Iβm currently working on Loading...
- π± Iβm currently learning
["Go", "Rust", "Spatial Design Systems"] - π― Iβm looking to collaborate on
["Javascript", "WASM"]projects - π€ Iβm looking for help with
["Video", "Audio"]transcoding and streaming technologies - π« How to reach me: factman60@gmail.com
- β‘ Fun fact: My names are user-friendly
"Odunayo"=>"Ayo"=>"AY"||"Factman"
Chief Technology Officer at Simple Finance Nigeria (Jan 2024 - Present)
Led the technology team to implement technological solutions that improved the overall efficiency and profitability of
the company.
Managed the company's technology resources and ensured they aligned with the organization's goals.
Developed and implemented the company's technology strategy, including the selection and deployment of new systems and
infrastructure.
Collaborated with senior leadership to define technology initiatives that support business growth and success.
Managed technology projects and ensured they were completed on time and within budget.
CTO & Co-Founder at ETeam Technology (May 2017 - Present)
Provide visionary leadership for the company's technology strategy and implementation.
Develop technology budget and make investments that align with the company's goals and vision.
Oversee the implementation of functional areas of technology, including software development, enterprise architecture,
quality assurance and testing, production operations, technical support, network and systems administration, and
information security management.
Collaborate with senior leadership to develop and execute technology initiatives that drive business growth.
Lead a team of technology professionals and manage technology projects from concept to completion.
Frontend Lead Engineer at Mazadat (Oct 2023 β Mar 2024)
As the Frontend Lead Engineer at Mazadat, I have been entrusted with a pivotal role in driving the company's
technological and strategic initiatives. My primary responsibilities include Strategic Execution, Technical Leadership,
Mentorship, Onboarding, and Individual Contributions.
I leverage my extensive expertise in frontend technologies to contribute significantly to critical projects, ensuring
they meet and exceed quality standards and deadlines.
I Collaborate with cross-functional teams to streamline development processes, resulting in a significant increase in
project efficiency.
Senior Frontend Engineer at Mazadat (Apr 2023 β Oct 2023)
Work in a cross-functional mission team with engineers, designers, and analysts.
Help the team to iterate fast and learn about the customer's needs by designing, launching, and iterating on A/B
experiments.
Continuously keeping track of the latest modern trends and building intuitive designs according to the
requirements.
Enhance SEO ratings, Implement high-quality Software following appropriate modern design patterns for lightweight and
fast websites.
Work with modern technology like ReactJS, Vanilla ES6, Elasticsearch, MS Azure, MongoDB, Docker, Jenkins...
Chief Technology Officer at Simple Finance Nigeria (Dec 2021 β Jan 2023)
Led the technology team to implement technological solutions that improved the overall efficiency and profitability of
the company.
Managed the company's technology resources and ensured they aligned with the organization's goals.
Developed and implemented the company's technology strategy, including the selection and deployment of new systems and
infrastructure.
Collaborated with senior leadership to define technology initiatives that support business growth and success.
Managed technology projects and ensured they were completed on time and within budget.
Chief Technology Officer at Travoofy (Dec 2021 β Aug 2022)
Provided visionary leadership for the company's technology strategy and implementation.
Supervised the technology team and ensured they provided timely resolution of IT-related issues.
Developed and implemented technology initiatives that aligned with the company's vision and goals.
Evaluated and deployed new systems and infrastructure to improve the overall efficiency and profitability of the
company.
Collaborated with senior leadership to develop and execute technology projects that drive business growth.
Engineering Manager at Investa.ng (Jan 2021 β Jan 2022)
Managed the technical aspects of the organization to align with the company's growth targets.
Collaborated with senior leadership to define technology initiatives that support business growth.
Provided technical leadership to the technology team and ensured they were geared towards technology development.
Managed technology projects and ensured they were completed on time and within budget.
Provided technical expertise to other departments and ensured they had the necessary technology resources to perform
their functions.
Chief Technology Officer at 386konsult (Jan 2021 β Mar 2021)
Provided visionary leadership for the company's technology strategy and implementation.
Developed the company's strategy for using technology resources efficiently, profitably, and securely.
Evaluated and deployed new systems and infrastructure to improve the overall efficiency and profitability of the
company.
Managed technology projects and ensured they were completed on time and within budget.
Collaborated with senior leadership to define technology initiatives that support business growth.
Information Technology Support Specialist at Afe Babalola University (2018 β Oct 2020)
Provided technical support to faculty, staff, and students, including hardware and software installation,
troubleshooting, and maintenance.
Assisted with the development and implementation of technology initiatives to improve the efficiency and functionality
of the university.
Collaborated with technology vendors to evaluate and deploy new systems and infrastructure.
Ensured technology resources were used efficiently, profitably, and securely.
Provided technical expertise to other departments and ensured they had the necessary technology resources to perform
their functions.
Information Technology Consultant at Peace Mass Transit (Jul 2020 β Aug 2020)
At Peace Mass Transit, I served as an Information Technology Consultant, providing advice and recommendations on the
implementation of new technology systems.
I also resolve technical issues and ensured that the company's technology resources were being used efficiently and
effectively.
Senior Full Stack Developer at NANO BLOCKCHAIN LTD (Jun 2018 β Nov 2018)
At NANO BLOCKCHAIN LTD, I worked as a Senior Full Stack Developer, responsible for front-end development using various
technologies such as Angular, Material-UI, and React.js.
I also worked on back-end development using technologies such as Node.js and PHP.
Web developer and designer at JIT Solutions (Jan 2013 β Dec 2017)
At JIT Solutions, I worked as a Web Developer and Designer, responsible for designing and developing websites for
clients.
I used technologies such as HTML, CSS, and JavaScript to create dynamic, interactive websites that met the needs of the
clients.
Tip
βYou can only write a logic you can see. Picture it firstβ
- Factman
This repository also holds the source of my portfolio website (Angular, prerendered to static HTML, hosted on Vercel).
-
Node 24 (LTS) via nvm. The version is pinned in
.nvmrc:nvm install && nvm use -
pnpm 10 via Corepack. The exact version is pinned in
package.json(packageManager). Use pnpm only; npm and yarn lock files are ignored.corepack enable pnpm -v
| Command | What it does |
|---|---|
pnpm install |
Install dependencies from pnpm-lock.yaml |
pnpm start |
Dev server on http://localhost:4200 |
pnpm build |
Validates data, generates the models and builds Storybook, then the production build; every static route is prerendered to dist/factman/browser, with the static Storybook at /storybook |
pnpm build:preview |
The same build with preview settings (noindex, analytics off); Vercel uses it for preview deployments |
pnpm data:validate |
Checks src/data/*.json against their JSON Schemas and the cross-reference rules. How to edit content: docs/data-authoring.md |
pnpm data:docs |
Regenerates docs/data-reference.md, the field reference, from the schemas (test:scripts fails when it's out of date) |
pnpm data:types |
Generates TypeScript models from the schemas into src/app/shared/models/generated |
pnpm test:scripts |
Tests for the build scripts (data validator, design tokens) |
pnpm ds:tokens |
Regenerates src/styles/factman/tokens.css from the design system's tokens.json |
pnpm ds:fonts |
Self-hosts the fonts: copies the woff2 files, writes fonts.css and the preload link |
pnpm ds:brand |
Resizes the design system's logo artwork into the web logo files, favicon set, apple-touch icon, maskable app icons and web manifest |
pnpm ds:portraits |
Exports the profile photos at responsive sizes as AVIF and WebP (src/assets/profile/) |
pnpm ds:og |
Renders the 1200 Γ 630 Open Graph image from the data files with Chromium (src/assets/og/default.jpg) |
pnpm ds:split |
Splits the design system's bundle.css into global.css and one file per component |
pnpm lint:styles |
Stylelint: component styles must use design tokens, never raw colours or sizes |
pnpm test |
Validates data and generates the models, then unit tests (Vitest + Angular TestBed) |
pnpm lint |
ESLint (incl. Atomic Design boundaries), Stylelint and the lint-rule fixture test |
pnpm typecheck |
Generates the models, then the TypeScript check for app, specs and scripts |
pnpm format / pnpm format:check |
Prettier write / verify |
pnpm storybook |
Storybook on http://localhost:6006 |
pnpm build-storybook |
Static Storybook in storybook-static; build copies it into the site at /storybook (ETE-220) |
pnpm test:storybook |
Story tests in Vitest browser mode, with axe accessibility checks |
pnpm test:headers |
Checks vercel.json security and cache headers, for the app and for /storybook |
pnpm test:build |
Builds, then checks the output: content data (services, clients β¦) stays out of the JavaScript every page loads, the CSP allows every inline script by its hash, and the static Storybook is at /storybook |
pnpm csp:hashes |
Builds, then writes the hash of each inline script into the CSPs in vercel.json, the app's and Storybook's separately (run it when test:build asks, e.g. after a Storybook upgrade) |
pnpm e2e |
Builds (or restores the build from cache), then Playwright against the prerendered files. Run pnpm e2e:install once first |
Every script above runs through Nx (pinned in package.json), with the Nx Cloud remote cache. The targets live in project.json and the shared settings in nx.json; each package.json script is a one-line nx run factman:<target>, so nothing is chained with &&.
- Order. Nx runs a target's dependencies first:
data:validate,data:typesandbuild-storybookbeforebuild,data:validateanddata:typesbeforetest,data:typesbeforetypecheck,startand Storybook, andbuildbeforee2e.lintruns ESLint, Stylelint and the lint-rule test.lintandtestdo not depend on each other. - Cache. Builds, lint, tests and checks are cached in
.nx/cache(git-ignored). A repeat run with unchanged inputs is replayed from the cache, anddist/is restored if it was deleted. Docs, workflow files and Markdown changes do not invalidate the build. Use--skip-nx-cacheto force a run,--skip-remote-cacheto ignore Nx Cloud, orpnpm nx resetto clear the local cache. SetNX_NO_CLOUD=trueto work without Nx Cloud. - Arguments pass through to the underlying tool:
pnpm test --watch=false,pnpm e2e --args="--project=chromium". - Graph.
pnpm nx graphshows the task graph;pnpm nx show project factmanlists every target.
Every deployment, production and previews, serves the static Storybook at /storybook (ETE-220). build depends on build-storybook and tools/build/add-storybook.mjs copies storybook-static into dist/factman/browser/storybook, adding a <base href="/storybook/"> so the manager works without a trailing slash. vercel.json gives it its own headers: a CSP with its own inline-script hashes plus 'unsafe-eval' (Storybook's Angular renderer compiles stories at run time), a same-origin preview frame (frame-src 'self', frame-ancestors 'self', X-Frame-Options: SAMEORIGIN), X-Robots-Tag: noindex and no long-term caching (its file names have no hash). Every other path keeps the app's strict CSP, without 'unsafe-eval'. e2e/storybook.spec.ts loads a story under that CSP.
GitHub Actions (.github/workflows/ci.yml) runs on every pull request and on every push to dev or main: format check, lint, typecheck, unit and Storybook (axe) tests, the prerendered build, then Playwright E2E against the built files. Each job runs its checks through Nx (nx run-many in the static job) and shares results through the Nx Cloud remote cache (nxCloudId in nx.json, free Hobby plan). A task that already ran with the same inputs, in another job, another run or on a developer machine, is replayed from the remote cache, and the E2E job takes the build from it instead of rebuilding. Each job ends with nx fix-ci (Self-Healing CI): when an Nx task fails, Nx Cloud analyses the failure and proposes a fix on the pull request for review. The workspace is a single Nx project, so CI runs every target rather than nx affected; switch to nx affected if the repository grows more projects. Vercel deploys every push (ETE-21).
vercel.json holds the build settings (pnpm build β dist/factman/browser), security headers (CSP, HSTS, X-Content-Type-Options, Referrer-Policy, Permissions-Policy). The CSP allows exactly one frame source, https://calendar.google.com, for the "Schedule a call" modal (ETE-214); every other frame is blocked, long-lived caching for hashed JS/CSS, revalidation for HTML, and the static 404.html fallback. Production is https://www.factman.dev; Vercel redirects the apex factman.dev to it (308). https://factman.vercel.app is the staging address: it serves the same deployment with X-Robots-Tag: noindex, nofollow, so only the custom domain is indexed. Preview deployments get Vercel's own noindex.
Environment variables (set in the Vercel project and in GitHub Actions secrets):
| Variable | Used by | Notes |
|---|---|---|
GITHUB_TOKEN |
sync:github |
Read-only token for public repo data. Script lands with the data layer. |
When analytics (GA4/GTM) is added, its hosts must be added to the CSP in vercel.json.




