e-Manual by Emmanuel: Part 1

Emmanuel Jose (he/him)
31 min readOct 12, 2020


Success After Coding Bootcamp: Soft Skills and Interview Questions

Photo by Tim Mossholder on Unsplash


If you’re about to graduate or have recently graduated from a coding bootcamp program, Congratulations! You’re on your way to the rest of your life — You got this!

  • If you’re nervous about searching for a job, it’s okay to be stressed!
  • Finding a job is a job in itself, but it doesn’t have to be as unnerving as you think.
  • I’m about to graduate from a coding bootcamp in a few weeks, and as I start focusing on the job search, I’ve collected nuggets of knowledge from instructors, alumni, workforce/training professionals, and Google.
  • In this e-Manual: Part 1, the focus will be on the value of soft skills and non-technical job interview questions.
  • Disclaimer: There won’t be much on whiteboard/technical interviews.
  • Keep an eye out for e-Manual: Part 2, which will cover networking and tips on how to enhance your LinkedIn and social media presence.

There is a lot of information here, but feel free to read the sections out of order, or read just the ones you’re interested in!


Click on section banners to return to the Table of Contents at any time.

The TOC and banner links do not work on the mobile app. Apologies for the inconvenience.


Soft Skills

The Cultural Fit Interview

Virtual Interviews

Non-Technical Interview Questions

100 More Interview Questions

The STAR Interview Format

If You Don’t Know How to Answer

Thanking Your Interviewer

Whiteboard/Technical Interviews

Salary Negotiation

The Key Takeaway

YouTube Resources



Soft Skills are the non-technical attributes you need for success on the job. Soft skills involve your personality, interpersonal skills, communication skills, and how you work with others. Soft skills are people skills.

Programming involves logic, code, and algorithms, but at its heart, Programming is about people.

  • As a developer, you work with people.
  • As a developer, you create for people.
  • A program can have perfect functionality, but no program is complete without the user.

Below are a few critical soft skills that employers will always look for.


Empathy is the capability to put ourselves in the place of another person and experience their feelings. It’s a valuable skill that enables us to interact effectively and harmoniously with everyone. Empathy is the foundation of successful collaboration and for creating a positive user experience.

The first step in developing empathy is to acknowledge that the world doesn’t revolve around you. Pause to consider someone else’s thoughts and perspective:

  • If I were in their position, what would I be thinking right now?
  • How am I affecting their feelings and experience?
  • How can I help?


At a coding bootcamp, you may have disliked having paired programming labs or paired projects. However, as a professional developer, you will continue to have paired or team collaborations, and the value of effective communication cannot be overstated.

As developers, we deal with abstract and confusing vocabulary, and often from multiple programming languages. Remember to simplify and stay on message:

  • Speak clearly and with confidence.
  • Listen more than you speak.
  • Don’t memorize vocabulary, be able to understand the concepts instead.
  • Communicate with verbal and non-verbal cues.


Empathy and Communication contribute directly to teamwork skills. In this Covid-19 era, many tech companies have shifted to remote work. You may be working from home and perform the bulk of your responsibilities alone. But no person is an island. You will be interacting with others.

Regardless of the changing workplace landscape, “you should be able to think of your work in the context of the company’s broader goals and communicate your accomplishments to other people within the organization.”

There will be times when you disagree with your colleagues, but successful teams thrive from diverse and different points of view. The tricky thing with developing teamwork skills is that they cannot be practiced on your own. It takes time and involves others, but a question to always ask yourself is:

“Do I want to work with myself?”

If the answer is not an enthusiastic “Yes!,” then consider these tips:

  • Ask for feedback often (if you are in contact with your cohort and instructors, ask them! Your family and friends will also be brutally honest).
  • Be open.
  • Don’t assume.
  • Expand your perspective.


These skills are a two-way street. No matter how independent or self-sufficient you are, you will need help, and it’s okay to ask for help.

If you don’t establish rapport with others, it will be difficult to find help when you need it. When you put people at ease, they’re more likely to help you and trust you.

Being approachable and helpful does not mean you have to be loud, talkative, extra-cheerful, or extroverted. It does, however, involve making the first move to build interaction, but anyone can develop approachability by being present and by being fully engaged when communicating.

You don’t have to put up a front to be approachable or helpful. Put yourself in a position to open up and share a little. By being Real, you will be relatable.


Just because you’re seeking employment as a developer, it doesn’t mean you’ll only interact with developers on the job. In fact, the opposite may be true.

Your patience will be tested every time you collaborate with colleagues and clients who are not developers. They’ll have many questions, just like you did when you were brand new to programming!

Practice explaining concepts to family and friends who do not have a technical background. You’ll also gain greater clarity on concepts by being able to explain them to someone else.

Your patience will also be tested when you are tasked with something you don’t agree with, or is completely beyond a feasible scope. Take a step back to assess, and do not make rash decisions. Think things through. You will save yourself a lot of frustration by being able to effectively communicate your reservations and by answering your colleagues’ questions.


Open-mindedness is about being receptive to new ideas, experiences, and ways of living that differ from your own. Tolerance is a huge factor in this, and you’ll be working with people with different life experiences than you.

Take the time to know everyone without judgment and critique. Respect goes a long way, and you’ll be surprised how much you actually have in common with others.

When you’re open-minded with your colleagues, clients, and even yourself, you’ll develop an ability to turn so-called bad ideas into good ideas. Inspiration can strike at any time, so don’t immediately dismiss ideas and practices that initially appear to have no value or use.

Keep your mind open, because the programs you create will leave your hands and enter the hands of users. They’ll have the best insight for what works and what doesn’t work.


Problem-solving involves many of the soft skills listed here. How you approach problems and how you go about resolving them has a ripple effect on your own personal experience and that of your colleagues and users.

At a coding bootcamp, you were presented with bugs and problems on a regular basis, and that will continue when you’re a working developer. What a coding bootcamp does best is that it teaches you how to think, and that skill can be applied to any problem, even if it’s one you’ve never seen before.

Problem-solving Steps:

  • Define the problem. Break it down objectively and into smaller parts.
  • Ideate. Brainstorm all possible solutions and ask for help. Fresh eyes are critical to view problems and solutions from different angles.
  • Decide on a solution. Evaluate, assess, and keep an open mind. Consider all factors such as implementation, resources, and time. How does the solution meets all objectives and deliverables and how does it fit with policies and procedures?
  • Implement the solution. Develop an action plan and clearly communicate directives and feedback channels.
  • Monitor Progress and Make Adjustments. Continually measure progress and review data and feedback from others. Implement new or alternative solutions if needed.


We’re Human. We all make mistakes — Don’t hide or run from them.

No matter how difficult it might be to acknowledge your mistakes, take full ownership of them and admit responsibility.

Don’t make excuses, ignore the issue, or blame others. Own it.

When in doubt, this skill’s all about doing what you say you’re going to do. This is the core of integrity and it builds trust.”

You’ll earn the trust and respect of your colleagues by being forthcoming, and every mistake is an opportunity for growth and learning.


Whether you know it or not, Programming is an art. As developers, we create all the time, and creativity is crucial for innovation and problem-solving.

