<?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 Rami Luisto, PhD on Medium]]></title>
        <description><![CDATA[Stories by Rami Luisto, PhD on Medium]]></description>
        <link>https://medium.com/@ramiluisto?source=rss-db91009082bd------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*7ibtGiOfGsiBqAZsrpuhSQ.png</url>
            <title>Stories by Rami Luisto, PhD on Medium</title>
            <link>https://medium.com/@ramiluisto?source=rss-db91009082bd------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 10:55:57 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@ramiluisto/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[Moving from academia to industry — a fully industrialized mathematician]]></title>
            <link>https://ramiluisto.medium.com/a-fully-industrialized-mathematician-abc9fdd8bbd2?source=rss-db91009082bd------2</link>
            <guid isPermaLink="false">https://medium.com/p/abc9fdd8bbd2</guid>
            <category><![CDATA[mathematics]]></category>
            <category><![CDATA[career-paths]]></category>
            <category><![CDATA[data-science]]></category>
            <dc:creator><![CDATA[Rami Luisto, PhD]]></dc:creator>
            <pubDate>Tue, 14 Feb 2023 07:50:31 GMT</pubDate>
            <atom:updated>2023-03-10T07:47:21.679Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*4LTgqoVsHVHS_iT1" /><figcaption>Photo by <a href="https://unsplash.com/@kowalikus?utm_source=medium&amp;utm_medium=referral">Krzysztof Kowalik</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>So, after more than two years it is time to return to complete <a href="https://ramiluisto.medium.com/moving-from-academia-to-industry-a-mathematicians-tale-d8dfda40604f?sk=07e0318bd4f4847ca6d849a53a19f26f">the</a> <a href="https://ramiluisto.medium.com/moving-from-academia-to-industry-some-months-later-e9352be4a5a9?sk=b915a921da34793b12041048d446190c">trilogy</a> and answer the critical question: “How does the industry feel now that the dust has settled and the occupational honeymoon has ended?” In short; still loving it, but do read on for details.</p><p>In this third part I’ll focus less on the differences between the academia and the industry and discuss more on how the industry feels in the long run ‘from the inside’. I’ll describe what I’ve been up to and how I’ve evolved. Besides these, the text also ended up including a long-ish discussion on ‘Business’ from a technical person’s point of view. I’m hoping for it to be useful to those who wonder what the requirements of “business understanding” mean when applying for positions, but you should be wary of the content as I am not an expert on whatever ‘Business’ actually is.</p><p><em>As before, the caveats of these writings stack up. I see all of this through the experience of this singular narrative that I’m living, YMMV.</em></p><h3>Introduction</h3><p>I’m happy that I wrote the earlier parts of this trilogy during the transition as I am getting more and more hazy on remembering why the current situation felt different than before. I also think that the usefulness of these posts is decreasing at an exponential rate for the same reason I think that for the Analysis 101 classes it is good to have somewhat young students as course assistants. C.S. Lewis put it well when he said “<em>The fellow-pupil can help more than the master because he knows less. The difficulty we want him to explain is one he has recently met. The expert met it so long ago that he has forgotten.</em>” So I would suggest treating the first part of this trilogy as the most significant one and parts 2&amp;3 as kinds of curious addendums. Or maybe as comforting tidbits that tell you that even years after transitioning I’m still happy with no regrets.</p><p>Despite these warnings that I’ve forgotten a lot of how it was before the industry, all has not been lost. As a good refresher last spring, a bit before my 2 year mark at the company, I got the honor to be the opponent of a former colleague’s doctoral defense. This gave me the excuse to really go deep into math and helped me recall some of the feeling I had while working in the academia. It also helped me to remember some of the contrast between the two worlds.</p><p>But besides this and some other small excursions, I’ve now pretty much settled to my own personal new normal as a cog in the machine. A big reason for this feeling at home is a combination of close new colleagues, the ingestion of a thousand little skills, and all the silent knowledge that I have been able to amass. I can’t properly verbalize all or even most of the little and big things that I’ve learned, so the rest of the article will not be a very long list of bullet points. Instead I will try to describe some of the bigger ideas I’ve learned that I think would be useful for others to know as well.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZzDsSSK2Ize-Uk2MkXAqkw.png" /><figcaption>DALL-E’s rendition of (me as a) a cog in the machine.</figcaption></figure><h3>Setting the scene — What have I been up to?</h3><p>For the past year and a half or so I’ve been largely working on two overlapping projects: as the lead data scientist on one long major project, and as the lead data scientist slash part-time project manager of another six-month project. This has been in contrast to the start of my career here when I would work in supporting roles on various projects, sometimes in parallel, for various amounts of times going from 1 to 6 months. In general seeing the larger arc of a project going from planning to execution, deployment, hypercare and finally to quarterly status review meetings has been enlightening, but let’s look at each of these two major projects in detail.</p><h4><strong>The longer project — Medical NLP</strong></h4><p>Of the two mentioned above, this is the one I consider the main one. It is in the field of medical AI, largely in NLP and classification, and I’ve been the main ML-architect/developer responsible for creating various ML-solutions together with large parts of the system architecture. It was the first project where I got to start working from scratch. This project introduced me to a whole new set of interesting challenges, some of them technical considerations in ML-engineering and MLOps/DevOps, but also many of them in the legal, bureaucratic and ethical side of things. The latter stem from the fact that EU in general and Finland in particular takes a very strict view on handling peoples’ medical data and on having computer programs being involved in patient care. As a human and a citizen I’m really happy on the level of scrutiny we had to go under, even though at times my data scientist side was feeling impatient to get some data in our hands. In the end I believe that that impatience was just growing pains and an important part of being a data scientist in a given field is to grow accustomed to the realities of the subfield. The project went and is going well, and largely in honor of this I was even given the title of “Healthcare Industry AI Lead (Data Scientist)”. This did not bring me any new responsibilities, but was more of a reflection on the position I had gravitated into.</p><p>It would be really hard to try and enumerate all the things, or even all the important things, that I learned in this project, but the two lessons that I really want to highlight here were that <em>data is not always abstract</em>, and that <em>classification is not a discrete problem</em>. The first lesson stems from the fact that in order to do proper data science work it is really important to familiarize yourself with the data. In this project with the data being related to medical conditions I got to have very long discussions with medical professionals about many of the different ways people can be broken and how they might be then fixed. The most sobering experience for me was having a discussion where I asked why a given class of data was so underrepresented compared to others and a doctor told me that the class was related to such a severe a medical condition that the people affected would usually perish before producing more data for the class. So nowadays the term “imbalanced classes” brings to my mind not only SMOTE and other clever techniques but also the human condition. I think this is a very positive and humane evolution for me which helps me remember that the things I do are not just fun intellectual exercises but actually touch human lives.</p><p>For the second lesson about classification not being a discrete problem, let’s look at the classical task of “Classify the incoming data to given classes.” At the surface this sounds like a very straightforward problem that we’ve seen before in various ML-tutorials or other study materials. With a bit more advanced material you might even get some mentions about some percentage of the data being mislabeled, or that the ground truth might rely on the vote of a committee of human experts who might not always agree. In some cases you might even look at situations where there wasn’t a perfect one-to-one mapping between the set of labels and the set of classes that exist in reality. What I wasn’t at first prepared for at all was the fact that for some some data <em>there simply isn’t one correct category</em> where the datum might belong to. The problem gets interesting when every datum at hand does receive a label, but some of those labels might contain the unnamed classes of “this case requires more information to classify” or “this datum could belong to various classes”. Many of the technical challenges this poses can be solved with the same tools that handle mislabeled data, but conceptually the difference is quite big and needs to be discussed with the people actually involved in using the system. In the end the single most import tool in these types of cases has been increased communication with the client’s subject matter experts together with extended meetings with the stakeholders about the situation. (In a majority of AI-related issues, the best solution, or at least a very important part of the solution, tends to be ‘increased communication’.)</p><h4>The shorter project — Custom data extraction</h4><p>The shorter parallel project was a bureaucratically less heavy custom AI-project related to structurizing data from video sources. I had less to do with the more complicated AI-components, but instead had my responsibilities focused on customer interactions, system architecture and managing the ML-work of a few other data scientists. The data scientist management side of this project was not very remarkable as I have highly skilled and very self-sufficient colleagues, and my managing of them constituted mostly of describing a problem and then waiting a few days for a solution to pop up. One of the more interesting technical sides of the project was, however, on how to build a system that has several components built by various people. On these topics I don’t have such clever insights to share yet, but in general I would here give a shout-out to <a href="https://www.goodreads.com/en/book/show/13629">the Mythical Man-Month</a>.</p><p>The project also provided learning possibilities in the more technical side of things. I had used Docker in various settings before to encapsulate various solutions and whatnot, but it was during this project that I really got a chance to dig deep to the world of docker-compose. (A big recommendation to <a href="https://www.goodreads.com/book/show/36411996-docker-deep-dive">Poulton’s book</a> on the topic.) Organizing a multi-container system with innards made by various other people was a delightfully complicated process and it was incredibly rewarding (not to mention initially a bit surprising) to see the whole pipeline work.</p><h4>All the other things that I’ve been doing</h4><p>Aside from these two big projects I’ve spent maybe 10–20% of my work time to various other things that can only be classified as a bucket labeled “Misc.” I don’t want us to lose the forest for the trees so I won’t delve here in detail, but I don’t want to omit it completely either.</p><p>This bucket of misc does include some shorter projects where I have provided some consulting or other small help with creating AI-components, but that is not all. Just as there is a lot more to ML-work than just doing technical stuff with data and models, there is a lot more that I have on my table than just working on singular projects. As an ‘expert explainer’ I am often involved in both internal and customer facing meetings where the possibilities and limitations of AI are discussed together with various estimates on how much work and time it might take to produce a given solution. I’ve also had the semi-official responsibility of familiarizing myself with many out-of-the-box AI-solutions that the major providers in our field are offering so that we can better understand which tools are available and how they compare.</p><p>For me the most interesting types of tasks here tend to be those where I get to take part in the more strategic discussions — looking at what might be the big directions in which AI might be used by the company in the future. Besides strategical discussions, these kinds of smaller variable tasks are not my main focus, nor are they my favorite kinds of tasks to do, but they are still usually fun to do. At minimum they provide some variation on the daily grind. And I do usually seem to thrive better than many when given unusual tasks with no clear existing guidelines — Jack of many trades and master of one?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kIkfwryzMjhgFi3Lz1itDg.png" /><figcaption>DALL-E generated cubistic painting of Business.</figcaption></figure><h3>Thoughts on ‘Business’</h3><p>Here I want to talk about Business with a capital B. The motivation comes from when I was still in the transitioning phase and in many places I would see this requirement that Data Scientists should understand not only Programming and ML but ‘Business’ as well. And this would cause me some concern. Whenever I would get the feeling that “I need to understand programming better.” or “I need to understand ML better.” I could, with slight hyperbole, just grab a book called “Introduction to Programming/ML.” and start reading. But it didn’t seem that there were clear technical manuals called “Introduction to Business.”, and when there were, they all seemed to discuss different topics with languages that were strange to me.</p><p>Now, after a few years, I think that I have an instinctive feeling of what it seems people meant by ‘understanding business’. Maybe. The concept is still a bit ephemeral to me, but I’ll try to explain here some views and concepts to hopefully pass on useful information to fellow non-business background Data Scientists about what it is that some people are after. Here I talk with much less confidence than in some other areas, so take this with a grain of salt — what ever the platonic ideal of ‘Business’ is, I’m not an expert in it.</p><p><em>As an additional caveat: this part has also been described as ‘somewhat adorable’ and ‘bravely honest about my level of understanding’ by some of my proofreaders who have spent more time outside the bubble of Academia. So if it feels like a section filled with naive truisms, you should probably skip it. I’m still hoping that it will serve some purpose to those (of us) who’ve spent many years in the academical world, shielded form things like profit margins.</em></p><h4>Why are Data Scientists concerned about ‘Business’?</h4><p>Before getting to ‘Business’, there’s gonna be a small rant about the concept of defining things outside the world of pure mathematics, with a certain Venn-diagram as the specific target.</p><p>So there is this sort of classical Venn-diagram on “what is data science” which I think describes what we would like data science to be, or at least what I personally would like to claim I know as a Data Scientist — deep knowledge in all three fields of Math&amp;Stat, CS and Business.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*MG1UH2T9VdpU7IfHyAkMtA.png" /><figcaption>Left: Data Science as the intersection. Right: Data Science as the union (and them some). Not Pictured: The concept that this whole approach of trying to define Data Science is flawed.</figcaption></figure><p>I am not the first one to note that this diagram has some shortcomings, some of them more nuanced like “<em>Data Science is it’s own field that shouldn’t be defined only through other fields no more than mathematics should be defined as the intersection of Numbers and Theoretical Philosophy.</em>” and some of them more practical like what I’ll discuss here. To my eyes the term “Data Science” is more of an umbrella term and I’ve met with data scientists working inside (and outside) of all the areas of the above Venn diagram, not only in its intersection. That being said, there is of course some grain of truth here as admittedly the various subjects mentioned in the diagram can be very useful in data science projects. I think that this diagram should be in the same box as the Bohr model for atoms — good as a first approximation to show to new people, but served with caveats in bold red letters.</p><p>One big particular practical grievance I have with this diagram is the more generic notion that outside of mathematics <em>terms and words are not defined via singular definitions you find in dictionaries or diagrams but by their use in the real world</em>. When linguists put together grammars, they are not making up rules on how to use the language, but creating a record on how the language is used. And similarly for definitions of words in dictionaries. In my mind this idea applies very strongly to data science — we are still more or less figuring out what the different tasks are that a Data Scientist might do, and what titles might we use to give more specific information on the responsibilities and competencies of a particular data scientist. So even if these types of diagrams and guides provide useful information, I would approach them as descriptions of what we’ve observed data scientists doing in the wild instead instructions or requirements that should be enforced.</p><p>A related element here is that since the exact content of the field of Data Science seems still be quite fluid, the phrase “it’s not what you know now but what you can learn to do” rings even more true. You might get to do very different kinds of things under the umbrella of data science, both in the technical and more general sense, and having the ability to learn and adapt quickly can be huge benefit.</p><p>So with my rant about the Venn diagram that originally brought ‘Business’ to my study to-do list over with, let’s move on to discussing what the strange blob of ‘business’ in these types of diagrams might mean. Because despite the shortcomings of definitions and diagrams, I do feel that understanding ‘Business’ better has made me better at what I do. I am not even going to attempt to give any sort of definition, but instead we are going to look at a few different example cases, and hope that there is some concept that you can gleam as the actual thing from which these are just a sampling.</p><h4>A practical example — “distance to product”</h4><p>In short, “distance to the product” is pretty much what it says on the tin: how close are you to the ‘product’ i.e. the thing that your company trades for money? This can have a huge effect on how much salary or appreciation you can get, especially in times when the economy is feeling low and people want to prioritize the immediate profits compared to long term strategic goals.</p><p>As an example, using Data Science skills to help the board understand strategical long term trends in the company turnover is important, but in a pinch the actual ML-based software solution that will bring your company immediate income every month might take precedence when your company wants to report quarterly earnings. Naturally the situation is never as simplistic as “immediate money good, long-term planning bad”, but a big part of the idea here is <em>to know where you stand and try to keep up where the company’s current priorities lie. </em>Furthermore being aware of the concept of distance to product can be very fruitful as it is can help you to understand the business model around and behind what you actually do day to day. This in turn can help reduce any remnants of Fraud Syndrome you might have, as you can clearly see how you’re making more money/value to the company than they are paying you. (Personally, seeing this reduces my fraud syndrome levels, but if instead it makes you feel like you should be cutting out the middle man, you might enjoy some of the essays in <a href="https://www.goodreads.com/book/show/41793.Hackers_Painters">Graham’s book</a>.)</p><h4><strong>A practical example — your company’s business model/idea</strong></h4><p>You don’t need to speak fluent corporate or understand the details of how quarterly earnings are reported, but you should try to get a rough feeling on what makes your company tick. Some stuff you might want to figure out, e.g. from listening monthly townhalls might be things like:</p><ul><li><strong>Where do the profits come from?</strong> Are you getting your main income from consulting, or selling software products, or from service fees to your solutions portal? Is the majority of your revenue from existing customers who will keep paying the same amount every month for the foreseeable future, or do you rely in constantly getting new customers who need your services?</li><li><strong>What is the field or subfield in which you operate?</strong> Do you provide services for customers or for other businesses? Are you a major player in this field and if not, then what is your competitive advantage? Who are your competitors?</li></ul><p>This is essentially on the same spectrum as “distance to product”, but on a different scale with distance to product discussing your position relative to the company, and the business model discussing the position of your company relative to the world.</p><h4><strong>A practical example — ROI</strong></h4><p>Many companies, especially younger ones, rely heavily on investors putting money in the company so that the company can e.g. expand.<strong>*</strong> The investors are taking a risk since your company might go under, and to compensate for the risk they will want to get better returns for their investment than they would get from more secure investment options. This means that it’s very rarely enough for a company to just break even — you want to <em>consistently</em> make more money than you are spending, <em>by a margin</em> that is better than your standard index fund. Also when you are planning to start a new project with a customer, you have to take into consideration the risk that the project doesn’t pan out for some reason, and that the profits from the particular project will also have support the running costs of the company like office rent and HR salaries. I’m personally very happy that I’m not the one who has to do these calculations, but understanding the basics can help you see why the company might favor some projects over others.</p><p>In some sense this is again a variation on the two earlier points, or maybe another perspective on the position that you have in the company and the company in the wider world. And it can be crucial for you to understand if you are involved in project planning — partially because you’ll understand the context better, and partially because you’ll probably be taken more seriously if you can demonstrate that you’re not clueless to the market realities.</p><p><strong>*</strong> <em>”Why doesn’t the company wait until it has ‘naturally’ generated enough excess profits and use those for expansion?”, I hear you ask. One reason might be that there are new markets opening up and if you wait a year to expand 10%, your competitor will have already scooped all the new possibilities up by taking in investments to expand by 100% in a month, to give an exaggerated example.</em></p><h4>‘Business’ in summary</h4><p>I don’t think I can properly summarize what I have in my head when I think ‘business’, but hopefully the three examples above can give some insight to what I think might be useful for a data scientist to know. The ability to learn new stuff without things explicitly spelled out for you, picking ideas up from the context you are working in, can be immensely valuable here.</p><p>If all of the things mentioned above were basic information to you, then I say well done you! For me most of this was far from obvious when I started. A lot of this stuff is just things I picked up along the way, and it might be distorted or plainly wrong compared to what actually is going on in the business world so please, again, take it with a very big grain of salt.</p><p>As I mentioned earlier, I haven’t found a singular book that I would consider a good “Introduction to Business”, but if you’re like me and would really like to have a book to read on the topic, I did enjoy reading <a href="https://www.goodreads.com/book/show/657329.Hidden_Order">Friedman’s Hidden Order</a> when I was a grad student. I would maybe start with this and/or look at the reviews to see which books people think are better and go from there.</p><h3>My technical evolution</h3><p>In a previous post on this trilogy I mentioned how I was excited on how much more natural programming, especially in Python, has turned into in only a few months and how I was curious to see where I would be at the 2 year mark. It’s now a bit beyond that, and the feeling is good. This section is the most me-specific and self-serving, but I’ve tried to include some general ideas about learning that might be beneficial to others than me as well. So let’s look at a few different areas to see how one might advance when they do this kind of thing for a few years on a daily basis.</p><h4>Python code quality</h4><p>Python is still the language of choice for me with 99% of the code I write being Python, though I’ve dabbled in Java, JavaScript and C# for various projects. I’ve gotten opportunities both during projects and time for personal training to improve myself in Python, and I think it is really starting to show.</p><p>I don’t think that there is a very big need for me to try and specify my exact skill level in Python, but there are some aspects in it that I want to try and explain. One fundamental feeling I have about my particular skills is related to something I call ‘the generic programming language’. This is kind of like the ‘pseudocode solutions’ you see sometimes as answers to algorithm design problems, where you write generic loops and conditionals to bring the general idea across without actually fixating to a particular language. I feel that once I learned to program in the first few languages I came across (hello TI-BASIC, Java and MatLab) my brain kind of abstracted this general idea of what most programming languages do. (Note that I was raised on descendants of Fortran/C instead of languages like LISP, Haskell or APL which must have a huge effect on my conceptual idea on programming.) After you get the first few languages under your belt, you can quite quickly adopt new languages on the most basic level where you are just writing these generic pseudocode solutions — to write a json parser in C# I just needed to learn the base syntax and how iterators are used and I was pretty much there. But that doesn’t mean that I learned C# in a day, since I am only using it at this generic way that I would use any other similar language whose syntax I’d studied for a week. I don’t actually know how to use C# in the native C# way, and I think that this is a very crucial difference when I’m reflecting on my own programming skill.</p><p>In any case, what I’m driving at here is that with Python I think I’ve gone way past this post, meaning that when I write python code I write Python instead of just ‘generic programming with Python syntax’. I’m not yet at a level that I would consider mastery of the topic, especially due to my lacking of understanding of the Python internals, but I feel that I am starting to get the main idea. What would really help me for next steps, and what I hope to do in the near future, is to get on a comparable level with another language so that I could compare on the similarities and differences properly.</p><h4><strong>Increased system complexity</strong></h4><p>This is less Python specific and more about what kind of systems I build and what kind of tools I use to build them. I’ve gone from Emacs/vi to VS Code and from singular script files to using docker-compose to build multipart systems that enable large asynchronic pipelines with multiple AI and non-AI components. I’ve also spent enough hours to re-invent a few of the common wheels and I think I’m slowly learning that it really does pay off to learn how to use e.g. FastAPI instead of building my own (worse) version from scratch.</p><p>Combining the increased system complexity with the fact that I’m at the same time getting more and more familiar with the cloud stack and how networks work or don’t work (it’s always the DNS), I am at times starting to think if it would be cool to push myself even deeper in the architecture side and towards being Full Stack. Though at the same time I also kinda think that a “Full-Stack Data Scientist” is a bit like Santa Claus: they don’t actually exist, but once in a while it’s nice to have someone put on the red dress with a fake beard to play the part. Especially as this usually provides the service that people *actually* need even though originally they were asking for a capitalist demigod equipped with supersonic reindeer.</p><h4>ML-mindset</h4><p>A lot of the important points about my growth in the ML-side of things were already mentioned when I discussed the medical NLP-project I had been working on, but they are a part of a larger theme, I think. This probably again goes to the more general theme of having an intuitive sense of what I am doing, what the customers are usually expecting (and actually need) and what the current tools can accomplish.</p><p>Here I can offer the least advice or suggestions on what to read or do, except for very generic and borderline unhelpful banal things like “work with messy data” or “try to get involved in actual ML project from project planning stages to hypercare”. One singular good advice that prof. Roos keeps repeating is that whenever you do ML stuff:</p><blockquote>Always start with an easy and simple model to establish a baseline.</blockquote><p>And I feel this advice is good enough to repeat any time I get the chance. If you are doing a complicated NLP classification project, just do a quick wordbag + decision tree/forest -solution to get some sort of idea how the thing goes. Or any other prebuilt model you get from scikit-learn or Azure AutoML. It’s easier to try and understand if the 86% accuracy of your hypertuned transformer is good or not if you decision tree is hitting an 82% accuracy with 0.01% of the resources.</p><h4><strong>How can you keep learning?</strong></h4><p>This is less on what I’ve learned and more on how I was able to keep learning. I’ve had various people reach out to me after the previous posts to ask me further questions, many of which have been now included in this text, and a few have been asking me how to keep learning in the industrial world and not get stuck doing just one thing. There is, naturally, no one single answer on how to keep learning, but I do strongly suggest you do. There’s this one cool <a href="https://www.reddit.com/r/MaliciousCompliance/comments/8myu68/dapper_dan_fails_to_think_things_through/">reddit story about the folly of ‘Dapper Dan’</a> that mentions the following advice:</p><blockquote>“Each job pays you twice. You get your money now, that’s your wage. You also get experience now, that’s how you get paid in the future. So. Are you still getting paid? Yes? Are you still learning? No? Figure out how to keep learning, or leave.”</blockquote><p>And this is something I largely agree upon. It doesn’t mean that every day of every week you should be getting to study fun new topics, but I think it’s good to keep a little monthly or quarterly check with yourself to see if you have been able to improve yourself, be it in technical topics or something more generic like ‘getting better at handling customer expectations’. The amount of learning you want to keep doing is, of course, a subjective thing, but it would be good to be at least aware of what is actually happening.</p><p>Personally I’ve been once again lucky as the company I work for is quite supportive of my continuous learning efforts, so in particular my advice might not transfer well. In any case, my first hint here again ties to the earlier discussions on ‘business’ — if you are involved in project planning and timeline estimations, you can more easily try to sell the idea that a few days of the long project could be directed to you learning a new tool to help with the task. Or if you see that the company strategy is shifting, you can try and sell that in order to support the new directions it would be beneficial for you to be trained in X, for example during the next quarter when the company is estimating the business to be slow anyway. Selling these ideas is much easier when you have a grasp of what the company in general is valuing and doing.</p><h3>Thoughts on math</h3><p>So how’s the math after two years? Surprisingly good, I would say. Admittedly I have no <a href="https://doi.org/10.5642/jhummath.202201.41">essentially new</a> publications, but I’ve been able to get myself involved with both mathematics and mathematicians. The latter part in particular has been important for me, since the one thing I do miss is he mathematicians’ community and e.g. the way you can randomly end up spending half of your 12-hour work day in the department coffee room, discussing and debating the root cause why 3-sided dice with straight faces cannot exist in our world/geometry, interspersed with horrible topological puns.</p><p>But luckily I am not completely cut off from the terrifying beauty that is the math department coffee room culture. As briefly mentioned above, last spring I got one of the highest honors one can get after getting their PhD — I got to be an opponent for someone defending their thesis. This made me quite happy in many ways, not the least being the feeling that I’m still being considered as a part of the mathematical community. Getting to be the opponent is a bit being like a godfather in that you can’t really go around and ask if someone would take you, you have to wait to be asked. And not everyone gets asked. In addition the more humane benefits of getting to do this, there was the more technical advantage that I finally had a proper reason to really delve into mathematical publications. And not just skimming them, but actually studying them to the level of questioning the results, which is no mean task for research-level math. This felt good, in part because the papers were actually remarkably good and on interesting topics, and in part because it was good to see that I still had it in me to understand them.</p><p>Besides this one big endeavor I do sometimes read exciting math either from my own field (I still subscribe to <a href="https://arxivist.com/">Arxivist</a>) or <a href="https://arxiv.org/abs/math/0408144">exciting things that I happen to come across</a>, but more to satiate my own curiosity rather than at the level of trying to create something new. I do sometimes pick up old big conjectures that I used to work on, just to see if time would have brought me a new perspective, but I don’t harbor any actual belief that I might be able to actually solve them. Sometimes I even only look at problems that I’m certain I won’t solve, just to make sure that I won’t actually have to start doing the work of writing down a publication-grade solution. It seems that I still like flexing my math-muscles every now and then, but I don’t feel the need to actually get properly down to business anymore. The technical stuff with e.g. learning Python details and using it to solve problems seems to be scratching the same itch as mathematical research did, though it’s nowhere near the level of technical complexity or abstraction of math research. But it can be difficult and complex enough in other ways. And I’m happy with this. In particular as this type and level of challenges connects with some of my favorite things — sleeping in your my own bed, consistently living in the same city as my family and not having to apply for jobs every year or two.</p><p>I think that the feelings I’m getting here are comparable to a professional sportsperson of some sort — a few years ago, at the height of my postdoc period, I was the best I’ve ever been in math and the best I ever will be. I’m still very good in math, way above the 99th percentile, but I will never again have the level that comes with the singular focus you get from dedicating most of your waking hours to perfecting one topic that you’ve been practicing for over a decade. And I’m fine with this — it felt good being at the level I was, but my life as a whole feels better and more balanced now.</p><h3>Epilogue</h3><p>I doubt there will be a fourth part in this trilogy, mostly because I don’t really see what I could add in e.g. 5 years time that would be any different than all the career advice and stories we already have from other jaded professionals. If something actually interesting comes up, I might write about it and link it also here, but you shouldn’t wait up. Until then, good luck and keep on sciencing the data!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xDA6PFd9wOFi3FSjrWpugg.png" /><figcaption>“A painting of the end.” by DALL-E (A very rare example where DALL-E gets the text right!)</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=abc9fdd8bbd2" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Moving from academia to industry — some months later]]></title>
            <link>https://ramiluisto.medium.com/moving-from-academia-to-industry-some-months-later-e9352be4a5a9?source=rss-db91009082bd------2</link>
            <guid isPermaLink="false">https://medium.com/p/e9352be4a5a9</guid>
            <category><![CDATA[career-paths]]></category>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[mathematics]]></category>
            <category><![CDATA[academia]]></category>
            <category><![CDATA[careers]]></category>
            <dc:creator><![CDATA[Rami Luisto, PhD]]></dc:creator>
            <pubDate>Sun, 31 Jan 2021 15:05:46 GMT</pubDate>
            <atom:updated>2023-02-14T08:00:39.842Z</atom:updated>
            <content:encoded><![CDATA[<h3>Moving from academia to industry — some months later</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*HyZtul_XfdD1W82l" /><figcaption>The daily grind I have at the tensorforge. Photo by <a href="https://unsplash.com/@kennyluoping?utm_source=medium&amp;utm_medium=referral">Kenny Luo</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>So, it took me a bit longer to get back to this than I originally thought, but time flies when you’re having fun. My <a href="https://medium.com/@rami.luisto/moving-from-academia-to-industry-a-mathematicians-tale-d8dfda40604f">previous post</a> on transitioning from the academia to industry received a lot more positive feedback than what I had hoped — many people reached out to me afterwards, some to ask questions and some to empathize with the feelings I was discussing. Thus it felt prudent to stay true to my word and provide the second part of this nascent trilogy by telling how it’s going after a few months. In short: working in the industry rocks. For details: keep reading.</p><p>This text will consist of 4 parts, which are “How has it been in general”, “What do I actually do day to day?”, “How does the private sector compare to the Academia?” and “Afterword”. I’ll try to keep the descriptions as general as I can, both to make the text more accessible to people planning to work in an non-identical sector and to make sure I stay well within the various NDAs I have signed.</p><p><em>Before starting the story proper, this piece of text requires an even bigger caveat than the one before. In addendum to the previous small print, here in particular my experiences are strongly tied to the (type of) company I ended up working in. YMMV.</em></p><h3>How has it been in general?</h3><p>In short; I really do like it. To elaborate a bit, I haven’t regretted the decision to transition <em>at all</em> so far. There are many things that I do miss in varying amounts, but they do not counter all the positive things — not even close.</p><p>The work I do is challenging enough that I have to use the skill sets of a researcher. The problems might not be quite at the level of “Nobody has been able to do this and brilliant minds have been trying for decades.” but still in the level of “No one has done anything quite like this before, and many of the relevant projects are company secrets that we can’t get direct access to.” In particular, many of the projects start with studying the research literature on the topic on how these types of problems have been approached by other groups, planning a first approach and starting research-type cycle of “try, fail at least partially, learn from failure, adjust and start again”.</p><p>The problems can also be very open-ended, where the task might be improve the profitability of a system by reducing computational resource expenditure, improving accuracy or both. Sometimes the solution might even be “we don’t actually need to run this complicated selection component, we get a high-enough accuracy just by always choosing the last element in the list anyway”. This leaves a lot of room to maneuver and thus room for creativity and out-of-the-box thinking. What I have especially appreciated (and trepidated) from the start is that I’ve been given at the same time both big responsibilities and quite a lot of freedom in how to perform them.</p><p>There is still a slight difference between my daily work and doing research in math, though. Every now and then when I do end up doing some actual research-level mathematics, usually when a collaborator calls with a cool idea or question, I am reminded of the contrast between being able to do good work on a machine learning project and doing something in which I have perfected my skills for a decade. So it’s not quite the same, and sometimes I do feel the ping of yearning, but this does not happen daily or even weekly. Also, the fact of the matter is that I do have time outside the nine-to-five schedule that I could use for research questions, but I mostly don’t; in increasing amounts it goes to spending time with the family or to various hobbies. On average I think I spend a few hours every month thinking again about one of the toy problems I like to play with, and a varying amount of time to discuss with some of my co-authors on some referee-reports or new ideas related to finished projects. I think that a big factor here is that I get to learn and do things on the job which are complicated enough to satisfy that original research itch for now, but we’ll see what I have to report in a few years.</p><p>To summarize, despite the notable difference to my previous life in math research in the content and some differences in the spirit of things I do, I haven’t had an identity crisis. This is something I had been a bit worried about before, since after doing mathematics for well over a decade my self-image is/was largely built around the idea of being a mathematician. Relying on the old adage “if it works, don’t touch it” I haven’t spent too much time probing my concept of self recently, but it seems that my mind is either happy in identifying as “someone who solves complicated technical problems and then explains them” (which is almost the same as saying that you’re a mathematician) or then I still find myself as a mathematician who’s just doing some more applied stuff at the moment. It might be even possible that I exist independently of the label I put on the stuff I do, who knows.</p><h3>What do I actually do day to day?</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*VrJe4mBfZ9ihzt19" /><figcaption>In my mind our offices look and feel like this, but in a good way. Photo by <a href="https://unsplash.com/@rozetsky?utm_source=medium&amp;utm_medium=referral">Ant Rozetsky</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>First of all, to set the scene, I work as a part of the AI-team at <a href="https://digitalworkforce.com/">Digital Workforce Services</a>, which has the delightful balance of being like a small startup inside an established company. This means that the workplace in general is secure, but within the AI-team there are not so many dedicated responsibilities or large bureaucracy; anyone can, at least in principle, get to do anything. To my mind this has mostly ups as we get to experience many parts of the project workflow and I’ve been getting to learn various new things, gravitating towards responsibilities where I can excel.</p><p>My actual job title is ‘Data Scientist’, which by itself does not tell very much, since ‘Data Scientist’ is <a href="https://www.reddit.com/r/datascience/comments/j1q5w2/data_scientist_web_master_from_the_90s/">kind of an umbrella term</a> that can describe various different roles going from machine learning engineers to various consultancy-type roles. In my particular case I do a bit of everything, and the main tasks I tend to work on are:</p><ol><li>Writing Python code to implement various machine learning and non- machine learning solutions to technical problems.</li><li>Discussing with the project team and planning what we should do and how.</li><li>Discussing with managers, salespeople and customers on how the current projects are going.</li><li>Discussing with managers, salespeople and customers about what we could provide in the future.</li></ol><p>Note that three out of four of my main tasks start with the word ‘Discussing’, and even programming usually includes chats with various colleagues. So the part about ‘communication skills being important’ mentioned in the previous part was more than just words.</p><p>On a monthly average I’d say that my time is split roughly 50/50 between the computer interaction part of my job, the coding, and the human interaction part of my job, the meetings. Let’s look at these separately.</p><h4>The coding</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*tM-mpKabxUDILuK4" /><figcaption>An almost accurate visualization on my coding habits. Photo by <a href="https://unsplash.com/@weareprocreator?utm_source=medium&amp;utm_medium=referral">Procreator UX Design Studio</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>The supermajority of the technical side of my daily functions is writing code and Python is the language of choice for our team. Before starting here, most of my programming experience was in fact with Python, but that is not saying much as my previous projects were usually small scripts of a few dozen lines to do technical calculations or some graphical presentations of things. Even when doing ‘a lot of coding’ in my postdoc days, this would usually amount to using some hours within the span of a week to produce a just good enough solution to some particular problem. The amount of expertise I’m gaining now when I’m spending several hours every single day with Python is just exhilarating. The Bill Gates quote, “<em>We tend to overestimate what we can do in a day, and underestimate what we can do in a year.”</em> seems to fit my situation very well, even after a few months instead of a year, and I can’t wait to see how my skills look at the one year mark.</p><p>Some people have asked me what was the actual level of my Python skills when I was applying for non-academical jobs for the first time. A good example of my then high-level performance might be this <a href="https://github.com/ramiluisto/VisualCryptography/blob/master/ImageMixer.py">visual cryptography thing</a>. It’s not awful, I think, as it is pretty well commented and you can mostly follow what it is doing, but it is far from great or even good. In particular, even though it is doing well the one single thing it’s doing, it would be really hard to extend, maintain or alter. In particular, if you read <a href="https://www.goodreads.com/book/show/3735293-clean-code">uncle Bob’s book</a> (which I highly recommend) you can see that my code is breaking basically all the guidelines. The major thing here, from my non-expert’s point of view, is that there is a huge difference between some code you wrote to do a thing on your own computer, and with code that will be worked on by several people and should yield an actual usable and maintainable product. (<a href="https://www.goodreads.com/book/show/13629.The_Mythical_Man_Month">Another book recommendation</a> on that topic.)</p><p>With regards to creating code, I knew beforehand that there are more nuances to the Art than I could even guess, so I wasn’t starting <em>quite</em> at the top of the bad peak in the <a href="https://en.wikipedia.org/wiki/Dunning%E2%80%93Kruger_effect">Dunning-Kruger</a> curve, but I’m still not sure if I’ve started to properly ascend or if I’m still just learning more about how little I know. The academical meta-skill of “how to cope with impostor syndrome” has helped me dramatically while improving myself in this endeavour, but not as much as my new colleagues who seem to have a lot of patience to answer my repeated questions.</p><p>Finally — and I guess this might be true of most things — the further I get and the more I learn to use the fancier methods of Python or of the more general machine learning things, the more important it gets to remember when <em>not</em> to use the shiniest and newest tools. There have been cases where we’ve noticed that a simple algorithm can produce a 90% accuracy with 0.1% of the computational resources that our fancy ML system might use to produce 95% accuracy. There is never a singular correct solution, or even a well-defined solution in the mathematical sense, just (hopefully) good solutions with various tradeoffs, which makes the work all the more interesting.</p><h4>The meetings</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*CwurCaLpKT7CWoMt" /><figcaption>Well, actually the meetings are now all in MS Teams for some reason, but this is how I try to feel during. Photo by <a href="https://unsplash.com/@iamdarosaa?utm_source=medium&amp;utm_medium=referral">Jessica Da Rosa</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>I usually spend an hour or two in various kinds of meetings every day, but this number can vary from zero to eight hours depending on the day and week. One excellent thing I have noticed, though, is that unlike in Academia, most meetings are not an (un)avoidable evil but an essential part of various processes. In particular; the meeting is not a boogeyman keeping you from doing the actual work, but<em> instead the meeting is part of the actual work</em>. This also means that the goals and expectations you have do take into account the fact that a large part of your work effort in the project is partaking in meetings. As this is true for all the other people as well, the meetings themselves can be very fruitful events indeed.</p><p>The importance and variety of the meetings also increases in a setting where most of the people do not hold a PhD in my particular narrow branch of research. In mathematical research I often took part in projects that I could not have done on my own, but even in those I had a very good grasp on the skill sets, challenges and workload of the other people in the project as we were all researchers in math. In the industry the projects have a much wider scope; not only could I not do them on my own because my focus in a specific skill set is not covering the area, but there are whole domains of expertise that are completely alien to me yet crucial to the project. The projects transition the capabilities of a person and span across various domains, which means that no single person is capable of understanding everything in detail. This necessitates a huge amount of communication between both individuals and groups. Thus any project needs to be organized in various pieces that abstract the inner mechanical workings of those pieces and which then interface on the abstraction levels. In short; meetings are how the interfaces of the various pieces interact to make sure that the necessary amount of information is flowing.</p><p>Here I feel that the caveat of this article has to be emphasized, since I’ve probably gotten very lucky with the company I work in, especially regarding the meetings culture. I am vividly aware that not all meetings outside the Academia are beautiful congregations of fluid information sharing, but in my experience they can be positive events in a workday. (Though this might be also affected by the Covid-pandemic and people noticing how many meetings really can be just emails.) I furthermore don’t want to claim that every single meeting I’ve been in has been a positive event; naturally there have been times when I’ve realized that I’ve ended up in a meeting where my input will not be needed nor will I need the information presented, but these are in the clear minority.</p><p>Finally, somewhat relatedly, a standard task for us is to respond to Request For Proposals (RFPs) which are basically announcements by possible customers on projects in which they would like companies to bid for solutions. In my eye, these are basically grant applications, as you know what your skills are and what the client would need, and then you need to bridge the gap between these two and explain why your particular skill set is so very suitable for their task. The bids for a RFP naturally require input from various teams in the company, meaning that I get to use my application-writing skills without needing to bog down to the financial details.</p><h3>How does the private sector compare to the Academia?</h3><p>I don’t want to start by completely bashing the academy, but I really need to point out that <a href="https://www.nature.com/articles/d41586-020-03191-7">working</a> <a href="https://www.nature.com/articles/d41586-020-03235-y">in</a> <a href="https://www.nature.com/articles/d41586-019-00688-8">the</a> <a href="https://www.theguardian.com/science/head-quarters/2017/aug/10/the-human-cost-of-the-pressures-of-postdoctoral-research">academia</a> <a href="https://medium.com/@catherine.oakley/there-is-a-large-scale-crisis-of-mental-ill-health-at-doctoral-and-postdoctoral-levels-that-demands-42fcad6b1525">is</a> <a href="https://www.sciencemag.org/careers/2014/07/stressed-out-postdoc">not</a> <a href="https://www.sciencemag.org/careers/2014/02/paying-graduate-schools-mental-toll">always</a> <a href="https://www.nature.com/articles/d41586-020-02541-9">fun</a>. The longer I have now spent in the industry, the more it seems to pop out that many researchers seem to have formed working habits that would be illegal in the private sector. For me the reason behind pushing myself to unhealthy limits was that I didn’t feel like I was <em>working</em> for a university as a grad student or postdoc, I was just doing math while someone was giving me money on a monthly basis so that I can pay my bills and buy food. The blurred lines between ‘what I do for living’ and ‘what I am’ can give rise to very satisfying experiences, but it can also easily mean that you overextend and damage yourself by working too much. The following quote from Chesterton feels like it fit me (and many colleagues as well) quite well:</p><blockquote>“A man must love a thing very much if he practices it without any hope of fame or money, but even practice it without any hope of doing it well. Such a man must love the toils of the work more than any other man can love the rewards of it.”</blockquote><p>You don’t care that you work for 60+ hours a week and never rest properly in an environment where you have continuous uncertainties about your future when you can’t see the difference between your work and yourself. Even with a supporting family, good friends and exciting hobbies the line between work and non-work can sometimes be hard to find. Don’t get me wrong, I do love the people in the academia, and what I miss most from the academia are the people and communities, but as a whole <a href="https://equilibriabook.com/">good people with good intentions can form systems that are not globally optimal for well-being</a>. At the industry side my position is permanent, my pay is higher, my hours are fewer, the work-life balance exists and the goals are reasonable.</p><p>After I wrote the first part several people reached out to me to share their feelings with me privately. Many just wanted to talk about various topics, like about how to decide or prepare to transition, but some of them really wanted and needed a ‘safe’ person to talk to as they were worried to share their academia-related insecurities, frustrations and doubts in public. The reason for their worries was that even though in one sense the infamous anonymous review panels in academia are very fair as the people in the panels can tell their opinions without fearing the politics, they do have the downside that people applying for positions can never know who in the coffee room might be deciding their fate in some later occasion. In particular, panelists can judge applicants based on non-transparent criterion like “I do remember this person having doubts about staying in the Academia — maybe we should fund someone else who never expresses such doubts and toes the party line a bit better”. On the one hand you naturally want to hire the person who will stay for sure, but on the other hand the environment you create by punishing people who express any doubts towards the system is not a good one. I’m not saying that this actually happens, but it is enough that people are concerned that it <em>might</em> happen — I know I was, especially after some older and politically more savvy colleagues explicitly warned me about this.</p><p>So, after saying that I don’t want to overtly complain about the academy and then writing an essay on the topic, let’s move on to looking at positive things I’ve felt since the transition.</p><h4>The particularly good things and some of the downsides in the industry contra academia</h4><p>I’ve already mentioned the immediate, obvious and materialistic aspects: job security, salary, work-life balance etc. Let’s next look at the ones that are harder to measure in numbers.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*5QsODPgoiJBpKimL" /><figcaption>Not actually me, but the vibe of the image fits. Photo by <a href="https://unsplash.com/@cdc?utm_source=medium&amp;utm_medium=referral">CDC</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>First of all, the rhythm of life in our company is quite different than in academia. When I was still a postdoc, my duties were basically divided between teaching and research. The teaching responsibilities created daily and weekly deadlines (lecture preparations and lectures etc) with an underlying deadline of getting the full course completed in the x months it would last. Feedback was provided in small form almost weekly and in a more organized form after the course ended. The research parts, instead, were usually concerned with producing research items a few times a year. By the nature of research, this meant that there were no clear deadlines that could be guaranteed. Feedback on research comes quite sporadically and in different forms, and it’s sometimes impossible to guarantee that by working really hard the whole month you’ll get some information on if the idea is good or bad.</p><p>In the industry, at least in our company, trying to tell the manager or project leader that “this should be done in about 9–12 months” would not be well received. It is much preferable to spend time, usually together, to figure out how that 9–12 months would be divided — first to major parts like ‘planning’, ‘design’, ‘implementation’, ‘production’, ‘handover’ etc and each of those to smaller parts as well until we reach the scale of 1–10 days. Even though this planning does take effort, it gives various benefits to everyone involved:</p><ol><li>The management, HR and finance people can better estimate the amount of work that is needed, whose input is needed and when, and how much resources will all of this take.</li><li>The technical people will have clear weekly or monthly goals, which means that they (we) can concentrate on reasonable sized blocks of work, get feelings of achievement and not be overwhelmed by the totality of things we need to still accomplish. In addition you get much more frequent feedback</li><li>Everyone involved can try to see which parts are taking roughly the amount of time we were estimating them to take, or if there are certain parts which are falling behind and might require extra resources or redesign.</li></ol><p>This goal-orientation is well implemented in our company; you have your goals and if they are achieved then everyone is happy and you get a (monetary) pat on the back. If there seem to be problems in getting things done on time, the ‘system’ detects this and we can figure out what should be changed. The goal-oriented approach also has the nice effect that I get to choose how I wish to get things done — no one but me is managing my day-to-day doings, though we do usually have bi-weekly meetings with the team where we talk about how our projects are going.</p><p>Naturally, I have less choice on what I do day to day in the industry than I had when I was a grant-funded researcher. Back then I had the freedom to do what I wanted and fail as I wanted without anyone officially interjecting. Here the projects are born out of customers’ needs and might be put on hiatus or cancelled based on completely external factors. This means both that I don’t have to spend my time wondering which projects I should pursue and for how long, but on the flip side even the most fascinating project I have might suddenly go away, regardless of my personal wishes or performance. In this, as well as in many other aspects of the world, there is a balance to be found between freedom and security. For me personally the tradeoff so far has been great and has done wonders for my mental well-being; having more shorter-term goals that can be achieved — or even exceeded — feels great. (And in hindsight maybe one of the things I sometimes miss from being an undergraduate is having small clear goals i.e. courses that I should pass with good marks and then be done with them. A similar thing holds for teaching.) And even though it can be very annoying to be told to stop working on an interesting project, this is usually a delay instead of cancellation as the company naturally wants to take advantage of the ideas and experience gathered so far in the project.</p><p>As an additional but somewhat separate note, an unexpected benefit in industry has been to learn that <a href="https://medium.com/software-arguments/i-grew-out-of-free-software-9c493444de8b">MS office and other non-open source software is surprisingly good</a>. I used to be an avid user of open source software and Linux, which worked great in an environment where more than half of my colleagues use their own exotic combination of Linux-distros and text-editors for their workflow. But now that 99% of the people surrounding me use the same MS Office package that integrates calendars and workflows, it turns out that these proprietary programs really do seem to have more money available for development etc.</p><p>Finally, I mentioned earlier that what I do miss from the Academia are the people and communities, which is true, but I should also emphasize that I have naturally found new great people and communities as well. The difference is that e.g. in the AI-team even though around half of the people hold PhD’s in various complicated topics, we all excel in slightly different fields. We do have a common ground, but everyone in the team is clearly much better than everyone else in at least one large field. A similar thing naturally holds in an even greater extent with regards to colleagues working in other teams. As an experience, it’s not better or worse, just different.</p><h3>Afterword</h3><p>Even though this second part was delayed, I’m still planning to turn this into a trilogy, meaning that I’ll hopefully post a <a href="https://ramiluisto.medium.com/a-fully-industrialized-mathematician-abc9fdd8bbd2?source=friends_link&amp;sk=356d6d39912e3c73b7e2e5873df71a37">third and final part </a>where I describe the feelings after 1–2 years of experience in the industry. If you just can’t wait, someone else also wrote about <a href="https://medium.com/@zacernst/leaving-academia-for-the-private-sector-seven-years-later-fbb7849182f6">how the private sector feels seven years after the transition from the Academia</a>. It was a nice read.</p><p>To conclude: join the dark side, we have cookies (and job security)!</p><h4>Acknowledgements:</h4><p>Thanks to Anne, Olli and an assortment of various Franks on the feedback, their comments improved both this (and the previous) text considerably. Also thanks to all of you who read the previous part, especially to those who reached out.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e9352be4a5a9" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Moving from academia to industry — a mathematician’s tale]]></title>
            <link>https://ramiluisto.medium.com/moving-from-academia-to-industry-a-mathematicians-tale-d8dfda40604f?source=rss-db91009082bd------2</link>
            <guid isPermaLink="false">https://medium.com/p/d8dfda40604f</guid>
            <category><![CDATA[private-sector]]></category>
            <category><![CDATA[academia]]></category>
            <category><![CDATA[mathematics]]></category>
            <category><![CDATA[career-advice]]></category>
            <dc:creator><![CDATA[Rami Luisto, PhD]]></dc:creator>
            <pubDate>Sat, 01 Aug 2020 09:09:02 GMT</pubDate>
            <atom:updated>2023-02-14T07:59:17.238Z</atom:updated>
            <content:encoded><![CDATA[<h3>Moving from academia to industry — a mathematician’s tale</h3><figure><img alt="A picture of a huge library shading into a massive industrial factory floor." src="https://cdn-images-1.medium.com/max/1024/1*JboTaHYL_6nfrIzfSeBX0w.png" /><figcaption>How the transition from acadmy to industry looks like. Combined from Unsplash images. (<a href="https://unsplash.com/photos/GWOTvo3qq7U">This one</a> and <a href="https://unsplash.com/photos/io7dX_1EFCg">this one</a>.) <em>Here and in what follows the term ‘industry’ simply refers to any non-academical company or position.</em></figcaption></figure><p>After spending almost fifteen years of my life in various universities, going from a freshman student to a postdoctoral researcher in mathematics, I finally decided to take a big leap and move from the academical world to the private sector. The process of the transition was not completely simple, so I thought that it would be useful for me to write down some of my experiences. In particular, I aim to tell here the kinds of things that I would have liked to have known beforehand. In this text I’ll first say a few words of my professional background and then describe the transition process from preparation to finish.</p><p><strong><em>Caveat lector</em></strong><em>: this is a description of a specific journey from the academical world to the private sector by this specific mathematician, not a step-by-step guide. In particular, when I was born I hit the birth lottery jackpot and I am in the top 1% of pretty much any unfair privilege group, YMMV.</em></p><h3>Personal Background</h3><p>I started my math studies at the University of Helsinki in 2006, and roughly ten years later I got my PhD in mathematics from the very same institution. Despite studying a small amount of computer science, university pedagogy and physics, by my estimate I finished as a ’95% pure mathematician’. By this I mean that even though I’ve always been interested in things beyond just mathematics, my research profile and thus majority of my work was completely focused in math for the sake of math in a field with few immediate applications to the real world.</p><p>After getting my PhD I spent four-ish years doing various postdocs at UCLA (3 months), University of Jyväskylä (6 months), the Charles University in Prague (1 year) and again at University of Jyväskylä (2 years). Getting the chance to work in so many different research environments was a huge plus and it considerably expanded both my research profile and my social networks, but it also had the downside of having to move around a lot during these years. The constant instability and uncertainty about future workplaces can be, and was for me, very grating. In the end the yearning for stability was one of the larger motivations for the transition, together with the ever increasing need to actually live in the same city as my wife, family and friends. Travel is much more fun when it’s the exception and not the rule.</p><p>During my graduate studies and my postdoc periods my work concentrated on research and teaching, but one of my primus motors in life is learning new (technical) things and I’ve pretty much always had the hobby of ‘studying various topics’. Usually these hobbies are short-lived, spending few months studying something new, but they do build up during the years. In particular, I’ve had an on-again, off-again type of relationship with programming since I was 16. I wouldn’t go as far as saying that I’m was good programmer when the process started a year ago, but I was an adequate script-writer in a few different languages.</p><h4>Motivations for the change</h4><p>Besides the ‘negative pressure’ from instability of the academical work life and the frustrations from the cumbersome application rounds, there were also several positive motivations to seek new professional vistas.</p><p>A particularly large influence on the decision to transition was hearing experiences of other people moving to the private sector. Especially in hindsight I get the feeling that mathematicians in the academical career path have a skewed view of the employment possibilities outside of the math department. I don’t think that it is intentional propaganda, but I believe that <em>identifiable role models have a huge effect on what kind of life and career people pursue</em>, and the role models available at math departments tend to be very biased. From the university research and teaching personnel with permanent positions that I personally know, I’d say one in a hundred have had significant work experience in the private sector after getting their PhD. The rest have, as far as I know, followed the unwavering path of academy positions until tenure. There is nothing bad in this career progression, but it would be healthy to be more aware of the alternatives. And yes, there are of course career events and colloquia where we get to hear from the other possibilities, but those don’t have nearly the same impact as spending countless hours in a community where 99% of the people you look up to have gone through the same path. I do not know how math-specific this bias is and it is probably related to the fact that research in pure mathematics is done only in universities — it would be interesting to plot the percentage of e.g. tenured professors in various department who have worked for at least 12 months in the private sector after receiving their PhD, but the data would take some time to come by.</p><p>The important lesson here for me was to find out that there is big world of interesting and challenging work opportunities outside the walls of the math department. Indeed, besides the second hand stories, I had the chance to do some professional consulting related to AI and mathematics and thus practice a bit what it is like in the industry. I was very pleasantly surprised to find complicated and interesting problems that required methods from my mental research toolbox to solve. The aims and goals can be, of course, a little less fanciful than ‘exquisite mathematical beauty’ and more in the vein of ‘the board requires a 5% performance increase this quarter’, but this doesn’t mean that the work isn’t fascinating. Furthermore, having quantifiable achievable goals can do wonders for your mental well-being. In particular, in my research I very rarely if ever feel that I’ve exceeded the expectations of others or of myself — the proof could always have been prettier or I could have found the correct lemma sooner — whereas producing a 18% speed increase in this quarter will get you appraisal and pats on the back, maybe even a bonus!</p><p>Within the private sector, I also feel that I can do more direct Good than in the research environment. This is not to say that research does not do Good — I strongly believe that fundamental research, knowledge for the sake of knowledge, is not only important but even crucial for humanity at large. However, the benefit of research in pure mathematics to the general human condition can be quite a few steps detached from the day-to-day life of a mathematician. And even though I believe the work to be useful it does not mean that I feel it in my heart of hearts on a daily basis. Working as a technical consultant isn’t quite the same as healing the sick, but at least you can imagine a chain of effects leading from your work to concretely helping the society.</p><p>For me, it has been eye-opening to see the different types of job opportunities the private sector has to offer for someone coming from the pure math research environment. And though you do sacrifice some freedoms the benefits can be very much worth it. This does not mean that the choice is easy or fast to make. For me the decision was both difficult and stressful. Especially since for pure mathematics it is exceedingly hard to apply for research positions if you spend a few years not publishing research articles in your field. For me the many long discussions with my wife about the topic were completely invaluable.</p><p><strong><em>Addendum:</em></strong><em> This section has focused on the influences that were moving me to the private sector. This focus has the unfortunate effect of underrepresenting the various motivations I had to</em> not <em>leave the academia, and there are many of those. I won’t start listing all the best things in the academical world in here, but it simply can’t go unsaid that the biggest reason to hesitate leaving the academia was the people. Mathematics is absolute and without adjectives, but the mathematicians are anything but. The communities they form and which I’ve have had the privilege of being part of have given me experiences, friends and memories that I’ll treasure forever.</em></p><h3>The transition</h3><p>Even though the timeline of the situation was not quite that clear cut, for the sake of clarity of the exposition we’ll look at the progress in three steps: Preparation, Application submissions and Interviews.</p><h4>Preparation</h4><p>The idea of working in the private sector had been rolling in my mind every now and then, but I seriously started to consider it in May 2019. (Incidentally, the results and feedback of the Finnish Academy grant application rounds in math are usually announced around May.) I decided to steer my work and hobbies to a direction that would be more applicable not only to my current research and teaching but also to possible future non-academical jobs. I was still planning to possibly stay in academia, but I started hedging my bets.</p><p>The first thing to do was trying to figure out what kind of jobs I could be interested in and what was available. To this end LinkedIn and some other local job-seeking sites proved to be very helpful, along with friends who were already working in the industry. In the end it turned out that jobs related to AI, cybersecurity or scientific programming were those to most arouse my interested and the common denominator in all these positions was programming. Thus the next step was to enhance the skills to an more employable level.</p><p>Though I didn’t need to learn to code from scratch, it didn’t mean that I could <a href="https://norvig.com/21-days.html">turn into a proficient programmer overnight</a>, so the plan was to figure out ways to include some programming as a part of my daily routines and maybe start a few hobby projects as well. After some discussions with people already in the private sector, I also set up a proper GitHub account and uploaded any reasonable coding projects I had had in the past. Think of GitHub as an extension of your CV and remember that, if you are like me and don’t have a lot of things to showcase, it is better to be able to signal both interest and that you are able to design and implement algorithms in readable commented code than to have nothing to show. Depending on your level of coding skills, I would also recommend looking at various online courses available. There is a large variation in their price, quality and value, but for example the deep learning specialization course by Andrew Ng at <a href="https://www.coursera.org/specializations/deep-learning">Coursera</a> was great for me both in refreshing my Python skills and in solidifying my scattered knowledge concerning neural networks in practice.</p><p>Having even a minimal presence at job sites can be very fruitful since, as it turns out, there are people out there looking for math PhDs who know how to program. I had thought that it would take me a long time to make myself hireable and that I would need to have credentials <strong>X</strong>, <strong>Y </strong>and <strong>Z</strong> before starting to seriously apply for positions. In removing this misunderstanding I was helped along by a headhunter who cold-called me in December to ask if I have been planning to work at the private sector. It turns out that there is demand in the industry for people who have a PhD and know how to write code. In the end it got the feeling that many companies seemed to be more interested with the fact that I’m the kind of person who will learn to be better at given tasks than with the particular technical skills I currently possess.</p><h4>Application submissions</h4><p>My original plan had been to wait until around June to start applying for positions with my certification-boosted CV, but this changed with the call from the aforementioned headhunter. In my limited experience, headhunters tend to be kinda hype-y about your hireability and skills, but the pep-talks I got from them were really useful for me and I decided to give a go at applying for a position in a company that we will call <strong>Company D</strong>. Unrelated to this, on the same week a colleague sent me an email about an interesting math consulting position they had noticed, and motivated by the push from the headhunter I decided to give it a go and apply for this <strong>Company S </strong>as well. The key point I got from the headhunter and what you should remember is that your skills as a PhD are valuable and there are companies who would be eager to have you.</p><p>To apply, you then of course need a CV. Most people know that you should adjust your CV for each position you are applying for, but even further I highly recommend to also create a new CV from scratch if you haven’t applied to private sector before. This is due to the fact that most academical CVs I’ve seen, at least for mathematicians, tend to be several pages long and contain a lot of specifics. (See below.)</p><figure><img alt="A comparison of a page of an academical CV next to a one page CV. The academical CV is a wall of text, the other not." src="https://cdn-images-1.medium.com/max/1024/1*9jEy0CnUnwjUCIQI7I6neA.png" /><figcaption>For comparison, here are side by side <strong>page 2/4</strong> of my ‘academical CV’ (<a href="https://luisto.fi/documents/CV-Luisto.pdf">https://luisto.fi/documents/CV-Luisto.pdf</a>) and my one-page ‘industry CV’ (<a href="https://luisto.fi/documents/CV-Luisto-OnePage.pdf">https://luisto.fi/documents/CV-Luisto-OnePage.pdf</a>).</figcaption></figure><p>The kind of detailed information in an academical CV is often relevant when applying for academical positions where the panel might want to check for specific experiences or merits, but usually a complete overkill for a more normal recruitment process. Google around for examples of modern CVs and read a few blog-posts on LinkedIn on what the people who read the CVs have to say about the topic. Make it easy for the reader to quickly see why they should be interested in you and ask you for an interview.</p><p>One very important piece of advice from the headhunter was, that companies can be very interested in your communication skills. (This might be particularly true for people with science PhDs as there are some not completely inaccurate stereotypes about our communication abilities.) In this it can be very useful to highlight your teaching experience, public outreach activities and any presentations you have given. You don’t need to be a superb orator, but it is good to signal that you can discuss complicated topics with people who are not in your own small research group bubble. Most of the jobs require you working as a part of a team, and teams tend to work bad if the information is not flowing. Communication skills can and should be signaled in your CV, but bear in mind that this is something that the recruiters will be assessing also in the interviews.</p><p>I’ll go into more detail about the interview process in the next section, but the end result here was that I wasn’t hired by either of the two companies <strong>D</strong> or <strong>S</strong>. Both companies did say, however, that they would like to contact me in roughly six months in their next hiring round, and claimed that I had apparently been ‘the best of the ones not hired’. At this point I decided to wait until June for most of applications, but to take action if anything particularly interesting came up. Thus I ended up sending an application to the company that ended up hiring me after a good friend mentioned that they are looking for an AI-expert / Data Scientist. Around the same time I was also contacted by <strong>Company E</strong> who had seen my CV on a job-seeking site and asked me for a few interviews. With <strong>Company E</strong> I feel that the interviews went well and I probably would have gotten an offer from them had the COVID-19 shutdown not started during the interview process.</p><h4>Interviews</h4><p>Academical positions, at least on the postdoc level, very rarely have actual job interviews. Thus, by December 2019 I had had essentially one proper job interview for a university teacher position, but no relevant interview experience for technical roles in the private sector. Even though I am quite extroverted and happy to improvise, I was exceedingly nervous. Here there is another good argument for starting to apply early as you will get experience in being in interviews. I don’t know if I learned to be interviewed better, but at least after the first few times I was a lot less nervous before and during.</p><p>The diagram below tries to visualize the flow of the interviews for the four companies I ended up applying to. In short; in one company I had only one interview, in the other companies I got to second interview as well and for the company that in the end hired me I had three interviews all together. The interviews varied a lot from company to company, but in those with multiple interviews the first one tended to be a more high-level discussion with some people from HR, and the latter interviews had more people from the actual teams that I would be working with.</p><figure><img alt="A flow chart of the results of various interviews." src="https://cdn-images-1.medium.com/max/1024/1*BkoHKfUJepWiUsgH1ciGmg.png" /><figcaption>Because literally everything is better with Sankey diagrams, and because it’s nice to have some colorful pictures every now and then.</figcaption></figure><p>No two interviews were alike, which is quite natural since no two discussions are alike. Remember; you are at the interview because they are interested. You are a valuable asset and you are there to <em>discuss </em>if you are the best fit for <em>each other</em>. The interview is not an exam but a first date where you are talking about each other’s preferences to see if your skills and interests are a match. Don’t just answer questions, but try to ask questions yourself as well to see if the company and team feel like the right place for you. They are not looking for an automaton who’ll complete tasks but a colleague to work with.</p><p>In all interviews I was asked to introduce myself and ‘tell about yourself’. In the first interviews I think I was a bit too eager, telling a lot more than needed for the position, in later interviews I decided to give somewhat more broader strokes. Like with the CV, the ‘tell about yourself’ is good to fine-tune to the particular company and position. Even better if you are able to read the room — try to feel what information is interesting to the particular people you are talking with. The same holds true for many other topics that will come up; try to figure out both beforehand and in situ how your skills and experiences could be useful for the particular position.</p><p>The topic of ‘communicating and working in groups’ also came up in various forms, and here it’s good to remember that they are not asking you to list credentials on how you are good at communicating and working with others, but you need to <em>communicate</em> the information to them. The whole interview is you working together with this group of people, trying to solve to question of how well you would fit together. In one company, part of the process was also giving me a technical AI-paper and asked to give a short presentation about the content to the team I would be working with. This was, naturally, a bit scary but also a big plus as it helped me to imagine what it would be like to work with these people.</p><p>Naturally, I’ve omitted here many of the standard interviewing advice like ‘dress sharply’ and ‘research the company beforehand’ as I’ve wanted to focus on the things that I feel were specific to me being a math PhD applying for the first time to the private sector. Some of the general advice is obvious, some of it not and I do recommend Google and reading a few blog posts about what interviews are all about.</p><p><strong><em>In a nutshell:</em></strong><em> Knowing at least one programming language is a huge plus, you should flaunt your teaching experiences as communication skills, and understand that you are a valuable asset that many companies are happy to hire.</em></p><h3>Afterword</h3><p>A year ago when I was first starting to seriously consider leaving the academia, the idea filled me with varying levels of dread. I had many conflicting fears and worries, many of them revolving around feelings of loss and defeat. Now, a year later, I don’t feel at all like I had given up or lost. There are some wistful feelings, of course, but mostly I feel relief, content and excitement. My exciting job will actually stop in the afternoons, I get to sleep in my own bed next to my wife every night of the week and I don’t have to spend a month every year just to apply for my own job. The decision was hard and stressful and it took me months to process and to come to terms with, but in the end it was worth it. So if you are planning a transition and feel worried: it’s quite normal to be scared, take it easy, talk to your loved ones about it and be assured that it can actually feel pretty awesome on the other side.</p><p>This text has described the transition phase of moving from academy to the industry. I am planning to write two more longer texts, <a href="https://ramiluisto.medium.com/moving-from-academia-to-industry-some-months-later-e9352be4a5a9">one in roughly three months from now</a> and <a href="https://ramiluisto.medium.com/a-fully-industrialized-mathematician-abc9fdd8bbd2?source=friends_link&amp;sk=356d6d39912e3c73b7e2e5873df71a37">another roughly one or two years from now</a>, describing what happens after the transition. At least if there seems to be interest to such texts. And if I remember to.</p><p>What I personally look forward to in these future texts will be the story of what happens with my relationship to mathematical research. I currently think that there will be little hope for me to continue to produce cutting-edge new math, at least by myself, but I’d be ready to believe that I could be able and willing to make contributions to some collaborative projects where the onus of the work is not on me. Even more than such projects that do aim to produce publishable results, I hope that toying around with a few choice research problems that I haven’t quite cracked yet will remain a part-time hobby. But I guess only time will tell. Thank you for reading.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d8dfda40604f" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>