Ex­pe­ri­ence re­port Paul

Ju­ni­or Soft­ware Developer

Immedia­te­ly af­ter com­ple­ting my training as an IT spe­cia­list for ap­p­li­ca­ti­on de­ve­lo­p­ment, I was ac­cep­ted into a pro­ject team that de­ve­lo­ped an exis­ting soft­ware from scratch. The tran­si­ti­on was re­la­tively seam­less. Howe­ver, it took some time to get it up and run­ning, be­cau­se for the first time I was working 100 per­cent pro­duc­tively on the code. At the be­gin­ning, most dif­fi­cul­ties were in cor­rect­ly esti­ma­ting the ef­fort re­qui­red for a re­qui­re­ment and sche­du­ling the right time for im­ple­men­ta­ti­on ac­cord­in­gly. Howe­ver, this im­pro­ves as ex­pe­ri­ence in­cre­a­ses. In ad­di­ti­on, one has much more con­ta­ct with soft­ware pro­blems and er­rors, but one also ex­ch­an­ges in­for­ma­ti­on in­ten­si­ve­ly with col­leagues and learns fas­ter and faster.

Af­ter ano­t­her chan­ge to ano­t­her pro­ject, I now work con­ti­nuous­ly with de­ve­lo­pers from other coun­tries. This not only hel­ps you to im­pro­ve your Eng­lish skills –  you also get to know new per­spec­ti­ves on cer­tain ques­ti­ons. In the new pro­ject I am now working in the ba­ckend (ser­ver side) as well as in the front­end (cli­ent side).

Pro­duc­ti­ve work is de­man­ding, but abo­ve all it is also sti­mu­la­ting. Thanks to re­gu­lar mee­tings, you ex­chan­ge ide­as with col­leagues and also have a good con­nec­tion to each other. This is also whe­re the dif­fe­rent are­as of in­te­rest come tog­e­ther, which ma­ni­fests its­elf in an ex­ten­si­ve pool of in­for­ma­ti­on and ex­pe­ri­ence – from which you can draw tog­e­ther. The working at­mo­s­phe­re is a va­ried mix­tu­re of hu­mour and pro­fes­sio­nal se­rious­ness – with a hint of ga­ming jar­gon – and the­re­fo­re very pleasant.


More ex­pe­ri­ence reports

Ju­ni­or Soft­ware Developer

Ju­ni­or Data In­te­gra­ti­on Specialist

Re­se­arch Engineer

Close Menu