My name is Zediwa De Jesus, and after completing the Engineering Pathway, I have worked as a backend developer with ESDIAC. My mentors are Bassirou Rabo and Ahmad Abbati, who are both software engineers. I began my internship on August 29th, and I work 3 times a week.

My internship experience was new to me. I worked both in-person and in an office, but my mentors didn't work in the same office as me: they lived in diferent states. This situation forced me to communicate completely virtually, which seemed like a major problem at first, but I learned to overcome this. I worked on Backend Developing, which is where engineers write code and manage databases, which is what my responsibilities were, as well as testing and troubleshooting. 

Purpose of Internship site

ESDIAC is a software and telecommunications company dedicated to redefining global communication and making connection with others borderless. The company was founded in 2015 to address the problem of extra costs associated with making international calls. ESDIAC exists to break down geographical, technological, and financial barriers, ensuring instant, reliable, and meaningful connectivity. 

Type of Work Performed

The work at ESDIAC is focused on creating smart and efficient digital communication space. This involves building and maintaining the software platforms that support millions of calls and transactions for over 40,000 customers. Core activities include designing high-availability server architecture, developing APIs to manage customer accounts, and focusing on innovation to turn challenges into opportunities for affordable access for everyone.

Mission/Goals of Department

In the department of Backend Services, the goals are to design, implement, and maintain high-performance APIs that underpin ESDIAC's core service offering, allowing users to make and pay for affordable international communication. Our current goals focus on improving scalability and reducing latency by migrating critical components to modern frameworks like FastAPI, ensuring that distance no longer define users' relationships.

Tools, Software, or Equipment commonly used

The engineering environment heavily relies on programming languages, with the main programs being Python, Java, and Javascript. The primary Integrated Development Environment is Visual Studio Code, which is used for writing and managing source code files.  The main framework used for building APIs is FastAPI.

A. Project Description

The goal of this project was to create a functional REST API (Application Programming Interface) from the ground up. A Rest API is a set of rules that allows two computers to communicate and exchange data with each other. This project matters to ESDIAC because APIs are the engine of their apps; they handle everything from looking up a user's balance to updating account details. My role was to write the code that data that is sent to the server is correct.

B. Process + Engineering Methods

1: I used Command Prompt to download the latest versions of Python and FastAPI to ensure that the project would be compatible. 

2: I used Visual Studio Code to write my code. I used Pydantic to create an Item class, which ensured that any data entered is the correct type.

3: I programmed specific API paths, such as Root (verifies that the server is live), GET (retrieves specific data using Path Parameters), and PUT (updates existing information).

4: I ran the server using "fastapi dev main.py", which created a link that opened a server that showed that API was successfully created.

The biggest challenge that came from working at my internship was communicating with my mentors. Although I worked both in an office and at home, my mentor lives in California, where the company is based. Having to learn online instead of face-to-face has lead to delays in learning, especially with different time zones. but this has been overcome by finding my own resources to help me on top of my messaging my mentor using Slack instead of emailing.

Backend Coding: I developed the ability to create virtual environments using Command Prompt. An example of this was using "python -m venv my_web_app", which created a project that I could code on.

Engineering Design Process: I applied a structured design process to go from a blank file to a working API. This involved identifying the problem, brainstorming necessary routes, and prototyping in Visual Studio Code. Afterwards, I had to repeat my design to ensure the data models matched the requirements of the task.

Troubleshooting & Diagnostics: I learned how to diagnose issues when my code didn't appear to be updating in the browser. A real example was when I realized my browser was showing old results because my code wasn't being saved in VS Code. Learning to check the Command Prompt logs to ensure the output was matching with the input became a key part of my workflow.

Communication & Teamwork: Realizing that I don't know everything and knowing when to ask for help became one of the best skills I picked up. When starting my internship, I wasn't sure how to find the earliest version of Python, as well as how to download it onto Command Prompt. I reached out to my mentor, and he was able to thoroughly walk me through it so I'd be able to do it on my own.

