Vocabulary
Student should learn these before the lesson with teacher
- overwhelmed (adj) – /ˌoʊvərˈwɛlmd/
Meaning: Feeling like something is too much to handle.
- workstation (n) – /ˈwɜrkˌsteɪʃən/
Meaning: A special desk or area where you do your work, usually with a computer.
- duty (n) – /ˈduːti/
Meaning: Something you must do because it is expected of you.; a responsibility.
- procedure (n) – /prəˈsiːdʒər/
Meaning: A way of doing something, usually involving several steps.
- acquainting (v) – /əˈkweɪntɪŋ/
Meaning: Helping someone know or learn something.
- tentative (adj) – /ˈtɛntətɪv/
Meaning: Unsure; not final; might change later.; done without confidence.
- architecture (n) – /ˈɑrkɪtɛktʃər/
Meaning: he overall structure of a software system or computing
- suffice (v) – /səˈfaɪs/
Meaning: Be enough or adequate.
- responsibility (n) – /rɪˌspɒnsəˈbɪlɪti/
Meaning: Something you are expected to take care of or manage.
- aesthetically (adv) – /ɛsˈθɛtɪkli/
Meaning: In a way that relates to beauty or the appreciation of beauty.
Reading
Short introduction about Onboarding process
The onboarding process helps new employees get started at their new job. It usually has a few important steps. Before the first day, there might be paperwork to complete, and the company might set up a workstation or provide necessary equipment. On the first day, new employees typically meet their team members, tour the office, and learn about the company’s rules. After that, they often receive training on their specific job duties, the software they will use, and other company procedures. It’s also important for new employees to get ongoing support. This could include regular meetings with their boss, feedback sessions, or even a mentorship program. Each company’s onboarding process can be different. Some have a formal and structured approach, while others might be more casual.
Dialogue 1
Conversation between Human Resources (HR) and a new IT quality control (QC) staff
HR: Hello and welcome! I’m Taylor from HR. It’s great to have you join us. How are you feeling on your first day?
QC: Hi Taylor, thank you! I’m feeling quite excited to start and a bit overwhelmed with everything new.
HR: That’s completely normal. Let’s start by touring your primary workspace and then see other key areas of the company.
They walk towards the new QC workspace
HR: Here’s your desk. You’ve been equipped with all necessary tech and access. If you find you need additional resources, just let me know.
QC: Everything looks perfect, thanks!
HR: Let’s walk through the office. First, the Engineering Department, where you’re based. You’ll be working closely with developers and engineers to ensure software and systems meet our quality standards.
QC: I’m eager to meet the team and dive into the projects.
They continue walking.
HR: This is our Customer Support Center. They’ll be essential for gathering user feedback related to technical issues.
QC: It’s good to know where the feedback comes from. I’ll keep in touch with them.
They walk towards a leisure area.
HR: Here’s the break room. Coffee, tea, and snacks are available here. It’s a nice spot for a break and informal chats.
QC: It looks like a great spot for a break. I appreciate having a place to relax and recharge
HR introduces more departments & places to QC…
HR: That’s pretty much it. Let’s head back to your desk. Any questions?
QC: All clear for now. Thanks for the tour, Taylor.
HR: You’re welcome! Remember, I’m here for any further questions. We’ll check in at the end of the week. Have a great start!
QC: Thanks, Taylor! Looking forward to it.
Introduce yourself as a new staff
As the new staff tours different departments, you could introduce yourselves using a concise but friendly approach like this:
Hi everyone, I’m Alex, a new member in the Engineering department, focusing on software quality control. I’m really looking forward to collaborating with all of you and learning from your experiences. I hope to support the team effectively and contribute to our projects and our company. Looking forward to your support and a great working relationship. It’s a pleasure to meet all of you!
OR
Hello everyone, I’m Jordan, the new Back-end Developer in the IT department. I’ll be working behind the scenes on our server-side applications and databases. I’m excited to collaborate with each of you and contribute to our ongoing projects. Looking forward to your support and a great working relationship. It’s a pleasure to meet all of you!
Dialogue 2
Conversation between Project Manager/Supervisor and a new staff
Just choose one of these dialogue which match/nearly match with student role in IT.
- Business Analyst
- Quality Control
- Front-end developer
- Back-end developer
- Product Manager
- UI Designer
One-on-One conversation between a project Manager and a new IT Business Analyst on first day
PM: Welcome aboard! I’m Chris, your project manager. How are you today?
BA: Thanks, Chris! I’m excited to start. What project will I be working on?
PM: You’ll help enhance our systems. Your role involves system analysis, documentation, and gathering user requirements.
BA: Great! How do I begin with system analysis and documentation?
PM: Start by familiarizing yourself with our current systems and documenting any initial findings.
BA: And for gathering user requirements?
PM: You’ll work directly with clients, using our standard protocols. I’ll provide you with all the necessary training.
BA: What about collaborating with other teams?
PM: You’ll work closely with the development and Quality Control teams. They’ll help you with technical details and testing.
BA: Who do I contact for technical help?
PM: Reach out to Janet and Tom from development. For anything else, I’m here to help.
BA: Thanks, Chris. I appreciate the guidance. What’s the first step?
PM: Let’s get you set up with system access and some initial materials to review. We’ll touch base again soon.
BA: Sounds good. Looking forward to it!
PM: We’re glad to have you. Let’s make great progress together.
One-on-One conversation between a project Manager and a new IT Quality Control on first day
PM: Welcome to the team! I’m Chris, your project manager. How’s your first day going?
QC: Thanks, Chris! Excited to be here. What are the main projects I’ll be involved in?
PM: You’ll focus on ensuring our software meets quality standards. This involves testing, creating checklists, and facilitating User Acceptance Tests.
QC: Got it. What’s my first task?
PM: Start by acquainting yourself with our current testing protocols and software tools.
QC: Will I be working directly with the development team?
PM: Yes, you’ll coordinate with them to identify and resolve issues early in the development process.
QC: How should I report any problems I find?
PM: Document the issues clearly and discuss them in our weekly team meetings. Immediate concerns can be emailed directly to me.
QC: Understood. And who do I approach for technical guidance?
PM: Janet from development will help with technical specifics. You can also come to me with any overarching concerns.
QC: Perfect. Is there an existing schedule for the User Acceptance Tests?
PM: Not yet. We’ll need you to set up a timeline based on project milestones.
QC: I’ll draft a tentative schedule by the end of the week.
PM: That sounds great. We’re happy to have you onboard. Let’s make sure our products are excellent.
QC: Thank you, Chris. I’m ready to get started and contribute to our success.
PM: Excellent. We’re glad to have you. Let’s touch base at the end of the week.
One-on-One conversation between a project Manager and a new Front-end developer (FE) on first day
PM: Welcome! I’m Chris, your project manager. How are you feeling about your first day?
FE: Thanks, Chris! I’m excited to get started. What will I be working on first?
PM: We’re glad to have you. You’ll initially focus on improving the user interface for our main product. We’re aiming to enhance user experience and accessibility.
FE: Sounds interesting! Are there specific technologies or frameworks I should start with?
PM: Yes, you’ll mainly be using React and Javascript. Start by getting familiar with our current codebase and the design guidelines we follow.
FE: Got it. Who should I talk to for code reviews or when I have technical questions?
PM: Janet, our lead developer, will be your go-to for code reviews and any detailed technical issues. She’s great with React and has a deep understanding of our product’s architecture.
FE: Perfect. Will I be collaborating with any other teams?
PM: Absolutely. You’ll work closely with the UX/UI designers to ensure the technical feasibility of designs and with backend developers to integrate APIs smoothly.
FE: How often should I update you on my progress?
PM: Let’s have a brief daily check-in. For detailed updates, a weekly meeting should suffice. And of course, feel free to reach out anytime if you hit a major obstacle.
FE: Sounds good. What’s the best way to document my progress?
PM: Use our project management tool to log tasks and mark them as complete. Keep notes on any challenges or significant changes for our weekly review.
FE: Will do. I’m eager to dive in and contribute.
PM: We’re excited to see what you bring to the table. Let’s catch up at the end of the week to discuss your initial impressions and any support you might need.
FE: Looking forward to it, thanks Chris!
PM: Welcome aboard. Let’s make some great improvements together.
One-on-One conversation between a project Manager and a new Back-end developer (BE) on first day
PM: Welcome aboard! I’m Chris, your project manager. How’s your first day going?
BE: Thanks, Chris! I’m ready to get started. What are my main tasks?
PM: You’ll focus on building and maintaining server-side logic and managing our databases using Node.js and MongoDB.
BE: Which technologies are we integrating with?
PM: You’ll mainly integrate with front-end applications via APIs using Express.
BE: Who do I work with for API issues?
PM: Janet, our senior back-end developer, will assist with any complex problems. She’s great with system integration.
BE: How do we handle code reviews?
PM: Submit your code through GitHub. Janet or I will review it to ensure it meets our standards.
BE: What’s the update schedule?
PM: We have daily stand-ups for quick updates and a weekly meeting for detailed discussions.
BE: Where should I log my work?
PM: Use our project management tool to track your tasks and document issues.
BE: Any initial priorities?
PM: Start by familiarizing yourself with our existing APIs and then tackle any outstanding bugs to understand the codebase.
BE: Got it. Looking forward to contributing.
PM: We’re glad to have you. Let’s check in at the end of the week to discuss your progress.
BE: Thanks, Chris. I appreciate the overview.
PM: Welcome to the team. Let’s make some great progress together.
First day conversation between a product manager (PM) and their supervisor (SV)
SV: Welcome aboard, Alex! How’s your first day going?
PM: Thanks! I’m excited to get started. Can you outline my main responsibilities?
SV: Certainly. You’ll oversee the development and launch of our products, ensuring they align with business goals. You’ll bridge our technical teams and business units.
PM: What are our current product priorities?
SV: Focus on improving user experience and integrating customer feedback. We also have new product launches coming up.
PM: How often should we review progress?
SV: Weekly for regular updates and monthly for strategic reviews.
PM: Which teams will I work with closely?
SV: Mainly engineering, marketing, and customer service. Effective collaboration is key.
PM: What tools do we use for project management?
SV: We use Agile methodology and Jira for project tracking.
PM: Any initial steps I should take?
SV: Get to know your team and familiarize yourself with our product roadmaps and key customers.
PM: Sounds good. I’ll start on that right away.
SV: Great. I’m here if you need any guidance. Excited to see your impact.
PM: Thank you, I appreciate the support.
SV: Welcome again. Let’s achieve great things together.
One-on-One conversation between a project Manager and a new UI Designer (UI) on first day
PM: Welcome to the team, Jordan! How are you feeling about your first day?
UI: Thanks, I’m excited to be here! I’m eager to learn more about our projects and how I can contribute.
PM: That’s great to hear. Your main role will be to design intuitive and aesthetically pleasing user interfaces for our digital products.
UI: What projects will I start with?
PM: Initially, you’ll work on redesigning the user interface for our flagship app. We’re aiming to enhance user experience and increase engagement.
UI: Do we have existing design guidelines and user feedback I can use as a starting point?
PM: Yes, we have a style guide and user feedback reports. I’ll make sure you get access to those. It’ll help align your designs with our brand and user expectations.
UI: Who will I collaborate with mostly?
PM: You’ll work closely with the UX team and front-end developers. Regular coordination will ensure that your designs are feasible and implemented accurately.
UI: How often do we have project meetings?
PM: We meet weekly to review progress and discuss any design challenges. Additionally, we have daily stand-ups where you can give quick updates.
UI: What tools do we use for design and collaboration?
PM: We primarily use Sketch for UI design and Figma for collaborative design work. You’ll also use Jira for tracking tasks and deadlines.
UI: Sounds good. Is there a priority task I should focus on this week?
PM: Yes, start by familiarizing yourself with our current app design and brainstorm initial redesign ideas. We’ll review them in our next meeting.
UI: Will do. I’m looking forward to making a positive impact.
PM: We’re excited to see your creativity in action. Let me know if you need anything to get started.
UI: Thank you, I appreciate it.
PM: Welcome again, Jordan. Let’s create something great together.
Listening
Answer the questions following video:
- What time is Jessica’s lunch break?
- Jessica’s lunch break is at 12:30pm and lasts for one hour.
- Jessica’s lunch break is at 12:30pm and lasts for one hour.
- Jessica will be reporting to Miss Johnson at her new job.
- Jessica will be reporting to Miss Johnson at her new job.
- Jessica is asked to focus on learning the company’s rules and policies during her first few days, and can also start on the orientation paperwork.
Discussion
- What are the essential elements (yếu tố thiết yếu) of an effective onboarding program?
Example answer: I think an effective onboarding program should include a warm welcome, clear explanations of my job responsibilities, thorough training sessions, and access to a mentor. These elements help me feel supported and confident as I start my new role.
- How can new employees prepare to get the most out of the onboarding process?
Example answer: I think that, to get the most out of the onboarding process, new employees should start by researching the company’s culture and values to better understand the environment they will be joining. It’s also helpful to prepare a list of questions about the role and responsibilities to ask during training sessions. Engaging actively by seeking feedback and making an effort to connect with new colleagues can further enhance the onboarding experience and help new employees integrate more effectively into the team.
- What do you think about inviting drinks and snacks/foods for everyone in the company on your first day at work?
Example answer: I think it’s a friendly gesture. It can help make a good first impression and show your new colleagues that you’re approachable and kind. However, make sure this fits the company culture.
- Nowadays, many companies work online/remotely. Do you think onboarding is still necessary?
Example answer: Yes, onboarding is still necessary for remote jobs. It helps new employees understand their roles and the company even if they are not physically present. Effective onboarding can build a strong foundation for remote work by ensuring employees feel connected and informed.
Tài liệu đầy đủ: https://drive.google.com/file/d/1VqdmmudJDNqxrEWFOfUWQp_k7p8oXcwn/view?usp=sharing
