<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Jacob Simon</title>
    <description>The latest articles on DEV Community by Jacob Simon (@jacobsimon).</description>
    <link>https://dev.to/jacobsimon</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F214018%2Fa696b8a1-01e7-46f4-9b03-ffde114e4582.jpg</url>
      <title>DEV Community: Jacob Simon</title>
      <link>https://dev.to/jacobsimon</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/jacobsimon"/>
    <language>en</language>
    <item>
      <title>Three Tools to Help Your New Remote Team</title>
      <dc:creator>Jacob Simon</dc:creator>
      <pubDate>Tue, 24 Mar 2020 05:32:56 +0000</pubDate>
      <link>https://dev.to/jacobsimon/three-tools-to-help-your-new-remote-team-3j2i</link>
      <guid>https://dev.to/jacobsimon/three-tools-to-help-your-new-remote-team-3j2i</guid>
      <description>&lt;p&gt;As companies across the world continue to take precautions against COVID-19, many teams find themselves "suddenly remote" and adjusting to a new set of challenges on top of their daily work. At &lt;a href="https://tryexponent.com/?src=devto"&gt;Exponent&lt;/a&gt;, we've been operating as a remote team for most of the past year, with engineers, designers, and PMs spread across several time zones—not to mention thousands of users around the world who are part of our Slack community and &lt;a href="https://tryexponent.com/questions"&gt;Interview Practice&lt;/a&gt; forum.&lt;/p&gt;

&lt;p&gt;While we don't have all the answers, we wanted to share a few of our favorite tools that we've been using to keep our team together:&lt;/p&gt;

&lt;h2&gt;
  
  
  1. Tandem
&lt;/h2&gt;

&lt;p&gt;The largest obstacle to progress as a remote team (or any team for that matter) is the lack of direct communication between team members. When you work in an office, you know when people are around, you can tap on someone's shoulder when you have a question, and you feel like a part of the same team.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://tandem.chat"&gt;Tandem&lt;/a&gt; gives you back some of this convenience in the form of a lightweight 'remote office' where you can instantly chat and share your screen with coworkers. To be honest, the always-on nature of the app is a bit off-putting at first (read: lots of mouth-sounds), but it's so much faster than setting up a conference call or pinging someone on Slack to see if they're available.&lt;/p&gt;

&lt;h2&gt;
  
  
  2. Figma
&lt;/h2&gt;

&lt;p&gt;Another major problem with working remotely is that it's hard to communicate visually with teammates on rough ideas, sketches, and designs. &lt;a href="https://figma.com"&gt;Figma&lt;/a&gt; was a game-changer for our team in the way that we iterate and share designs at Exponent, allowing us to quickly gather feedback and create a source of truth for final design on our team. And even though Figma is technically meant for user interface design, we've found it to be useful as a more general collaborative workspace, where we can share inspiration and organize various projects that we're working on.&lt;/p&gt;

&lt;h2&gt;
  
  
  3. Notion
&lt;/h2&gt;

&lt;p&gt;There are tons of products for writing and organizing docs—Google Docs, Paper, Coda, etc—but we've found that &lt;a href="https://notion.so"&gt;Notion&lt;/a&gt; has the best balance of organization and ease of discovery (you'll learn to love the Cmd-P search bar). It's not perfect for everything, but it's quickly become our home base for meeting notes, product specs, and even drafts of blog posts like the one you're reading. Plus, we love the ability to quickly publish beautifully formatted docs online and share them with anyone.&lt;/p&gt;

&lt;p&gt;Do you have any tips or favorite tools for remote work? Share your thoughts below in the comments!&lt;/p&gt;

</description>
      <category>career</category>
      <category>productivity</category>
      <category>inter</category>
    </item>
    <item>
      <title>Interview: How Levels.fyi Brought Salary Transparency to the Tech Industry</title>
      <dc:creator>Jacob Simon</dc:creator>
      <pubDate>Tue, 10 Sep 2019 07:47:50 +0000</pubDate>
      <link>https://dev.to/jacobsimon/interview-how-levels-fyi-brought-salary-transparency-to-the-tech-industry-52d2</link>
      <guid>https://dev.to/jacobsimon/interview-how-levels-fyi-brought-salary-transparency-to-the-tech-industry-52d2</guid>
      <description>&lt;p&gt;&lt;em&gt;As part of &lt;a href="https://tryexponent.com"&gt;Exponent&lt;/a&gt;'s interview series, I interviewed &lt;a href="https://twitter.com/zuhayeer"&gt;Zuhayeer Musa&lt;/a&gt;, co-founder of &lt;a href="https://levels.fyi/?src=exponent"&gt;Levels.fyi&lt;/a&gt;, to discuss careers in tech, launching MVPs, and negotiating salaries.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;J: What motivated you to build and launch Levels.fyi?&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Z: Around 2 years ago, my co-founder Zaheer and I were chatting about what I'd do after college. I was looking at companies to apply to and had just joined an app called Blind (an anonymous community forum for chatting about the workplace). Zaheer was in the middle of looking for a new job and was complaining about how difficult it was to compare titles across companies. As we scrolled through Blind we noticed several of the same types of questions, "At what level can a Senior SDE/Level 63 at Microsoft be placed at Google?"&lt;/p&gt;

