Shadowing Practice: Top 10 Behavioral Software Engineering Interview Questions - Learn English Speaking with Video

בחר מצב תרגול

כל מצב פותח חדר תרגול במסך מלא.

91 משפטים
אם המשפטים קצרים או ארוכים מדי, לחץ על ערוך כדי להתאים אותם.
1
Here are the 10 most common behavioral software engineering interview questions and how to answer them.
2
Number one, tell me about yourself.
3
This sounds obvious, but it's the most common question that you get when you walk into the interview room.
4
Interviewers just want to understand a little bit more about who you are,
5
your background, and what might be relevant for you as you interview for this role.
6
Keep it short, simple, and clear and keep it to maybe a few points
7
that you really really want to make sure that your interviewer remembers after the interview.
8
Number two, tell me about a project that you've worked on.
9
In this interview question your interviewer is just trying to get a better sense for your experience.
10
Tell them a little bit more about the challenges you had with the project, the successes, and the impact that it had on the team.
11
Still keep it short.
12
The interviewer doesn't want a whole story, they just want to understand a little bit more about what you did
13
and they'll ask follow -up questions
14
that they want to learn more number three disagreement questions these questions might look like tell me about a time
15
that you had a disagreement with your manager
16
or tell me about a time when you're working cross -functionally with a product manager
17
or with a designer
18
and you had a disagreement in these interview questions your interviewer is assessing your capacity for conflict
19
and being able to navigate conflict
20
which is a necessary part of any sort of engineering job in this question showcase case
21
that you dealt with a challenging scenario, that you learned how to actively listen, how to collaborate, how to compromise,
22
and how to ultimately come to a solution that worked well for both yourself and the engineering team, as well as everyone else involved.
23
If you want to go deeper on how to actually answer these questions,
24
and to learn more about different types of questions that are asked in behavioral software engineering interviews,
25
check out tryexponent .com, where we have a list of thousands of interview questions
26
and detailed guides on how to answer these questions as well
27
as mock interview videos where we show you how the interviewers
28
themselves answer the question number four technical fluency in these types of questions your interviewer wants to understand
29
that you know how to take your technical knowledge
30
and translate it into layperson speak what i mean by this
31
is a question sort of like tell me about a time
32
when you had to go about explaining a technical concept to
33
a non -technical person your interviewer wants to make sure that
34
if you join their company
35
that you'll be able to collaborate not just with other engineers who are very technical
36
but with other folks on the team in various divisions who
37
may not have a grasp of the same technical concepts
38
that you do this is an important skill in any sort of software engineering role
39
but in particular comes up in the behavioral interview questions number
40
five handling constraints questions these questions might look something like tell me about a time
41
when you had to work on a tight deadline
42
or tell me about a time when you had to decide between a code refactor
43
or shipping something sooner rather than later as a software engineer you're always battling against different constraints
44
and your job is to make sure that you're prioritizing the company
45
and the project objective and balancing the different constraints
46
so these questions assess for
47
that in these questions just make sure to articulate how you
48
thought about handling the different constraints how you thought about the different options available to you
49
and why you ultimately picked the option that you did
50
and the eventual impact that it had on both yourself the project
51
and the team number six what's an area of weakness
52
you're working on these questions assess your ability to be self -aware
53
and to be coachable it's important for software engineers to be able to grow
54
and to learn and everyone has their weaknesses so be honest
55
and upfront about what those might be oftentimes interviewers ask this
56
question to get a better sense of what the managerial relationship might look like for instance
57
if i were to manage you maybe i need to make sure
58
that i'm very thoughtful about making sure that you're organized
59
because that's an area of difficulty for you this isn't a bad thing it's just getting your interviewer
60
and you a better sense of what your relationship might look
61
like number seven what are your career goals these questions get
62
a better sense of how you might want to grow in the organization be upfront
63
and honest about what it is for you that you're excited about.
64
It might be about moving into certain industries, it might be working on certain types of projects,
65
for instance, moving more into front -end versus back -end,
66
or it could even be more about being on a manager track versus being on a senior IC track.
67
This will help your manager get a better sense of what it might be like to manage you
68
and how to sort of manage you in the right direction
69
and making sure that your career goals map up to what the company's goals are.
70
Number eight, why do you want to work for this company?
71
This is a question that comes up in most behavioral interviews
72
and is really really important my number one recommendation here is
73
to simply do your research understand the company deeply understand the goals of the company
74
and understand how your goals and your interests fit in
75
and map to the goals of the company number nine why do you want to leave your last company
76
this is an opportunity for you to share a little bit
77
more about what didn't work with your past company my recommendation here is to not be super disparaging of your previous company,
78
but just be thoughtful about what worked and what didn't work and how this company might be a better opportunity for you.
79
Now, if you've been laid off, that might be a slightly different story.
80
My recommendation is still to be honest
81
and upfront about what happened in the scenario and what you're really excited about in this company and in this role.
82
Number 10.
83
What are you looking for in your next role?
84
This is a really great opportunity to share what you're excited about with both the company and the role.
85
There's an opportunity here also to sort of shape your relationship with who might be managing with you
86
or who might be on your team, which often case the interviewer is.
87
In this case, share a little bit more are you interested in mentorship learning opportunities
88
or maybe gaining more technical expertise this will help make sure
89
that there is an alliance between both you as the employee
90
and the manager in the role i hope
91
this was a helpful overview of the top 10 most common software engineering interview questions good luck on your upcoming interview

