<?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 Mahima Chawla on Medium]]></title>
        <description><![CDATA[Stories by Mahima Chawla on Medium]]></description>
        <link>https://medium.com/@startuptechnologist?source=rss-4599fd0cdcd5------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*ZXvZGt58ysX3cgnNM-2l6g.jpeg</url>
            <title>Stories by Mahima Chawla on Medium</title>
            <link>https://medium.com/@startuptechnologist?source=rss-4599fd0cdcd5------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 02:43:18 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@startuptechnologist/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[Gaps in the Education, Hiring and Retention of Software Engineers]]></title>
            <link>https://medium.com/@startuptechnologist/gaps-in-the-education-hiring-and-retention-of-software-engineers-6c5fd435cf09?source=rss-4599fd0cdcd5------2</link>
            <guid isPermaLink="false">https://medium.com/p/6c5fd435cf09</guid>
            <category><![CDATA[technical-recruiting]]></category>
            <category><![CDATA[computer-science-student]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[women-in-tech]]></category>
            <category><![CDATA[computer-science]]></category>
            <dc:creator><![CDATA[Mahima Chawla]]></dc:creator>
            <pubDate>Mon, 27 Dec 2021 23:34:44 GMT</pubDate>
            <atom:updated>2021-12-27T23:34:44.259Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/470/1*e4CkuguLid8cg85TNIT3Rw.jpeg" /></figure><p>Software engineering is a misunderstood career. While one can, and usually does, enter into software engineering with a background in computer science, the knowledge-sets required for software engineering are vastly different to those of software engineering. The relationship between software engineering and computer science is similar to the one between lawyers and English majors. An English major, <em>without appropriate training in law</em>, will not make a competent lawyer. Doing well in both computer science and as a software engineer requires analytical thinking and complex reasoning, but there are few shared characteristics beyond those.</p><blockquote>The most likely candidate to break into tech today, however, has the following two qualities:</blockquote><blockquote>At least one computer science degree from a recognized university, and</blockquote><blockquote>Leetcode proficiency developed and honed over months or years</blockquote><p>Prestige hiring and credentialing is the leading cause of the rampant diversity problem in tech, and why good candidates are kept out while ‘traditional’ candidates are brought in. Eliminating candidates based on their academic laurels is a form of gatekeeping that has been behind the supposed “pipeline problem” in tech which implies that the lack of good candidates is due to there not being enough good candidates, and not due to looking in the wrong places and measuring the wrong things. This exempts technical recruitment from <strong>considering non-traditional backgrounds such as being self-taught, or bootcamp-taught as equally qualified, and from reforming technical interview to be more inclusive.</strong></p><p>Leetcode is the name of a platform that has become synonymous with the content offered on the platform. The content comprises questions such as “given a list of numbers, find the 3 that add up to the target sum 75”, which are then solved in code. The goal is to solve this quickly and efficiently, so that the method used takes the operating system the least amount of time and memory possible. The questions share less in common with math problems, where formulas remain the same and are applied on different inputs, but instead, are more akin to riddles, in that the coder has to find a pattern first, and translate the pattern to code after.</p><p>These riddles are extremely hard to crack consistently, even for engineers with decades of experience. <strong>The problems are entirely unrelated to the actual role of a software engineer, and are therefore a very weak signal on software engineers.</strong> The reason Leetcode is still the interviewing standard of the industry is that it allows just the right percentage of people to succeed. A method is needed that can weed out a very large portion of the applicant pool, while still appearing fair and somewhat related to the job, which leetcode provides.</p><p>Far from fair, however, practicing leetcode problems requires solving a few hundred problems and memorizing the tricks used to solve them. Some companies, like Facebook, even send lists of hundreds of practice problems to applicants before their interviews. These problems take at least a few months to work through, even for experienced software engineers, given how different they are from any problem a software engineer faces on the job. <strong>This means that for a candidate to break into tech or move around within tech, several months of unpaid labor are required, which may not be an option for many.</strong></p><p>Once a candidate plays the numbers game and eventually breaks into the role of a software engineer, however, they find themselves completely unprepared for the role. <strong>Today, the majority of software engineering is learned on the job in the first 3–6 months in the role</strong>. Until then, a new engineer is expected to have a net negative impact on the output of the team.</p><p>In the first 3- 6 months, the engineer’s primary resource to learn is usually another, more experienced engineer on the team. While this is best practice at the moment, it presents several challenges. The foremost inefficacy of this onboarding system is that <strong>it asks experienced engineers to perform the daunting task of teaching someone years worth of unorganized googling via 30-minute pairing sessions</strong>. The statement “I don’t know what I don’t know” is a sentiment early career software engineers share, thus making pairing sessions ineffective. Imposter syndrome tends to spike, leaving many thinking they are simply not cut out for the role.</p><p>Technologies, frameworks, best practices, design patterns and stacks are extremely variable, which functions as a cover for the fact that most engineers are severely unprepared for the role, since even experienced engineers need to constantly learn. Hidden behind jokes about a software engineer’s job being primarily googling how to solve problems, is the fact that initially, panicked googling and pretending to know what one is doing is the only way for new engineers to slowly develop an understanding of the field.</p><p>This problem can currently be circumvented via software engineering bootcamps geared towards creating professionals in the field. These bootcamps are taught by experts working in the field and the syllabus is based on skills useful to the job, such as relevant frameworks and design patterns. However, <strong>bootcamp candidates have a harder time pushing through prestige hiring</strong>. Another solution to avoid the uphill battle of onboarding is for aspiring software engineers to take on “personal projects”, or innovative projects demonstrating a deep understanding of one or more technologies commonly used in the industry. The expectation is for a singular, inexperienced engineer to perform the unpaid labor of creating an industry-standard project over several months to demonstrate know-how as a beginner, only to move past the initial resumé screen. It goes without saying that <strong>only a small percentage of aspiring software engineers are able to commit to and complete impressive personal projects, therefore creating another high barrier to entry and contributing to the perceived “pipeline problem”</strong>.</p><p>Beyond the first 6 months, software engineers’ main challenge remains upskilling throughout their career. Teams are forced to constantly reevaluate the efficacy of their tools and frameworks for the solution they are building, which leads to frequent changes in their stacks. An engineer with years of experience in a language, may now need to transition to one they have never worked in. The problem of continuous development is currently solved by training budgets that allow for engineers to take online courses and read books, but the pattern most commonly employed tends to be to let the engineers figure it out as they go. This means that as a piece of code needs to be translated to a new language, the engineer starts to read through the documentation for precisely the parts they need to learn and applies it immediately. <strong>Over time, experienced engineers possess large magnitudes of experiential learning, that doesn’t clearly translate to expertise in any one topic. Experienced engineers are instead, masters of learning how to learn quickly and efficiently, by accessing resources such as documentation, Stack Overflow and trial and error.</strong></p><p>This reinforces imposter syndrome among experienced engineers able to create impressive works, but unable to account for exactly what they know. It also makes it harder to measure a good engineer when everyone’s experiences have been different, leading to expertise that looks very different. If every expert knows different subjects in depth, how does one measure an expert?</p><p>These questions plague tech companies in recruitment and also in retention. Engineers can not be categorized by the quantitative value they add to the company, since lines of code or complexity of code doesn’t translate to value. Instead, their performance is measured by qualitative attributes such as how well they executed a large project. This can include how well they managed communications, how the project was perceived, whether it was within the intended timeline etc. Mentorship is often one of the qualitative measures. These measures are feeble and very prone to unconscious bias. Good communication, leadership, organization, execution and mentorship is subjective. <strong>The engineering career ladders reinforce stereotypes of who seems like a good software engineer, which tends to falter to who seems like a “traditionally” good software engineer</strong>.</p><blockquote>Innovative solutions for the following problem spaces, are therefore needed for the industry to unlock, hone and retain talent:</blockquote><blockquote>1. The ability to measure early-career/potential software engineers using stronger indicators than leetcode, and more equitable indicators than university degrees.</blockquote><blockquote>2. The ability to measure experienced software engineers for their vast, intricate and unorganized technical knowledge and contribution.</blockquote><blockquote>3. Effectively onboarding new/early-career software engineers and reducing their dependence on teammates that may/ may not be good teachers.</blockquote><blockquote>4. Creating a sense of community for students from underrepresented backgrounds to allow them to participate in the crucial developmental activities including pair programming, group projects and hackathons.</blockquote><blockquote>5. Creating a sense of community and belonging for software engineers from underrepresented backgrounds.</blockquote><blockquote>6. Helping software engineers continuously upskill, and organize their learning to make a clear case for their increased value and progression.</blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6c5fd435cf09" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Handbook For Your First Week As A Software Developer]]></title>
            <link>https://medium.com/@startuptechnologist/handbook-for-your-first-week-as-a-software-developer-741c6bc208f0?source=rss-4599fd0cdcd5------2</link>
            <guid isPermaLink="false">https://medium.com/p/741c6bc208f0</guid>
            <category><![CDATA[career-change]]></category>
            <category><![CDATA[first-jobs-out-of-college]]></category>
            <category><![CDATA[internships]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[first-job]]></category>
            <dc:creator><![CDATA[Mahima Chawla]]></dc:creator>
            <pubDate>Tue, 20 Nov 2018 04:35:40 GMT</pubDate>
            <atom:updated>2018-11-20T04:35:40.776Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/425/1*exGtb2kJ7C04g6PberLhxw.jpeg" /></figure><p>Take a moment to think about how today has been so far. Every thought, action, event, and feeling today has been the culmination of many years of deliberate work, decisions, and perseverance. Although life may often feel like it’s simply “going with the flow”, each day is shaped by the millions before it; In order to reach one’s career goals, it’s crucial to harness the power of that first day, first week, first month and set the right tone to make the climb towards one’s goals a natural flow.</p><p>Habit formation is known to be the key to success, and interestingly, it’s easiest to form new habits when there is a natural life-altering change: A new job, a new home, travel — all trigger the formation of new habits, which in turn change the pattern of our lives. Over the years, I’ve worked hard to ensure that I start my career on the right foot and set the optimal tone for my ambitioned future. I have learned through trial and error, had regrets and big successes and have developed a successful methodology for an intentional and impactful first week as a software developer for those who want to go beyond simply what is expected.</p><p><strong>Create a high-level success routine</strong>, not just for the morning before work or the night before work the next day, but for the hours that you are <em>at</em> work. Thinking of an 8 hour work day as one solid block of time is an easy way to kill productivity and feel worn out. A truer interpretation of a work day resembles a typical school day: An introspective student will know to create separate blocks of time for tasks that involve different types of work: Programs, readings, math, and participating in student organizations, all require different parts of your brain, and performing them at different and suitable times, locations and durations help perform each one to the best quality.</p><p>I didn’t realize this initially, and interpreted an 8-hour work-day as a marathon: one long stretch to get as much code out as possible. Here’s a typical result of such an approach:</p><blockquote>Passionate, hard-working intern M wants to get as much done as possible, and therefore comes into office at 10 am and vows not to move until they have solved 3 stories/bugs. According to M, the most efficient way to do this is to jump into the code and start fixing. M is brilliant and ends up completing the development of the first task. They then send it out to be peer reviewed. It’s going to be at least a few hours until they hear back from their colleagues, so M jumps right into the next task and starts writing code. This task is a little more complicated so M struggles and then reaches out to someone knowledgeable. However, M still has this “maximize development to maximize productivity” mindset, and so M starts the third story.</blockquote><blockquote>M walks out at the end of the day exhausted, not having truly completed a task but worked non-stop on writing code. Regardless, M is sure they will be able to send all three tasks to completion tomorrow. The next day, however, while motivation is high again, M goes back to writing more code and dipping their fingers in more tasks. M takes no time for maintenance, clean-up, and other such routine activities. The cycle repeats until M has pushed through and written the code for all their stories, however, none of them are peer-reviewed, none of them are corrected according to peer suggestions, the team is unsure of the status of any of M’s stories since they are all still “dev-complete” but nowhere near being closed, and M is stressed out because although they have written all the code, they are one day away from the deadline and none of their tasks are near completion.</blockquote><p>Not only does concentrating only on the development portion of tasks lead to last-minute stress, but the peer review, testing, and integrations can often take a longer time than anticipated, and create a delay in closing tasks which will throw off the team’s velocity. Additionally, this approach doesn’t allow agile tools like JIRA to accurately collect data on time spent developing solutions since tasks were simply sitting ‘in development’ while M was working on other tasks.</p><p>This is why it’s important to create time for maintenance on a daily basis and strategize for each kind of activity to be in an individual chunk of time to avoid similar-task burnout and ensure that one performs rituals that will keep the system on track daily, without falling into a game of perennial catch-up. The maintenance tasks necessary include the following:</p><ol><li><strong>Research:</strong> Gain context on the problem, brainstorm other possible solutions or methods of implementing solutions, define completion tests, clear distractions, gain as much background information on the system, tool, and architecture as possible.</li><li><strong>Code Writing</strong></li><li><strong>Peer Reviewing</strong>: Set time apart daily to either put code out for reviewing or review a teammate’s code.</li><li><strong>Closing</strong>: Attempt to test, perform all integrations, and overcome any challenges Github may pose, to keep all progress ready to be merged and submitted.</li></ol><p>Performing these rituals daily is what makes one a good software developer, however, in order to make big strides towards one’s overarching career goals, it’s important that one also performs daily tasks towards professional development.<strong> Creating habits that keep motivation high and keeps one moving forward with their larger ambition requires a daily appointment as well.</strong></p><p><strong>Setting up meetings related to projects, ideas or research outside of assigned tasks</strong> is an easy way to gain knowledge, resources and share positive, motivational energy with others within the organization. Whether it be someone in sales or the CEO, there is no better way to stick to your goals than sharing them with others and keeping yourself accountable. It’s also the most efficient way to gain insight into a different sector of the organization in a short amount of time. Creating such appointments help keep that pep in one’s step, and creates excitement about new interactions and opportunities.</p><p>On days without such an appointment, spending time feeding one’s creator personality will provide fodder to discuss over upcoming meetings, and is the time when true progress will be made on larger goals related to career growth. <strong>Thinking of activities and initiatives that are exciting outside of work, and finding a way to marry it with one of the organization’s goals </strong>is an easy method of finding a project idea that one is passionate about. Some examples could be starting a program to give back to the community, a lunch-talk series, a workout group, an intern walk-and-share, a mini-hackathon, or, as I once did, researching productivity killers in different departments and coming up with solutions.</p><p>If coming up with a project idea is intimidating, one could also take a different approach to taking initiative: A proposal for a new tool, a different way of using an old tool, a unique architectural approach, an unusual metric to record, a weekly presentation, or an additional scrum meeting: Such <strong>optimizations to pre-existing systems can prove to be big projects on their own</strong>, and help one gain a quicker, deeper understanding of systems, take on a leadership role as a “faux expert” and help one meet and pitch to other colleagues. Looking for such solutions develops an inquisitive mindset that is invaluable. Taking the time to be the person that constantly thinks of ways to optimize and improve the organization and the software produced will lead to interesting questioning and innovative suggestions. This is a key characteristic in a problem-solver, an entrepreneur and a leader.</p><p>One of the largest assets to be gained from a new job is the social capital, and the first week of meeting a lot of new people can be exhausting, intimidating and often, futile if not done correctly. It is unrealistic to expect to remember all the names and details of the people introduced to you, and therefore, it is important to concentrate on<strong> creating a few truly memorable conversations and relationships</strong>. Knowing the names of, or being connected on LinkedIn with a hundred people is less valuable than a real friendship and connection with a colleague, and it is important to initiate some of these friendships as early as possible. Asking meaningful questions, investing time and following-up on conversations with a few people will lead to far better opportunities than hundreds of acquaintances.</p><p>The first week on a new job is when one can choose who they are going to be and situate in that personality and those habits. While it’s easy to simply fall into the role of being a shy intern that speaks when spoken to, it’s not easy to bloom into an employee that is integral to the operation and respected by their team. Being deliberate in developing one’s professional personality right at the beginning will accelerate the journey to the top. Well begun is half done!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=741c6bc208f0" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What To Say Over Coffee with the CEO]]></title>
            <link>https://medium.com/@startuptechnologist/what-to-say-over-coffee-with-the-ceo-3b0eafdeecce?source=rss-4599fd0cdcd5------2</link>
            <guid isPermaLink="false">https://medium.com/p/3b0eafdeecce</guid>
            <category><![CDATA[social-capital]]></category>
            <category><![CDATA[intern]]></category>
            <category><![CDATA[professional-development]]></category>
            <category><![CDATA[conversations]]></category>
            <category><![CDATA[ceo]]></category>
            <dc:creator><![CDATA[Mahima Chawla]]></dc:creator>
            <pubDate>Wed, 07 Nov 2018 22:14:03 GMT</pubDate>
            <atom:updated>2018-11-07T22:14:03.792Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>What To Say Over Coffee with the CEO</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7KHf8QzlY32Or7qRrjB51Q.jpeg" /></figure><p>There is hardly an easier time to connect with executive leadership than during an internship. The company has a vested interest in its interns, considering they’re essentially spending resources on training you with the hope of a return on investment. As an intern, one is also inherently more interesting than a regular employee — a fresh energy, one foot still in higher education, an unchartered plethora of opportunities, and the Gen Z advantage. It’s often true that simply the Gen Z advantage, and a completely new perspective, can solve some of the hardest problems that the company is dealing with — an innocent question could spark an idea, a cultural misunderstanding could create a solution, and the signature unearned confidence could lead the next big project. Higher leadership is fascinated by us youngins, and rightly so. And therefore, as an intern, it would be a wasted opportunity to not attempt to form a real connection with people that would exponentiate one’s social capital, such as executive leadership.</p><p>Now, let’s say, you took the leap, reached out to the CEO to discuss some of your “most interesting findings and ideas over the past three months”, and have been granted a classic 15-minute slot to juice this metaphorical orange. Congratulations, you’ve already done more than the average ‘keep your head down’ intern, and are now up against the overachieving population of students that have also grabbed this opportunity. The challenge now, however, is two-fold. One, anticipating social interaction is not always possible — one might say all the right things, but simply not achieve a deep connection. And two, there’s inherently stiffer competition for this person’s attention than most. In order to maintain your advantage and ensure success, it’s important to prepare suitably, and this includes planning conversation starters, openers and closers, a call-to-action, and most importantly, your mindset.</p><p>While the soft skills for an impactful conversation remain the same: allowing the other person to talk, listening intently and noticeably and leading the conversation to where they want to take it naturally, this specific scenario requires a stronger game plan. I, therefore, created a checklist to maximize the outcome from any short yet important conversation.</p><p>1. Plan out and practice the moment you meet, and the moment you depart. These are crucial to setting the tone and greatly impact how you the experience will be remembered. Your introduction should be smooth, deliberate and include an informal thesis statement- to allow for a clear context switch. Think of a lecture where your professor doesn’t begin with “Today we will discuss…” — it’s a lot harder to pick up the material without context. When meeting someone from a different world than you, that probably doesn’t have a lot in common with you, it’s necessary to portray the sentiment that this is a natural connection, that you are meant to be there, and that there is nothing awkward about this conversation. Let that shine through your glib introduction and breezy goodbye.</p><p>2. Think of a problem you found and a solution you implemented or were part of. This could be really small, in fact, surprisingly, the more miniscule the better. There are a few reasons this is important: it touches upon the common base that is the organization and the shared sentiment of helping it grow. Additionally, although the executive leadership team wants to, and feels a responsibility to know about everything going on in the company, it’s simply not possible. However, this mini catch-up is more valuable to them, because they get to feel involved in some of the inner workings, and get to seem knowledgeable about such intricacies at the next high-level meeting. Any node of information you share with someone that gets them to make a mental note also includes a pointer to you, and portrays you as passionate, well versed in the systems, and a problem-solver.</p><p>3. A faux revolutionary idea. This is the bit that will take the most planning, and a couple eureka moments to figure out but don’t waste an opportunity to meet one of the most rewarded high-level thinkers of the organization, and not speak with them on their level. Spend the majority of your preparation time coming up with one solid, revolutionary idea for the company — it requires no actual execution, and you don’t really need to ever follow up, but make it exciting, buzzworthy, and with clear, defined positive outcomes. Successful entrepreneurs, idea machines, and deep thinkers enjoy absurdly ambitious and interesting proposals, and will often look past the immediate hurdles and practicalities and savor the possibility of a revolutionary change. It is this endorphin rush from new ideas and possibilities that brought them there, so give them something to enjoy, mull over, and even if you end up deciding it won’t work — it’s the kind of conversation they’ll find most enjoyable, and will provide most interesting insight on.</p><p>4. If you still have a few moments, touch on a recent news story or a finding in a domain of mutual interest — whether that be fitness, apparel, America or even just entrepreneurship. Not only is it an easy and smart conversation to have, but will keep you memorable when that topic is touched upon and serves as a “proof of camaraderie”. Future emails could include more information on “the interesting conversation we had about *insert topic here*”.</p><p>5. Always give people a way to support you, especially when they are in the position to do so. Choose a personal project that you think will greatly benefit from their possible association and don’t be afraid to bring it up. Even if they decline your particular request, they may still look up the project later out of curiosity, or mention it to someone else. On the other hand, if this goes well for you, it also provides a great segue into asking for a method of maintaining contact that they will actually pay attention to. Read the vibe, the project and the person — this may range from a Snapchat to a work email or even a mutual contact’s email.</p><p>Maintain strong body language, and enjoy your conversation. Your social interaction is already far richer than your average day and has provided you with an incredible learning experience, savor it. Regardless of the outcome, whether you successfully form a memorable connection or not, realize how at this moment, you are interacting with one of the most important and possibly, inspirational people you have recently, and the value of your social capital has increased tremendously. Absorb the energy, feel worthy of that conversation and realize the prospect of a future of many more such intelligent, enriching conversations and connections.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3b0eafdeecce" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Lasting Impressions Are The Key To Parties and Careers]]></title>
            <link>https://medium.com/@startuptechnologist/lasting-impressions-are-the-key-to-parties-and-careers-4fa0682f1c1c?source=rss-4599fd0cdcd5------2</link>
            <guid isPermaLink="false">https://medium.com/p/4fa0682f1c1c</guid>
            <category><![CDATA[career-advice]]></category>
            <category><![CDATA[college-life]]></category>
            <category><![CDATA[first-impressions]]></category>
            <category><![CDATA[job-hunting]]></category>
            <category><![CDATA[career-fair]]></category>
            <dc:creator><![CDATA[Mahima Chawla]]></dc:creator>
            <pubDate>Sun, 30 Sep 2018 02:36:12 GMT</pubDate>
            <atom:updated>2018-09-30T02:36:12.955Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*B3MXyoz9g-xBcUC8m_APXQ.jpeg" /></figure><p>Looking back at the past three years as an undergraduate at the world’s best party school (go Badgers!), I realize that I have gained a unique perspective on human interactions through the positions I have held. I have been on both sides of opportunities: the vying hustler, as well as the offeror. I have hustled for opportunities and been in the privileged position of giving out the same opportunities: For example, while I have been the freshman trying to get into a party, the campaigner trying to votes, the board member trying to make it to President, the student trying to get a job, and the intern trying to get a recommendation, I have also been the president, the director, the recruiter, the student body representative and the person with the free booze. Seeing the same situation from both sides in such a short period of time has given me a unique perspective on each interaction that involves a seeker of opportunities and a giver of opportunities. Deep introspection of these interactions has led me to the conclusion that opportunities walk up and present themselves to the people with the most lasting, positive impressions.</p><p>We all have resources that are valuable: friends, connections, invitations, positions, funds, answers, knowledge, experience, material items, and given the right person and moment, we have all been willing to share these resources or pass them down. As a seeker of opportunities, it is critical to be that right person and to create that right moment with as much of your social network as possible. Like any other skill, the art of creating an impression can be finessed. Below, I will explain some actionable tactics I use to create a lasting impression in a short period of time, but before I get into it, I’m itching to share a PSA that’s unrelated to behavioral tactics and is, instead, the olfactory component of creating an impression. Career fairs, parties, networking events, happy hours- they’re all long, late and adrenaline-inducing, which means a lot of coffee or other clinging beverages, and a lot of sweat. Looking fresh and smelling good makes a big difference in how much people subconsciously enjoy hearing you talk, and how positively you’ll be remembered.</p><p><strong>Develop a host-attitude</strong>. This is the attitude that helps me integrate at parties where I don’t really know anyone, which happens more often than you’d think. The truth about parties is that no one belongs there, and everyone does. The venue is no one’s home, a lot of people haven’t come with friends, a lot of people aren’t even invited, a lot of people show up with friends that they don’t like or that don’t like them — yet everyone wants to integrate. In such situations, I play the host. I play the person that introduces you to other people, asks you if you need a drink, and encourages the groups to get on the dance floor. Develop a host attitude because anyone can, and stepping up to it creates an impression that you truly belong, are comfortable and are important. At a career fair, I would walk up to representatives that I wanted to build a relationship with, Google representatives for example, and offer them swag from the company I interned at, ClassPass. I’d talk to them about ClassPass, ask them about their experience at the career fair, how they feel about the applicants they’ve met, talk about my experience with applicants, and in general take on a host attitude. It just so happens that this host or ‘faux-recruiter’, is actually still a student and has resumés on her. Just like at parties, this differentiates you — it differentiates your vibe, makes you more important, comfortable to talk to and builds deeper relationships.</p><p><strong>Take time, but leave on a high point</strong>. Don’t rush the conversation. The key is to get the giver of opportunities so interested in the conversation — whether it be about their kids, cows, or an anthropology course they took in college — that they want to spend their time talking to you. Don’t feel guilty about keeping the 50 people in line waiting, or that they’ve got other things to do. Time is an expensive investment and is directly related to how memorable you will be. If they put in a good chunk of time talking to you, they will look at you when you leave and subconsciously think “hey, I got a lot off my chest, I felt like I communicated about things important to me and felt heard and understood, I feel good!” and put that little star on your resume that will take you just a little further. But there are caveats to this rule: sometimes it just doesn’t feel right: the conversation starts dwindling, or a connection is simply not developing — it is crucial to leave before it gets to that point. Don’t push it. If things go well, leave while there is still a lot in the inventory to talk about. Take the hint and leave before you get the vibe that they want to move on.</p><p><strong>Choose the right opportunity giver</strong>. A lot of things in life are random and based on chance, but a large portion of these don’t actually have to be based on luck if we don’t want them to be. Identify the person at the booth that you want to talk to, and don’t let yourself be randomly assigned. The person you want to talk to is the one that seems to be giving others their full attention, seems talkative and if you can pick up on the vibe, seems important. This is usually the person with the host-attitude and the person with the highest likelihood of creating a deep relationship in a short time. Ask to talk to them — say you have a question about something you heard them say, or read their badge and ask a position-specific question. Create an impromptu excuse for why you need to talk to that person specifically, and you will.</p><p><strong>Give prompts, but don’t be the talker</strong>. One of the biggest lessons from my holy grail self-help book, ‘How To Win Friends and Influence People’ is that positive associations are much higher when you allow the other person to talk, while you listen attentively. When people feel heard, understood, and validated — they like you. It’s that simple. Ask intelligent and relevant questions and guide the conversation where you want it to go, but don’t do the most talking. Whether it be at an interview, a bar, or a police station — letting the other person explain and vent while you listen attentively is often the best route.</p><p><strong>Make your compliments over the top or don’t give one at all.</strong> If you’re too embarrassed to give a compliment that is truly memorable and will make the giver of opportunities walk out of the room while still thinking about what you said and smiling to themselves, then don’t bother giving a compliment at all. Don’t give the “wow”s or the “that’s impressive”s or the “that’s so cool”s because these half-hearted appreciations will either be smiled at and forgotten or worse still, thought of as flattery. However, if you find something unique and truly praiseworthy about what they tell you about themselves, be generous with your compliments. If they seem to have advanced in their career at an impressive pace, ask them to post about their journey on social media because of the huge impact it would have on other women in technology trying to boost their career and looking for role models. That’s a meaningful, heartfelt compliment they will remember and probably think about the next time they post on LinkedIn.</p><p><strong>Don’t sound rehearsed.</strong> You may be a glib talker with a great vocabulary, but your pitch shouldn’t sound like a pitch.</p><p><strong>You don’t have to share every related anecdote</strong>. Steer the conversation where they want it to go, to topics they seem to want to talk about even if you’re not particularly interested. Just because you have a story that related, doesn’t mean you should tell it. Give succinct, intelligent comments, and be clever in where you take the conversation.</p><p><strong>Respond with your expressions</strong>. Let your expressions respond to what they’re telling you! Even if it feels exaggerated and silly at first, it is important to look deeply interested and respond, laugh, and engage without taking the mic back. Facial expressions are the easiest and most instant way to do that. Make them feel like a great storyteller and let yourself be hooked!</p><p>Instant and deep connections have always proven far better at bringing me absurdly cool, unexpected opportunities than any other relationships, even long-term friendships, because you are immediately opening yourself up to a whole new world that someone else is excelling at, or has access to. Every day is an interview because every day someone needs a crowd at their party and or an employee at their company. Mastering the art of impressions is what will make you memorable when that opportunity arises.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4fa0682f1c1c" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>