Check out your Company Bowl for anonymous work chats.
Bowls
Get actionable career advice tailored to you by joining more bowls.
Followed companies
Stay ahead in opportunities and insider tips by following your dream companies.
Job searches
Get personalized job recommendations and updates by starting your searches.
Blip (Portugal) interviews FAQs
Senior Software Developer applicants have rated the interview process at Blip (Portugal) with 3.5 out of 5 (where 5 is the highest level of difficulty) and assessed their interview experience as 50% positive. To compare, the company-average is 51.7% positive. This is according to Glassdoor user ratings.
Candidates applying for Senior Software Developer roles take an average of 33 days to get hired, when considering 2 user submitted interviews for this role. To compare, the hiring process at Blip (Portugal) overall takes an average of 25 days.
Common stages of the interview process at Blip (Portugal) as a Senior Software Developer according to 2 Glassdoor interviews include:
Group panel interview: 20%
Personality test: 20%
Phone interview: 20%
Skills test: 20%
One on one interview: 20%
Here are the most commonly searched roles for interview reports -
I applied through a recruiter. The process took 4 weeks. I interviewed at Blip (Portugal) (Portugal) in Feb 2024
Interview
The interview process was extensive, consisting of four stages:
Initial Interview with HR: This was an introductory call with Human Resources, where we discussed my professional background, career aspirations, and initial fit with the company culture.
Online Technical Test via DevSkills: I completed an online coding test through the DevSkills platform to assess my programming skills and problem-solving abilities.
Technical Interview: This stage involved a technical discussion with senior developers or team leads, where I was asked in-depth questions about my technical knowledge and previous experiences.
Technical Interview with a Practical Test: In the final stage, I participated in a practical coding test as part of the interview. This allowed me to demonstrate my hands-on coding abilities in a real-time environment.
Interview questions [1]
Question 1
Big O Notation: They asked questions to evaluate my understanding of algorithm efficiency and how to analyze time and space complexity using Big O notation.
Immutable Classes: I discussed the concept of immutability in classes, including the benefits of immutable objects and how to implement them in Java.
Types of Testing: They inquired about different testing types, such as unit tests, integration tests, and end-to-end tests, and asked me to explain the purpose and advantages of each.
Design Patterns: I was questioned about various design patterns, including the Strategy, Builder, and Singleton patterns, where I explained how each pattern works and scenarios where they are useful.
Multithreading and Thread Safety: They also asked about multithreading, focusing on thread safety, synchronization, and how to manage concurrent operations in a way that prevents race conditions and ensures data consistency.
I applied through a recruiter. The process took 5 weeks. I interviewed at Blip (Portugal) (Porto, Oporto) in Apr 2023
Interview
5 weeks process with 3 stages: - HR screeing followed by a technical challenge. - Java OOP interview with other 3 software engineers. - More Java questions, algorithms, and software design. They take too long to schedule the interviews. In the last stage I was told that I was going to solve algorithms in a pairing session, but the interview was like the second with Java questions related to performance optimization, and the software design. In the software design part, they didn't agree with me when I suggested a NoSql solution for a key-value pair. Instead one of the developer said a SQL solution would be better. I insisted NoSql was better for read intensive applications, while SQL is better for write intensive. That was useless because he already decided he was right. He kept throwing edge cases where a no sql solution would be worse, but they didn't apply to a key value problem while pretending a full SQL database would be the best solution for such simple problem. Sadly these developers get out of touch, and pretend they would know all this stuff before hand.
Interview questions [5]
Question 1
Where method calls are stored in memory in the JVM?