HANOI UNIVERSITY

FACULTY OF INFORMATION TECHNOLOGY

RESEARCH PROPOSAL

GROUP 6: FULL STACK DEVELOPMENT

 GROUP MEMBERS

1. Đỗ Văn Hòa (Team leader)

2. Nguyễn Long Vũ
3. Tăng Bá Minh
4. Trần Xuân Ninh
5. Phạm Tiến Thành
6. Nguyễn Văn Huyện
7. Nguyễn Quốc Bảo
8. Nguyễn Quốc Khánh
9. Dương Thị Huệ
10. Phùng Anh Quân
11. Vũ Thị Phương Anh
12. Nguyễn Duy Khánh
 ABSTRACT

With the strong development of science and technology, it is clear that one of the most
prominent jobs in the 21st century is information technology. Today, countries focus on
applying information technology to most areas of their lives, so IT is divided into many
different jobs. And one of the tendencies for students to choose new jobs is a Full Stack
developer. As the title suggests, the aim of this paper is to help students understand fully
what full-stack development is and understand the popularity of full-stack development
among young IT students. Based on data aggregated from a combination of interviews and
questionnaires with Information technology student carried out within Hanoi University
and reviewed literature, our project’s team analyze, discuss and evaluate student opinions to
show the full-stack development becoming popular and the interest in this career for IT
students. Another key point feature in this paper is to contribute another point of view about
the future of the full stack developer and distinguish vague careers in this field. Thus, it is
believed that this paper can serve students who want to research this job and gain additional
knowledge about their future career choice.

i
 TABLE OF CONTENTS

ABSTRACT..................................................................................................................... i
TABLE OF CONTENTS............................................................................................. ...ii
1 Introduction...................................................................................................................5
2 Background...................................................................................................................5 
3 Literature Review..........................................................................................................6
4 Research questions, hypotheses and their contribution to knowledge.........................10
5 Research Objectives and Scope....................................................................................10 
6 The significance of the study………………………………………………………....11
7 Research Methodology and Justification.....................................................................11 
    7.1 Research Methodology and Methods…................................................................11 
    7.2 Site of Research.........................................................................................………11
    7.3 Methodological Approach...............................................................................…..12   
    7.4 Data Collection......................................................................................................12
    7.5 Data Analysis.........................................................................................................13
    7.6 Justification............................................................................................................14
8 Ethics and Risk Considerations....................................................................................15
    8.1 Ethics Considerations............................................................................................15
    8.2 Risk Considerations...............................................................................................15
9 Research Plan...............................................................................................................16
REFERENCES................................................................................................................17
APPENDICES.................................................................................................................20

ii
1. Introduction
Nowadays, with the development of information technology (IT), enterprises and small
businesses have to upgrade their marketing and management method to keep themselves in
the market, this phenomenon leads to the need of Information Technology engineers who
must be responsible for the production efficiency from scratch until it becomes the final
product. Hence, the number of undergraduates choosing this particular field is exceeding
expectations as employers are willing to pay lots of money to whoever can perform multi-
function work. However, to be in the desired position, these future-engineers will need to
keep updating an enormous range of knowledge and are expected to cover up to 6 areas of
expertise related to the field (Shropshire, 2018). This high-demanded job is known as “Full
Stack development”. The topic “Full stack development”, indeed, have already been
studied carefully, yet a few of those studies could give a clear description of the role of full-
stack development job playing in the I.T. job market as well as its potential in the future
Therefore, the purpose of this study is to answer 2 consensus questions. The first question
is: To what extent do Hanoi University students in the I.T. department understand the term
full-stack development? And the second one is: What do they think about the future of the
full stack developer?

2. Background
Web development has arisen in recent decades. The web development will continue to
evolve fast to adapt to the constant change of human demands. Together with the breaking
out of social media, creating a website and managing the data is now no simpler but
complex. Consequently, companies in the Information Technology field intend to hire a
web developer with some specific skills, such as ReactJS developers, Angular developers.
This does not mean that there is no need for web design developers (front-end) and web
development (back-end), but business companies are now requiring developers who can do
both these jobs, instead of singular specialization.

