Author Archive

LLI spotlight: Isabelle Krauze

Isabelle is originally from Curitiba, Brazil, and she now lives in Krakow. Join us as Isabelle tells us more about herself and her work at LLI.

How do you usually get your day started at work?

As a fully remote worker, I start my day by turning on Slack. This, for me, is the equivalent of arriving at the office! Now that the weather is getting colder, I light up a scented candle and pour myself a cup of tea (with honey, of course).

At this point, I get started on my set of day-starter tasks: First, I’ll open my company profile at Google chrome, with the same set of tabs on it (email, my personal task tracker on Notion, my calendar, and GitHub).

Next, I check all the updates and unread messages on Slack. I then go through my weekly tasks on Notion (that I define first thing on Monday mornings) and plan out the day ahead. I’ve also been using Tomito as a Pomodoro timer (which is essential for me).

Each morning, I have a project stand-up in which I inform my team members of my current plans. Sometimes these plans change according to the project requirements. If they do, I reorganise my daily plan accordingly. And finally, around 10:00, I start working on my tasks for the day.

What are you most proud of that you’ve recently accomplished at work?

I think I don’t have one particular accomplishment that I’m most proud of; instead, I continuously love the feeling of having solved a problem.

I’m very dialled into the process of things, and I can be just as proud of the path that my thoughts and ideas took to produce something as I am of its final result. With that in mind, what has been making me proud lately is to have received really positive feedback on my latest deliveries for a big project that I’m currently working on.

What do you love about being part of the LLI team?

I really appreciate the sense of trust that we have at LLI. Nobody is breathing down your neck to monitor your work, nor is anyone just killing time. Being a remote-first company, these can be issues that require expertise to handle properly.

My feeling is that the company’s approach is to expect the best from everyone and that we’re all doing something to add value and growth to ourselves and, consequently, to what we produce. For me, that’s gold!

Which tools or resources do you use or refer to to keep improving your professional skills?

On a daily basis, you can find me watching a lecture or listening to a podcast on YouTube or Spotify. I usually refer to them either when trying to learn something new or when looking to hone my knowledge on something that I already know about. 

Some resources that I particularly like include:

Any words of advice for those getting started out in a career in design?

Be meaningful. User experience design as a career path is very hot right now, and as a result, there is a significant amount of “Become a UX Designer in 6 months” messaging (and related courses) circulating around the internet. I’m not against these – I am 100% pro people having easy access to knowledge – however, it’s not because it’s easy to learn about it, that is going to be easy to do. So, go deep, investigate, be critical, explore. 

Furthermore, be meaningful in what you do. Don’t rely on your own assumptions. Don’t choose a colour just because you like it. Don’t design it for you; instead, understand who you are designing for and create something meaningful for them.

Tell us about your favourite weekend activity.

A perfect weekend for me would have more than one kind of activity. I need to go out of the house for a few hours to compensate for the amount of hours I stay inside during the week. So, going for walks, meeting friends around the city, going to a museum, cinema, anything goes.

But I also love to stay at home doing some sort of handmade crafts. I’m currently knitting a sweater, but I can also be found painting with watercolours, sewing, or trying out any other kind of arts and crafts.

We’re so glad to have had the chance to chat with you, Isabelle! 

If you’d you check out more of our LLI spotlights, you can read our first instalment of the series. Stay tuned for more upcoming LLI team members to be featured.

In the meantime, would you like to know more about LLI’s team culture and open positions? Check out our Careers page and follow us on LinkedIn and Facebook.

LLI spotlight: Grace Macej

We’re proud of having a diverse, talented group of professionals at LLI.

To showcase some of the awesome people that make up our team, we’re starting a series of LLI spotlights – in-depth articles that highlight specific members within the company, what they do at work, and some details about them as individuals. 

Starting off our LLI spotlight series is none other than Grace Macej, LLI’s Content Marketing Manager. Grace (or Gracie as a nickname!) has been with LLI since January 2021, meaning that she’s approaching her two-year anniversary with the company in a few months!  Born and raised in the Pacific Northwest of the United States, Grace has been calling Europe home since 2013.

