Job Offers at Triax Technologies

Role Overview

• This is a leadership-and-architecture role. You are hiring judgement and the ability to carry other people, not just raw coding speed. The strongest individual contributor is not automatically the right lead, and conflating the two is one of the more common hiring mistakes.

Responsibilities

• Own the overall technical architecture across Triax's platforms, setting the standards and patterns the rest of the team builds against.
• Lead, mentor and grow the engineering and technician team, distributing work fairly and deliberately developing the people beneath them rather than hoarding the interesting problems.
• Take final responsibility for release management: deployment, staging, migrations, rollbacks, and the integrity of production at all times.
• Translate business and regulatory requirements into sound technical decisions, and translate technical realities back to leadership in plain language.
• Own the security and compliance posture of the systems, ensuring identity and financial data are handled to NAICOM and broader regulatory expectations.
• Design and safeguard integrations with external partners such as banks, DisCos and payment providers.
• Lead incident response when systems fail, restoring service calmly and conducting honest post-mortems that prevent recurrence.
• Set and uphold engineering discipline across code review, testing, documentation and secret management.

Requirements

• At least five to seven years of hands-on full-stack or systems experience, with a meaningful portion of it in a production environment where real users and real consequences were involved. Time spent only on prototypes or coursework does not count the same way.
• Demonstrable experience leading or coordinating a small technical team, even informally. Look for evidence they have mentored juniors, run a release, or owned a system end to end rather than just a feature.
• Solid architectural judgement: deciding where state lives, when to choose a relational store over something else, how to design an API that an external partner like a bank or a DisCo can safely consume, and how to keep a system maintainable as it grows.
• Non-negotiable security and regulatory awareness: secure handling of identity and financial data, audit logging, access control, and the understanding that the system must be able to answer a regulator's questions. Someone who has worked in a regulated environment before is worth a premium.
• A track record of safe deployment and incident handling: rollbacks, staging, careful database migrations, and a calm, communicative manner when something breaks at an inconvenient hour.
• Communication that matches the code. They will be translating between the engineers and the rest of Triax, including non-technical leadership, so explaining a trade-off in plain language is part of the job, not a soft extra.

Nice to Have

• Desirable criteria
• Prior fintech or insurtech experience, and familiarity with the Nigerian regulatory landscape, NAICOM in particular.
• Experience integrating with external systems such as bank KYC flows, payment rails, or utility billing infrastructure.
• A relevant degree or professional certification, though demonstrated work is weighted above paper.
• Exposure to cloud infrastructure, CI/CD, and managing secrets properly.
• Disposition and character
• Honesty under pressure, especially the instinct to disclose a problem rather than quietly paper over it.
• Self-awareness, including the ability to name a past mistake.
• The temperament to stay structured when things are on fire.
• A genuine willingness to grow the people under them rather than hoard the interesting work.

go to method of application »

Role Overview

• These roles are more about keeping things running, supporting users, and handling the day-to-day infrastructure than about building new systems. They are included separately because the criteria genuinely differ. Holding a technician to an engineer's standard, or the reverse, wastes everyone's time.

Responsibilities

• Provide first-line support to staff, resolving everyday hardware, software, connectivity and access issues promptly and patiently.
• Maintain and monitor day-to-day infrastructure, including devices, networks and basic system configuration.
• Manage user access requests within defined boundaries, respecting the seriousness of sensitive systems.
• Log, track and escalate issues that exceed their level, rather than tinkering blindly with things they do not fully understand.
• Perform routine maintenance and setup tasks dependably, from device provisioning to basic backups and checks.
• Support engineers and the team leader with operational tasks during deployments and incidents as needed.

Requirements

• A foundational understanding of IT systems: networking basics, operating systems, hardware, and common troubleshooting. One to two years of relevant experience, or strong evidence of practical aptitude even if the formal experience is light.
• The ability to diagnose and resolve everyday issues: connectivity, device problems, user access, basic system configuration, with a logical, patient approach to problems they have not seen before.
• Basic data-handling discipline. Even at this level they may touch systems holding sensitive information, so they need to understand access boundaries and the seriousness of customer data. This is where a lot of organisations get careless, and exactly where breaches start.
• Clear communication with non-technical staff, because much of the job is helping colleagues who are frustrated and not fluent in the jargon. Patience here is a real skill, not a nicety.

Nice to Have

• Desirable criteria
• Relevant certifications such as CompTIA, networking, or vendor-specific credentials.
• Some scripting ability for automating repetitive tasks.
• Familiarity with the kind of office and field environments Triax operates in.
• Disposition and character
• Dependable, willing to do the routine work without cutting corners.
• Honest about escalating things beyond their level rather than tinkering blindly.
• Steady with people who are having a bad tech day.

go to method of application »

Role Overview

• These are your builders. They need to be technically solid and trustworthy with sensitive systems, but they are not yet expected to carry a team or own the overall architecture.

Responsibilities

• Build, test and ship features across the stack to the standards and architecture set by the team leader.
• Write clean, secure, maintainable code, with particular care around financial transactions and customer data.
• Implement and maintain integrations with third-party APIs and external services.
• Participate actively in code review, both giving and receiving, and contribute to a culture of shared quality.
• Debug and resolve issues in existing systems methodically, fixing root causes rather than symptoms.
• Support deployments and respond to production issues within their area, escalating appropriately when something exceeds their scope.
• Keep reasonable documentation so that the systems they build can be understood and maintained by others.

Requirements

• Two to four years of practical development experience, with at least some of it on systems that went live and were used by real people. Comfortable across the stack, or clearly strong on one side with a working understanding of the other.
• Real competence in at least one back-end language and framework, plus front-end fundamentals: how the browser works, how state flows, and how to build an interface that holds up on a mid-range Android phone and a patchy connection, which is the reality for many of your users.
• Sound database fundamentals: transactions, why a half-completed financial operation is dangerous, and how to write queries that do not fall over under load or open the door to injection.
• A working grasp of web security: the common vulnerabilities and the standard defences. They should know passwords are hashed rather than reversibly encrypted, and understand why customer data deserves careful handling. Not a security specialist, but someone who will not introduce an obvious hole.
• A methodical debugging temperament. When something that worked yesterday fails today, they investigate before they guess, and they isolate the problem rather than thrashing.

Nice to Have

Desirable criteria

• Experience with APIs and third-party integrations.
• Exposure to version control discipline, testing, and code review.
• Some familiarity with deployment pipelines.
• Any prior fintech, insurtech, or regulated-data experience is a strong plus.
• Disposition and character
• Coachable, honest about what they do not know, and able to say "I'm not sure, but here's how I'd find out" instead of bluffing.
• Reliable on the unglamorous parts of the job, not just the interesting features