Consequently, understanding these two terms “front-end” and “back-end” is the key to
know more about the topic of Full Stack development. Firstly, front-end typically refers to
everything that you can see on a site in the browser. The front-end developers are mostly
working with design languages namely HTML, JS and/or CSS code which can create a
graphical user interface and make it easier to use for users. For instance, the developers
design layers, buttons, images, navigation, and internal links that allow users to click, input
or retrieve information on the website. On the other hand, back-end is a term, which is
often called “server-side”, that basically describes how a site works, updates and changes.
Back-end developers are responsible for creating a dynamic site that constantly changing
and updated data in real-time. A dynamic site requires a database which stores all
information from users like user accounts or profiles, blog posts or images they have
uploaded to the site. Back-end developers mostly work with programming languages like
PHP or .NET. They write the codes which communicate with the servers and then tell the
site to interact with the browser. For simplicity, front-end developers are the ones “is in
front of the screen”. Contrarily, back-end developers are “behind the screen”.

3. Literature review

While most of the early work in Full Stack development tended to focus heavily on the
technological aspect, few researchers have taken people’s opinions and understanding
about the term full-stack into consideration. Interestingly, no academic articles about this
topic were identified. Only practitioner-oriented publications and websites have attempted
to define and discuss the meaning of Full Stack development. It is assumed that this
research represents one of the first attempts for academic research to investigate the term
understanding and the thought on the future from people, in particular, Information
Technology students from Hanoi University.

In 2018, a paper published by the Association for Information Systems (AIS), “Towards a
Consensus Definition of Full Stack Development”, analyzed the top five most referenced
and visited definitions of “Full Stack developer” to extract a general clarification. In the
end, the research proposed a universal definition of Full Stack development:
“Full Stack development is a methodology which addresses all stack layers and in doing so
creates a complete, implementable solution to business requirements. Full Stack developers
have broad experience among all stack layers and expertise in a few layers. They should be
able to render a minimum viable product in a given stack.”
While this definition is certainly a step in the right direction to defining what a Full Stack
developer is, it is still bound to provoke opinions from extreme viewpoints on either end.

The first notable area of disagreement is the level of expertise required to be considered a
Full Stack developer (Borowski, 2017; Shiotsu, 2016). Some definitions suggest that a Full
Stack developer must have deep experience within each stack layer, including writing all
around top-notch client side and server side (or front-end) code at the same level as a front-
end or back-end specialist, managing the server infrastructure, handling the non-technical
project management and business demands of coordinating their work with product (Yared,
2017). However, according to Daniel Borrowski, on “A Guide to Becoming a Full Stack
Developer”, being a Full Stack Developer does not require the ability to master everything
required to work with the front-end or back-end, but it means the ability to work on both
sides and the understanding of the workflow when building an application.). In short,
working knowledge of all stack layers is sufficient.

Another area of disagreement is the ability to convey their skills to work. Some resources
indicated that a Full Stack developer should be able to deliver a complete and
implementable business product that is ready for production (Westberg, 2015; Wiggins,
2017). An equivalent number of sources indicated that this is not significant (Edelman,
2015; Yonatan, 2016). Numerous definitions demonstrated that the Full Stack developer
must have the ability to convey a working solution which can be then enhanced by other
developers with specializations. This is similar to the theory of the MVP (Minimum Viable
Product), a concept used in start-ups to show that a concept will work and deserves to be
expanded (Borowski, 2017). Further review of the definitions yields several commonalities
regarding developer role and the purpose of Full Stack development (Shora, 2013).

In association with the concept around the definition of Full Stack development, there is
also a big contrary to the ideas of the future of the Full Stack developer. Although the high
demand from companies for Full Stack developers has been admitted by both sides of
views (Varshneya, 2018; Kumar, 2018), many debates on one should make Full Stack as
their career in the future are still present.
On one hand, some studies suggest that the Full Stack developer is an ideal job in the
future. The studies from this group share the same idea that companies need all-around
developers who have the broad expertise and the versatility of Full Stack knowledge to
build projects with limited people and resources (Borowski, 2017). This recommendation is
supported by the fact that specialization is not suitable for everyone, or for every business
goal.

In response to those studies, Andy Shora, in “The Myth of the Full Stack developer”, has
pointed out that most companies that are hiring Full Stack developers are only small
companies and startups. In her publication, Shora demonstrates the huge involvement of the
term “stacks” in the past decade, basing on that, she concluded that despite the
employability of a true Full Stack developer is extremely high, the chances of finding a
good Full Stack developer are low. Following Shora, in 2016, Yonatan, in “Four reasons
not to hire a “Full Stack” developer”, refused the existence of a flawless performance in
every facet due to the increasing complexity of today's technology. The same idea has been
strongly supported by Varshneya, Co-founder at CurveBreak, in 2018, “companies such as
financial or global organizations that don’t make too many changes, but require a high level
of stability, will likely require a performance expert”. Despite the fact that those studies are
mostly based on individual opinions, they still contribute strong evidence against the other
group, making the concept unclear.

