All levelsVocabulary#soft-skills#professional-english#teamwork#communication
Soft Skills Vocabulary for IT
5 exercises — the professional vocabulary every developer, analyst, and engineer needs: alignment, bandwidth, escalation, stakeholder, and mentorship. Use these words correctly in meetings, Slack messages, and performance reviews.
Essential IT soft-skills vocabulary
Alignment — shared understanding of goals/direction across a team or org
Bandwidth / capacity — available time and resources to take on work
Escalation — raising an issue to a higher authority; expected and professional
Stakeholder — any person/group with interest in the project outcome (broader than "user")
Buy-in — support or agreement from key parties before a decision
Mentorship — ongoing guiding relationship for professional growth
Ownership — taking responsibility for a feature, system, or outcome end-to-end
Blockers — obstacles preventing progress; surfaced in standups and retrospectives
0 / 10 completed
1 / 10
During a sprint planning, a team lead says: "We need to make sure everyone is on the same page about the product direction before we commit to the roadmap." Which soft-skills term best describes the goal of this conversation?
Alignment in an IT context means ensuring that all stakeholders share the same understanding of goals, direction, or decisions. "Getting aligned" is a standard phrase in sprint planning, OKR setting, and cross-team meetings. Related phrases: "Let's align on the priorities for Q3." / "Are we aligned on the acceptance criteria?" / "We need cross-team alignment before the launch." Escalation (option A): raising an issue to a higher authority or management level because it cannot be resolved at the current level — e.g., "I need to escalate this blocker to the VP." Bandwidth (option C): available capacity to take on work — "I don't have bandwidth for that this sprint." Buy-in (option D): support or agreement from stakeholders, often before a decision is made — "We need buy-in from the security team before deploying." Buy-in is close to alignment but more specifically refers to obtaining approval or commitment, not just shared understanding.
2 / 10
An engineer says to their manager: "I can't pick up the new feature this week — I'm fully committed to the migration and two critical bug fixes." Which word best replaces "fully committed to" in professional IT English?
Both bandwidth and capacity are widely used in IT teams to mean "available time and resources to take on work", and in everyday professional communication they are largely interchangeable. Bandwidth comes from networking (the maximum data transfer rate) but is used metaphorically for human/team workload capacity. You'll often hear it in agile/startup environments: "Do we have bandwidth to take on another initiative?" Capacity is the more formal term, used in capacity planning, sprint capacity calculations, and resourcing discussions: "Team capacity this sprint is 40 story points." Availability (option D) is not wrong but is less common in this context — it usually implies scheduling ("Are you available Tuesday at 2?") rather than workload. In daily standups you'll hear: "I don't have bandwidth/capacity for this because I'm blocked on..." ↔ "I have spare capacity if anyone needs help."
3 / 10
A junior developer is working on a new payment module. They encounter a security issue beyond their authority to fix. Their team lead is on vacation. What is the correct action, and what is it called?
Escalation is the formal process of raising an issue, blocker, or decision to a higher level of authority when it cannot be resolved at the current level. It is a standard, expected practice in professional IT environments — not a sign of failure. When to escalate: security or compliance risk beyond your authority → when a blocker affects delivery timelines → when a decision requires resources you don't control → when a conflict can't be resolved between peers. How to escalate professionally: "I want to flag a security concern that's outside my authority to address — I'm escalating to you so we can decide on next steps." Escalation vocabulary: "escalate an issue", "escalation path", "escalation matrix" (who to contact for what type of issue), "escalate to management/stakeholders". What NOT to do: option C (parking) silently delays risk; option D (silent self-resolution) bypasses governance. Option A (ownership transfer / delegation) is different — it's choosing who does the work, not raising a risk.
4 / 10
A product manager writes in a project brief: "The primary stakeholders for this feature are the sales team, the compliance team, and five enterprise customers." Which definition of "stakeholder" is correct in this context?
A stakeholder is any individual, team, or organisation with an interest in or impact on the outcome of a project — regardless of whether they use the product directly or approved the budget. Stakeholders can be: Internal — engineering, product, design, legal, sales, compliance, senior management. External — customers, partners, regulators, investors. Stakeholders vs. end users: "end users" are the people who use the product daily; stakeholders is a broader category that includes users but also business and regulatory parties who have interests even if they don't touch the UI. Key phrases: "stakeholder management" (communicating with and balancing the needs of stakeholders), "stakeholder mapping" (identifying who has interest and influence), "key stakeholders", "stakeholder requirements", "stakeholder sign-off". In practice: "We'll hold a stakeholder review before the feature goes to production." Related: "RACI matrix" — Responsible, Accountable, Consulted, Informed — a common tool for mapping stakeholder roles.
5 / 10
A senior engineer regularly reviews junior developers' PRs with detailed feedback, answers questions, and helps them grow into independent contributors. What is this practice called, and which word best describes the senior engineer's role?
Mentorship is an ongoing relationship where an experienced professional (the mentor) guides and supports the growth of a less experienced person (the mentee). It goes beyond code review — it includes career guidance, knowledge transfer, skill development, and professional confidence building. In IT contexts, mentorship includes: reviewing and explaining PR feedback in depth rather than just approving. Discussing engineering trade-offs and reasoning. Guiding career development. Providing safe space to make and learn from mistakes. Related terms: Code review (option A) — evaluating specific code changes for quality, correctness, style. Can be part of mentorship but is narrower. Pair programming (option C) — two developers working together on the same code simultaneously, real-time: driver (writes code) + navigator (reviews and guides). Onboarding buddy (option D) — someone assigned to help a new hire during their first weeks; often time-limited and role-specific, not a long-term growth relationship. Key phrases: "mentorship programme", "act as a mentor to", "mentor-mentee relationship", "give mentorship", "seek out a mentor".
6 / 10
Sarah, a UX designer, sends a Slack message to the development team: 'Hey guys, just wanted to flag that the proposed UI for the new dashboard is causing significant usability issues. We need to iterate quickly!' What soft skill does Sarah primarily demonstrate in this message?
Sarah's message highlights her ability to identify and communicate potential problems early on. 'Proactive communication' accurately describes this behavior, as she's actively raising concerns before they escalate. The other options represent less effective responses – simply stating a design isn't pleasing doesn't address the usability issue, and passive observation or delayed feedback would be detrimental.
7 / 10
During a code review, David comments on Maria's PR: 'This section could benefit from clearer variable names to improve readability.' What is the most appropriate technical term for David's suggestion?
'Refactoring' specifically refers to restructuring existing code without changing its functionality – in this case, improving variable names is a key aspect of refactoring. While 'code clarity' captures the goal, 'refactoring' is the more precise technical term used within development teams. 'Optimization' and 'technical debt' relate to different concerns.
8 / 10
Alex, a team lead, is writing a Pull Request description for a new API endpoint. He writes: 'This PR introduces the /users endpoint, which allows clients to retrieve user data.' Which of the following best describes Alex's approach?
Alex is creating 'technical documentation,' which is crucial for explaining the purpose and functionality of a new API endpoint. This type of documentation provides clarity for other developers who will be using or maintaining the code. The other options represent different stages of the development process—a user story focuses on the *why*, an API design review examines the overall architecture, and a feature specification outlines broader requirements.
9 / 10
During a standup meeting, Ben says: 'I'm currently focused on resolving the high priority bug in the payment processing module and documenting the new authentication flow.' What does Ben demonstrate through his statement?
Ben's statement clearly demonstrates 'prioritization,' as he identifies the most critical task (the bug) and acknowledges his commitment to it. This is a common practice in software development to focus on immediate needs. The other options represent different concepts—task delegation involves assigning work, scope creep refers to uncontrolled expansion of project requirements, and risk mitigation focuses on identifying potential problems.
10 / 10
Emily is mentoring a new developer, Liam. She consistently provides detailed feedback on his pull requests, answers his questions thoroughly, and helps him understand best practices. What is this process called?
'Knowledge transfer' accurately describes Emily's role in mentoring Liam. She is actively sharing her expertise and guiding him to become a more proficient developer. While the other options relate to aspects of software development, they don't capture the core element of mentorship: the passing on of information and skills.
What does the "Soft Skills Vocabulary for IT" vocabulary exercise cover?
This exercise tests real IT vocabulary related to soft skills vocabulary for it through 10 multiple-choice questions, each built from realistic workplace sentences rather than abstract definitions.
Is this vocabulary exercise free to use?
Yes. Every exercise on CoderSlingo, including this one, is completely free — no account, sign-up, or payment required.
How many questions does this exercise have?
This exercise has 10 questions. Each one shows a real-world sentence or scenario with multiple-choice options and an explanation once you answer.
What happens after I answer a question?
You'll see immediate feedback showing whether your answer was correct, along with a short explanation of why — then a button to move to the next question, and a full results screen at the end.
Can I retry the exercise if I get questions wrong?
Yes. Once you reach the results screen, click "Try again" to reset your answers and go through the exercise from the start as many times as you like.
Do I need to create an account to take this exercise?
No account is needed. Your answers are scored in your browser during the session — nothing is saved to a server, so you can jump straight in.
Is my progress saved if I leave the page?
No — progress within an exercise resets if you navigate away or reload. Each exercise is short enough to complete in a few minutes in one sitting.
Are these vocabulary exercises connected to other topics?
Yes — browse the full vocabulary exercises hub to find related modules covering adjacent IT topics and roles.
How is this different from reading a glossary or blog article?
Exercises like this one are active recall drills — you have to choose the correct term or phrasing yourself, which builds retention faster than passively reading a definition.
Where can I find more vocabulary exercises?
Browse the full Vocabulary exercises hub for hundreds of modules covering Agile, DevOps, security, databases, architecture, and more — organised by IT role and skill.