IT Engineer (Mid-Level Developer)

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

Application Closing Date
Not Specified. 

Method of Application
Interested and qualified candidates should:

Share this job: