AI Engineering · Software

I make AI features reliable enough to ship.

I build and debug LLM-powered software. I pay attention to what happens when model output has to fit an actual product.

RELIABILITY PATH / 01 — ILLUSTRATIVE TRACEVALIDATE BEFORE USE
  1. UNSTRUCTURED OUTPUTraw
  2. SCHEMA VALIDATIONcheck
  3. FAILEDinvalid
  4. CONSTRAINT / RETRY / CONTEXT FIXintervention
  5. VALID OUTPUTpass

Illustrative: model responded with mixed prose + malformed structure.

required: title, level, yearspending

Gate: does output match product contract?

— missing quotes, dropped fields, prose bleed

  • Explicit JSON schema
  • Few-shot anchor
  • Context re-injection

Illustrative: now conforms to product contract.

  • Computer Science student
  • Open to AI engineering internships

Case 01 / Syncareer

The AI worked in the demo. Production exposed what the demo didn't.

Syncareer is an AI-integrated career platform built by Stephen. This trace previews how an output moves from raw model to product-ready.

Syncareer SynAI interface showing personalised career guidance based on Stephen's profile, quick actions and a message input.
Product surface / SynAI

The AI feature combines profile context with career-guidance entry points inside the product.

Reliability narrative

Failure, engineering response, then a product contract.

Scroll the three states or use the state controls. The detailed trace remains directly selectable below.

State 01 / Observed failure

Production exposed three failure modes.

Inconsistent formatting, dropped context and response variance broke the expected product contract.

Evidence state01 / 03
Illustrative bad outputRaw
To become senior, you should...
- build projects

{
  title: Senior Dev
  level: 
  years: "five?"
  • Formatting

    Missing schema

  • Context

    Context dropped

  • Response variance

    Inconsistent output

Evidence Confirmed observations from production use.

State 02 / Engineering response

Each failure mapped to a tighter response path.

The prompt, examples, context and output constraints were made more explicit.

Evidence state02 / 03
  • Prompt restructuring
  • Few-shot anchor
  • Explicit context management
  • Tighter output constraints

Evidence Related interventions listed in the case study.

State 03 / Product contract / evidence boundary

Valid output is a contract, not a reliability metric.

The output shape can match product needs while the evidence boundary remains explicit.

Evidence state03 / 03
Product expectstitle, level, years, next_steps
Validationrequired fields + types
Illustrative valid outputValid
{
  "title": "Senior Developer",
  "level": "senior",
  "years": 5,
  "next_steps": [
    "ship one AI feature",
    "add validation",
    "test beyond happy path"
  ]
}

Interpretation Prompt structure, context handling and the expected output needed tighter control.

Measured result Not yet supplied. No reliability threshold is claimed here.

Direct stage inspector

Inspect the six underlying stages.

Select a stage to see what happened at each step. Keyboard: arrows to move between stages. Values marked ILLUSTRATIVE are demo shapes, not historical logs.

01 / INPUT

User activity + profile context

Syncareer supplies Claude with explicit context from the student profile — degree, interests, activity, progress and weaknesses — so guidance can be tailored.

EvidenceProduct record — context visible in SynAI surface.

Technical index — evidence linked

Technical Toolkit

Project-relevant capabilities stay visible. Select one to see where I used it and what I actually did with it.

Project capabilities

  • Used in
    Evidence
    • custom system instructions
    • explicit context management
    • output constraint design
More technical tools12 tools

Languages

Backend & AI Integration

Databases

Infrastructure & Tools

Data & ML

SelectedPrompt engineering
Used in
Evidence
  • custom system instructions
  • explicit context management
  • output constraint design

About

A little about me.

I'm a Computer Science student at Ashesi University. I'm curious, analytical and attentive, especially when details are easy to miss.

Stephen Mensah

Experience

Where I've worked

  1. Software Engineer InternAmalitech

    We are examining how farm production data is captured and used, then developing a system to improve record-keeping, production visibility, and operational decision-making.

  2. DataCamp Donates Program CoordinatorDataCamp

    Coordinate access to DataCamp's data science and AI learning resources for a group of 35+ learners. My role includes managing license distribution and helping participants stay engaged with the program.

  3. Student Library AssistantAshesi University

    Supported students with academic resources, research materials, printing, scanning, and database navigation. I also regularly helped people work through technical problems by translating unfamiliar processes into straightforward instructions.

Selected credentials & recognition

Evidence

A few things that are easier to show than describe.

SAT1520 / 1600
Ashesi UniversityDean's List
Cropped Ashesi letter addressed to Stephen confirming his Dean's List recognition.Open full-size evidence

DetailB.Sc. Computer Science

Royal Commonwealth Essay CompetitionGold Award
National Sharks QuizQuarterfinalist

Start a conversation

Have an AI engineering role to discuss?

I'm looking for entry-level AI engineering opportunities where I can contribute to product work and learn from experienced engineers.

Direct contactstevemensah333@gmail.com