|
Title: Μεταπτυχιακό, Διδακτορικό ή PDEng ? Post by: ^^DaRk_HunTeR on March 01, 2015, 21:04:38 pm (Updated 3TU became 4TU) Λοιπόν, ανοίγω αυτό το τοπικ περισσότερο για να με αναγκάσω στο άμεσο μέλλον να αφιερώσω περισσότερο χρόνο στην παρουσίαση αυτού του κυρίως Ολλανδικού ιδιότυπου φαινομένου που ονομάζεται PDEng = Post - M.Sc.
Ένας συνασπισμός Πανεπιστημίων φέρνει αυτήν την "καινοτομία", 4TU: four universities (of technology) in the Netherlands are jointly committed to strengthening and pooling technical knowledge.
- Υπάρχουν πολλά παιδιά απο το τμήμα μας (και συναφή) σε αυτά τα προγράμματα αλλά για κάποιο λόγο όπως και σε πολλά άλλα θέματα κανείς δεν μπαίνει στον κόπο να τα αναλύσει... (sharing is caring) - Ενδιαφέρουσα πληροφορία αποτελεί το γεγονός ότι τα περισσότερα παιδιά που έρχονται εδώ απο όλο τον κόσμο έχουν 2-3 χρόνια εργασιακή εμπειρία στο αντικείμενο, δεν έρχονται απευθείας απο το Πανεπιστήμιο!- Η μεγαλύτερη ιδιομορφία του είναι ότι βασίζεται σε projects και όχι σε courses και ότι είναι industry oriented. Αυτό για να πάρετε μια ιδέα σε τι διαφέρει απο το κλασσικό M.Sc., από ένα Ph.D και απο ένα Internship. Κάθε PDEng έχει τις δικές του ιδιαιτερότητες και το δικό του "πρόγραμμα σπουδών" οπότε δεν μπορώ να πω πολλά για τα άλλα παρά για αυτό που ξέρω. PDEng programs Are you a young professional graduate or currently completing your Master's at a university of technology? Are you interested in technological design, and would you like to increase your opportunities on the employment market? Are you specifically looking for a career in industry or business? Then the two-year post-Master's PDEng programs focusing on technological design at TU/e may well be what you're looking for! What does a PDEng program involve? The PDEng programs are two-year salaried programs in the field of technological design. After gaining your Master's degree in a technological field and a stringent selection process, you can do PDEng program. The programs lead to a Professional Doctorate in Engineering degree. During your program you will increase your technological knowledge, but you also learn how to apply it in practice. As well as that you work on your professional skills to increase your career opportunities. Like a doctoral candidate, you will have the status of a TU/e employee. That means you will receive a salary and have excellent secondary conditions of employment.
Ο σκοπός μου είναι να κάνω μια αναλυτική παρουσίαση των προγραμμάτων και δη του δικού μου προγράμματος για να βοηθήσω ανθρώπους που θα θέλαν να κάνουν το βήμα προς τα εδώ. P.S.: Υπάρχει αρκετό ενδιαφέρον απο τους υπεύθυνους για τη σχολή μας. Για να μιλάμε με αριθμούς σε δύο PDEngs που γνωρίζω απο πρώτο χέρι: automotive-systems-design + software-technology στο TU/e Απο τα συνολικά 32 άτομα 6 είναι Έλληνες εκ των οποίων 3 απο το ΑΠΘ. Στο παρελθόν έχουν γίνει κάποιες live παρουσιάσεις στο τμήμα και κάποιες νύξεις (από τότε βέβαια έχουν αλλάξει πολλά): https://www.thmmy.gr/smf/index.php?topic=5343.0 https://www.thmmy.gr/smf/index.php?topic=6090.0 To be continued! Title: Re: Μεταπτυχιακό, Διδακτορικό ή PDEng ? Post by: ^^DaRk_HunTeR on March 01, 2015, 22:33:43 pm (Updated)General (Programs' Background)
Society in general and industry in particular are faced with rapid developments that pose tremendous challenges. From a technical point of view we observe that systems (e.g., consumer products) are becoming more and more complex. We also see that they are becoming increasingly more interconnected. From a business point of view, we are not only confronted with increasingly competitive markets, shorter time-to-market, and shrinking resources, but we are also more and more faced with multi-disciplinary products, international multi-site projects, and large-scale project teams with people from various national and professional cultures. In the early 1980's, the Dutch industry indicated a strong need for universities to educate and train motivated and talented people in such a way that they would not only have a strong academic background, but also excellent social and communicative competencies, strong technical leadership competencies, and strong project management competencies. Industry needed professionals who were immediately deployable in the various companies. Consequently, the technology-oriented universities in the Netherlands set up a number of post-graduate education and training programs for motivated and talented university graduates who had already successfully completed their M.Sc. studies. Currently, there are seventeen of these post-graduate (post-M.Sc., doctoral) programs operational in the Netherlands and several more in preparation. In contrast to the situation with regular B.Sc. and M.Sc. programs, people cannot simply register or enroll in these programs, but they need to apply for admission. Only after a strong selection process are a small number of candidates actually allowed to participate in these programs. To emphasize the importance and relevance of these programs for Dutch industry, the fellows are salaried employees of the respective universities. Upon successfully completing the program, they are awarded a Professional Doctorate in Engineering (PDEng) degree, emphasizing the fact that they have outstanding qualifications after finishing their education and training program. Formalities
+ First Travel Expenses (airtickets, trains, taxis, buses,etc.) + Moving Expenses (furniture etc) + Relocation Bonus (~1500 euros) + Laptop Title: Re: Μεταπτυχιακό, Διδακτορικό ή PDEng ? Post by: ^^DaRk_HunTeR on April 18, 2015, 16:18:43 pm Software Technology (20+ positions)
In the context of the post-graduate (post-M.Sc.) Software Technology program of the Stan Ackermans Institute, we prepare our trainees to work in large-scale industrial projects related to the design and development of software for resource-constrained, software-intensive systems (e.g., real-time, embedded or networked systems). In addition, we prepare them to cope with the developments and challenges in industry. During our intensive and immersive education and training program, we confront our trainees with authentic situations under real-life circumstances and corresponding uncertainties and challenges. During the last nine months of our program our trainees are out-placed at a company to participate in a relevant project to get on-site experience and provide an added-value to that project in terms of a transfer of state-of-the-art methods and techniques, tools, best-practices, and other relevant competencies, including knowledge. Thus, our trainees are given ample opportunities to improve their competitive competencies for a future career as a senior software designer or software architect in an international setting in the context of companies, such as Philips, TNO, ASML, Océ, NXP or CERN. Engineer, Designer, or Architect? In order to position the program, we shortly describe our nomenclature for the various functions in industry. The entry level for the program is that of Software Engineer. A software engineer can handle all phases of the software development life cycle, from problem description and requirements to deployment, as an independent professional. A software engineer typically will work on software projects with a complexity that one person can handle independently within a year or less. When he or she is a member of a team the software engineer typically is responsible for a well specified task or module. Because of the coverage of most of the phases of the software development life cycle, this function clearly exceeds that of a programmer whose activities are mostly limited to the creation and maintenance of code. The next major level of software professional is that of Designer. A software designer exceeds the level of an experienced software engineer by the capacity to deal with more complicated problems. In addition to possessing more advanced problem solving skills, a designer typically deals with problems with a size that require a team to realize a solution within a limited amount of time. The designer is responsible for developing the concept for the solution of the problem and then decomposing the problem into smaller problems that can be handled by the software engineers in the team. The designer then needs to provide the technical leadership to the team such that the integrity of the concept is safeguarded and the solutions to the sub-problems can be integrated into an overall solution for the initial problem. A software development team will be composed of specialists from various areas of software technology. The problem typically is concerned with a one-of-a-kind or first-of-a-kind software product. When the complexity of the product increases still further, because the product has to be realized in a number of subsequent versions or in several variations such that a product family emerges, a professional at the level of Architect is needed. An architect is concerned with products that have a longer lifetime, are realized in stages, and have a strategic value for a company. Architects are often involved in the creation of the company product roadmap, and as such have to coordinate the work of the various teams working on different versions or variations of a product. Software architects are concerned with software products; system architects are responsible for products requiring multidisciplinary expertise. Program Goals The ST program has been set up to take young software engineers to the level of software designers. The entry level of the program is that of a junior software engineer, who should meet the following requirements:
Upon successful completion of the Software Technology program, in line with our definition of the designer function, a graduate should (the labels below are introduced for further reference): E1. Have a sound background in, knowledge of, and experience in using state-of-the-art methods and techniques for design, development, and implementation of software for resource constrained software-intensive systems. In particular he or she should have genuine experience in the full design and development life-cycle including a. articulation of the problem (stakeholder analysis, use case modeling), b. analysis of the problem (requirements), c. modeling the problem (abstract, formal, conceptual), d. refinement of the solution (architecture, global design, detailed design, implementation), e. taking emerging and possibly conflicting constraints into consideration, f. integrating parts of a solution, g. verification and validation of the solution E2. Be aware of and have experience in using various state-of-the-art methods and techniques for managing and controlling software design and development projects. E3. Be aware of relevant industry best-practices in the context of business developments where products are becoming more multidisciplinary, increasingly complex, and increasingly interconnected and distributed; where markets are becoming increasingly competitive with an ever shorter time-to-market; and where projects are becoming larger, increasingly multidisciplinary, and multi-site. E4. Have a scientific approach to design. A graduate should be capable of systematically exploring the available design options and be proficient in motivating the appropriateness of the particular design choices made for the context they apply to. E5. Be able to take a leading role in solving multidisciplinary problems and have the competencies to effectively and efficiently cooperate in various roles in an international and multidisciplinary project-oriented environment. a. Effectively participate in a team in the design and development of complex, innovative products from a computer science background. b. Collaborate with engineers from other disciplines for the realization of the aforementioned products. c. Technically lead a team of software engineers and designers from a computer science background. This results in a number of competitive advantages for a career in the design and development of software for the high-tech, resource-constrained, software-intensive systems in Dutch industry. Program Elements In order to foster the abilities mentioned above, several ingredients have to be present in the program. Our training program consists of a number of strongly related courses (trainings) and projects that focus on the various aspects related to
In the context of the first category, our training program includes training primarily related to the early phases of design, such as usage modeling, requirements engineering, system, software, and hardware architecture, object-oriented analysis and modeling, and some training related to relevant domain specific knowledge, such as real-time scheduling, language technology, system validation and concepts of distributed systems. In the context of the second category, our training program includes short trainings primarily related to controlling the design and development process, such as project management, configuration management, quality assurance, and quality control. In the context of the third category, our training program includes a personal professional development program, including assessments, short awareness trainings, and reflection sessions to develop a learning attitude, related to the relevant non-technical competencies necessary for effective and efficient communication and behavior, such as presentation techniques, meeting techniques, designer competencies, teamwork, discussion techniques, decision making techniques, and leadership techniques. The program covers sustainable competencies such as the various relevant aspects of systems architecting and software design, including technical aspects, business and management aspects, and professional development aspects. It also covers topics that add domain knowledge that is required for the projects (see below). This course and workshop-oriented training is supplemented with several other elements such as excursions to (dubbed TIXX events: Thematic Industry eXperience eXchange) and seminars from industry partners and alumni. These activities help to acquaint the trainees with the role of software in the high tech industries and to give them a view on the state of the art in the industrial application of new software methods and technologies in practice. The training program provides the theoretical background, supported by small exercises, for end terms E1 through E5. The practical foundation for the end terms E1 through E5 is laid in the project part. Our program also includes two kinds of projects, each with a different focus. The first kind of project is the in-house project. These are short (6 – 11 week) projects in which all trainees work together to solve an authentic problem from an industry partner. Each project involves a new problem and technology domain. These projects are meant to provide an environment for the trainees to learn to work in a team and experience the different kinds of roles, structures, and communication needed to make a team successful. They also serve to let the trainees experience working with a real customer, dealing with real timing constraints, and other realistic projects, such as ill-defined problems, incomplete information, and multidisciplinary teams. The multidisciplinary character arises naturally by the choice of industry problems from different problem domains in which the software problems are situated in a mechanical, electrical, physics or business context. During the second project, the trainees are out-placed for nine months to one of our industry partners to participate in an authentic, operational on-site project. This arrangement provides a real-life situation in the sense that trainees are working as an employee on an operational project in industry. During such a project the trainee has to start and manage a process to get from ill-defined wishes and needs to concrete results. These projects are usually related to a feasibility analysis, a proof-of-concept, or first-of-a-kind development. This project is basically the concluding proof-of-ability. Table 1 summarizes the link between the program elements and the end terms they contribute to mostly. Please note that some elements contribute to the theoretical background, whereas others contribute to the practical experience (http://i61.tinypic.com/211npxh.jpg) Software Technology Program Structure The program elements, described in the previous section have to be placed in a balanced structure to make sure they are effective and coherent. This is done by dividing the two year training period into five in-house periods of roughly three months and one on-site period of nine months (see Figure 1). (http://i58.tinypic.com/2w1sdhx.jpg) As indicated, the core elements of the in-house periods are intensive training periods during which the relevant sustainable competencies are covered (by deepening, broadening, or reinforcing) and project periods during which teams of trainees are working (in a competitive, comparative, or collaborative fashion) on the design and development of software for a specific problem domain using a given technology domain. The training period precedes the project period. Not being like a conventional M.Sc. the curriculum is not structured with ECTS but based on the needs of the program and the trainees. Instead of a curriculum the distribution of the hours for the Class of 2010 is presented in the following table: (http://i58.tinypic.com/14d3ns7.jpg) In addition to the scheduled courses and trainings mentioned above, 376 hours (non-native speakers spend 80 of these on Dutch conversation skills) is available for activities such as introductions, tests, homework, and portfolio work. A certificate of level B1 is given to all candidates upon successful completion of the 2-year Dutch course. In-house projects C-2009 1. ViNotion: Camera control with Geo-referencing. Cameras have a reference system of their own. When several cameras need to work together, a world model is needed as well as a mapping for each local reference system to the world model. Support for such a world model makes it possible for a static camera to spot an “intruder” and pass on the position of the intruder to another non-static camera that can then take over the surveillance of the intruder and track him. 2. TechUnited: TURTLE Vision simulator. The adaptation of the software in a Turtle soccer robot is time-intensive. A robot simulator makes it possible to try out the software and refine it before it is deployed to the robot. One of the software components in a robot is responsible for the robot vision. A vision system simulator would need to be able to given a situation on the field during the soccer game – generate a video stream such as would be produced by the robot camera and use this to test the robot vision component. 3. EE: PreMaDoNa Tool Chain design flow The PreMaDoNa toolset automates large portions of the effort needed to transform a PC application into an application that can run on embedded hardware, such as an FPGA. The transformation consists of steps in which the application is partitioned, the hardware platform is specified, and the allocation choices are determined. 4. ASML: System SD group Model Driven Development One of the components of the ASML System software is the TX engine that plans, schedules, and dispatches the tasks that are needed for the control of the mechanical parts. The software for the control application is generated for each mechanical component based on a domain-specific language, named TReCS. The engine is being redesigned in this project in conjunction with a redesign of the DSL to incorporate data dependencies. Title: Re: Μεταπτυχιακό, Διδακτορικό ή PDEng ? Post by: ^^DaRk_HunTeR on May 31, 2015, 02:52:19 am The post-master (PDEng) program Automotive Systems Design (ASD) was started in 2011 and is part of the Graduate Program Automotive Systems of the Graduate School of Eindhoven University of Technology (TU/e). It is part of the unique cross-disciplinary automotive learning line at TU/e that consists of the Bachelor program Automotive, the Master program Automotive Technology, the ASD PDEng program and the PhD students involved in Automotive. The model for the ASD program was based on the successful Software Technology PDEng program. In the context of this ASD program of the Stan Ackermans Institute, we prepare our trainees to work in large-scale industrial projects related to the effective and efficient design and development of technologies and applications for modern high-tech automotive systems. In particular there is a focus on the multidisciplinary design aspects of project-based research and engineering in high-tech automotive systems, reflected in the key contributions by five TU/e departments. In addition, we prepare them to cope with the developments and challenges in industry. During our intensive and immersive education and training program, we confront our trainees with authentic situations under real-life circumstances and corresponding uncertainties and challenges. During the last nine months of our program our trainees are out-placed at a company to participate in a relevant project to get on-site experience and provide an added-value to that project in terms of a transfer of state-of-the-art methods and techniques, tools, best-practices, and other relevant competencies, including knowledge. Thus, our trainees are given ample opportunities to improve their competitive competencies for a future career as a senior designer or system architect in an international setting in the context of companies, such as DAF Trucks, Bosch Transmission Technologies or NXP Semiconductors. Program Goals The ASD program has been set up to take young engineers to the level of (automotive) designers with the final goal to provide a basis for faster development towards the level of System Architect. The entry level of the program is that of a junior engineer, who should meet the following requirements: -- M.Sc. in o Mechanical Engineering o Electrical Engineering o Automotive engineering o Computer Science and Engineering, o Systems and Control, o Industrial Design, o or a related discipline, with the requirement that the total program (bachelor + master or equivalent) encompasses at least 5 years or an equivalent of 300 ECs. Furthermore the study program should contain a sound theoretical basis in one of the major engineering disciplines (mechanical and/or electrical engineering). In exceptional circumstances also candidates with a degree from a polytechnic program and at least 4 years of relevant working experience can be admitted. Selection Procedure The program has a structure, in which all trainees follow the same courses, workshops and participate as teams in the so-called in-house projects. As a result of this, there is only one inflow moment annually, around the 1st of October. The program announces the application procedure annually by various means, such as extensive mailings to major universities around the world, based on contacts from associated scientific personnel, active trainees and alumni. Next to that both the Stan Ackermans Institute and the 3TU organization are active in various PR activities around the world to promote the PDEng programs. The application procedure is open from January till the end of June (or July). Applications are usually performed through the website of the program and are subsequently followed up by the ASD secretariat to make sure that all required documents are obtained. In this process part of the applicants, that clearly do not fulfill the requirements are notified that they are not eligible. The remaining dossiers are subsequently first evaluated by the program coordinator. In this process again part of the applications is denounced. The remaining applications are sent out to members of the steering committee, for a next evaluation. If this leads to a semi-positive result, the candidate is invited for an interview, which can be in person or – in most cases- by means of Skype. This interview can be with the program coordinator or a member of the steering committee. Based on the report on the interview and in many cases also on the graduation thesis report (as well as grades, English proficiency etc.), the application is rated in one of the following categories: 1. Absolute Positive 2. Positive 3. Possible 4. Reject Around the beginning of June, based on the number trainees that can be admitted according to the business model and agreements with the University and the department, the candidates are chosen from the first 3 categories mentioned above, with the obvious ordering. In case of doubts, the scientific director and the program manager create a preference list. Next to the above described procedure, the management also evaluates the background of the candidates, in order to assure a sufficiently balanced mix (i.e. mechanical, electrical, embedded systems etc.). Furthermore the management keeps a preference list of possible candidates in case one of the chosen candidates choses to decline. The official procedure for hiring and the connected procedures for visa, work permits, arrangements for housing etc. are taken care of by the HR section of the department. Program Structure The program elements, described in the previous section (excluded) have to be placed in a balanced structure to make sure they are effective and coherent. This is done by dividing the two year training period into five in-house ‘modules’ of roughly three months and one on-site period of nine month. (http://s24.postimg.org/ji7g1a2ph/ASD_Structure.jpg) Program modules
Training program The trainees are subject to the TU/e employment regulations. They all work 40 hours per week and have a total of 328 leave hours (41 days). When incorporating public holidays, this comes down to a total of 214 working days or 1712 hours annually. The following schedule is not fixed, and subject to changes annually, but gives a fair impression of the course package and workload. (http://s16.postimg.org/ru4clbded/Pages_from_ASD_Training_Guide_v3_1.jpg) Examples of In-house Projects Functional Safety Assessment of Automated Toyota Prius The objective of the project is to provide proof of concept according to the ISO 26262 for the longitudinal and lateral control functions of an automated car. The problem defined, has been approached from two different perspectives namely, top-down and bottom-up. Top-down approach involves the use of E-GAS architecture, while the bottom-up uses the existing architecture from the customer TNO. Powertrain Analysis and Modelling of a Lightweight Electric Vehicle with In-Wheel Motors As Engineers look for the 'next best thing' in Electric Vehicle technology, this project dealt with the evaluation of an In-Wheel Motor (IWM) drivetrain for an electric vehicle. A prototype IWM module, designed by TeamWork Technology BV, was tested and evaluated during this project. A suitable powertrain layout was conceptualised and the various components of the powertrain were sized for a hatchback car. Finally, simulations were conducted to evaluate the performance of an EV with the IWM drive train DAF Trucks: “Auto-Docking and Lane Merging systems” The project is a part of the Advanced Driver Assistance Systems under development in DAF. Auto-Docking and Lane Change Assist are to be developed as a “proof-of-concept” which includes designing the controllers along with the HMI’s (Human Machine Interaction) of the Auto-Docking and Lane Change Assist systems.[/list][/list] Title: Re: Μεταπτυχιακό, Διδακτορικό ή PDEng ? Post by: Lampros on May 31, 2015, 12:41:06 pm Πολύ ενδιαφέρον. Εχεις κάποιο λινκ; Που τα βρίσκεις αυτά; Τι αλλά courses προσφερονται;
Title: Re: Μεταπτυχιακό, Διδακτορικό ή PDEng ? Post by: ^^DaRk_HunTeR on May 31, 2015, 15:18:26 pm Τα κύρια links τα έδωσα πιο πάνω...
Στο website του κάθε PDEng μπορείς να βρεις βασικές πληροφορίες. Αυτά που βάζω είναι απο τους "οδηγούς σπουδών" που πήρα απο τους supervisors των προγραμμάτων οι οποίοι δεν είναι public γιατί είναι σε draft μορφή προς το παρόν. Μερικά απο αυτά βρίσκονται και στο internet... Αν έχεις συγκεκριμένες απορίες ρώτα ή εδώ ή σε pm. Όταν λες τι άλλα courses τι εννοείς και σε ποιο πρόγραμμα? Title: Re: Μεταπτυχιακό, Διδακτορικό ή PDEng ? Post by: Lampros on May 31, 2015, 18:00:15 pm Ναι δεν το έθεσα σωστά.
Τώρα που είδα και τα λινκς κατάλαβα καλύτερα. Γνωρίζεις ή παίζει να μάθεις και άλλα "προγράμματα σπουδών" απο το TU/e? επίσης μπορείς να μεταφέρεις την δική σου εμπειρία σε αυτό το πρόγραμμα? Title: Re: Μεταπτυχιακό, Διδακτορικό ή PDEng ? Post by: ^^DaRk_HunTeR on May 31, 2015, 18:33:22 pm Για τα υπόλοιπα PDEngs του TU/e θεωρητικά μπορώ να προσπαθήσω αλλά δεν ξέρω κατα πόσο είναι εφικτό υπο την έννοια ότι δεν έχω άμεση επαφή με τους supervisors, όπως έχω με αυτά τα δυο.
Ο σκοπός του ίδιου του τοπικ είναι να γίνει αυτό σε βάθος χρόνου, είτε απο εμένα είτε απο άλλους... Αλλά για να αντιστρέψω το ερώτημα, έψαξες για κάποιο και δεν σε κάλυψαν αυτά που βρήκες? Και αν ναι για ποιο? Και τι δεν σε κάλυψε...? Έλληνες υπάρχουν σχεδόν σε όλα οπότε θεωρητικά μπορείς να ψάξεις και να ρωτήσεις απο μόνος σου αν μιλάμε για λεπτομέρειες... και αν το ενδιαφέρον είναι μεγάλο και άμεσο τότε μπορω να το ψάξω απο εδώ. Η δική μου εμπειρία είναι δύσκολο να μεταφερθεί γραπτά γιατί είναι πολλά σε πολλά επίπεδα... Συγκεκριμένες απαντήσεις σε συγκεκριμένες ερωτήσεις είναι προτιμότερο. Γενικά, η εμπειρία μου είναι πολύ θετική και για αυτό άλλωστε μπήκα στη διαδικασία να κάνω το Topic ώστε να το μάθουν περισσότεροι και να βοηθηθούν ώστε να κάνουν το βήμα... Title: Re: Μεταπτυχιακό, Διδακτορικό ή PDEng ? Post by: Lampros on May 31, 2015, 19:07:04 pm Έχει μόνο γενικές πληροφορίες ας πούμε για το Information and Communication Technology έχει μόνο γενική περιγραφή και θα ήθελα να δω τα courses που έχει. Λέει ας πούμε "Design-oriented courses and projects", οκ δεν μου λέει κάτι όμως αυτό.
Στο Qualified Medical Engineer ας πούμε έχει ακόμη λιγότερα. Το ενδιαφέρον είναι μεν μεγάλο αλλά όχι τόσο άμεσο. Απλά είμαι τηλεπικοινωνιακός και δεν είδα κάποιο πιο τηλεπικοινωνιακό πρόγραμμα. Γενικά η δουλειά που κάνεις είναι πιο ακαδημαϊκή ή πιο "πρακτική"? Το ακαδημαϊκό επίπεδο είναι υψηλό? Δυσκολεύτηκες να προσαρμοστείς (όσον αφορά τη δουλειά σου όχι τη ζωή)? Γενικά πήρες αυτό περίμενες, καλύτερα, χειρότερα? τέτοια πράγματα θα ήθελα να μάθω Title: Re: Μεταπτυχιακό, Διδακτορικό ή PDEng ? Post by: ^^DaRk_HunTeR on June 06, 2015, 17:33:25 pm Για τα συγκεκριμένα προγράμματα δε μπορώ να σου απαντήσω με περισσότερες πληροφορίες πέρα από αυτές που βρίσκονται ήδη στο διαδίκτυο. Νομίζω πάντως πως πέρα από το site του TU/e αν ψάξεις σε Facebook, forums, brochures, etc. θα βρεις πολλά. Στο μέλλον θα προσπαθήσω να έρθω σε επαφή με ανθρώπους απο άλλα PDEngs αλλά ελπίζω και σε πρωτοβουλίες άλλων.
Τώρα για τις υπόλοιπες ερωτήσεις… Προσωπική μου άποψη (για το δικό μου πρόγραμμα) είναι ότι αυτό που κάνω είναι 70-30 πρακτικό-ακαδημαϊκό (ίσως και περισσότερο). Ως μέτρο σύγκρισης βέβαια έχω το ΤΗΜΜΥ ΑΠΘ οπότε δεν μπορώ να ξέρω τι γίνεται σε όλα τα Masters ανά τον κόσμο, παρόλα αυτά μια ιδέα την έχω από άλλους. Επιπρόσθετα, αν κατα τη διάρκεια του προγράμματος ανακαλύψεις ότι σου αρέσει η έρευνα μπορείς να το συνεχίσεις (σε συνδυασμό με το τελικό 9μηνο project συνήθως) για Ph.D. χωρίς να χάσεις χρόνο. Εξετάσεις προς το παρόν δεν έχουμε πέρα από τα Ολλανδικά, κάποιες χρονιές είχαν σε κάποια courses. Το πρόγραμμα είναι project-oriented το οποίο σημαίνει ότι τον περισσότερο χρόνο των πρώτων 15 μηνών κάθε μέρα πας στο γραφείο και δουλεύεις πάνω σε ένα project για μια εταιρεία. Π.χ. τώρα δουλεύουμε για την NXP Semiconductors. Κατά τη διάρκεια του project έχεις ρόλους όπως σε μια εταιρεία, Project Manager, Team Leader, Architect, Tester, etc. συναντιέσαι με τους πελάτες και γενικά βλέπεις το Software Development Process από την αρχή μέχρι το τέλος. Τα θέματα των Projects είναι στο state-of-the-art και αρκετά challenging. Προφανώς οι περισσότεροι δεν έχουν την εμπειρία σε όλους αυτούς τους ρόλους και επειδή ακριβώς θέλουν να μας προετοιμάσουν για το Industry κατά τη διάρκεια αυτών των μηνών πολλές φορές μέσα στο project (ή πριν) υπάρχουν training Workshops ανάλογα με τις ελλείψεις και το ενδιαφέρον. Εκεί βλέπεις και το λιγότερο πρακτικό κομμάτι (ακαδημαϊκό μέρος), γιατί είτε είναι καθηγητές από TU/e, είτε εξωτερικοί συνεργάτες, είτε ακόμη και στελέχη συνεργαζόμενων εταιρειών. Το αν είναι το ακαδημαϊκό επίπεδο υψηλό δεν ξέρω τι σημαίνει για σένα και είναι πολύ αμφιλεγόμενο ερώτημα, αυτό που θα σου πω εγώ πάντως είναι ότι νιώθω ότι μαθαίνω συνεχώς και αυτό δεν θεωρείται (σοβαρό) μειονέκτημα υπό την έννοια ότι οι περισσότεροι έχουν Software background και ακαδημαϊκό και επαγγελματικό. Το οτι βρίσκεσαι σε ένα mutli-cultural περιβάλλον by design παίζει πολύ μεγάλο ρόλο και έχει τις δικές του δυσκολίες και ευκαιρίες για προσωπική ανάπτυξη/βελτίωση (εδώ το λένε personal development). Συνήθως δεν υπάρχουν πολλοί Ολλανδοί στο πρόγραμμα, φέτος έχουμε τρείς και ξεχωρίζουν, σχετικά, στο θέμα γνώσεων στο αντικείμενο και αυτό σε κάνει να σκεφτείς γιατί το επίλεξαν ενώ μπορούσαν να πάνε να δουλέψουν κατευθείαν έξω με περισσότερα χρήματα. Για την προσαρμογή στη δουλειά, προσωπικά δεν δυσκολεύτηκα ιδιαίτερα αλλά αυτό είναι και στον άνθρωπο. Το πρόγραμμα ξεκινάει σχετικά εισαγωγικά και το πολύ καλό επαναλαμβάνω είναι ότι συνδυάζει το Πανεπιστήμιο με τη Βιομηχανία και άρα αν αισθάνεσαι ότι χρειάζεσαι αυτό το μεταβατικό στάδιο (για το εξωτερικό) θα σου ταιριάζει σίγουρα. Έχεις την προστασία του Πανεπιστημίου για τα όποια λάθη (educational/learning aspect) θα κάνεις και έχεις και το πρακτικό κομμάτι των intensive projects. Το αν είναι αυτό που περίμενα είναι μεγάλη κουβέντα, αλλά σε γενικές γραμμές είμαι ευχαριστημένος και για αυτό το προτείνω σε ανάλογες περιπτώσεις. Αν αισθάνεσαι ότι έχεις την εμπειρία και τις γνώσεις να πας να δουλέψεις κατευθείαν σε έναν τομέα που σου αρέσει (στο εξωτερικό) τότε μην έρθεις. Αν θέλεις να εντρυφήσεις και να κάνεις και κάτι πρακτικό (a.k.a ένα είδος προϋπηρεσίας) τότε σίγουρα θα σε βοηθήσει. Το σημαντικότερο όλων για μένα είναι ο supervisor και η πλαστικότητα του προγράμματος, το ένα συνδέεται με το άλλο και ανά πρόγραμμα υπάρχουν τεράστιες διαφορές. Ο superviror που έχουμε είναι ένας απίστευτος τύπος που κάθεται και σε ακούει με υπομονή παρά τα 60 του χρόνια, την απίθανη εμπειρία του στο χώρο, το Phd, etc. και αν προτείνεις κάτι καλό για το πρόγραμμα μπορείς ουσιαστικά να το αλλάξεις on the fly… Είτε αυτό έχει να κάνει με νέα workshops, με κατάργηση παλιών, με προσέγγιση εταιρειών, με νοοτροπίες κτλ κτλ… Υ.Γ.: υπάρχουν προφανώς και διάφορα αρνητικά αλλά επειδή αυτά είναι για λεπτομέρειες καλύτερα για όποιον ενδιαφερθεί συγκεκριμένα (σε pm). Title: Re: Μεταπτυχιακό, Διδακτορικό ή PDEng ? Post by: ^^DaRk_HunTeR on July 15, 2016, 00:58:26 am Αντιγράφω απο mail: (Υπάρχουν θέσεις ακόμα)
----------------------------------------------------------------------------------------- To whom it may concern We would like to point out the option to apply for a PDEng traineeship position for the next round of the 2 year Post-MSc Software Technology program. The program will start on October 31, 2016. More information on the program is available at www.tue.nl/softwaretechnology The link to the vacancy on TU/e application site is: http://jobs.tue.nl/en/vacancy/pdeng-trainee-positions-toio-software-technology-260035.html There you can also find the requirements, deadlines etc. You must finalize your MSc before the start of the program. The application site does not allow you to upload more than 5 documents of max 2 MB each. If you need to supply more, please do so by sending them by email to: ooti@tue.nl with the subject line: Addition to ST application For questions, please also use the email address: ooti@tue.nl With kind regards, Désirée van Oorschot Management Assistant Dept. Mathematics & Computer Science – Software Technology program https://www.4tu.nl/en/ Title: Re: Μεταπτυχιακό, Διδακτορικό ή PDEng ? Post by: ^^DaRk_HunTeR on September 05, 2017, 15:22:33 pm I copy from email:
3 Available Positions still - 2017 intake --------------------------- Dear members, Each year we hire 20 highly talented Computer Science graduates to be involved in our post-Master Software Technology program (paid position) to prepare them for becoming professional software designers and architects. Attached you can find the general brochure for our program. For those just graduated or soon to be we would like to point out the option to apply for a PDEng traineeship position for the next round of this program. We still have 3 positions available for good candidates ! Maybe you know of a Master student (Dutch and/or EU-national) who would be interested. In that case please forward this information and brochure a.s.a.p. We thank you in advance for your kind cooperation. The program will start on October 30, 2017. More information on the program is available at www.tue.nl/softwaretechnology The link to the vacancy on TU/e application site is: http://jobs.tue.nl/en/vacancy/pdeng-trainee-positions-toio-software-technology-304234.html There you can also find the requirements. You must finalize your MSc before the start of the program. The application site does not allow you to upload more than 5 documents of max 2 MB each. If you need to supply more, please do so by sending them by email to: ooti@tue.nl with the subject line: Addition to ST application For questions, please also use the email address: ooti@tue.nl With kind regards, Désirée van Oorschot Management Assistant Dept. Mathematics & Computer Science – Software Technology program In office: Mon-Tue-Thu (9.00-15.30h), Wed (8.30-13.00h), Fri (9.00-17.00h) Visiting address: De Zaale, 5612 AJ Eindhoven, the Netherlands (building MF-5.080a) Postal address: P.O. Box 513, 5600 MB Eindhoven, the Netherlands T +31 40 2474334 E ooti@tue.nl I www.tue.nl/softwaretechnology Title: Re: Μεταπτυχιακό, Διδακτορικό ή PDEng ? Post by: ^^DaRk_HunTeR on June 17, 2018, 15:38:42 pm Αντιγράφω απο μειλ
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Dear all, Each year we hire 20 highly talented Computer Science graduates to be involved in our prestigious 2 year doctorate level PDEng Software Technology (ST) program to prepare them for becoming professional software designers and architects. Attached you can find the general brochure of our program and a promotion poster for information and distribution. Application deadlines: For Dutch nationals: October 15, 2018 For EU nationals: September 30, 2018 For non-EU nationals: August 15, 2018 due to long visa procedures. The program will start on October 29, 2018. More information on the program is available as well at www.tue.nl/softwaretechnology (http://www.tue.nl/softwaretechnology) The link to the vacancy on TU/e application site is: https://jobs.tue.nl/en/vacancy/pdeng-trainee-positions-toio-software-technology-334300.html (https://jobs.tue.nl/en/vacancy/pdeng-trainee-positions-toio-software-technology-334300.html) There you can also find the requirements. Candidates are required to finalize their MSc before the start of the program. The application site does not allow you to upload more than 5 documents of max 2 MB each. If one needs to supply more, please do so by sending these by email to: ooti@tue.nl with the subject line: Addition to ST application For questions, please also use the email address: ooti@tue.nl Thanks very much in advance for your help ! With kind regards, on behalf of PDEng ST management (Dr. Y. Dajsuren PDEng / Dr. A.T.M. Aerts / Prof.dr. M.G.J. van den Brand), Désirée van Oorschot Management Assistant Dept. Mathematics & Computer Science – Software Technology program Visiting address: De Zaale, 5612 AJ Eindhoven, the Netherlands (building MF-5.080a) Postal address: P.O. Box 513, 5600 MB Eindhoven, the Netherlands T +31 40 2474334 E ooti@tue.nl I www.tue.nl/softwaretechnology - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - |