Chiemezie Nweke · Dublin, Ireland

Chiemezie Nweke, Solutions Engineer.
Fintech and payments.

Looking for Solutions Engineer, Sales Engineer or Technical Solutions Consultant roles at B2B fintech and payments companies. Dublin or remote.

  • 10+go-lives of XNETT at PremiumTrust BankNigeria's Fastest Growing Bank. 6 branches then, 37 now
  • $300K+in 3 monthsA manual-first launch I proposed at Revolve
  • 55% to under 15%failing testsTwo client apps, MySirigu and Tra-Vu, at LarvaBox
  • 2,000+users on YadsaleA marketplace I help run, grown as a team of 9

Scroll to clear the slip. Each role stamps what it taught.Download CVPlain version

01ReceivedJul 2022 to Oct 2022

Technology Analyst (internship)

Technology consultancy

  • Supported current-state assessments for enterprise clients, finding operational gaps and recommending system-level improvements.
  • Contributed research to a digital transformation proposal for a state government.
  • Ran the options analysis for a fleet management system and a competitor analysis for a peer-to-peer product.
  • Gathered requirements from stakeholders across client organisations.

Carried forwardDiscovery · Requirements · Options analysis

02ClearedNov 2022 to Feb 2024

Technical Consultant, Deployment and Integration

Pan-African banking and payments technology group (40+ institutions, 13 countries), embedded at a bank. Hybrid, Lagos. 15 months embedded at the bank.

10+go-lives, as the bank grew from 6 branches to 37.

A bank growing that fast needs clearing and payments that keep up. XNETT kept up. The platform was FASYL's. Making it work at the counter, and keeping it working, was mine.

ProblemCheques and electronic transfers had to clear through the national clearing house and post correctly into core banking, branch by branch.

How it works, and what I did
How it works
  1. XNETT Pay moves transfers and collections in real time, with maker-checker approvals before anything leaves.
  2. A transfer starts in EFT. A cheque is scanned at the branch in CTS, and its image is stored with its data.
  3. XNETT exchanges it with the national clearing house.
  4. The cleared item posts into FLEXCUBE, and it has to match exactly: cheque number, customer name, amount. Then the customer gets an E-Alert.
What I did
  • Took XNETT live 10+ times across the bank's 6 branches, and demoed every release to the bank's stakeholders and project managers before it went out.
  • Listened to the cashiers, service managers and clearing team, and turned what they said into product: transaction limits compliance could control themselves, direct debit as a new clearing instrument for the bank, and a clearer interface for the clearing team.
  • Built those changes in Flask (Python), Angular, TypeScript and Oracle SQL.
  • Checked every transaction from XNETT into FLEXCUBE, down to the scanned cheque images in the database.
  • When direct debits failed in production, traced it to malformed XML from empty database results, fixed it, and verified it before the next settlement window.
  • Ran L2 support, resolving incidents in 10 to 60 minutes by severity. Once, that meant getting the head branch's cheque scanner back up.
  • Customised the E-Alert messages PremiumTrust customers get after every transaction.
  • Wrote the deployment, migration and rollback docs, so the consultants after me could set up servers and deploy without me.

Carried forwardProduct demos · Clearing and settlement · SQL · L2 support · Rollback docs

03ScheduledJan 2023 to Jan 2024

Organising committee, speaker management

TEDxAbuja, volunteer. Theme: "Bottom Up".

8speakers on stage, for 118+ people.

A team of 29 made that happen. I was one of them.

ProblemEight speakers had to be ready, within TED content guidelines, and in the right city on the right day.

How it works, and what I did
How it works
  1. Rehearsals and reviews against TED's content guidelines.
  2. Travel planned around the schedule.
  3. Trackers for before, during and after the event, shared across the committee.
What I did
  • Prepared the speakers, with the speaker team.
  • Built the trackers, with the rest of the 29-person committee.
  • Ran registration for walk-in guests on the day.

Carried forwardStakeholder comms · Run sheets · Fixed deadlines

04TestedJun 2024 to Jun 2025

QA Engineer and Technical Project Manager

Product consulting firm for early to mid-stage companies. Contract, remote. Team of 5 to 6.

55% to under 15%failing tests. No duplicate records since.

The fixes were the developers'. Flagging it until it stuck was mine. And both apps shipped: MySirigu onboarded 150+ users in its first month, and Tra-Vu's MVP landed on time with every feature in scope.

ProblemMore than half of test runs were failing, and the same kinds of defects kept returning. Then duplicate records reached production.

How it works, and what I did
How it works
  1. Every build goes through regression testing, then client demos and UAT.
  2. Payments run through Paystack and Stripe, for users in Nigeria, the UK and the US.
  3. Every API gets checked in Postman before anything ships, then builds go out through TestFlight and Google Play.
What I did
  • Reviewed every PRD with the product manager, on both apps, and made the build decisions together.
  • Set up the Tra-Vu team with the product manager, and was part of its architecture decisions from the early stage.
  • Kept the engineers' tasks current, tested every push, and held each release to good UX before it went out.
  • Wrote 300+ test cases while we built MySirigu, then tested 30+ of its builds through launch, and 17+ Tra-Vu releases on TestFlight and Google Play.
  • Demoed to both clients with the product manager, and worked with them through UAT.
  • Flagged the same patterns of bugs back to the mobile developer, every time, until they stopped coming back.
  • Tracked down websocket and Firebase authentication bugs with the backend and mobile engineers.
  • When the duplicates hit, helped write the script that cleaned them up, then added idempotency checks to every regression run.
  • Wrote the product docs for both apps, and drew the architecture flowchart the client's own developers took over with.

Carried forwardUAT · Idempotency · REST APIs · Paystack and Stripe

05VerifiedOct 2024 to Sep 2025

Technical Product Manager and QA Engineer

Cross-border payments startup on stablecoin rails. Contract, remote. Corridors: USD to NGN, and USDT to NGN or USD.

$300K+moved in three months.

That's volume, not revenue. The idea was mine. The operations team made it work.

ProblemCustomers were ready to move money between USD, USDT and NGN. The platform was delayed.

How it works, and what I did
How it works
  1. A customer is verified through Prembly.
  2. We serve them directly on WhatsApp.
  3. Money moves on stablecoin rails: USD to NGN, and USDT to NGN or USD.
What I did
  • Proposed the manual-first launch.
  • Brought in Prembly for KYC, and sat in on the calls choosing a provider.
  • Led planning for the platform's first version, and ran its technical project management.
  • Tested every pre-launch build and API, as the only QA.

Carried forwardKYC · Go-to-market · Product planning

06ReconciledJan 2025 to Jun 2026

MSc thesis, built solo

MSc Big Data Management and Analytics, Griffith College Dublin

1,845buying signals across 24 categories, from 3,032 validated posts.

67.2% were people simply trying to find something.

ProblemBuyers ask "who sells?" on X every day. That demand is real, but it is scattered and informal.

How it works, and what I did
How it works
  1. X API v2 pulls the posts into Cloud Storage.
  2. Python sorts and scores them with rule-based NLP.
  3. The results land in BigQuery and Looker Studio. Airflow on Cloud Composer runs the whole thing.
What I did
  • Built the pipeline, end to end, on my own.

Carried forwardPython · BigQuery · Airflow

07PostedFeb 2025 to present

Technical Product and Operations Manager

Peer-to-peer marketplace with escrow payments (SafePay). Part-time. Co-lead a cross-functional team of 9.

No accountneeded to buy.

The platform, not me alone: 2,000+ users.

ProblemBuyers had to create a profile and verify by SMS before they could buy. Some never got through.

How it works, and what I did
How it works
  1. PostHog, GA4 and Microsoft Clarity follow a buyer from first visit to purchase.
  2. Funnels show where people leave. Session recordings show why.
  3. Payments, escrow and refunds run on Paystack, through SafePay.
What I did
  • Set up the analytics, and built the funnels.
  • Found a sharp drop at SMS verification, and traced it to texts failing on certain numbers. The team shipped a WhatsApp fallback.
  • Turned what we learned into guest checkout and guest offers.
  • Write the specs, from revenue reporting to coupon tracking to admin permissions, and catch edge cases before release, like a buyer ordering more than a seller has.
  • Dig into payment, escrow and refund issues with Postman and SQL.
  • Split our users into sellers, buyers, both and inactive with SQL, for campaigns reaching 1,500+ people, and led the campaign for our interstate delivery launch.

Carried forwardSpecs · Funnels · Escrow and refunds

08Settled

“If you do everything, you'll win.”

Napoleon Bonaparte

Every role handed me something. I kept all of it. That gap is my work.

Settling into Solutions Engineer, Sales Engineer or Technical Solutions Consultant roles at B2B fintech and payments companies. Dublin or remote.