<?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 Shums Kassam on Medium]]></title>
        <description><![CDATA[Stories by Shums Kassam on Medium]]></description>
        <link>https://medium.com/@skassam21?source=rss-a7acab38630------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*XJzZIfnX6nnsOZ6sREoDTQ.jpeg</url>
            <title>Stories by Shums Kassam on Medium</title>
            <link>https://medium.com/@skassam21?source=rss-a7acab38630------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 09:22:39 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@skassam21/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[Acing the Technical Interview: Lessons from 30 Tech Companies]]></title>
            <link>https://medium.com/hatchways/acing-the-technical-interview-lessons-from-30-tech-companies-386fdc073425?source=rss-a7acab38630------2</link>
            <guid isPermaLink="false">https://medium.com/p/386fdc073425</guid>
            <category><![CDATA[interview]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[toronto]]></category>
            <category><![CDATA[developer]]></category>
            <dc:creator><![CDATA[Shums Kassam]]></dc:creator>
            <pubDate>Thu, 15 Nov 2018 18:47:37 GMT</pubDate>
            <atom:updated>2019-02-27T02:44:40.856Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kE91GtI8CBFtf_bGnW1OYQ.png" /></figure><p>I recently started a company called <a href="http://bit.ly/hatchways">Hatchways</a>, a platform designed to match candidates with paid work placements to help them discover fulfilling work at any stage of their life. We have worked with over 30 companies and 100 candidates in the last six months. Having seen how these companies conduct technical interviews, I have put together this basic guide to help you prep for the technical interview.</p><blockquote>Disclaimer: the following guide is based on full-stack web development interviews for internship roles in Toronto-based startups. This interview prep is for people who are interviewing for similar positions at similar companies.</blockquote><h3>What do companies look for?</h3><p>A common assumption is that technical interviews are about getting the best answer in the shortest amount of time. However, it is so much more than that. There are many factors that come into play when deciding if a candidate is strong or not. Here is what I have found companies to look for:</p><ul><li><strong>Can you communicate?</strong> Companies want to see <em>how</em> you understand the question and your ability to discuss your solution.</li><li><strong>What is your thought process? </strong>Often companies want you to not only solve the problem, but to consider the tradeoffs of different solutions. This is why understanding time and space complexity is crucial for technical interviews, regardless if they ask about<a href="https://rob-bell.net/2009/06/a-beginners-guide-to-big-o-notation/"> Big O Notation</a>.</li><li><strong>Can you code? </strong>At the end of the day, companies want to see if you can code. They want to see if you can easily write a for loop or a conditional statement. This is a strong indicator that you code on a regular basis.</li><li><strong>How do you code? </strong>It’s not just about your ability to write code. Do you test your code? Is your code readable? Is it efficient?</li><li><strong>Do you have relevant experience?</strong> Small startups value experience in their stack — they want to see if you can jump into their team with little training. Be prepared to answer specific domain related questions.</li></ul><h3>Approaching technical problems</h3><p>Based on what companies are looking for, I have put together this step by step approach to technical interview questions:</p><h4><strong>1. Comprehension of Question</strong></h4><p>The first step is to <em>understand</em> the problem. Repeat the question back to the interviewer to show that you understand it clearly.</p><h4><strong>2. Discussion</strong></h4><blockquote>A tip to candidates in an interview is to discuss your approach to a problem before you start coding.</blockquote><p>Before writing any code, discuss your approach with the interviewer. This immediately demonstrates your ability to approach the problem, and also allows you to get feedback about your solution without wasting time on coding. If the interviewer has a problem with your approach, they may question it, allowing you to reach the solution faster. The ability to discuss the question with the interviewer shows strong communication skills.</p><h4><strong>3.</strong> <strong>Keep it simple</strong></h4><p>If you don’t immediately know the best solution, start with a simple one! Sometimes interviewers don’t care if you have the optimized solution. Interviewers may just want to see if you can code and <em>how</em> you code. If you take a long time thinking in silence before writing anything, this can be problematic. At least attempt the naive and inefficient solution if you are stuck thinking about a more optimized one. This also buys you time to think of a better solution and sometimes, the inefficient solution can shed light on a more optimized one.</p><p>If you are having trouble coming up with any solution, try solving some examples of the problem. By walking through the solution of an example, it can help shed light on the programmatic solution.</p><h4><strong>4. Optimize it</strong></h4><p>Keeping it simple is a great starting point, but companies will want to see if you can optimize your solution. This is where you start to think about using data structures and other programming techniques (dynamic programming, etc.) to improve your solution.</p><blockquote>Optimizing your solution can sometimes mean there are other tradeoffs. Often a solution with better time complexity could have worse space complexity. Interviewers want to see if you can discuss these tradeoffs.</blockquote><h4><strong>5. Test, test, test</strong></h4><p>Good programmers don’t just write code and assume it works. You need to try to break your solution! If you do, that’s a good thing, not a bad thing. Think about edge cases, and demonstrate that you have the competency to walk through your code using examples.</p><h3>Conclusion</h3><p>Acing the technical interview goes beyond getting the best answer in the shortest amount of time. Companies are looking for individuals with strong communication skills, good programming practices, and relevant experience. The best practice you can do is to keep coding — either working on projects to improve the relevance of your experience, or to practice technical interview questions.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=386fdc073425" width="1" height="1" alt=""><hr><p><a href="https://medium.com/hatchways/acing-the-technical-interview-lessons-from-30-tech-companies-386fdc073425">Acing the Technical Interview: Lessons from 30 Tech Companies</a> was originally published in <a href="https://medium.com/hatchways">Hatchways</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Building IPLv2 in Kik]]></title>
            <link>https://medium.com/kinblog/building-iplv2-in-kik-4c2b127d9a9?source=rss-a7acab38630------2</link>
            <guid isPermaLink="false">https://medium.com/p/4c2b127d9a9</guid>
            <category><![CDATA[developer]]></category>
            <category><![CDATA[kik]]></category>
            <category><![CDATA[bots]]></category>
            <category><![CDATA[kin]]></category>
            <dc:creator><![CDATA[Shums Kassam]]></dc:creator>
            <pubDate>Fri, 05 Jan 2018 17:09:25 GMT</pubDate>
            <atom:updated>2018-09-13T19:23:09.843Z</atom:updated>
            <content:encoded><![CDATA[<p>Recently we launched the first<a href="https://medium.com/kinfoundation/first-kin-earn-and-spend-experiences-live-in-kik-762b5760b103"> Kin earn and spend opportunities in Kik</a>, which we have been calling IPLv2. The goal of IPLv2 as discussed in a<a href="https://medium.com/kinfoundation/iplv2-product-overview-45c59f321c8a"> previous post</a> was to introduce crypto to Kik users, minimize time to production and experiment with a two-sided economy. Today, we’ll review the high level technical details of the project, and how we minimized time to production.</p><p>The end result is a workflow that would allow any bot to use Kin, but only to the small number of restricted users on Kik that are able to participate in the IPLv2 Kin experience.</p><p>To start, I should probably introduce our team’s role in the project. Located in Toronto, our team is responsible for the development and design of the <a href="https://dev.kik.com/">Bots Platform</a> at Kik. Using the Kikteam bot to introduce our power users to Kin was a natural choice. Our team built the Kikteam bot experience as well as the UI for the Kin wallet.</p><h3>The Kik Team Experience</h3><p>Kikteam is every Kik user’s first friend — it was the logical choice to use as an introduction to Kin to our users. In IPLv2, this bot also takes care of sending the user polls, and rewards them for answering poll questions:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*4u6asm0YHDzYRGzY." /><figcaption>Kik Team Onboarding User Experience</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*yeT-9h5U5EqcJCMe." /><figcaption>Kik Team Survey Experience</figcaption></figure><h3>Wallet UI</h3><p>Our team was also responsible for the frontend development of the Kin wallet in Kik. This wallet interacts with the different earning and spending services and also contains a bridge to call native code, which handles sending Kin and store the user’s Kin wallet.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/375/1*E8YI6BTv5IV5ViUzFpBvbg.gif" /><figcaption>Kin Wallet UI</figcaption></figure><p>Now, let’s take a moment to talk about the components involved in building this project.</p><h3>The Components</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*4CsOtHb8SqOMj1o2." /></figure><h3>IPLV2 Components Breakdown</h3><p>The diagram above shows all of the implementation components and where they live. Note, that Kik and Kin are separate, because none of the Kin components are specific to Kik. In fact, they can be used by any mobile service. For IPLV2, the service that’s using them is Kik.</p><p>Let’s examine each of the components.</p><h3><a href="https://github.com/kinfoundation/erc20token-sdk-python">ERC20 Token Python SDK</a></h3><p>This python SDK allows any web developer to send and receive Kin. In our example, our third-party service uses this repo to send Kin to users given their public address. In order to access the public address of the user, the service must use the wallet.</p><h3>Third-Party Service Web Server</h3><p>This component is the web server that powers the Kikteam bot, and uses the ERC20 Token Python SDK to send and receive Kin.</p><h3>Third-Party Service Frontend Website</h3><p>This component is the frontend webpage associated with the web server. It is allowed to interact with a component called Kin.js — which calls the KinPlugin either directly or via the wallet.</p><h3>Kin.js</h3><p>A javascript library that allows a webpage to grab information about the user’s wallet. It can be called by any web page on Kik — however, only the wallet can access some of its functionality. It utilizes a bridge that calls mobile code from the web browser. Kin.js provides a number of important interfaces for Kin integration:</p><h4>isWalletAvailable:</h4><ul><li>Available to all web pages on Kik</li><li>Indicates whether a user has a Kin wallet or not</li></ul><h4>getPublicAddress:</h4><ul><li>Available to the wallet only</li><li>Retrieves the public address of the current user’s Kin wallet</li><li>A 3rd party website can call this function, however the Kik app will open the wallet (which has the actual permissions to get the public address) and display this page:</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/375/0*OGgyjBgiz_HG_7ca." /></figure><ul><li>The data is passed back to the third-party website if the user accepts the request — this is all facilitated through<a href="https://dev.kik.com/#/docs/kikjs#picker-mode"> kik.js (picker mode)</a></li></ul><h4>sendKin:</h4><ul><li>Available to the wallet only</li><li>Sends the amount of Kin from the current user’s wallet to a specified address</li><li>Similar to getPublicAddress, a 3rd party site can call this function, and the following page is presented to the user:</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/375/0*Z5tuAuSaro9h8OLG." /></figure><ul><li>If the user accepts, the transaction ID is passed as data back to the requesting 3rd party site</li></ul><h4>getOrCreateWallet:</h4><ul><li>Available only to wallet</li><li>Returns the existing Kin wallet (public address and private key) or creates a new wallet and returns that</li></ul><h4><strong>exportKeyStore:</strong></h4><ul><li>Available only to wallet</li><li>Returns the key store of the current Kin wallet for import into a new wallet</li></ul><h3>Wallet:</h3><p>The frontend website that has access (via kin.js) to the user’s Kin wallet. This wallet has access to all the functions described in the section above.</p><h3>KinPlugin:</h3><p>The native mobile code that wraps the Kin SDK. Kin.js uses a custom bridge to call the native mobile code written in this component.</p><h3>Kin SDK:</h3><p>The SDK that communicates with the blockchain — it securely stores the private key (and the public address), which can never leave this SDK, as well as can send Kin, and get the balance of the user’s Wallet.</p><h3>Time to Market</h3><p><a href="https://chatbotsmagazine.com/were-the-architects-and-the-builders-bc560c727ae9">We work iteratively,</a> so we tried to reuse as much of our existing infrastructure as possible. In this way, we were able to bring our experiment to the masses very quickly.</p><p>The main criteria we used to build IPLv2 was speed to completion. We decided to do most of the work through frontend and backend web code, as opposed to rely on slow review cycles that are introduced by writing native code.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4c2b127d9a9" width="1" height="1" alt=""><hr><p><a href="https://medium.com/kinblog/building-iplv2-in-kik-4c2b127d9a9">Building IPLv2 in Kik</a> was originally published in <a href="https://medium.com/kinblog">Kin Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>