--- title: "How Do You Verify a Remote Developer in Nigeria, Kenya or South Africa?" description: "A code test proves the code ran. It does not prove who wrote it, whether they read the spec, or whether they will flag a slipping deadline. The proctored half of a cross-border engineering hire, priced per candidate in USD. Facts verified 4 September 2026." canonical: https://www.assessall.com/solutions/remote-developer-verification-africa source: AssessAll --- # The code test is the half you already run. Verifying a remote developer in Africa means proving the things a coding test does not: that the person who wrote the code sat the session, that they can read a spec or an API changelog without inventing the missing half, that they can trace logic they did not write, and that they raise a problem before a deadline slips. Measured under proctoring, in one sitting, paid per candidate in US dollars. ## What goes wrong today - **A code test tells you the code ran. It does not tell you who wrote it** — Every unproctored technical exercise now measures the candidate plus whatever assistant they had open, and the artefact looks the same either way. That is not an argument for abandoning code tests — it is an argument for knowing which parts of your evidence were produced under observation and which were not. The parts that were not are the parts you should stop weighting. - **Cross-border engineering hires rarely fail on syntax** — They fail on the ticket that was read too fast, the ambiguity nobody flagged, the changelog whose breaking-change note was skipped, and the deadline that slipped for three days before anyone said so. None of those appear in a passing test suite, and all of them are measurable — reading under time pressure, tracing logic you did not write, and judgement about when to escalate. - **You cannot audit a vetted-marketplace bar** — Buying pre-vetted talent moves the assessment behind someone else's wall. The bar is real and often good; it is also unpublished, unversioned, and not comparable between two providers or between this year and last. If you never see the instrument or the score, you cannot re-cut your own bar when a cohort underperforms — you can only change supplier. - **Candidate-paid screening does not work in this corridor** — Card penetration and currency friction make "pay to take our test" a dead end in exactly the markets with the deepest junior and mid-level engineering supply. Here the employer pays per candidate in US dollars; the candidate opens a link on a phone, needs no account and no card, and the player resumes where it stopped when a connection drops. ## What AssessAll does - **Program logic, without a language** — Pseudo-code & Programming Logic — 20 questions in 25 minutes on reading and tracing program logic: loops, conditions, accumulators, nested iteration, integer division, string handling, value-versus-reference on a simple copy, function composition, a bug-spotting trace, and concept checks on FIFO and linear time. Language-agnostic — no syntax knowledge required, only the ability to execute logic in your head. Every traced answer in the bank was verified by running equivalent code. - **Reading the documents engineers actually misread** — Technical Reading Comprehension — 16 questions in 24 minutes on a product manual, an API changelog and an SOP, probed for conditions, exceptions, deadlines and precedence, plus compliance checks against specs, config rules, release notes and warranty clauses. Every answer is decidable strictly from the text, which is the point: the failure mode being measured is the assumption, not the vocabulary. - **Executing a process exactly as specified** — Flowcharts & Process Logic — 18 questions in 22 minutes tracing two realistic multi-branch flows under different inputs, plus loops with exit conditions, retry counting, decision tables, parallel-path durations, dependency ordering and escalation timing. This is the competency behind on-call runbooks, deployment checklists and anything automated. - **Deduction, including the refusal to conclude** — Deductive Logic & Syllogisms — 22 questions in 20 minutes: categorical syllogisms, modus ponens and modus tollens with the invalid forms most people fall for, disjunctive elimination, chained implications, contrapositive versus converse versus inverse. Several items are keyed to "may or may not", so the discipline of refusing an unwarranted conclusion is itself scored — which is exactly the habit you want in someone reading an incident timeline. - **Data and digital fundamentals** — Spreadsheet & Data Literacy (20 questions, 22 minutes — absolute references, IF/COUNTIF/VLOOKUP semantics, format-versus-value, the single-column sort disaster, median-versus-mean under outliers, truncated axes, CSV and mixed units) and Computer & Digital Fundamentals (25 questions, 18 minutes — files and formats, cloud concepts, networks and IP, plus a security block on passwords, phishing, 2FA, HTTPS and ransomware backups). - **Judgement, escalation and ownership** — Workplace Judgment — 16 realistic scenarios in 25 minutes: errors already sent to a client, conflicting senior instructions, confidential data exposed, impossible deadlines, scope creep, Friday-evening discoveries. Scored with graded partial credit, so a plausible-but-suboptimal response earns partial marks and the test separates sound judgement from merely avoiding the obviously wrong answer. - **Working English, written and spoken** — Written accuracy, register, concision and comprehension, plus AI-scored speaking and listening from the candidate's own recorded voice — a task no chatbot can sit for them. For a distributed engineering team English is not a nice-to-have; it is the medium the entire job happens in, and "fluent" on a profile becomes a score you can set a bar against. - **Proctoring whose evidence you can open** — Identity-baseline photo at the start, face-presence and additional-face monitoring, tab-switch, paste and screen-capture counters, and a High/Medium/Low integrity band computed from the published weights above — with the underlying evidence attached to the attempt rather than summarised away. A band you cannot inspect is just another claim. - **One link, any phone, no accounts** — Delivery is a share link or a QR code. Candidates create no account and need no card, the player is mobile-ready and resumable when a connection drops, and results rank the moment each person submits. That is what makes screening practical across Lagos, Nairobi and Cape Town without scheduling a single call. ## Use cases - US, UK, EU and Australian employers hiring engineers directly in Nigeria, Kenya or South Africa - Screening a large inbound applicant pool before any engineer's time is spent - Adding the non-code layers to an existing code-test process - Agencies and staffing firms evidencing an offshore engineering shortlist to a client - Talent marketplaces verifying their own supply side under their own branding - Re-verifying an existing contractor before a renewal or a rate increase --- Source: https://www.assessall.com/solutions/remote-developer-verification-africa