Intermediate Software Development Engineer (DBN) at BETSoftware

You Bring:

• Languages - C#, Javascript, HTML (non- negotiable).
• Knowledge of Front end and Back End development.
• Front End - Understanding Javascript Frameworks.
• Understanding of API design requests and response cycles.
• Knowledge of creating database and managing information.
• Familiar with Rest API.
• Understanding of object orientated programming.
• Postman (advantageous).
• At least 3-5 years’ experience within a development environment is advantageous.
• 2-5 years database experience.
• 3-5 years server/client- side languages is advantageous.
• Good written and verbal communication skills.
• Strong attention to detail.

What You’ll Do:

Technical Outputs:

Perform Planning

• Identify and establish objectives for self and team.
• Work on objectives or goals within timeline.
• Consider all reasonable factors, impediments and obstacles.
• Identify potential alternative strategies and refactor approach for maximum benefit within the shortest possible time.

 Implementation - Ensure the Solution is Functionally Complete

• Deliver a solution which covers all the agreed specified tasks and user objectives.
• Deliver a correct solution which provides the correct results with the needed degree of precision.
• Ensure checked in code is reviewed to ensure standards are met.

Implementation – Ensure the Solution is Reliable

• Ensure the solution performs appropriately under agreed conditions for extended periods of time without the need for intervention (despite potential attacks).
• Ensure all steps are taken to reduce the occurrence of faults due to misunderstood requirements, design errors, and implementation errors.
• Ensure the solution is robust and remains continually available.
• Respond to outages and failures when and where needed.
• Improve fault tolerance even when operational conditions are not optimal.
   

Respond to Outages & Failures

• Provide proactive support to Peers, Testing, Dev Support and Operational teams so number of escalations to the development team is reduced, thereby maximising development time.
• Ensure the solution is durable so that as user volumes and requirements change the solution can evolve over the long term.
• Ensure the solution simplifies support and maintenance support through traceability, and effective error messaging.
• Ensure over time, the solution becomes more mature where the interval between the interventions remain operational, become less frequent.
• Ensure in the event of a failure reduce effective downtime is to the minimum possible.

Implementation – Ensure the Solution has Effective Security

• Ensure the solution is secure, and confidential by protecting all information and data (also data transmission).
• Ensure persons or other solutions have the degree of access appropriate to their level of authorisation and types.
• Ensure the solution has high integrity where the solution prevents unauthorised access to, modification of computer programs, data, or settings.
• Ensure the solution has a high degree of survivability despite third-Party interventions (attacks, human errors, hardware or software faults).
• Employ logs and records so that actions and events can be proven to have taken place and cannot be disputed/repudiated later.
• Ensure wherever possible actions can be traced uniquely to the entity which performed it.
• Ensure wherever possible the identify of an entity can be proved to be the correct one.

  Implementation - Ensure the Solution is Maintainable

• Ensure the solution and its relevant code base supports ease of modification for future maintainers.
• Ensure the use of appropriate standards and methods.
• Ensure where possible (without affecting performance/security) the solution catersformaintenance by support teams rather than developers.
• Ensure modularity where the solution consists of discrete components so that a change in one component has minimal impact on other components.
• Ensure relevant documentation is provided to support teams to reduce development support burden.
• Apply a strategy of reusability so an asset can be used in more than one solution or in building other assets.
• Where possible provide a mechanism for the solution to analyse its own faults and provide reports prior to a critical failure.
• Develop the solution in a manner which supports modification for future developers thereby reducing the numbers of defects or negatively affecting system quality.