Creativity is frame of mind, and it can be developed:

  • Learn a new language. Branch out and learn new skills.
  • Start from the ground up. Square One is your friend. We all have to begin from somewhere.
  • Question everything. Tear down any assumptions.
  • Do it for Fun. Build numerous and small personal projects.
  • Never Stop Testing Ideas. Ideas change over time, and refinement brings improvement.
  • Find a Passion. It’s not about “how,” it’s about knowing your “Why.”
  • Master Your Tools. Practice, play, experiment, break, and test.
  • Make Abstract Associations. How would you design a container for bubbles? How do I turn a fridge into a bike? The more absurd, the better.
  • Think of structures as tools, not limitations. Necessity is the mother of invention.
  • Don’t Knock It till You Try It. There are no stupid questions or ideas. Never assume anything until you’ve tried and tested it.
  • Remember to KISS: Keep It Simple, Stupid. Laziness is a virtue of programmers.
  • Build off the Code of Others. Code is open source, and you don’t have to reinvent the wheel. A great idea is sometimes just modifying what’s already been done.
  • Collaborate. Be inspired by others, and let a shared goal fuel a brilliant flow of ideas.
  • From the Basic, Create the Beautiful. Like Legos, programmers can take very basic code to build beautiful programs. Marvel in the possibilities and be mindful of the big picture.
  • Fantasize and Daydream. All. The. Time.


Time management is a hard skill to master, and it’s crucial for any job. Fortunately, you’ve gotten a good taste of how important it is in your coding bootcamp journey. With every lab and every project, you’ve become project managers in your own right.

Developing better time management skills will require planning and reflection on your part. Adopt these following strategies:

  • Make a To-Do List. It sounds so simple, but this will help to prioritize everything you want to accomplish.
  • Learn to use Calendars. You can’t remember everything, calendars are your friends!
  • Avoid Multi-Tasking. Your attention will be divided and you’ll be less productive than if you just focus on one task at a time.
  • Limit interruptions. If possible, create a calm workspace environment for yourself. Turn off non-essential notifications, and cut down on constantly checking your phone.
  • Set Goals. No matter how big or small, work on accomplishing short and long-term goals on firm deadlines, and remember to reward yourself!
  • Learn to say “No.” By staying on track, you earn the respect of yourself and everyone around you.
  • Stay Organized. Clutter will only cloud your progress. Organize your workspace, your desktop, your bookmarks, your files. Clean it all up!
  • Apply the Pomodoro Technique. Embrace the power of the tomato.
  • Create a Kanban Board to visualize workflow. Buy a lot of Post-it Notes.
  • Take Care of Yourself. Self-care, de-stress, eat well, and get enough sleep.


The previous section was lengthy and covered just a few soft skills for a reason. You’ve put in a lot of hours at coding bootcamp, but the vocational and technical skills you’ve gained do not guarantee you employment.

Ultimately, an employer wants to know the answers to these questions:

“Do I want to work with you?”

“Will you fit in with the company?”

“Will you thrive in our environment?”

Often, the cultural fit interview is the first interview. How you are as a person is more important than your technical prowess. Cultural fit is also crucial for staff retention, engagement, productivity, cohesion, and communication. Now more than ever, there is a greater priority on determining cultural fit before hiring an employee.

In some situations, you may even bypass whiteboard technical interviews by excelling in the cultural fit interview.

Do your homework when you apply for various companies. Know the culture, values, principles, and mission statements of companies you’re interested in. If a company’s culture resonates with you, research further and inquire, but don’t waste anyone’s time if you haven’t done the homework.

In any interview (virtual or in person) remember to:

  • Breathe, exhale, and slow down.
  • Think before you speak.
  • Showcase your personality and soft skills.
  • Speak clearly and with conviction.
  • Maintain eye contact and engage.
  • Be an active listener.
  • Be mindful of your body language.
  • Wear professional or business attire, and have great hygiene.
  • Tell your inner saboteur and imposter syndrome to shut up!
  • Recognize that you bring immense value outside of the scope of your technical skills and expertise.
  • Don’t speak ill of previous employers, colleagues, or yourself.
  • Keep in mind that it comes down to the human connection. Programming is about people.
  • Be Genuine. Be Yourself.