הורד אפליקציה

כל מה שאתה צריך כדי לדבר בשטף

הגיית AIציון לכל משפט
תרגול IPAשלוט בכל צליל
אוצר מיליםבנה את מאגר המילים שלך
משחק אוצר מיליםלמד תוך כדי משחק

אותו ערוץ

FOR YOU

המלץ על סרטון

אוצר מילים והערות הגייה לשיעור הזה

שיעור הדיבור הזה מבוסס על הסרטון “Top 10 Behavioral Software Engineering Interview Questions”. המילים שחוזרות הכי הרבה: interview, interviewer, technical, software, engineering. בסרטון הזה יש 91 משפטים ו-1196 מילים לתרגול Shadowing. הדיבור נמשך 5:53. הדובר מדבר מהר, כ-203 מילים בדקה, אז צפו לצלילים מחוברים ומקוצרים. 88% מהמילים נמצאות בין 3,000 המילים הנפוצות ביותר באנגלית, כך שקל לעקוב אחרי אוצר המילים.

אוצר מילים מרכזי בסרטון הזה

15 מילים מהסרטון שכדאי ללמוד, עם ההגייה והמשמעות שלהן:

מילההגייהמשמעות
recommendation שם עצם/ˌɹɛkəmɛnˈdeɪʃən/הַמְלָצָה
disagreement שם עצם/dɪsəˈɡɹiːmənt/מחלוקת, מַחְלֹקֶת
versus/ˈvɝsəs/נֶגֶד
weakness שם עצם/ˈwik.nɪs/חולשה
collaborate פועל/kəˈlæb.ə.ɹeɪt/שיתף פעולה
designer שם עצם/dɪˈzaɪnɚ/מְעַצֵּב
skill שם עצם/skɪl/מְיֻמָּנוּת, כִּשּׁוּרִים
alliance שם עצם/əˈlaɪ.əns/בְּרִית
objective שם עצם/ɒbˈd͡ʒɛk.tɪv/מַטָּרָה
difficulty שם עצם/ˈdɪfɪkəlti/קושי
compromise שם עצם/ˈkɑmpɹəˌmaɪz/פְּשָׁרָה
overview שם עצם/ˈoʊ.vɚˌvjuː/סקירה
organize פועל/ˈɔɹɡənaɪz/ארגן
translate פועל/tɹænzˈleɪt/תִּרְגֵּם
mock פועל/mɑk/סנט

Phrasal verbs שתשמעו

מילהמשמעות
check out פועלבדק

דקדוק בסרטון הזה