Another prominent reason that has been shared in the majority of articles is that Full Stack
developer is one of the most high-paying tech jobs. However, this claim has recently been
challenged and argued by the results of recent reports.
According to the data from Paysa’s report, while back-end and front-end developers make
$90k, a Full Stack developer makes only $76k. In addition, the data for the 75th percentile
has emphasized the gap: $104k, $106k and $90k for backend, frontend and Full Stack,
which means, Full Stack developers are getting paid fifteen-percent less than the others.
This problem has been strongly criticized by Taher, an expert in full-stack developer
himself: “This is a scam, this is a myth, that's everyone agrees upon. The greatest scam
where you are paid less for doing more. Even if it's the same hour you work, even if its
same 8 hours job. You are expected to solve all of their problems while getting less and less
amount of salary”.
Above all, both the definition of Full Stack development and the potential in the future of
full-stack developers still demand a further study for better refinement. Therefore, our
research, with incorporating feedback from representative practitioner groups and
conducting empirical evaluations, will hopefully provide subsequent improvements to the
current conceptualization.
4. Research questions, hypotheses and their contribution to knowledge.
The first question “To what extent do Hanoi University students of Information Technology
(I.T.) major understand the term “Full Stack development”?” aims at discovering whether
IT students have awareness of the research topic and how many of them get a deep
understanding in this area. Solving this question brings the opportunity to sense the
popularity of the full-stack development job amongst young potential programmers in the
massive IT job market at the time this research paper being conducted.

The second question “What do Hanoi University students of Information Technology major
think about the future of the full stack developers?” is to discuss the potential of the full-
stack development job. With the results gained from this question, the paper would be able
to provide highly reliable predictions about the development path for this job. For example,
depending on the responses from I.T. students, who will get into the job market in the next
few years, of whether this job is tempting or not, this research could conclude the position
of the full-stack development job in the near future.

The research hypothesis, based on these two questions, is: Full-stack development is
becoming and will become more and more prominent amongst IT students. This paper is
then to conduct a study to affirm the correctness of this assumption.

5. Research objectives and scope

The ultimate objective of this research paper is to investigate the popularity of Full Stack
development job through the angle of university students in I.T major. The main object of
this research, therefore, is those young people who, in the next few years, will participate in
the I.T. workforce. Due to the limitation of time, finance and human resources, the case
study is students who are studying I.T. at Hanoi University. The scope of this case study is
400 students of the I.T. department.
Besides, the study also conducts interviewing 10 specialists in I.T. fields, who has at least 5
years working in the I.T. job market of Vietnam in order to get more reliable information
for the quality of the study.

6. The significance of the study

This research is the journey of discovering the position of full-stack development jobs in
the massive I.T. job market. Through that, the study results, if possible, could reinforce the
existed theory about the definition of full-stack development, as well as contributing
another point of view about the future of this job and then opening further discussions of
vague careers in this field.

7. Research Methodology and Justification

The primary purpose of the study is to inform readers what Full Stack development is and
the future of Full Stack developers in order to differentiate ambiguous points around this
field. Following the research goal, the key research questions and objectives, this section
will offer the methodological approach, data collection, data analysis and justification to
explain the research questions

7.1. Research Methodology and Methods

Research Methodology refers to the overall strategy and hypothesis of your research.
Specifically, it includes studying the methods employed in the research paper and the
theories or principles behind them, so as to strongly promote the approach that is suitable
for your objectives (McCombes, 2019).

A method is simply the tool used to solve your research questions (Brookshier, 2018). It
means that how the researcher(s) will collect the data. There are many methods to conduct a
research such as Contextual inquiry, interview, survey and so on.

7.2. Site of Research

Most of the offline surveys will be conducted at Hanoi University in each IT classroom and
some online surveys are posted on Hanoi University on K16, K17, K18 FIT HANU and
Facebook fan page Department of Information Technology – Hanoi University.
Furthermore, many IT students are interviewed at the schoolyard and some IT experts in
eminent companies and academies such as Mr.Steve Hoang, CEO at Vietnam AI System,
Mrs.Thao Phuong, CEO at CodeGym Vietnam and Mr. Tien Le, CEO at Botbanhang.vn
will also participate in the interview.

7.3. Methodological Approach

