A requirement to send information to and receive information from a third party company. There was no specification in my
company regarding what this should look like and very basic (and somewhat inaccurate) documentation as to the third party’s systems.
Additionally there was no UI specified for colleagues in my company to view or action the information returned from the third party.
Create a command line application to send information to the third party – plus I identified that the information returned was useless
to my colleagues in the business without UI for viewing and taking action on the returned information.
The information was originally to be sent to an API but it was discovered at the last moment that the API was not production ready
so I rewrote the code to send the information in .CSV files via ftp.
As there was no mention of any UI I identified a need for same and wrote a Blazor application enabling the business to view the returned
information and to take action to resend the files which had not been processed (and therefore returned as ‘failed’) to the third party.
I successfully created a command line application that sent information to and received information from the third party.
I created a Blazor application to display the results of the send and receive actions and allow colleagues in the business to
take required actions.
As I was the only person in the company with Blazor experience I mentored colleagues in the use of this technology and helped
by means of demonstrations and paired / tripled programming tuition to upskill them.
A requirement was raised to add some UI to an existing application to assist with compliance with the Consumer Duty regulations
from the Financial Conduct Authority (FCA) to manage and report on Vulnerable Clients. The request was originally to add one checkbox and one textbox to a current application.
The current application uses very old technology and is very hard to work with.
Read up on the FCA’s Consumer Duty requirements to familiarise myself with them.
Doing so made me realise that the UI requested was utterly inadequate for the recording of vulnerabilities in line with the
FCA’s requirements so I asked my boss for permission to prototype an application which would provide the necessary functionality. This was given.
Liaise with the business – specifically the Compliance team – further to gather requirements and to understand how this was currently
being managed in their team.
It transpired that they were using a spreadsheet to record this information but, as good as this spreadsheet was, it was not entirely
fit for purpose. In addition to this it is obviously not ideal to have to try to produce reports from a spreadsheet.
Design and build an application which would meet or exceed their requirements.
Further mentor and upskill colleagues in the use of Blazor / .Net Core.
I designed and built this Blazor application with little external input apart from encouragement
and constructive comments from the business as to the functionality that was required.
I delivered this application and the stakeholders in the business were pleased and impressed with the result.
I further mentored and upskilled those colleagues who were interested in the project.
Design a form for the web site which will allow potential candidates speculatively to upload their CV
for consideration for future roles.
Create a form with the facility to upload CVs and specify which types of jobs are of interest.
Save the applicant's details to the database, upload the CV attachment and email it to HR.
Create a console application to query the HR database for new jobs posted, check the job category against an applicant's specified categories of interest and send an email (with an 'unsubscribe'
option) to a candidate where there is a match. Create an executable for this code.
Success - a Scheduled Task was created to run the executable, thereby sending the emails.
Company CRM data needs cleaning as records are very out of date.
Design an application to send a templated email to all clients in the database asking them to log in and update their details.
The client can either confirm that their details are correct, update the details or remove the details from the database.
Send an email containing a link to a website where the client's information is retrieved from the database (removing the client's ID from the querystring
to prevent anyone from trying to access any other account details).
Record dates and times of visits and updates to enable a follow-up request to those who have either not visited the site or visited the site but didn't update their details.
Success - outstanding response with hundreds of client details being updated.