Blog
/
Current post

Motherboard Memoirs: Harry's Internship Review

In continuation of our series spotlighting the achievements of Motherboard's Internship Program participants, we're thrilled to present the latest review.

Harry Promise, an Engineering analyst, shares insights into his journey, highlighting his contributions and growth throughout the internship program.

Why did you decide to apply to the Motherboard Internship Program?

I applied to Motherboard because I was interested in the work they were doing in the employee benefits space. They had an interesting product, simplifying benefits management for HR professionals and improving compensation packages with a wider range of perks. Having reviewed the job description and requirements, I was excited about the opportunity to contribute my expertise in programming and software development, and I also knew I would be able to learn much more in return. 

What was the application and interview process like for you?

I came across the Engineering position at Motherboard through their post on LinkedIn and applied. Shortly after submitting my application, I received an email from Motherboard, inviting me to complete an assessment that involved crafting a pitch on how to expand the platform's features and grow the user base from 15,000 to 200,000 users across 200 companies. This step allowed me to showcase my problem-solving skills and technical proficiency. 
I then had an interview with the founder, Mr. Olalekan Olude, as well as some technical discussions with Motherboard's developers and the engineering lead. I appreciated the thorough and collaborative nature of the interviews, as it provided a holistic view of both my technical skills and how well I would fit into the team. The process also made it clear that Motherboard was committed to ensuring a strong alignment between the candidate and the company's goals. After completing the interviews, I received a job offer from Motherboard. Overall, my application and interview experience with Motherboard was a very positive one! 
Harry's Internship Offer Letter

How did it feel to get accepted?

Getting accepted for the engineering position at Motherboard was an incredibly gratifying and exciting moment. It was more than just securing a job; it felt like earning a place within a community of forward-thinkers and trailblazers.

What was the onboarding process like?

The onboarding process was well-organized. Right from the start, they made sure new team members felt welcomed and ready for their roles. I was first introduced to the onboarding modules which covered company policies, Motherboard's history, mission, and ongoing projects. The onboarding also included learning about Motherboard's collaborative tools and communication channels, promoting efficient teamwork and transparency.
I had a personalized orientation where I met my colleagues and mentors, making me feel like part of the team. As a Frontend Developer, I had a structured training program focused on Motherboard's tech stack, coding standards, and teamwork, preparing me well for my role.

What were your first impressions of Motherboard and the team?

My first impressions of Motherboard and the team were really good. Everyone, from long-term staff to fellow new hires (analysts), seemed proactive and excited to take on challenges to help the company achieve its goals. The managers were easy to reach and very helpful, showing me that Motherboard was a place where professional growth was not just encouraged but actively nurtured.

How did it feel to have ownership of a project?

Taking ownership of a project at Motherboard was both a thrilling and challenging experience. The project aligned perfectly with my interests and skill set, so it gave me a real sense of purpose. However, with the excitement came a heightened sense of responsibility. 
The project was one of the crucial components of the team's objectives, and I felt the pressure to make it a success. At first, I had worries. Would I meet expectations? What if things went wrong? However, I decided to see every challenge as an opportunity for growth and learning. Luckily, the team was very supportive. Motherboard’s culture encouraged asking for help, which made a big difference. When the project started reaching significant milestones, my worries turned into pride. Seeing the results of our hard work was amazing. Looking back, having ownership of the project really helped me grow. 

How did it feel to work on a vision document for your project? Was it your first time doing that? Did you face any challenges along the way?

I was excited to work on the Progressive Web App (PWA) station locator project for Motherboard Energy. While it wasn't my first time working on a PWA, this project brought new challenges and opportunities. The vision document was a collaborative effort. With the help of the designers, developers, and product managers, I was able to create a comprehensive doc that outlined the project's objectives, envisioned the user experience, and established a roadmap for development.
Once the real work began, we were met with challenges like integrating real-time data for station locations, ensuring smooth offline functionality, and optimizing performance for various devices. One notable challenge was refining the geolocation features to provide accurate and reliable results across different devices and network conditions. We were able to solve this after carrying out a series of tests and getting feedback from the team.  Working together was really the key to overcoming challenges. I’m thankful for all the brainstorming and code review sessions. 

Did you enjoy working with other people in the course of your project? Any struggles or lessons learned? 

I enjoyed working with other members of the Motherboard team. Each team member brought something unique, making the project better. I learned to set clear expectations, use collaborative tools well, and tackle communication issues. I also learned to balance the priorities and expectations of different teammates.
Some messages sent within the engineering team

What were the outcomes of your project? 

The PWA station locator project ended with some great results. Some of the key outcomes were:
1. User-Centric Design: We made a user-friendly PWA station locator with an intuitive interface. Screens were carefully designed to ensure a seamless user experience.
2. Real-Time Data Integration: We successfully integrated real-time data for station locations. The PWA automatically fetched and updated information, ensuring users had the latest details on available stations.
3. Offline Functionality: We made sure users could still access the app and get the necessary information they needed even without internet access. 
4. Performance Optimization: We worked hard to ensure that the app ran smoothly on different devices and internet speeds. 

Did you learn anything new in the course of planning and executing your project? Have you applied those learnings anywhere?

Planning and working on the PWA station locator was a journey of constant learning. I gained valuable insights that shaped the project’s success and even influenced future endeavors. 
I learned the importance of being flexible and adapting quickly to changes, understanding users’ needs, gathering user feedback, and making changes accordingly. This process helped me create a better app and has become the foundation of how I work. Thank you, Motherboard!
Subscribe to our newsletter
Get the latest HR and people management insights delivered straight to your inbox
Thank you for subscribing to our newsletter.
Oops! Something went wrong while submitting the form.