After this lesson, you will be able to: Develop the soft skills every hiring process tests and every job requires: technical communication, code review as communication, the STAR method for behavioral interviews, offer negotiation, and remote-work effectiveness.
Technical skills get you the interview; soft skills get you the offer and the promotion. This lesson, referenced by the Job Readiness lesson in every track, covers technical communication, code review as a communication act, the STAR method for behavioral interviews, negotiating an offer, and remote-work skills. These are consistently underprepared for and consistently decisive.
The most valued senior engineers can explain a complex decision to a non-technical stakeholder, write a clear design document, and document a post-mortem. The skill is translation: lead with the outcome and the why, not the implementation; use plain language and analogies for non-technical audiences; and structure writing so a busy reader gets the point in the first two sentences. A design doc states the problem, the options considered, the decision, and the tradeoffs. Practice explaining your last project to someone outside tech.
Code review is a human interaction, not just a quality gate. Giving feedback: be specific and actionable ('this can throw if items is empty, consider a guard' beats 'fix this'), separate blocking comments (must change) from non-blocking suggestions (nits, preferences), and critique the code, not the person. Receiving feedback: assume good intent, do not take it personally, ask questions instead of defending, and thank reviewers. How you behave in code review is one of the strongest signals of seniority.
Behavioral interviews ('tell me about a time when...') are best answered with STAR: Situation (brief context), Task (what you were responsible for), Action (what you specifically did), Result (the outcome, ideally quantified). Most candidates ramble on situation and skip the result; flip that. Prepare three or four STAR stories covering conflict, failure, leadership, and a technical challenge, and adapt them to the question. Example: 'A deploy broke checkout (S). I owned the fix (T). I rolled back, traced it to a migration, and added a CI check (A). We restored service in 20 minutes and the check has caught two issues since (R).'
Total compensation is more than base salary: bonus, equity (and its vesting and real value), benefits, and growth. Evaluate the whole package, not just the headline number. Almost everything is negotiable, especially at larger companies; the worst case is they say no. Negotiate respectfully and with a specific number backed by market data, and get competing context if you have it. At a startup, equity and learning may outweigh cash; at a big company, cash and stock are more concrete. Never accept on the spot if you want to think; 'thank you, may I have until Friday' is normal and expected.
Most tech roles are remote or hybrid, and remote work rewards different skills. Async communication: write clearly enough that people in other time zones can act without a meeting. Written clarity: a good message states the context, the ask, and the deadline. Build visibility when no one sees you work: share progress proactively, document decisions, and make your work legible. Respect time zones in scheduling. The engineers who thrive remotely over-communicate in writing and make their contributions visible without being asked.
Pick one.
Rambling through the Situation and skipping the Result in behavioral answers. Code-review comments that attack the person or are vague. Accepting the first offer without negotiating (leaving money on the table). Evaluating only base salary and ignoring equity and growth. Going silent in remote work and being invisible at promotion time. Assuming soft skills are innate rather than practiced; they are learnable and decisive.
Sign in and purchase access to unlock this lesson.