Experience

• 

  Solidium bv

  Feb 2000 - Jan 2001

  Software engineer / designer

  At Solidium BV I finished my school trainee ship and after this I became an employee of Solidium.During my school trainee ship I developed an automated course administration system from the analyse phase to the test phase followed by a presentation.The software development was done in Cool:Gen and therefore I followed the Fast Track Cool:Gen course which was given by Solidium itself.After my trainee ship I did some Functional design work for the company Vopak (company which stores large amounts of several chemical products).I also coached pupils in their traineeship by giving the fast Track Cool:Gen course. Minder weergeven

• 

  Ohra

  Jan 2001 - Jan 2003

  Software engineer / consultant

  Via software house Logica-CMG I worked for 2 years at Ohra in Arnhem as a software engineer.Ohra is an insurance company and a bank.I worked at the medical insurance department on a project called Tosca.Tosca is a automated claim processing system.The programming language was Object Star on IBM Mainframe.Programming was based on Technical and Functional design which was made in corporation with super users.Activities contained developing new as existing software and solving errors from the different test or production environments.I also participated in the Euro conversion project where Cobol was the programming language. Minder weergeven

• 

  Logica

  Jan 2001 - Jan 2003

  Software engineer / consultant
• 

  Belastingdienst bcict

  Jan 2003 - Dec 2007

  Cobol developer / software engineer

  Cobol Software Developer on IBM Mainframe at project ABS.The project ABS (Aangifte Belasting Systeem: Tax assessment and return ) is a large and complex environment which handles all kinds of tax handling of private persons and concerns. The whole project consisted of 150 employees, varying from designers, developers and testers.ABS has a lot of interfaces with other systems.The last 2.5 years I combined the role of software engineer with Team leadership of the Cobol team. The team consisted of 5 developers.In role of team leader I was responsible for making the planning/estimates and was monitoring the progress of the development of the workload. I was the linking pin between the Cobol team and the ‘world around it’. I was responsible for the delivery to the next phase and so on. All the input and output from the team had to came threw me.As a teamleader I reported twice a week to the project manager and was chairman of the team meeting that took place once a week. Minder weergeven

• 

  Ecoser-it

  Dec 2007 - Jan 2009

  Software engineer
• 

  Ing

  Dec 2007 - Jan 2009

  Software engineer

  Because of the integration of Postbank and ING the systems of Postbank needed a conversion because Postbank uses 7-digit account numbers while ING uses 10-digit.Postbank systems and programs were converted in such a way, that these systems also can handle 10-digit account numbers. The systems were part of the department Payments, which contains all the flows of payment.The software also had to be converted from a 3-office system into a single-office system.The software development was on an IBM mainframe in Cobol based on a technical design and TCS (Technical Consequence Study)Roles: Reviewer Technical designer Programmer Test supportingActivities: Reviewer:Review of Technical Consequence Studies (TCS).This document described the technical impact of a planned change.Review of technical designs.Review of changed Cobol programs or JCL developed by colleagues.With these reviews came a review document which contained findings. Technical designer:Writing a technical design based on a TCS. This technical design is stored in the version control tool Rochade.This tool can generate a Word document based on the contents. Programmer:Developing new and changing existing programs based on a technical design. Besides that, also JCL had to be developed.There were two types of JCL, a so-called ‘Good run’ JCL and a JCL with all the errors that could occur.The programs were developed and managed via Endevor. Test support:After a unit test the software is placed into the next state where a testgroup is testing all different pieces of programs together in a chain.These testers are supported when problems are encountered. Minder weergeven

• 

  Obtain

  Nov 2009 - Jan 2012

  Software ontwikkelaar
• 

  Kadaster

  Nov 2009 - Feb 2012

  Software engineer

  Working as a Cobol software engineer for Kadaster via Obtain Data Management.Roles:- Cobol Software Engineer- Technical Team coordination- Test supporting

• 

  Ecoser-it

  Feb 2012 - Jan 2019

  Software engineer / tester
• 

  Ing

  Feb 2012 - Jan 2019

  Software engineer / tester via ecoser-it
• 

  Ministerie van financiën

  Jan 2019 - now

  Senior medewerker informatievoorziening