With more tech companies working remotely due to the pandemic, virtual or video interviews are here to stay. It’s important to implement these tips to show you in the best light (literally and figuratively):

  • Find a quiet, private, well-lit location, free of distractions.
  • Ensure your computer is fully charged.
  • Test and ensure your internet connection is stable and strong.
  • Test and ensure your computer audio and webcam are working.
  • Test and ensure any supplemental light sources are working.
  • If you’re interviewing from home, communicate with your household ahead of time about minimizing distractions and noise.
  • Clear unnecessary web browser tabs and applications, and have appropriate desktop wallpaper. You may be asked to screen-share if you showcase projects or answer technical questions.
  • If you’re asked to share projects on Github, Heroku, or other servers, have them available and ready to launch.
  • Dress professionally, and avoid bright colors that may affect the lighting.
  • Have a pen, notepad, and a copy of your resume on your desk.
  • Use appropriate body language and hand gestures.
  • Practice looking into the camera of your computer (or webcam) instead of looking at your monitor. Eye contact is critical.
  • Silence any computer or phone notifications for the duration of the interview.
  • If you know the time of the interview well in advance, practice your virtual interview at that designated time for a few days. For example, if you have a Zoom interview on Tuesday at 2:00 pm, ask your family and friends to rehearse mock interviews with you on Zoom at 2 pm on Friday, Saturday, Sunday, and Monday. This way, you’ll get a sense of how to properly set up your environment and lighting. You’ll also be able to mentally prepare for the time of the interview.

Setting up for a virtual interview

In-depth preparation for a virtual interview


Always ask family and friends to rehearse mock interviews with you. Mock interviews are an excellent way to practice public-speaking.

It’s also a great idea to have mock interviews with your cohort classmates, and you can take turns with each other asking questions. Your classmates have spent the last 3 to 6 months with you, and they have excellent insight as to how you are over virtual meetings.

If you prepare answers for all the following questions, you’ll be able to anticipate the majority of any non-technical interview questions directed at you.

