C# / WPF / WCF / Winform Developer

London
9 months ago
Applications closed

Related Jobs

View all jobs

Full Stack Developer - C#.Net, React, SQL - Kent / Sussex

Senior/Lead Data Engineer

Data Engineer

Data Engineering Product Owner, Technology, Data Bricks, Microsoft

Senior SQL Developer

Data Engineer

Global bank based in Canary Wharf.

Role - C# / WPF / WCF / Winform Developer

Duration - 6 months with likely extension

Rate - £400 p/d (inside IR35)

Location - Remote / Canary Wharf

Tech Stack

C#
WPF
Winforms
SQL
OracleTasks

Tasks range from understanding business requirements, designing application structures, business data analysis, programming WPF (Windows Presentation Foundation) applications in Visual C#.NET on both Oracle and SQL Server database, testing with users, implementation through Development, Quality Assurance (QA), Production and Disaster Recovery environments. Supporting users and writing operation documents including User Helps (manuals) will also be required.
As well as application development, this role will also include all aspects of system constructions and support for existing programmes which are written as WinForms (C#.NET) applications. Also, applications written in other languages like MS VBA for Excel and Access, MS VB and MS Excel Macros will also be required.

Additional Tasks

Defining Database objects required in systems to connect with SQL and Oracle Database Administrators in both London and New York.
Providing script for database inquiry languages, i.e., T-SQL (SQL Server) and PL/SQL (Oracle) to perform data analysis based on requirements from business parties.
Setting up a system distribution method to Citrix and application servers for both Web and Window applications.
Troubleshooting systems in an event of failure and implementing necessary solutions by checking Windows Operating System, Internet Information Server and any other relevant environments where the JRIE applications are running. In some case this role will act to liaise with other application support team staff.
Following the existing team programming policy to keep a common development style to be shared in team members.
Updating versions of MS .Net Framework and MS Visual .NET platform to include any necessary changes of existing systems running in Production.
Liaising with the relevant support teams such as other Development sections, Technical Support, Network and Infrastructure and DBA where Business users experience system problems.
Assessing the impact of data processing loads on SQL and Oracle database and, when appropriate, finding alternative approaches.
Rolling out changes with a coordination of Release manager. It is important to maintain the change history of applicationsGCS is acting as an Employment Business in relation to this vacancy

Subscribe to Future Tech Insights for the latest jobs & insights, direct to your inbox.

By subscribing, you agree to our privacy policy and terms of service.

Industry Insights

Discover insightful articles, industry insights, expert tips, and curated resources.

How Many Data Engineering Tools Do You Need to Know to Get a Data Engineering Job?

If you’re aiming for a career in data engineering, it can feel like you’re staring at a never-ending list of tools and technologies — SQL, Python, Spark, Kafka, Airflow, dbt, Snowflake, Redshift, Terraform, Kubernetes, and the list goes on. Scroll job boards and LinkedIn, and it’s easy to conclude that unless you have experience with every modern tool in the data stack, you won’t even get a callback. Here’s the honest truth most data engineering hiring managers will quietly agree with: 👉 They don’t hire you because you know every tool — they hire you because you can solve real data problems with the tools you know. Tools matter. But only in service of outcomes. Jobs are won by candidates who know why a technology is used, when to use it, and how to explain their decisions. So how many data engineering tools do you actually need to know to get a job? For most job seekers, the answer is far fewer than you think — but you do need them in the right combination and order. This article breaks down what employers really expect, which tools are core, which are role-specific, and how to focus your learning so you look capable and employable rather than overwhelmed.

What Hiring Managers Look for First in Data Engineering Job Applications (UK Guide)

If you’re applying for data engineering jobs in the UK, the first thing to understand is this: Hiring managers don’t read every word of your CV. They scan it. They look for signals of relevance, credibility, delivery and collaboration — and if they don’t see the right signals quickly, your application may never get a second look. In data engineering, hiring managers are especially focused on whether you can build and operate reliable, scalable data systems, handle real-world data challenges and work effectively with analytics, BI, data science and engineering teams. This guide breaks down exactly what they look at first in your application — and how to shape your CV, portfolio and cover letter so you stand out.

The Skills Gap in Data Engineering Jobs: What Universities Aren’t Teaching

Data engineering has quietly become one of the most critical roles in the modern technology stack. While data science and AI often receive the spotlight, data engineers are the professionals who design, build and maintain the systems that make data usable at scale. Across the UK, demand for data engineers continues to rise. Organisations in finance, retail, healthcare, government, media and technology all report difficulty hiring candidates with the right skills. Salaries remain strong, and experienced professionals are in short supply. Yet despite this demand, many graduates with degrees in computer science, data science or related disciplines struggle to secure data engineering roles. The reason is not academic ability. It is a persistent skills gap between university education and real-world data engineering work. This article explores that gap in depth: what universities teach well, what they consistently miss, why the gap exists, what employers actually want, and how jobseekers can bridge the divide to build successful careers in data engineering.