המבנים שהדובר משתמש בהם הכי הרבה, עם המילים המדויקות מהסרטון:

מבנהבסרטון
הווה מושלם (Present perfect) have/has + past participle — פעולה שקרתה בעבר ועדיין יש לה חשיבות או השפעה עכשיוyou've worked · you've been laid
סביל (Passive voice) be + past participle — הדגש הוא על מה שקורה, לא על מי שעושה את הפעולהare asked · you've been laid

הגייה ששווה לשים לב אליה

הדובר משתמש ב-17 קיצורים וצורות מקוצרות, כמו you're, didn't, you've. אמרו אותם בצורה הקצרה, כפי שאתם שומעים אותם.

  • הצלילים של “sh” ו-“zh”: recommendation /ˌɹɛkəmɛnˈdeɪʃən/, showcase /ˈʃoʊˌkeɪs/
  • מילים ארוכות — שימו לב להטעמה: behavioral /bɪˈheɪvjəɹəl/, recommendation /ˌɹɛkəmɛnˈdeɪʃən/, disagreement /dɪsəˈɡɹiːmənt/, collaborate /kəˈlæb.ə.ɹeɪt/, difficulty /ˈdɪfɪkəlti/

צלילים שדוברי עברית מתקשים בהם:

  • /æ/ — פתוח יותר מה-“אֶ” העברית, לא כמו “a” ב-“cup”: collaborate /kəˈlæb.ə.ɹeɪt/, actively /ˈæktɪvli/, grasp /ɡɹæsp/, translate /tɹænzˈleɪt/, navigate /ˈnæv.ɪ.ɡeɪt/
  • /r/ — הלשון לא נוגעת בשום מקום, לא ה-“ר” הגרונית: behavioral /bɪˈheɪvjəɹəl/, recommendation /ˌɹɛkəmɛnˈdeɪʃən/, disagreement /dɪsəˈɡɹiːmənt/, scenario /sɪˈnɛəɹioʊ/, collaborate /kəˈlæb.ə.ɹeɪt/
  • עיצור קולי בסוף מילה — /b/, /d/, /g/, /z/, /v/ בלי להפוך אותם לאטומים: objective /ɒbˈd͡ʒɛk.tɪv/, compromise /ˈkɑmpɹəˌmaɪz/, expertise /ˌɛkspɜːˈtiːz/, organize /ˈɔɹɡənaɪz/, disparage /dɪsˈpæɹɪd͡ʒ/

איך לתרגל עם הסרטון הזה

  1. הקשיבו לכל הסרטון פעם אחת בלי לדבר, ורשמו את המילים שאתם לא מכירים.
  2. התחילו במהירות 0.75×, תרגלו Shadowing משפט אחר משפט, וחזרו למהירות רגילה כשזה מרגיש קל.
  3. הקליטו את עצמכם והשוו למקור, תוך תשומת לב למילים כמו recommendation, disagreement, versus.

מהי טכניקת השאדואינג?

שאדואינג היא טכניקת למידת שפה מבוססת מדע שפותחה במקור להכשרת מתורגמנים מקצועיים ופופולרית על ידי הפוליגלוט ד"ר אלכסנדר ארגואלס. השיטה פשוטה אך עוצמתית: אתה מקשיב לאודיו באנגלית ילידית וחוזר עליו בקול רם מיד — כמו צל העוקב אחרי הדובר עם עיכוב של 1–2 שניות בלבד. בניגוד להאזנה פסיבית או תרגילי דקדוק, שאדואינג מכריח את המוח והשרירים בפה לעבד ולשחזר דפוסי דיבור אמיתיים בו זמנית. מחקרים מראים שזה משפר משמעותית את דיוק ההגייה, האינטונציה, הקצב, הדיבור המחובר, הבנת השמיעה ושטף הדיבור — מה שהופך אותו לאחת השיטות היעילות ביותר להכנה לIELTS Speaking ולתקשורת באנגלית בעולם האמיתי.

טכניקת Shadowing: קרא את המדריך המלא שלב אחר שלב →