&lt;p&gt;We realized this was a common question and decided to build a simple visualization to compare software engineer titles across companies. The next few times a related question came up on Blind, we shared a link to our site. In a matter of days, traffic picked up as other people began sharing the site in response to leveling questions. A few months later we began collecting salary data after noticing the same gap in knowledge. The site naturally grew as we shipped features to make career decisions easier. Since then, we’ve expanded into Product Management, Software Engineering Management, and Product Design career tracks!&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;What was your background before starting Levels?&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;I previously interned at Uber, graduated from UC Berkeley in 2018, and then eventually started working on Levels.fyi full time. Zaheer graduated from UC Irvine, where he worked on his popular app, TagsForLikes. After graduating he started at LinkedIn before joining Amazon Web Services (AWS).&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;How did you build the first version of Levels, and how have things changed since launching?&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;At launch, Levels.fyi was a completely static website with leveling info for just 3 companies (Google, Facebook, Amazon). We quickly realized crowdsourcing information was the only way we could scale and grow. We developed a process to continually review and refresh data on the site as users contribute career ladders and submit salary data.&lt;/p&gt;

&lt;p&gt;We’re strong proponents of shipping the minimum viable product (MVP) first and iteratively adding features across the site. Most recently we added a dedicated page for compensation data where you can slice &amp;amp; dice our data (ex. product manager salaries). We found that users loved our website even when it was super minimal. A pretty website design is worthless if you can’t unlock significant value for users in the process.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;What’s next?&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Our vision is to bring transparency for employees and employers making career decisions. The market moves fast and companies are incentivized to keep information obscure. Employees have the lower hand. We hope that Levels.fyi can help level the playing field, but our work is far from done.&lt;/p&gt;

&lt;p&gt;Right now, we’re working on regionalizing our data and visualizations. We have a significant user base outside of the Bay Area, but some users believe we’re only focused on the biggest tech companies. Although we do collect city information, we previously didn't normalize the data or offer any filters. Along the same lines, we’re working on sourcing data for more companies. I once heard, “Your best customers are the ones you already have.” Although it primarily was encouragement for up-selling, it’s quite relevant to traffic as well. Optimizing your landing page and maximizing conversions from existing visitors is far more efficient than advertising.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Software engineering and product management are increasingly popular careers. What advice do you have for people who are considering careers in tech?&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Anyone can do it! Even if you don’t have a formal education, it's possible to get into tech by demonstrating your skills and that you’re willing to learn on the job. And a great way to do that is to work on fun side projects. Demand for employees in tech is at an all-time high and as more traditional industries become tech-enabled the demand will only increase.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Do you have any tips for negotiating a higher offer?&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;When evaluating opportunities, make sure you also properly evaluate yourself and know your worth. Nearly every employment offer can be negotiated, and you can probably command more compensation than you think. Fifteen minutes can earn you 5% or more in compensation (hat-tip to Geico). Having competing offers is usually the easiest way to negotiate but even if you don’t, do some research on salary bands and just ask. Not sure what the salary range for your position is? Check out &lt;a href="https://levels.fyi"&gt;Levels.fyi&lt;/a&gt;!&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Originally posted on &lt;a href="https://blog.tryexponent.com/levels-interview-tech-salary-transparency/"&gt;Exponent's Blog&lt;/a&gt;. Looking for help with your &lt;a href="https://www.tryexponent.com/?src=devto"&gt;product management&lt;/a&gt; or &lt;a href="https://www.tryexponent.com/software-engineering?src=devto"&gt;software engineering&lt;/a&gt; interviews? &lt;a href="https://www.tryexponent.com"&gt;Exponent&lt;/a&gt; offers courses and 1-1 practice interviews that help you land your next role in tech.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>career</category>
      <category>discuss</category>
      <category>productivity</category>
      <category>webdev</category>
    </item>
    <item>
      <title>What are your favorite open source projects?</title>
      <dc:creator>Jacob Simon</dc:creator>
      <pubDate>Sat, 24 Aug 2019 06:57:50 +0000</pubDate>
      <link>https://dev.to/jacobsimon/what-are-your-favorite-open-source-projects-1244</link>
      <guid>https://dev.to/jacobsimon/what-are-your-favorite-open-source-projects-1244</guid>
      <description>&lt;h1&gt;
  
  
  Top Open Source Projects in 2019
&lt;/h1&gt;

&lt;p&gt;According to GitHub, these were some of the top open source projects in the past year, based on the number of contributors. It's amazing to realize how many people are actively contributing to all these projects around the world; the VSCode repository has nearly 200 open pull requests at the moment!  &lt;/p&gt;

