Gabriel Favu

SW tester & Lead at iQuest Group
  • Claim this Profile
Contact Information
us****@****om
(386) 825-5501
Location
Cluj, Romania, RO
Languages
  • English Full professional proficiency
  • German Limited working proficiency
  • French Elementary proficiency

Topline Score

Topline score feature will be out soon.

Bio

Generated by
Topline AI

5.0

/5.0
/ Based on 1 ratings
  • (1)
  • (0)
  • (0)
  • (0)
  • (0)

Filter reviews by:

Iulian Matei

Gabriel's passion for testing can be recognized in his style of work. He is extremely dedicated to his duties, and effective in finding bugs. He has also the experience to cope with pressure and works well even in time limited periods.

You need to have a working account to view this content.
You need to have a working account to view this content.

Credentials

  • ISTQB foundation
    SEETB Examination board
    Nov, 2012
    - Nov, 2024

Experience

    • Germany
    • Software Development
    • 100 - 200 Employee
    • SW tester & Lead
      • Jul 2015 - Present

      At iQuest I'm involved in: - web-telecom hybris - interface modules: * card/sim * medical At iQuest I'm involved in: - web-telecom hybris - interface modules: * card/sim * medical

    • Ireland
    • Business Consulting and Services
    • 700 & Above Employee
    • SW tester & Lead
      • May 2014 - Jul 2015

      Accenture acquired Evoline in 2014. All activities continued unhindered. Starting 2014 I was responsible for both verification and validation. I was part of the Siemens team responsible for TUV assessment for both verification and validation. Accenture acquired Evoline in 2014. All activities continued unhindered. Starting 2014 I was responsible for both verification and validation. I was part of the Siemens team responsible for TUV assessment for both verification and validation.

    • Romania
    • IT Services and IT Consulting
    • 700 & Above Employee
    • SW tester & Lead
      • May 2013 - May 2014

      At Evoline I was involved with test-related activities (verification) for railway (Siemens): - build up and update the test environment at component level; - design and implement test-cases; - collaborate with the project team outside Romania; - test execution at component and sub-system level using in-house tools. Clear Case is used as test repository. Visual Studio is used for test implementation and execution. I was part of the Siemens team responsible for TUV assessment for the verification: - documentation - TUV presentation and demonstration Show less

    • Germany
    • Motor Vehicle Manufacturing
    • 700 & Above Employee
    • System Test Engineer
      • Mar 2010 - Apr 2013

      At Continental I was involved in testing automotive functions for BMW cars: - responsible on REM power-windows (expert), power management, window wiper, coding and flashing (~2.5 yrs); - responsible on BDC terminal control after REM fade-out. Daily activities: - providing support for fellow colleagues (testers, developers, hardware) - work with BMW tools for diagnose testing / flashing the ECU / coding the ECU - running manual / automated tests - updating manual / automated tests (based on new / changed requirements and tracked defects) * Doors is used as test repository - automate the existing manual tests (if the functionality allows it) - adding new manual / automated tests (based on new / changed requirements) - validating new SW versions - support for client's requests Extra: - "on site" testing session for twain appraisal at BMW Center in Munich Show less

    • India
    • IT Services and IT Consulting
    • 1 - 100 Employee
    • QA TL Romania
      • Dec 2006 - Jan 2010

      I created the QA team and managed it - a team of 6 testers for 1 year in the beginning. After the group was stable, I split it in 2 teams of 3 testers + TL in order to have a more flexible structure. The testing activity was black box testing on a large scale web application. Tools used: VS TFS, SQL. Duties: - training: *the new team members *on application system for the entire team (when needed) - planning: *new versions *maintenance for the production version - method: *project plan for new versions (it consists of the actual work-plan and the necessary time, also discussing it on higher management level as well as with the developers TL for a better integration of the QA team in the work flow) *maintenance for the production version: HF + SP - execution: *test plan writing *test plan execution by the adopted strategy (depending of the conditions existing in the execution phase changes in/of strategies appear) *performing maintenance **post-production (HF) **post-stabilization (SP) Show less

    • Israel
    • Software Development
    • 200 - 300 Employee
    • Q.A. TL
      • Dec 2006 - Jan 2010

      Q.A. Romania responsable. Q.A. Romania responsable.

  • Fluid Group Hagen
    • Iasi County, Romania
    • Repartition Manager
      • Oct 2005 - Dec 2006

      Managed field teams and office teams. Here I learned about customer care and business to customer relations. Managed field teams and office teams. Here I learned about customer care and business to customer relations.

Education

  • Universitatea Tehnică „Gh. Asachi” din Iași
    Master, Measurements and signal processing
    2005 - 2006
  • Universitatea Tehnică „Gh. Asachi” din Iași
    Electrical Engineer, Electrotechnics
    2000 - 2005
  • Universitatea 'Mihail Kogalniceanu' Iasi
    Law
    1998 - 2000

Community

You need to have a working account to view this content. Click here to join now