We sat down with Grace to ask her a series of questions about her work, hobbies, and more. Let’s dive in.

What is your daily “bread and butter” at LLI?

I manage marketing activities at LLI. Whether it’s writing and publishing blog posts, coordinating the communication strategies of our team’s current initiatives, or keeping track of our internal content calendar, I can be found creating and thinking about the materials that we share with the world and the way in which we’re perceived as a company.

I collaborate with various members of our team as needed. I’m often in touch with our designers, but I also occasionally work with our project managers, developers, and others to ideate, create, and deliver different forms of content and marketing materials. 

What have been your biggest accomplishments at LLI?

One of the first things that I did upon joining LLI in early 2021 was to revamp the content on our website. This was part of a larger initiative to optimize many of our customer-facing materials from a linguistic and grammatical point of view. 

Over time, I’ve also worked together with a few members of the team to update our brand messaging and values and have incorporated these on our website. Lastly, on an ongoing basis, I help spread the word about our brand through creating and publishing thought leadership content on our marketing channels.

What do you love about our company culture?

Remote-first environments give LLI’s team members the freedom and autonomy they need to thrive as individuals and professionals. Working remotely allows me to work when I’m at my sharpest and in an environment in which I’m the most productive. 

I feel supported in this model, and whenever I do feel like spending time with colleagues in person, I know that I can pay a visit to the lovely city of Warsaw and pop into the office.

What is the best lesson that you’ve learned in your career so far?

Always leave room to keep learning. Whether it’s learning through others, through your own challenges (and the process of eventually overcoming them), or taking the time to invest in targeted education to keep furthering your skills, there’s always something new that you can add to your individual skill set. And no matter how knowledgeable you are, stay humble.

Tell us something you’re passionate about.

I’ve played the piano since I was six years old. I was classically trained throughout my childhood and teenage years, competed for a handful of years in regional competitions and events, and I actually started out in university studying piano performance before eventually switching to my marketing degree! Today, I continue to play for pleasure and occasionally accompany the choir that I sing in.

What are the three words that best describe you?

  1. Adaptable
  2. Reliable
  3. Observant

Thank you, Grace, for taking the time to discuss these points. We’ve been ramping up our marketing efforts over the course of the past couple years, and you have been a key part in that effort.

That’s a wrap for our first LLI spotlight installment! Stay tuned for more upcoming LLI team members to be featured.

In the meantime, would you like to know more about LLI’s team culture and open positions? Check out our Careers page and follow us on LinkedIn and Facebook.

Why having a good QA engineer is essential for your project’s success

Question: What do Heathrow’s Terminal 5 and NASA’s Mars Climate Orbiter have in common?

Answer: Software bugs that could have been avoided with proper testing and quality assurance  (QA) during various software development processes. 


The case of Heathrow Airport’s Terminal 5


In June of 2008, a number of significant, large-scale problems cropped up during the opening of Heathrow Airport’s new Terminal 5. After the brand new baggage handling system shut down, things went downhill. A total of 42,000 bags were left behind and 500 planes were left stranded at airports, causing flights to be canceled. This resulted in a loss of approximately £16 million as well as a large hit to British Airways’ reputation.

So, what was it that caused this series of unfortunate events?

Due to a lack of sufficient quality assurance, several real-life scenarios were not thought through during the opening of the terminal. First off, the loading staff were unable to log in to the baggage validation system. As a result, they resorted to validating bags manually, which caused flight delays. Another problem was the situation in which customers asked for their luggage, e.g. because they had left their passport in it – the airport system was not able to return the luggage.
Furthermore, Terminal 5’s system did not receive information about baggage transferred to British Airways from other airlines. Thus, unrecognized baggage was automatically sent for manual sorting at the terminal warehouse. Each of these oversights ultimately caused the system to become overloaded and cease to function.


The failed mission of NASA’s Mars Climate Orbiter

During a mission to Mars in 1998, NASA’s Climate Orbiter, a robotic space probe originally designed to study Martian climate and atmosphere, eventually went missing in space. After extensive investigation into the error, it was discovered that a subcontractor on NASA’s engineering team had failed to make a simple conversion from imperial to metric units. 

This simple error caused the $125 million spacecraft to come fatally close to the surface of Mars after trying to stabilize a too-low orbit. Flight controllers believe the spacecraft fell into the Martian atmosphere, where the associated stresses crippled its communications, leaving it hurtling further through space in orbit around the sun.

Image credit: NASA/JPL-Caltech


These two stories have something in common: in both cases, their failures were caused by a lack of proper QA. They’re a testament to the power of QA itself, as well as the important roles of the engineers responsible for carrying it out. When solid QA is put into practice, it prevents errors that can result in financial or reputational loss. It also yields products that are delivered on time, designed according to business requirements, and are well documented and supported.

What are QA engineers responsible for?


In short, a QA engineer safeguards a company’s success and reputation by making sure the product meets requirements.

Over time, quality assurance has undergone a transformation from testing to a QA process throughout the product development lifecycle. One responsibility of the person responsible for QA is to conduct tests and confirm that a given functionality meets requirements and is free from errors. However, there’s more to their work than just testing.

Importantly, QA engineers support project owners and development teams by conducting research on what should be tested as well as how and under which conditions the tests should be carried out. By doing this, QA engineers transform use cases into test cases. QA actively participates in the project by implementing the testing strategy, thus minimizing the risk of errors in the project.

Having a good QA engineer on your team is invaluable for your project as a whole.


While automated testing is performed by coding and running scripts (for example, written in JavaScript using Cypress), manual testing is an important activity performed by QA engineers. Manual testing allows for creativity in finding errors and inaccuracies, while automated testing will perform strictly defined operations described in the code. Automated tests can be executed more quickly, but at the beginning of development, their creation consumes a good deal of time.

By combining manual and automated testing, teams can bring about great results, increase the quality of the application they’re working on and implement new functionalities faster. What’s more, by mixing various testing methodologies, QA simultaneously creates test documentation and regression tests. These tests are used before each release to the product environment to scan for appearances of errors that could cause serious financial losses.

QA engineers make sure that appropriate tests are launched at the right time, integrating them with continuous integration (CI/CD) tools to speed up and largely automate the testing process. Importantly, QA starts the testing phase from the very beginning of work on a new functionality. It’s an iterative process: when functions are developed, QA engineers test them, send them back to developers if necessary, test them again and move them forward in the process. Eventually, the functions are developed and new features are deployed, and the process begins again.


Furthermore, QA makes sure that the acceptance criteria defined in the user story (in other words, a description of a software feature from a user’s perspective) are provided before starting work on the functionality. Based on the story, QA creates a test case that describes in detail how to test the function, any necessary test data, and what is the pass or failure of the tested function. Rigorous application testing significantly affects the risk of failure in the production environment and contributes to the achievement of a high quality system, and manual testing increases confidence in the quality of the software.

Why should you have a QA engineer in your team?

Put simply: Whenever it’s possible to do so, preventing problems altogether is cheaper than fixing them after the fact. 

A quality assurance engineer is responsible for identifying errors, weaknesses and inconsistencies in the product in each of its stages. Therefore, QA safeguards not only the quality of the product, but also the reputation of your brand.

An efficient QA engineer will bring many unique qualities to your team:


In today’s competitive business landscape, delivering software that meets customer requirements is paramount. The amount of technology that modern businesses make use of has grown to the point that without having proper quality processes in place, it’s virtually impossible to deliver top-tier software.

While many businesspeople think themselves capable of performing sufficient testing on their products, this is rather a task designed for qualified QA professionals. This is because more often than not, bugs that are invisible from the user’s point of view (and that of a non-QA professional) are the cause of subsequent costly failures. Undetected flaws and defects can lead to serious business losses, which is why it’s so important to have dedicated team members regularly carrying out QA processes. Finally, having a QA specialist on your team will make your development more productive and your developers work more efficiently.  


The above knowledge paints a clear picture of how important QA is to satisfy customers and increase sales. In the past, QA services may be seen as an additional and unnecessary cost, but forming a deeper understanding of the product lifecycle and associated business needs have helped businesses across the globe appreciate the value of having proper QA in place.