Rehearse, Rehearse, Rehearse.

  • Tell me about yourself. This is the “30-second pitch” or “elevator pitch,” and it’s the most crucial question to prepare for. Master your answer to this, and it will successfully set the tone and foundation for all other questions to follow.
  • Why do you want to be a [your intended profession]?
  • Why are you interested in [coding / software engineering / programming / front-end / back-end / field of study]?
  • What are you looking for [in a job / in your next step]?
  • Walk me through your career history and background.
  • What have you built/created? (Be prepared to show projects, see section on Virtual Interviews)
  • What intrigued you about this role or company?
  • Why do you want to work for our company?
  • What are your weaknesses?
  • What are your strengths?
  • What are your salary expectations? (See section on Salary Negotiations)
  • What did you learn in the [coding bootcamp] program?
  • How was your experience in the [coding bootcamp] program?
  • What is one thing you like most about your current manager, and what is one thing you would change?
  • Give me an example of someone that you coached and developed and were able to promote. What did you work on with them to make it happen? (This question applies if a company is hiring for a managerial role)
  • Can you share a story (about anything) that speaks to who you are from a values perspective?
  • What is your perfect job?
  • How would you describe yourself in one word? (Don’t just blurt something out. Think and take time to reflect before answering)
  • Give me an example of a time that you lost your temper. Tell me what happened. What was the outcome?
  • Tell me about a time you made a mistake. What did you do to fix it?
  • Why do you think we should hire you over other qualified candidates?
  • How long are you willing to fail at this job before you succeed?
  • What are some of your hobbies?
  • What was the reason for leaving your last position?
  • What questions do you have for me?


  • What are the three things that are most important to you in a job?
  • Tell me about a time in the last [week / month / year] when you’ve been satisfied, energized, and productive at work. What were you doing?
  • What’s the most interesting thing about you that’s not on your resume?
  • What would make you choose our company over others?
  • What’s the biggest misconception your [family / friends / coworkers / classmates / teachers] have about you and why do they think that?
  • Describe the work environment or culture in which you are most productive and happy.
  • What are the characteristics exhibited by the best boss you have ever had — or wish that you have had?
  • In your experience, how does an organization encourage your use of discretionary energy and effort to get the job done? Discretionary energy is the willingness each employee has to go the extra mile, push harder, spend more time, and do whatever is necessary (or lack thereof).
  • Describe the management style that will bring forth your best work and efforts.
  • Describe what you believe are the most effective roles that a good manager plays in his or her relationship with reporting staff members.
  • Do you have a best friend at work? How do you feel about becoming friends with your coworkers? Is this a wise practice?
  • What are the positive aspects of your current job and work environment, or the last position you held before coming to this interview?
  • What is the single most important factor that must be present in your work environment for you to be successfully and happily employed? Now that you have answered that question, what were two others that you debated about responding before you gave the response that you chose?
  • What is your preferred work style? Do you prefer working alone or as part of a team? What percentage of your time would you allocate to each, given a choice?
  • How would your co-workers describe your work style and contributions in your former job?
  • What are the three to five expectations that you have of senior leaders in an organization where you will work successfully?
  • Tell us about an occasion when you believe that you delighted a customer, either an internal or an external customer.
  • When you work with a team, describe the role that you are most likely to play on the team.
  • How would co-workers describe the role that you play on a team?
  • When working with people, in general, describe your preferred relationship with them.
  • How would reporting staff members describe their relationship with you? What would they like to see you do more of, less of, start, and stop?
  • Provide an example of a time when you went out of your way and jumped through hoops to delight a customer.
  • Tell us about a decision that you made that was made based primarily on customer needs and input.


  • Tell me about a time when you were asked to do something you had never done before. How did you react? What did you learn?
  • Describe a situation in which you embraced a new system, process, technology, or idea at work that was a major departure from the old way of doing things.
  • Recall a time when you were assigned a task outside of your job description. How did you handle the situation? What was the outcome?
  • Tell me about the biggest change that you have had to deal with. How did you adapt to that change?
  • Tell me about a time when you had to adjust to a colleague’s working style in order to complete a project or achieve your objectives?


  • Give an example of when you had to work with someone who was difficult to get along with. How did you handle interactions with that person?
  • Tell me about a time when you were communicating with someone and they did not understand you. What did you do?
  • Tell me about one of your favorite experiences working with a team and your contribution?
  • Describe the best partner or supervisor with whom you’ve worked. What part of their managing style appealed to you?
  • Can you share an experience where a project dramatically shifted directions at the last minute? What did you do?


  • Tell me about the last time something significant didn’t go according to plan at work. What was your role? What was the outcome?
  • Describe a situation where you needed to persuade someone to see things your way. What steps did you take? What were the results?
  • Give me an example of a time when you felt you led by example. What did you do and how did others react?
  • Tell me about the toughest decision you had to make in the last six months.
  • Have you ever had to “sell” an idea to your coworkers or group? How did you do it? What were the results?


  • Recall a time when your manager was unavailable when a problem arose. How did you handle the situation? With whom did you consult?
  • Describe a time when you volunteered to expand your knowledge at work, as opposed to being directed to do so?
  • What would motivate you to make a move from your current role?
  • When was the last occasion you asked for direct feedback from a superior? Why?
  • What’s the biggest career goal you’ve ever achieved?


  • Tell me about a time when you had to juggle several projects at the same time. How did you organize your time? What was the result?
  • Tell me about a project that you planned? How did you organize and schedule the tasks?
  • Describe a time when you felt stressed or overwhelmed. How did you handle it?
  • Give an example of a time when you delegated an important task successfully.
  • How do you determine what amount of time is reasonable for a task?


  • Why should I not hire you?
  • How would your manager describe you? Now tell me, how would your best friend describe you?
  • It’s 12 p.m. one year from now. What are you doing?
  • Is it better to submit a project that’s perfect and late, or one that’s good and on time?
  • On a scale of 1 to 10, how weird are you?


  • What’s the biggest opportunity for this role?
  • What’s the most challenging element about this role?
  • What does success look like in this position?
  • If you could describe your team in 3 words, what would they be and why?
  • What type of person works well with this team?
  • How did the company determine its mission?
  • Why do people say [ ___ ] about your company?


  • If you know what companies you’ll be interviewing for, check out their Github.com accounts. Often, tech companies will post their job interview questions and any take-home tasks on their Github.


