Skip to content

A career built by learning the system from more than one side.

Teacher, developer, QA lead, project and product manager, and now Consultant Solutions Engineer. Each stage added another way to understand the people, constraints, and decisions behind useful software.

Nathanael Toussaint
Working principleUnderstand before prescribing.

Every role changed how I solve the next problem.

This is not only a title ladder. It is a progression from explaining systems, to building them, to improving how teams discover, validate, and deliver them.

  1. 01

    Self-taught computer scientist

    Learning mindset

    I was homeschooled and taught myself software development from the age of eight, learning from every source I could find. Formal computer-science education strengthened that habit of learning unfamiliar systems from first principles.

  2. 02

    IT teacher and student mentor

    Pierre Charles Secondary School

    Taught Information Technology and Mathematics, mentored students, and learned to diagnose misunderstanding instead of simply repeating an answer.

  3. 03

    Government employee and developer

    Government of Dominica

    Learned public-sector finance from inside the operation and carried the GOCD Budget Web Application from observed friction through stakeholder alignment, design, delivery, and adoption.

  4. 04

    Programmer Analyst

    National Cooperative Credit Union

    Built secure transaction services and pragmatic integrations that modernized infrastructure while protecting familiar branch and staff workflows.

  5. 05

    Trading enthusiast to QA lead

    Backtesting SaaS

    Turned hands-on trading knowledge into product judgment, then established triage, escalation, acceptance, regression, and cross-functional feedback practices.

  6. 06

    Project Manager

    Cross-functional teams

    Coordinated planning, risk, blockers, stakeholder communication, and delivery across software and business initiatives without losing sight of the user outcome.

  7. 07

    Product Manager

    Research, metrics, and prioritisation

    Combined user conversations, product evidence, incident learning, and trading-domain expertise to guide priorities and help teams make better product decisions.

  8. 08

    Consultant Solutions Engineer

    Discovery through reliable delivery

    Brings the full arc together: operational discovery, systems thinking, hands-on engineering, product judgment, quality, delivery, and knowledge transfer.

Breadth that makes discovery more useful.

The value is not having held many roles. It is knowing what each perspective reveals before a technical decision becomes expensive.

Translate the real need

Teaching and product work help stakeholders articulate needs they may not yet have language for.

See the connected system

Government and financial-sector engineering taught me to respect approvals, legacy tools, data, and operational continuity.

Carry quality through delivery

QA, project, and product leadership keep evidence, risk, acceptance, and handover present throughout the work.

Your problem does not need to fit one of my old job titles.

Bring the ambiguous system, workflow, or product decision. The career arc is useful because I can meet it from more than one angle.

Talk through the situation