<?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[Data Diva - Medium]]></title>
        <description><![CDATA[Ramblings About Data &amp; Feminism - Medium]]></description>
        <link>https://medium.com/data-diva?source=rss----dfd57f837653---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>Data Diva - Medium</title>
            <link>https://medium.com/data-diva?source=rss----dfd57f837653---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 20:26:25 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/data-diva" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[So You Want to Be a Data Scientist?]]></title>
            <link>https://medium.com/data-diva/so-you-want-to-be-a-data-scientist-7722a547a429?source=rss----dfd57f837653---4</link>
            <guid isPermaLink="false">https://medium.com/p/7722a547a429</guid>
            <category><![CDATA[data]]></category>
            <category><![CDATA[data-science]]></category>
            <category><![CDATA[analytics]]></category>
            <dc:creator><![CDATA[Jessica Kirkpatrick]]></dc:creator>
            <pubDate>Thu, 02 Jul 2015 03:21:13 GMT</pubDate>
            <atom:updated>2015-07-02T03:30:08.859Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/699/1*BNJmk_vJwmtBugDhUPtWyw.jpeg" /></figure><h4>A compilation of my writing on the topic.</h4><p>People reach out to me a lot asking how I got into data science and wanting advice about breaking into the field. Fortunately this is something I have written and talked about quite a bit!</p><p>Below is a compilation of the various things I have “out there” about my transition from academia to data scientist and what it’s like to be a data scientist:</p><p><a href="http://berkeleyjess.blogspot.com/2015/04/what-is-data-scientist.html">What is a Data Scientist?</a><br>General overview the answers to some frequently asked questions.</p><p><strong>Transitioning Advice / Information</strong><br><a href="https://medium.com/data-diva/astronomer-to-data-diva-e3c457f6621d">Astronomer to Data Scientist</a><br>Advice on how to make the transition from academia to data scientist.</p><p><a href="http://berkeleyjess.blogspot.com/2015/01/astrophysicist-to-data-scientist-talk.html">Astronomer to Data Scientist (Talk)</a><br>More advice, and some details about what I do for my job.</p><p><a href="http://womeninastronomy.blogspot.com/2013/01/astroVdatascience.html">Astronomy vs. Data Science</a><br>Compares and contrasts academia and the tech industry.</p><p><a href="https://medium.com/data-diva/nailing-the-tech-interview-a0e28e9bc608">Nailing the Data Science Interview</a><br>Advice for preparing for your interview and what to expect.</p><p><strong>Interviews</strong><br><a href="http://ladyparagons.com/2014/04/women-in-tech-interview-with-jessica-kirkpatrick-director-of-data-science-at-instaedu/">Interview with Lady Paragons</a><br>What my job is like, what I do, some other stuff too.</p><p><a href="http://ladyparagons.com/2014/07/women-in-stem-podcast-episode-2-jessica-kirkpatrick-director-of-data-science-at-instaedu/">Podcast with Lady Paragons</a><br>More about what it is like to be a data scientist.</p><p><a href="http://womeninastronomy.blogspot.com/2014/06/career-profiles-astronomer-to-data.html">Interview with AAS on Women in Astronomy</a><br>More about my transition and what my job it like.</p><p><strong>Recruiting Advice</strong><br><a href="http://h30458.www3.hp.com/us/us/discover-performance/info-management-leaders/2014/nov/An-astrophysicist-schools-us-on-where-to-find-data-scientists.html">Interview with HP</a><br>Advice on Where to Find Data Scientists.</p><p><em>Do you have more questions? Ask them below!</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7722a547a429" width="1" height="1" alt=""><hr><p><a href="https://medium.com/data-diva/so-you-want-to-be-a-data-scientist-7722a547a429">So You Want to Be a Data Scientist?</a> was originally published in <a href="https://medium.com/data-diva">Data Diva</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Astronomer to Data Diva ]]></title>
            <link>https://medium.com/data-diva/astronomer-to-data-diva-e3c457f6621d?source=rss----dfd57f837653---4</link>
            <guid isPermaLink="false">https://medium.com/p/e3c457f6621d</guid>
            <dc:creator><![CDATA[Jessica Kirkpatrick]]></dc:creator>
            <pubDate>Thu, 02 Jul 2015 03:08:50 GMT</pubDate>
            <atom:updated>2013-09-29T15:37:21.642Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/700/0*M9JTuj3SrHjZvuR1.jpeg" /><figcaption>Yammer Analytics , More than just Piña coladas</figcaption></figure><h4>How I transitioned from Academic to Techie</h4><p>A year ago, I made the transition from astrophysics researcher to data analyst on the Yammer Analytics team. Below are suggestions for people in academia / research who are interested in pursuing a tech job.</p><p>Most tech companies are interested in smart, talented people who can learn quickly and have good problem solving skills. Scientists have these attributes. Therefore if you apply for jobs at tech companies, you’ll likely get at least a response from a recruiter. However, once you get an interview, there are many other skills that the company will try to assess, skills that you may or may not have already. Below are some tips which will help you both in the application / interview process, as well as on the job at a tech company.</p><p><strong>1) Learn a Standard Language</strong></p><p>Sorry astronomers, but IDL isn’t going to cut it if you want to get a tech job. You need to learn one of the industry-standard programming languages. Python, Ruby, Java, Perl, and C++ are all good languages to pick-up. It would also be good to learn a statistical analysis package like R, SAS, SPSS or Excel, as well as a visualization package to show your results. Some jobs, involve a coding interview. These require some knowledge of computer science algorithms. <a href="http://blog.geekli.st/post/34361344887/how-to-crack-the-toughest-coding-interviews-by-gayle">Look online</a>, there are many example coding problems for you to practice.</p><p><strong>2) Learn About Databases</strong></p><p>“Big data” is the Web 2.0 it-word. If you want to play with big data, you are going to need to learn how to manage, handle, and access it. SQL is a must. It would be great if you could also familiarize yourself with Hadoop/MapReduce and Hive.</p><p><strong>3) Brush-up Your Stats</strong></p><p>Many of the tech interviews involve doing complicated math, probability, statistics, brain-teasers, and open-ended problems. Dust off some of your old statistics text books or pick up a book about data analysis using one of the above languages. Search online for <a href="http://www.glassdoor.com/Interview/index.htm">past interview questions</a> of the companies you are applying to.</p><p><strong>4) Communication is Key</strong></p><p>To be effective in a tech job, not only should you be able to program, analyze data, and solve problems — you need to easily explain your work to people who aren’t very technical. Communication is incredibly important for these roles, and a huge part of the interview process is gauging how well you explain complicated ideas to a lay-person. There are many opportunities to practice this skill within academia, so give many talks, teach classes, tutor, volunteer, or do whatever you can to become very comfortable explaining technical ideas to people with different backgrounds and skill levels.</p><p><strong>5) Convert Your CV into a Resume</strong></p><p><a href="http://chronicle.com/article/From-CV-to-R-sum-/44712">There is a difference, and it is important</a>. People at tech companies get 100&#39;s of resumes. It is important to succinctly highlight the skills you bring to each job. It’s great that you have published dozens of papers, given lots of talks, and taught many classes… but what is more important are the <em>skills </em>you acquired from those experiences. Resumes should only be 1-2 pages. Look at the skills required for the job you are applying for, and then try to demonstrate those skills by listing the relevant experience.</p><p><strong>6) Academic vs. Business Problems</strong></p><p>In academia the goal is usually to get the most accurate solution possible. Time and efficiency are less important than doing something thoroughly and rigorously. In business the goal is to increase your company’s value. Therefore any task must both optimize accuracy AND value. This is a difficult transition for many academics to make. Spend some time reading <a href="http://techcrunch.com/">TechCrunch</a>, <a href="https://news.ycombinator.com/news">Hacker News</a>, and other such sites to help familiarize yourself with the various metrics and problems that tech companies care about. Be prepared to work on short deadlines and to be able to prioritize tasks in order to increase the value of your work. Keep this in mind when answering open-ended interview questions such that you demonstrate your understanding of this difference.</p><p><strong>7) Do an Internship or a Project</strong></p><p>The best way to get your foot in the door of a tech company is to do an internship. Many of the major tech companies have paid summer internships that will introduce you to this type of work, as well as teach you many of the above skills. The <a href="http://insightdatascience.com/">Insight Data Science Fellowship</a> is an internship specifically designed for helping academics transition into tech positions. If you are unable to take the time off from your current job, then consider doing a project on your own. Create an application for your phone, or do a research project with one of the many free data sources out there. This will give you insight into the work you might do at a tech company, and an important set of talking points for interviews. If you have more questions about making the transition from academia to tech or the tech interview process, feel free to <a href="http://twitter.com/berkeleyjess">contact me</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e3c457f6621d" width="1" height="1" alt=""><hr><p><a href="https://medium.com/data-diva/astronomer-to-data-diva-e3c457f6621d">Astronomer to Data Diva </a> was originally published in <a href="https://medium.com/data-diva">Data Diva</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Nailing the Tech Interview]]></title>
            <link>https://medium.com/data-diva/nailing-the-tech-interview-a0e28e9bc608?source=rss----dfd57f837653---4</link>
            <guid isPermaLink="false">https://medium.com/p/a0e28e9bc608</guid>
            <dc:creator><![CDATA[Jessica Kirkpatrick]]></dc:creator>
            <pubDate>Thu, 02 Jul 2015 03:08:39 GMT</pubDate>
            <atom:updated>2013-10-10T21:44:25.363Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/650/0*YdirnZjqXjoKRUBl.jpeg" /></figure><h4>Lessons from Both Sides of the Interview Table</h4><p>A year ago, I made the transition from academic scientist to data scientist. One of the harder parts of making the transition was convincing a tech company (during the interview process) that I could do the job. Having now been on both sides of the interview table, I’d like to share some advice to those wishing to break into the tech/data science industry. While this advice will probably be applicable to candidates in general, I’m going to be gearing it towards applicants coming from academia / PhD programs.</p><p>Most tech companies are interested in smart, talented people who can learn quickly and have good problem solving skills. We see academics as having these skills. Therefore, if you apply for internships or jobs at tech companies, you will most likely get a response from a recruiter (the first step in the interview process). The problem is that once you get an interview, there are a lot of industry-specific skills that the company will try to assess, skills that you may or may not have already.</p><p>Below are some of the skills/traits we look for when recruiting for the Yammer Analytics team, descriptions of how we try to determine if a candidate has these traits, and what you should do to ‘nail’ this aspect of the interview.</p><ol><li><strong>Interest in the Position</strong><br>This sounds like a no-brainer, but you would be surprised at how many candidates haven’t done proper research about the company or the position. It is especially important for people coming from academic backgrounds to demonstrate why they are interested in making this transition and why they are specifically interested in this opportunity.<br>.<br>When I ask a candidate “Why are you interested in joining the Yammer Analytics team?” I often get responses like “I really want to move to San Francisco” or “I’m sick of my research.” Neither of these responses demonstrate specific interest in my team or my company.<br>.<br><em>How to Nail It</em>: Do research about the position you are applying for. Understand what the role entails, what the priorities are for the company, and the product(s) that you will be working on. Have a convincing story for why you are making this career change or why you want to leave your current position. Show enthusiasm for the opportunity — every interviewer should think that their position is your number one choice and that you can’t wait to join their team. More importantly, only apply for roles that you genuinely find interesting.</li><li><strong>Excellent Problem Solving Skills<br></strong>One of the most challenging aspects of the analyst/data scientist role is taking a vague question posed by someone within the company, and figuring out how to best answer it using our data sets. Testing (and demonstrating) this skill in an interview is also very difficult.<br>.<br>At Yammer we try to test this skill by asking a combination of open-ended problems, brain teasers, and scenarios similar to those we deal with on a regular basis. For many of these questions there isn’t a right or wrong answer, we are more interested in the way the candidate constrains the problem, articulates her thought process, and how efficiently she gets to a solution. For some data science positions you will be asked to do some coding problems. Familiarize yourself with some of the standard coding <a href="http://javarevisited.blogspot.com/2013/03/top-15-data-structures-algorithm-interview-questions-answers-java-programming.html">algorithms</a> and <a href="http://www.amazon.com/Cracking-Coding-Interview-Programming-Questions/dp/098478280X">questions</a>.<br>.<br><em>How to Nail It</em>: These types of problems are asked by many tech companies and there are <a href="http://www.techinterview.org/">plenty</a> of <a href="http://www.wallstreetoasis.com/forums/hardest-probability-and-statistics-interview-questions">examples</a> of <a href="http://www.mytechinterviews.com/">them</a> on the <a href="http://javarevisited.blogspot.com/2011/06/top-programming-interview-questions.html">web</a>. Practice constraining, coming up with a clear game plan, articulating that plan, and then following through in a methodical way. Many problems are hard to answer as posed and so trying simpler versions of the problem or looking at edge cases can give you insight into how to find patterns. Sometimes not all the relevant information is given by the interviewer, don’t be afraid to ask clarifying questions or turn the process into a discussion. If the interviewer tries to give you hints or tips, take them. There is nothing more frustrating (as an interviewer) than trying to guide a candidate back on track and have her ignore your help (it also doesn’t bode well for the interviewee’s ability to work well with others).</li><li><strong>Communication Skills<br></strong>As I said in my <a href="https://medium.com/yammer-analytics/e3c457f6621d">last post</a>, communication is key. We are looking for someone who can clearly articulate her thought processes, and can be convincing that her approach is correct even when being challenged by the interviewer. A standard way we will test this is by posing an open-ended question and when the interviewee says a reasonable answer, we give a reason why that isn’t right, then the she comes up with a different explanation, and we negate it again. We keep going to see how she deals with having to switch directions, and balances defending her answer and being flexible with taking the interviewer’s suggestions.<br>.<br>How to Nail It: Practice articulating your approach and methods for the above ‘technical’ interview questions. Come up with a big-picture game plan for approaching the problem, be clear about that plan, have a methodical approach, and then execute it — all the while articulating your thought process as much as possible. If the interviewer tries to make you change directions, it’s ok to defend your approach, but you don’t want to be too rigid, they might be trying to help you not go down the wrong path. Try to make the interaction as pleasant and warm as possible. Avoid getting defensive, frustrated, or just giving up. It is a very hard balance, but practice (especially with another person who can give you feedback) makes perfect.</li><li><strong>Culture Fit<br></strong>In tech companies you work collaboratively on projects on tight knit teams. We are going to be spending a lot of time with a candidate if we hire her; we want to enjoy that time together. Therefore we are also trying to assess if the interviewee would be a good coworker at an interpersonal level. Is she friendly? Does she work well on teams? Does she have the right balance of being opinionated but not domineering? Is she an interesting person? What are her passions and goals?<br>.<br>I can’t tell you how many times I’ve asked a candidate “What do you like to do for fun?” and they answer: “I like to read programming books.” Is that really what you like to do for fun? Or do you just think that is what you are supposed to say in a tech interview?<br>.<br>How to Nail It: Remember that your interviewer is a person too, and interact with them as a person. Try to show some of your personality, passion, sense of humor, and uniqueness in the interview. It’s hard to be relaxed in these situations, but personality goes a long way.</li><li><strong>Ask Good Questions</strong><br>At the end of the interview you will typically have a chance to ask questions. This is your time to take control of the process and turn the tables on the interviewer. Sometimes I learn the most about candidate in how she uses this portion of the interview. A interviewee I am on the fence about can really tip the decision one way or another by asking intelligent, thought provoking, and engaging questions at the end of an interview (or boring, uninformed, or generic questions).<br>.<br><em>How to Nail It: </em>Use this as an opportunity to demonstrate things you weren’t able to show in other parts of the interview. Demonstrate that you have researched the company, that you understand their business goals and the way you could contribute. Ask thoughtful questions about the role, demonstrate that you want something that is challenging and discuss types of skills you want to learn or apply. Use this opportunity to show the interviewer what you can bring to the role. If applicable, try to relate what you are learning about the job/company to what you’ve done in the past. Have tons of questions, write them down ahead of time and bring them to the interview. You shouldn’t run out of questions or have to repeat them over the course of the interviews.</li></ol><p>The above is by no means an exhaustive list of everything a tech company is looking for, and of course different companies have different approaches. However, I do hope that this helps demystifies the process, gives you insight into how one company goes about hiring data people, and helps you understand what we are looking for on the other side of the table.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a0e28e9bc608" width="1" height="1" alt=""><hr><p><a href="https://medium.com/data-diva/nailing-the-tech-interview-a0e28e9bc608">Nailing the Tech Interview</a> was originally published in <a href="https://medium.com/data-diva">Data Diva</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>