<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Shima Kanani on Medium]]></title>
        <description><![CDATA[Stories by Shima Kanani on Medium]]></description>
        <link>https://medium.com/@shima.kanani.t?source=rss-3b3f785137a5------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/2*X6zEZoqicmoOjEBs0xZalg.jpeg</url>
            <title>Stories by Shima Kanani on Medium</title>
            <link>https://medium.com/@shima.kanani.t?source=rss-3b3f785137a5------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 14:24:20 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@shima.kanani.t/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[My Summer Internship at Scotiabank FactoryU]]></title>
            <link>https://medium.com/@shima.kanani.t/my-summer-internship-at-scotiabank-factoryu-3786172b0f42?source=rss-3b3f785137a5------2</link>
            <guid isPermaLink="false">https://medium.com/p/3786172b0f42</guid>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[summer-internships]]></category>
            <dc:creator><![CDATA[Shima Kanani]]></dc:creator>
            <pubDate>Tue, 09 Oct 2018 01:44:07 GMT</pubDate>
            <atom:updated>2018-10-09T02:27:04.314Z</atom:updated>
            <content:encoded><![CDATA[<p>Scotiabank FactoryU is a new research and experiment center located in the heart of Waterloo’s fast-growing tech ecosystem. Newly operating since January 2018, FactoryU brings in a new cohort of tech students every four months to complete its lean team of user experience designers and software engineers. The team works together to use a design-first approach which aims to further explore the future of digital banking.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/984/1*zppHhfwmSnw13xs9YFMyRg.png" /><figcaption><em>FactoryU in Waterloo, Ontario</em></figcaption></figure><p>I had the opportunity to deliver a classified project aiming to transform the future of banking and redefine the relationship a customer has with their finances. I was a part of a team of four engineers which consisted of two full-time engineers and two co-op students. As students, both of us were mentored by the full-time engineers as they were each specialized in either server-side development or frontend development. Due to our small team, we worked closely with the mentors and received training as we took the lead on developing multiple features of the product.</p><p>My internship was a four-month intensive process where <em>I was a part of every step</em>; from ideation to development, execution, and delivery. The final product was <strong>fully built </strong>by the end of August and delivered to Scotiabank. It is important to note that the product is projected to reach customers in the following months. Even though the specifics of the project cannot be disclosed at this time as they are confidential, I will be exploring the technical and non-technical work that was done in order to deliver the project.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nKeo2akOO79Jvs8XMscdxA.png" /><figcaption><em>Google Ventures Design Process</em></figcaption></figure><p>As a team, we were given a banking problem to solve. This meant my internship was kicked off at the ideation stage. We conducted a Google Ventures design sprint which is a design process that goes through designing, prototyping, user testing, and validation of an idea all in just five days. On the first day of the sprint, we mapped out the problem and came up with a goal. This goal was used throughout the process to give us a vision for the final solution. We sketched out all the possible solutions on the second day. Next, we decided on which solutions we should tackle and we used them to form a testable hypothesis. The last two days consisted of prototyping and user-testing our final solution. After the sprint, we presented our solution to bank executives and project stakeholders and received approval. Once we had a solution and a clear vision for the product, we kicked off our development process.</p><p>We used a <em>feature-driven development process</em> simply because it is fast-paced, and we wanted to allow for changes as we received feedback from the project stakeholders. My role involved taking the lead on developing and delivering multiple features of our product. Working as part of a team of two full-time engineers and two co-op students meant that every feature that each of us undertook had to be delivered end-to-end. Primarily, the technical specifications of the feature were defined, software architecture was mapped out and then reviewed by the rest of the team. Upon approval, the development process would begin according to the mapped-out software architecture. Once the feature was built, unit tests were written to determine the correctness of the code. At this stage, the code would go under review by the rest of the team and any comments or feedback received from the other engineers required iteration and more testing. Finally, when the feature was approved by all team members, it would get merged into the final code base.</p><p>Moreover, knowing our product is projected to reach customers and having direct interaction with project stakeholders forced me to think strategically and go beyond my role. I constantly prioritized the stakeholder’s feedback and proper engineering practices to ensure the quality and scalability of the product for thousands of customers. Furthermore, I took the initiative to investigate new technologies for the project to help scale our product. I also constructed software architecture and documented technical requirements before development to increase productivity and project scalability by familiarizing other engineers with details of features built. Overall, our team efforts led to meeting the project’s strict deadline and efficiently deploying a highly scalable product.</p><p>In terms of <strong>technologies</strong>, we decided to use React Native to build our frontend because we were asked to deliver a native app by the project stakeholders, but we had very limited time and resources. Because of React Native, we were able to work closely together on one code base instead of splitting up the already small team of engineers we have into Android developers and iOS developers. In the end, it allowed us to save development time by coding once yet developing for both iOS and Android platforms. React Native’s resulting user interface is also very responsive and fluid thanks to JavaScript so using this framework was really helpful given the fact that we were building for an interactive app.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*z177NRjgHALZWC0_" /></figure><p>On the other hand, the <strong>server </strong>was written in TypeScript using the Nest.js framework running on Node.js. We chose to use the Nest.js framework because it gave us an easy way to write a <em>modular, layered, and easily testable system</em> that we could iterate on and pivot quickly as the requirements changed. We also used technologies such as Datastore which is a scalable NoSQL database and Redis which is a memory store. These technologies were used because they are specialized for the applications that we needed and have been tested by the industry experts throughout the field. All the backend services were running on <strong>Google Clouds Platform’s App Engine</strong> which is a platform as a service and made it really easy for us as a team of two and a half server engineers to stand up our server and keep it running throughout the entire development process. Finally, we used the Jest framework to write our tests and Circle CI to automate the process of running the tests.</p><p>Prior to this summer, I had no job experience that involved starting a project from scratch and turning an idea into reality. But at this internship, I had the opportunity to create a product and then <em>deliver it to the project stakeholders</em>. Even though I doubted myself many times about my lack of experience with the technologies used in our project, I was able to adapt quickly and deliver in an agile team. Therefore, not only did I gain hands-on experience with new technologies, but this internship also taught me how to <strong>rapidly learn new skills</strong> in fast-paced environments. I also improved my presentation skills by carrying out multiple presentations to vice presidents and directors of the bank who were our project stakeholders. This taught me how to work well in the context of a large organization and helped me better understand my role in the bank as an employee. Finally, due to our small team and the size of our project, teamwork and effective cooperation was crucial to our success.</p><p>Besides improving my technical skills, I also I had the opportunity to improve my professional network and make industry connections by attending many events at the bank. This helped me improve my soft skills and gave me the ability to leverage my network in the future to build my career.</p><p>Overall, my experience at FatoryU was more rewarding than I had expected. Although it was challenging at times, I enjoyed working with such a small, yet tight-knit team of engineers and designers towards our project goals. Every person in the team had a different kind of skillset and personality which made the experience even more valuable and authentic.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qZ4tXULUAQ3VRFZMSFCy7w.jpeg" /><figcaption>The FactoryU Team — Summer 2018</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3786172b0f42" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>