After considering four crucial aspects (timing, weighting, mixing, and theorizing) in order
to choose a suitable methodology approach, the authors decide to select Mix methods
including both Quantitative methods and Qualitative methods and a particular strategy
called Concurrent Triangulation Strategy. In addition, our topic research is complex and
arguable and therefore we determine to choose explanatory research. Besides, justification
and ethical considerations will be added in our research so as to make it more persuasive.
Some criteria for validity and reliability will be illustrated in the research. In terms of
validity, there are four main types of it. However, construct validity is a wonderful choice
to help us utilize existing theory and knowledge that are relevant to the topic such as Front-
end skills; Back-end skills and so on. In reliability, test-retest and internal consistency are
selected to support us in the aims of answering two important questions: Do we get the
same results when I repeat the measurement?; Do we get the same results from different
parts of a test that are designed to measure the same thing? (Middleton, 2019).

7.4. Data Collection

Data collection is an indispensable part of any research with a view to answering the
research question. There are many data collection techniques depending on the research
goal. As mentioned in the previous sections, this research will follow a concurrent
triangulation mixed-method approach, using quantitative and qualitative methods.
Quantitative data collection includes surveys and existing data. Qualitative data collection
consists of interviews. The rationale for these choices will be explained below.

Survey

The surveys consist of many multiple choice, scale and rating questions in order to test
correspondents’ awareness of the topic. Specifically, there are total 10 questions including
8 multiple choice questions, 2 checkbox questions and 1 scale ones. The purpose is to
conduct the survey with around 400 IT students of Hanoi University at the schoolyard,
lecture hall and classroom within 2 months. All of us agree that our probability sampling
method is simple random sample so as to increase the objectivity of our research.
Participants will be given about 15 minutes to complete the survey anonymously.
Moreover, there are two main ways to fill in it: online survey and offline one (in-person).
Our response rate is expected to be 30% online forms and 70% offline ones.

Existing data

To adequately understand the topic, our research team has to search a great number of
research papers relating to the field. However, few materials are selected to analyze on
account of the fact most of them are quite technical, not suitable to our target. The most
fantastic research paper we seek is “Towards a consensus definition of Full-stack
development”, written by Jordan Shropshire, Jeffrey P. Landry, and Steven S. Presley, and
published by SAIS 2018 Proceedings. Our team determines to choose it because it is a peer
review research paper and appropriate content for our requirements. There are three major
parts of the article. Firstly, the authors give a brief description of the generalization of the
term “Full-stack development”. Then, they mention an overview of technology stacks that
Full-stack developers frequently use. Finally, they discuss the most viewed and trustworthy
articles and problems with the level of expertise and breadth knowledge connecting with
the topic.

Interviews

With the aims of gaining better insight into Hanoi University IT students’ viewpoints about
the topic and increasing the credibility for our research, structured interviewed will be
conducted with 10 IT students and 5 IT experts from famous companies and academies in
Hanoi City in order to evaluate information we receive in the most accurate and objective
way (Zojceska, 2018). Regarding time response, students will be given around 10 minutes
to accomplish it and 25 minutes for IT experts. The interviews will be done in small
classrooms or business offices. Answers will be recorded by note-taking to analyze in the
next process.

7.5. Data Analysis

In this research, both quantitative and qualitative data will be analyzed by two progressive
tools: STATA and ATLAS.ti respectively.

STATA: quantitative data analysis

STATA is a multi-platform, interactive data analysis program, which can be used simple as
well as complex statistical analyses (Crossman,Ashley, 2019). It uses both a command
syntax and a point-and-click interface in order to produce a graphical visualization of data.
Furthermore, STATA is simple to use and anyone can implement it efficiently, which is
absolutely brilliant for those who have some or no coding knowledge (Paul, 2019).

ATLAS.ti: qualitative data analysis

ATLAS.ti is one of the most outstanding software for Qualitative Data Analysis for those
who would like to see the big picture and valuable information (Imanuel, 2018). It is used
to analyze a large amount of textual, qualitative data or pattern codes that contain a great
number of fragments such as images, videos and other types in digital formats. Moreover,
ATLAS.ti allows researchers to gain useful insights with the most percipient and
remarkable QDA software (H., 2018). ATLAS.ti 8 is so easy to study and use that
beginners can master this tool in a short period.

7.6. Justification