What was the most important thing you learned from your internship? 

The most important thing I learned throughout this internship is that working well with others is a vital part of the engineering process. Working on backend code made me realize that I don't know everything, and trying to solve every problem alone is actually less efficient than asking for help. It is crucial to be able to ask others for guidance when you are stuck because they might have a perspective you haven't considered yet. This experience taught me that sharing ideas within a group is how the best engineering solutions are found. Being open to feedback and collaboration turned out to be just as important as the actual coding itself. 

What engineering practices or mindsets did you see professionals using? 

The engineering practice I observed most frequently was a disciplined focus on digital organization and "clean coding" structures. Even though I worked in a remote setting at ESDIAC, I saw that professionals treat their code architecture exactly like high-quality physical wiring; every function is labeled, every directory is structured, and everything is placed where it belongs for maximum clarity. While working online, I noticed that engineers rely heavily on a mindset of Asynchronous Communication, where they document every technical detail thoroughly so the rest of the team can understand the progress without needing a live meeting. This level of structure is a critical engineering practice because, in a virtual environment, your code is the primary way you communicate your logic to the rest of the team. Whenever a bug pops up, having that organized foundation allows anyone on the team to find the designated location of the error and fix it immediately. Seeing the professionals at ESDIAC value this level of detail made me realize that an organized system is the only way a global telecommunications company can function successfully. 

What surprised you about the engineering workplace?

What surprised me most about the engineering workplace was how incredibly willing everyone was to help me succeed. Even though I worked remotely, the team was always available to answer questions and provide guidance, which made the distance feel non-existent. I had expected a remote environment to be isolating, but the engineers at ESDIAC proved that a strong team culture can exist anywhere as long as people are willing to support one another. This collaborative spirit was evident through our frequent video calls and messaging threads, where complex technical issues were broken down into manageable steps. Seeing how quickly my mentors would jump in to troubleshoot a bug with me taught me that professional engineering is truly a collective effort rather than a solo task. This open communication changed my perspective on virtual work, showing me that being part of a team is defined by engagement and shared goals rather than just sitting in the same office. 

How did this internship influence your future goals?

To be honest, this internship didn't influence my future goals much because I already know what I want become, which is a pilot. The aviation industry, especially being a pilot, has little to nothing to do with coding. However, this experience did show me that I have the focus and technical discipline required to master complex systems, which is a vital trait for anyone in a cockpit. Modern aircraft rely heavily on sophisticated avionics and software interfaces, so having a background in how these backend systems function gives me a unique perspective on the technology I will one day operate. I also realized that the troubleshooting mindset I used to fix bugs in my API is very similar to the systematic way a pilot must approach mechanical issues or emergency checklists. Even though I am choosing a path in the sky over a path in software development, the work ethic I built at ESDIAC has prepared me for the rigorous training and responsibility that comes with aviation. 

What advice would you give a future student in this internship?

 The best advice I could give to a future student is to put in as much effort and focus as you possibly can from the very first day. I honestly think I put more energy into this internship than I have into almost all of my other classes combined because it truly demands your full attention. You should use every extra minute you have—whether it is during lunch or before school—to stay on top of your code and keep it organized. If you let your project become an absolute mess, you will spend more time trying to find your mistakes than actually building new things. Don't be afraid to ask your mentors or your peers for help, because everyone is there to see you succeed. Finally, remember that the "frustrating" parts are just part of the process, and the feeling of accomplishment at the end makes all that hard work worth it. 

I presented an overview of my internship and my aviation journey on October 3rd and 10th for Drew's Career Steam Day. The intended audiences were EA and JA students. My presentation talked about my internship, what work I've done so far, and my aviation career so far. I talked to 4 different classes, and my experience and feedback from students were positive. This presentation connects to my internship experience by allowing me to present my work to a variety of students, which helps me in the future with presentations and speaking in front of different crowds.