How to properly discuss salary during an interview
Source: Fast Company
When almost every one of us receives a job offer, we feel a sense of excitement. But for many, this means it's time to start negotiating salary. A study conducted by JDP shows that 41% of candidates did not immediately agree to the proposed salary, but discussed their future income when applying for a job. Of those who negotiated, 83% received a better offer. Recruiting experts offer some tips on how to better negotiate your future salary.
-
Research the market and company
Try to find out how long the position has been open and how quickly the company wants to fill it. If you are confident that you are the right candidate and the company is interested in hiring, this can give you an advantage in the interview.
Research the salary range that other companies offer for a similar position. It is useful to see how the amount changes depending on the candidate's experience and office location. Please note that your work may be assessed differently based on the employer's financial performance.
-
Know your worth
Think about what value you can bring to the company and tie that to your expected salary level. Help the employer feel like they're getting a great deal by hiring you.
Analyze what other options are open to you, be prepared to name the minimum amount you expect. Don’t hesitate to ask about additional compensation options—bonuses, options. Unless, of course, we are talking about a company where granting options is a common practice.
-
Don't agree right away
Don't immediately say yes to the first salary offer. Tell the employer your expectations and ask for more. Go to the interview prepared: make a list of arguments that will prove that you deserve more money. State your salary expectations in an email. This way all interested parties will be able to familiarize themselves with them.
-
Discuss cashless components
Ask what additional benefits you can expect beyond your salary. Find out whether paid child care, compensation for transportation costs, and the number of vacation days are provided. Your employer may have strict salary restrictions, but may offer you a more flexible work schedule that suits you.
Don't be discouraged if your negotiations are unsuccessful. Think about how the new job will be useful for you and set your priorities correctly. Perhaps the salary in the new position is not so high, but this job will be a good step for a future career. In addition, over time, you will have the opportunity to prove to the employer that you are worthy of a salary increase.
How not to fail the development of your first MVP
Source: DZone
Having a minimum viable product (MVP) is a great way to establish yourself as an ambitious developer. Even if you're not applying for investment, adding a link to your own application to your resume will certainly improve your chances of getting hired. Just make sure that the MVP is truly impressive and not your first failure. Some of the most common mistakes that developers make when creating an MVP include:
-
Choosing the wrong problem to solve
A survey by CB Insights found that 42% of all startup failures are due to “lack of market need.” In other words, your application may be well written and have great functionality, but few people need it.
To avoid this scenario, before you sit down to develop an MVP, you need to ask yourself the following questions:- Who might be interested in my application?
- What problem does it solve?
- Is my idea the most effective way to solve the problem?
If you think your product is good for everyone, then you will almost certainly fail. Find your target audience.
-
Skip the prototyping step
Nobody builds a car without first creating a concept for it. Direct transition from idea to development process will lead to mistakes. Prototyping and iteration are essential to product development. Test the prototype with potential users. This way you will find out their opinion about your future application.
-
Targeting the wrong user segment
Remember that not all users are your target audience. So don't ask your friends or family to review the app if they aren't among your potential customers. Otherwise, the product will receive a biased assessment. It is important to focus on a segmented target market. This will help increase your chances of success.
-
Wrong development method
Jumping straight into the MVP process using the wrong development method is one of the main reasons why many abandon a project before completion. And this is one of the main factors influencing the statistics why 9 out of 10 startups fail.
There are two most common approaches to developing MVP products: Agile (agile methodology) and Waterfall (waterfall model).
Compared to Waterfall, Agile product development is more efficient because it adapts better to changing circumstances and allows you to deliver a project within a specific time frame. A 2018 survey by Ambysoft found that Agile has a 55% success rate, compared to 29% for waterfall development.
-
Confusion between qualitative and quantitative feedback
Qualitative and quantitative feedback are two different ways of collecting data from target users.
Qualitative feedback consists of results that relate to the user experience of a product or service's features. It directly evaluates system usability, helping developers analyze specific problematic UI elements.
Quantitative feedback comes in the form of metrics that determine whether tasks were easy or difficult to complete. It indirectly evaluates the usability of a design.
The ideal approach is to combine qualitative feedback with quantitative feedback—triangulation feedback to collect data for accurate interpretation, taking into account many different factors. This approach increases the chances of controlling threats to the product. If both feedback methods reach a common conclusion, then the developer will be more confident in the success of his application.
GO TO FULL VERSION