There are various beneficial points in conducting mixed-method designs. First of all,
mixing methods allows researchers to acquire more exact information, so validity, as well
as reliability, will be also enhanced dramatically. Besides, obtaining more accurate results
assist them to uncover mysterious aspects of a phenomenon and to enrich explanations and
theory synthesis. Therefore, integrating qualitative and quantitative data may be the best
selection to gain complete insight into research problems (Leahey, 2005). However, some
limitations to these methods can be clearly shown. Firstly, practical guidance is very
limited. Most articles or research papers of mixed methodology just pay attention to the
conceptual framework, thus applications of the articles into daily life face many difficulties.
Secondly, to reduce the time and to produce a quick result, many researchers have
overlooked some important research processes such as survey data, research plans and so
on, or if they do, they will carelessly implement these steps. As a result, many serious
problems can occur. One of them is ethical issues due to not ensuring the protection of data
confidentiality and human research subjects, which has been attracted to a large amount of
attention from participants recently.

Our research team also chooses concurrent triangulation strategy because of many
considerable advantages. This strategy is very familiar to most researchers, so it helps us
save much time in doing research. In addition, it supports us to figure out well-validated
and substantial findings. On the other hand, the strategy still has some cons. Firstly, it
requires huge attempts and knowledge to adequately study a phenomenon with two
different methods. Moreover, it is pretty vague to resolve the obstacles that arise in
comparing the results (W.Creswell, 2009).

After considering the pros and cons, we determine to select these methods and strategies
because there are two crucial things. Specifically, the advantages are over the other side and
the techniques are appropriate to our research goal.

8. Ethics and Risk considerations

8.1. Ethics considerations

The first requirement when we perform this research is keeping researcher safe is an
essential ethical consideration, for everyone involving in a study (Rebecca,Gibson,and
Will, 2010). The participants are fully and clearly informed about the survey. They can
know the reasons why they carry out this survey, and how the research will be used for.
Moreover, the participants take part in the survey voluntarily, there is no compulsion in the
survey.

8.2. Risk considerations

We will consider the general considerations and solutions to reduce the risk as following
this criterion: information security. When people participate in this survey, their individual
information may be leaked so data security is one of the most important criteria in the
research. Exploiting data users from the third party is not allowed. Besides, we only assess
relevant components that cause no problems for the participants and researchers.

9. Research plan

This project expected to be studied and composed within 2 months. The research plan can
be seen in these following stages:

- Stage 1: Search and study the literature. The literature resources are books, articles, etc. in
the library, the internet related to our research topic. At the time, we may contact the
lecturer and ask for any difficulties we may encounter.

- Stage 2: After we gather enough information, we will discuss with each other about what
we found; provide the outline for our research paper; design survey, interview questions for
additional data collection.

- Stage 3: Collect and analyze the data (after collecting enough data to work with).

- Stage 4: Writing the thesis and editing the paper (based on lecture’s advice).
 REFERENCES

Brookshier, K. (2018, January 22). Medium. Retrieved from UX Collective:

https://uxdesign.cc/method-vs-methodology-whats-the-difference-9cc755c2e69d

Crossman, Ashley. (2019, October 25). A Review of Software Tools for Quantitative Data
Analysis. Retrieved from ThoughtCo.: https://www.thoughtco.com/quantitative-
analysis-software-review-3026539

H., M. (2018, August 10). ATLAS.ti Review. Retrieved from Capterra:

https://www.capterra.com/p/171500/ATLAS-ti/

Imanuel. (2018, February 05). TOP 14 QUALITATIVE DATA ANALYSIS SOFTWARE.

Retrieved from Predictiveanalyticstoday:
https://www.predictiveanalyticstoday.com/top-qualitative-data-analysis-
software/#reply-form

Leahey, E. (2005). Convergence and confidentiality? Limits to the implementation of mixed

methodology. Department of Sociology, University of Arizona, P.O. Box 210027,
Tucson, AZ 85721-0027, USA: ScienceDirect.

McCombes, S. (2019, December 18). How to write a research methodology. Retrieved

from Scibbr: https://www.scribbr.com/dissertation/methodology/

Middleton, F. (2019, December 18). Reliability vs validity: what’s the difference?

Retrieved from Scribbr: https://www.scribbr.com/methodology/reliability-vs-
validity/

Paul, K. (2019, November 26). Which is better: Stata or R? Retrieved from Quora:
https://www.quora.com/Which-is-better-Stata-or-R
Rebecca, Gibson, and Will. (2010). The research ethics guidebook: a resource for social
scientists. University of Sussex.

W.Creswell, J. (2009). Research Design: Qualitative, Quantitative, and Mixed Methods

Approaches. United States of America: SAGE Publications.

Zojceska, A. (2018, January 24). Difference between structured, unstructured and semi-
structured job interviews. Retrieved from TalentLyft:
https://www.talentlyft.com/en/blog/article/92/difference-between-structured-
unstructured-and-semi-structured-job-interviews

Borowski, D. (2017, 8 1). A Guide to Becoming a Full-Stack Developer in 2017.

Retrieved from Coderbyte: https://medium.com/coderbyte/a-guide-to-becoming-a-
full-stack-developer-in-2017-5c3c08a1600c

Bryksin, G. (2017, 8 17). How to Choose a Technology Stack for Web Application
Development. Retrieved from Upwork: https://www.upwork.com/hiring/for-
clients/how-to-choose-a-technology-stack-for-web-application-development/

Edelman, G. (2017, 1 8). How to Choose Your Tech Stack. Retrieved from Silicon
Valley Software Group: https://svsg.co/how-to-choose-your-tech-stack/

Shiotsu, Y. (2017, 5 15). Writing a Job Description to Find a Great Full Stack Web
Developer. Retrieved from Upwork:
https://www.upwork.com/hiring/development/full-stack-web-developer-job-
description/

Shora, A. (2013). The Myth of the Full-stack Developer. Retrieved from

AndyShora.com.

Wiggins, J. (2017, 5 31). The Myth of the Full-Stack Unicorn Developer. Retrieved
from AtlanticBT: https://www.atlanticbt.com/insights/myth-full-stack-unicorn-
developer/

Yared, P. (2017, 11 9). The Rise And Fall Of The Full Stack Developer. Retrieved
from Crunch Network: https://techcrunch.com/2014/11/08/the-rise-and-fall-of-the-
full-stack-developer/
Yonatan, H. (2016). The Full Stack UXer. Retrieved from UX Magazine:
https://uxmag.com/articles/the-full-stack-uxer

Kumar, R. (2019, July 25). Full Stack Developer is 2019's Popular In Demand
Tech Job . Retrieved from Hackernoon: https://hackernoon.com/full-stack-
developer-a-popular-in-demand-tech-job-in-2019-ehxs3z6y

Lee, C. (2018, August 31). How Long Does it Take to Become a Full-Stack
Developer? Retrieved from LaunchSchool Website:
https://medium.com/launch-school/how-long-does-it-take-to-become-a-full-
stack-developer-a9d627b71898
APPENDIX A

SURVEY

FULL STACK DEVELOPMENT

We are team 6, FIT students, Hanoi University. We are conducting a research proposal on
the topic called Full Stack development. This survey is done to support us to acquire data
for our research proposal. We warmly welcome your viewpoints which significantly
contribute to the completion and the quality of our research proposal. Thank you so much
for your cooperation.

1. Have you heard the term "Full Stack Development"?

• Yes
• No
2. According to you, Full Stack Development includes:
o Back-end
o Front-end
o Front-end and Back-end
o Front-end and UI/UX
o Others (Please specify) ________________________________________________
3. In your opinion, which factors are the most suitable for Full Stack Developers?
o Good coding skills
o Proficient technology stacks
o Excellent communication skills
o Great solving problems
o Active learning
4. In your viewpoint, how many years will it take to become a Full Stack
Developer?
 o 1-3 years
o 4-6 years
o 7-10 years
o More 10 years

5. Do you know which centers or websites teach to become Full-stack Developer?

o CodeGym
o Simplilearn
o MindX
o Udemy
o Udacity
o Others (Please specify) ________________________________________________
6. In your opinion, what is the average salary of a Full Stack Developer in
Vietnam?
o Under 1,000 USD
o 1,000 USD - 1,499 USD
o 1,500 USD - 1,999 USD
o 2,000 USD - 2,499 USD
o 2,500 USD - 3,000 USD
o More 3,000 USD
7. According to you, what is the biggest obstacle to pursue Full Stack career?
o Explanation skills
o Teamwork skills
o Too many things to learn
8. In your viewpoint, can Full Stack Developers be replaced by advanced
technologies (AI, Robotics)?
o Certain
o Possible
o Neutral
 o Impossible
9. After hearing Full Stack Developer job, do you still want to pursue it?
o Yes
o No
o I don’t know

10. Your interest level in this career: (1-Do not care; 5-Really like)

1 2 3 4 5

O O O O O
APPENDIX B

INTERVIEW QUESTIONS

1. What is the jobs in a Full Stack Developer and what skills are suitable for a Full
Stack Developer?
2. Do you know celebrity in this field? Can you predict the growth in this career?
3. (only experts) Does Full Stack Development actually exist? Recommendations to
those who pursue the job?