&lt;ol&gt;
&lt;li&gt; &lt;a href="https://github.com/microsoft/vscode/"&gt;Microsoft/vscode&lt;/a&gt;    – 19K &lt;/li&gt;
&lt;li&gt; &lt;a href="https://github.com/facebook/react-native"&gt;facebook/react-native&lt;/a&gt;   – 10K&lt;/li&gt;
&lt;li&gt; &lt;a href="https://github.com/tensorflow/tensorflow"&gt;tensorflow/tensorflow&lt;/a&gt;   – 9.3K&lt;/li&gt;
&lt;li&gt; &lt;a href="https://github.com/angular/angular-cli"&gt;angular/angular-cli&lt;/a&gt;   – 8.8K&lt;/li&gt;
&lt;li&gt; &lt;a href="https://github.com/MicrosoftDocs/azure-docs"&gt;MicrosoftDocs/azure-docs&lt;/a&gt; – 7.8K&lt;/li&gt;
&lt;li&gt; &lt;a href="https://github.com/angular/angular"&gt;angular/angular&lt;/a&gt;   – 7.6K&lt;/li&gt;
&lt;li&gt; &lt;a href="https://github.com/ansible/ansible"&gt;ansible/ansible&lt;/a&gt;   – 7.5K&lt;/li&gt;
&lt;li&gt; &lt;a href="https://github.com/kubernetes/kubernetes"&gt;kubernetes/kubernetes&lt;/a&gt;   – 6.5K&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  What are &lt;em&gt;your&lt;/em&gt; favorite open source projects?
&lt;/h2&gt;

&lt;p&gt;What projects deserve more attention or contributors? Let everyone know in the comments below!&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Stay in the loop! Follow me for more posts about software, tech, and more. Check out &lt;a href="https://www.tryexponent.com/software-engineering?src=devto"&gt;Exponent&lt;/a&gt; for help with software engineering interviews.&lt;/em&gt;    &lt;/p&gt;

</description>
      <category>discuss</category>
      <category>opensource</category>
      <category>javascript</category>
    </item>
    <item>
      <title>The 3 Sins of Software Engineering Interviews</title>
      <dc:creator>Jacob Simon</dc:creator>
      <pubDate>Sun, 18 Aug 2019 03:59:35 +0000</pubDate>
      <link>https://dev.to/jacobsimon/the-3-sins-of-software-engineering-interviews-5fe0</link>
      <guid>https://dev.to/jacobsimon/the-3-sins-of-software-engineering-interviews-5fe0</guid>
      <description>&lt;p&gt;In my time as a software engineer, I've interviewed hundreds of candidates for front-end, full-stack, and backend developer roles. Here are some surprisingly common mistakes that you should avoid to improve your chances of passing the interview. &lt;/p&gt;

&lt;h2&gt;
  
  
  1. Using a language you don't know
&lt;/h2&gt;

&lt;p&gt;Forget what language is trending right now or what the company you're applying for uses—always use the language you know best. If you love Ruby, just use Ruby! &lt;/p&gt;

&lt;p&gt;Why? Because time is of the essence in a technical interview. If you choose a language that isn't second nature to you, you're going to waste precious mental cycles trying to remember which functions to use and gloss over obvious bugs.&lt;/p&gt;

&lt;h2&gt;
  
  
  2. Only coding in your IDE
&lt;/h2&gt;

&lt;p&gt;You may not realize how much you rely on the help of your IDE to autocomplete your code on a daily basis. Unfortunately, autocomplete doesn't work on a whiteboard. And some languages (&lt;em&gt;cough&lt;/em&gt; Java) can be quite verbose and slow you down in an interview. This isn't a showstopper, but it means you should &lt;em&gt;practice in an interview setting&lt;/em&gt; (in a text editor, on a whiteboard). If you want real-world practice, you should also check out &lt;a href="https://www.tryexponent.com/software-engineering?src=devto"&gt;Exponent's mock interviews&lt;/a&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  3. Not taking a &lt;em&gt;hint&lt;/em&gt;
&lt;/h2&gt;

&lt;p&gt;Getting stuck in an interview isn't the worst thing, but interviewers hate it when candidates veer off track and ignore their suggestions. Learn to recognize when the interviewer is trying to help you. If you find yourself answering vague questions—like "Why do we we need to do X?" or "How do you know Y?"—your interviewer may be suggesting you try to find an alternative (or simpler) solution. Use this hint as an opportunity to step back and think about your approach. Don't forget that half of the interview is about your communication skills – how well you explain ideas and how well you listen to feedback from the interviewer.&lt;/p&gt;

&lt;h3&gt;
  
  
  Want more help?
&lt;/h3&gt;

&lt;p&gt;Want help practicing for your interviews? Check out &lt;a href="https://www.tryexponent.com/software-engineering?src=devto"&gt;Exponent&lt;/a&gt;, where we match you with experienced mentors who've worked at top tech companies like Google, Facebook, Uber, and Dropbox. Subscribe to our &lt;a href="https://www.youtube.com/exponenttv"&gt;YouTube channel&lt;/a&gt; for more helpful tips and videos.&lt;/p&gt;

</description>
      <category>career</category>
      <category>study</category>
      <category>beginners</category>
    </item>
  </channel>
</rss>