This is a technique you can use when answering behavioral interview questions, which often begin with these phrases:

  • Tell me about a…
  • Describe a situation…
  • What do you do when…
  • Give me an example of…
  • Have you ever…

The STAR format will be your best friend in crafting and articulating answers to interview questions, and it breaks down into:

  • S (SITUATION) = Set the scene and describe the SITUATION in which the example took place. Explain the context of the situation and why it connects to the interview question.
  • T (TASK) = Describe the TASK at hand, and the role and responsibility you had. Describe the problem or issue to be resolved in relation to the task. Avoid negative judgmental statements and stick to the facts.
  • A (ACTION) = Explain the specific ACTION you took to address the situation. In what way did you resolve, complete, or overcome the challenge? A great answer will highlight how you added value to the situation and made logical decisions.
  • R (RESULT) = Explain the RESULT and outcome of the situation. A great answer includes concrete examples and quantifiable achievements, and you should explain the direct effects of your actions. If your actions did not result in success for the team or company, focus on what you learned and gained from the experience.

Practice, practice, practice structuring your answers in the STAR format. With preparation and strategy, your answers will feel natural and comfortable to talk about.

Examples of STAR format answers from Indeed.com:

Question: Tell me about a time you overcame a challenging situation at work.

Situation: “At my previous job, our senior graphic designer resigned without any notice. Since she led the graphic design team, we initially didn’t know what to do in her absence.”

Task: “As the junior graphic designer, I decided to take it upon myself to make sure all of her work was completed on time and to the client’s standards.”

Action: “To do this, I met with the creative director, and asked him to train me in the areas of her job I was not familiar with. Then, I worked through my lunch breaks for a week straight to get the work done. I delegated easier tasks to the interns.”

Result: “In the end, the client ended up loving the work. We were actually able to get the work done a day early. The creative director was so impressed by my efforts that he offered me a promotion as the senior graphic designer.”

Question: Describe a situation when you had to work with a difficult customer.

Situation: “When I worked at the garden nursery, one customer was upset that we did not have her favorite tulips in stock.”

Task: “As the customer service representative, it was my responsibility to think of a solution to her problem. A major part of my job was to make sure the customers left the store happy.”

Action: “After checking our inventory, I saw that she was incorrect, so I kindly explained that we moved the tulip display. I guided her to the display. She said that we didn’t have enough for her garden, so I contacted our seller to speed deliver more of the bulbs.”

Result: “Since I took the time to work with this customer, she went from upset to happy during our interaction. Later that evening, I noticed that she left us a 5-star online review and mentioned my name.”


Alison Doyle from www.thebalancecareers.com writes:

  • Stay Calm and Composed. Consider saying “That’s a great question, can I take some time to consider it and get back to you later?” or “Great question! I can answer it in part but would like to consider it further and get back to you.”
  • Buy Some Time. Rephrase the question or ask for clarification. Consider saying “That question is a bit of a stumper! Can I think about it, and come back to it at the end of our conversation?” This will also allow you to follow up in your thank-you note.
  • Try to Clarify. If you did not understand the question, or if you’re not sure what the interviewer wants to know, it’s okay to ask to define or explain their question. Try to identify what you found confusing, and you can say, “I’m not sure I understand what you’re asking. Can you explain it in greater detail?”
  • Don’t Fake It. It’s better to admit that you don’t know the answer than to make something up. Honesty is respected, and to admit that you don’t know the answer highlights your humanity, and it makes you relatable.
  • When a question stumps you, you can also say that you’ll be thinking about the question after the interview, and that you hope to learn more about the topic or concept if hired. If you give this as a response, relate to another time when you were unfamiliar with a concept and were then able to master it.


No matter how you felt about a job interview, always write a Thank-You note to your interviewer by way of mail or email.

Why Send a Thank-You Note?

Alison Doyle from www.thebalancecareers.com writes:

  • It’s good manners, and it’s expected behavior.
  • It leaves a positive, lasting impression.
  • It continues to sell you as a candidate. The note is a great way for you reference specific instances that came up in the interview, such as questions you wanted to follow up on.
  • Send your thank-you note no later than 24 hours after your interview.

Job Interview Thank You Letter Examples:


Admittedly, this e-Manual does not focus on whiteboard/technical interviews, but here are excellent articles with resources on how to prepare for them.

Everything You Need to Know to Rock Your Next Whiteboard Test by Debbie Chew

The Best Whiteboard Interview Advice I Ever Received by Nick Scialli

A Preview of e-Manual: Part 2..

This can be an uncomfortable issue for some, but if you’re in a position to negotiate salary, always negotiate.

If you don’t negotiate, you could be costing yourself $1 million, especially if you’re a woman.

Always know your worth, and never under-value yourself.

In this article by Deb Tennen from www.zapier.com, tech recruiters provided these salary negotiation tips.

  • Capitalize on the recruiter’s incentive to hire you. If the company has a recruiter, use them as a resource as much as you can. Like a real estate agent, the recruiter is your best friend during your salary negotiations. It’s in their best interest to get you to say yes to the offer. Do all negotiations through the recruiter, even if the hiring manager was the one to send you the offer.
  • Know Your True Market Value. Do your homework and reach out to other hiring managers and recruiters who are familiar with the position you’re applying for. Reach out to contacts on LinkedIn who work in the same company or the industry you’re applying for. “The best way to know what people make for a certain kind of job is to ask the people with similar qualifications who have that kind of job in your location.”
  • If you’re going to negotiate, do it early. Not only does early negotiation show enthusiasm for the position, but it avoids making the employer delay or prolong their decision-making timeline that could potentially affect other candidates.
  • Be the First to Say a Number When You’re Working with a Recruiter. Even if the employer doesn’t ask, providing a number anchors the conversation going forward, and it sets the expectations for all discussions moving forward. Even if your range differs from the recruiter’s range, you can figure out how to move forward by clearly defining your expectations.
  • Consider the Value of Benefits. Before negotiating the salary, take a tally of all benefits, including insurance, meals, transportation, and other quantifiable benefits. If you have to relocate, consider the cost of living at your new location and all moving costs. This will give you a more complete picture of the total compensation package before negotiations begin.
  • Be Gracious. At times, an offer can be retracted not because of the negotiation figure, but because of negotiating badly. If you are not cooperative with the recruiter, or your phrasing during negotiating is always in a demanding tone, the employer will lose their initial enthusiasm to hire you. Be appreciative of their offer, and navigate carefully to initiate a positive tone for the salary negotiations.
  • Use Negotiations As a Chance to Get to Know the Company. Look for red flags, such as the company not giving you the courtesy of talking to a manager or a recruiter.“If you say you have concerns about the offer and they don’t give you a chance to discuss it, what does that mean for your future at the company?” Pay attention to what they’re offering, and how they offer it.
  • Practice Makes Perfect. Recruiters appreciate confidence. To gain confidence, reach out to contacts who are (or may know) recruiters and hiring managers, even if they’re not in the tech industry. Just like mock job interviews, ask to practice talking with them, and in doing so, you will sharpen your skills in selling yourself when it comes time to making salary negotiations.


Common Interview Questions Require An Uncommon Answer.

Take the time to articulate answers that reflect YOU, your personality, and your experiences.



The TOC and banner links do not work on the mobile app. Apologies for the inconvenience.



The TOC and banner links do not work on the mobile app. Apologies for the inconvenience.