<?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 Artem Kholodenko on Medium]]></title>
        <description><![CDATA[Stories by Artem Kholodenko on Medium]]></description>
        <link>https://medium.com/@artemkholodenko?source=rss-92fb9640317------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/2*YMAv8ifJsnmr6jOBAN1RrQ.png</url>
            <title>Stories by Artem Kholodenko on Medium</title>
            <link>https://medium.com/@artemkholodenko?source=rss-92fb9640317------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 08:49:33 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@artemkholodenko/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[Giving Candidates Feedback: Focus on Signal, Not Shortcomings]]></title>
            <link>https://artemkholodenko.medium.com/giving-candidates-feedback-focus-on-signal-not-shortcomings-d35f76afc28c?source=rss-92fb9640317------2</link>
            <guid isPermaLink="false">https://medium.com/p/d35f76afc28c</guid>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[candidate-experience]]></category>
            <category><![CDATA[hiring-for-startup]]></category>
            <category><![CDATA[hiring-tips]]></category>
            <category><![CDATA[hiring]]></category>
            <dc:creator><![CDATA[Artem Kholodenko]]></dc:creator>
            <pubDate>Thu, 18 Sep 2025 00:25:25 GMT</pubDate>
            <atom:updated>2025-09-18T00:25:25.776Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*aymEUnOiv8IeEgMaIxkB0A.png" /><figcaption>Respectful feedback benefits both sides. Candidates leave the process feeling valued, even in rejection.</figcaption></figure><p>One of the toughest parts of hiring is providing feedback to candidates who don’t move forward. Many managers avoid it altogether, or default to phrases that, while technically accurate, often land poorly: <em>“We didn’t think your database skills were strong enough”</em> or <em>“You weren’t senior enough for the role.”</em></p><p>This framing makes feedback about the candidate’s shortcomings. That’s not fair, and it’s not helpful. In most cases, it isn’t that the person “wasn’t good enough.” It’s that the interview process didn’t produce enough <strong>signal</strong> in the areas needed to evaluate fit for the role.</p><h3>Why So Many Companies Don’t Provide Feedback</h3><p>A common reason given for not providing feedback is “company policy.” On the surface, it sounds like a legal safeguard. In practice, it often conveys something else: a lack of effort or willingness to give candidates thoughtful, respectful feedback.</p><p>The truth is, there are <strong>no legal restrictions</strong> on properly framed feedback. When feedback is professional, anchored to the role, and free of judgmental language, it is not a liability. On the contrary, candidates almost always value it — even when the outcome is disappointing.</p><h3>What “Signal” Means</h3><p>Interviews are about gathering evidence — signal — on whether someone can succeed in a specific role. That signal may come from:</p><ul><li>How they approach problems</li><li>The clarity of their communication</li><li>Their depth in technical areas relevant to the team</li><li>Examples of leadership or collaboration</li></ul><p>Sometimes the signal is strong and clear. Other times, despite relevant experience, it isn’t. Lack of signal doesn’t mean the person is incapable — it means the evidence wasn’t sufficient to make a confident decision.</p><h3>Reframing Feedback Around Signal</h3><p>Feedback lands more respectfully when it is framed around the signal gathered, rather than deficiencies in the candidate.</p><p>Instead of:</p><ul><li><em>“You didn’t show enough strength in database skills.”</em></li></ul><p>Say:</p><ul><li><em>“For this role, we were looking to get clearer signal on working with databases at scale. We didn’t get enough from our conversation to feel confident making that call.”</em></li></ul><p>Instead of:</p><ul><li><em>“You weren’t senior enough.”</em></li></ul><p>Say:</p><ul><li><em>“This role requires leading through ambiguity across multiple teams. We didn’t get enough signal from the discussion to be confident about that scope.”</em></li></ul><p>This shift takes the focus off shortcomings and emphasizes the evidence available for making a hiring decision.</p><h3>Principles for Respectful Feedback</h3><p>A few practices make feedback more constructive and respectful:</p><ol><li><strong>Anchor to the role, not the person.</strong> Keep feedback tied to what the role requires, not judgments about ability.</li><li><strong>Be evidence-based.</strong> Reference what was or wasn’t observed, not assumptions.</li><li><strong>Use “signal” as the framing device.</strong> It communicates that the decision was about confidence, not capability.</li><li><strong>Balance honesty with care.</strong> Provide enough detail to be useful, but not so much that it feels like a teardown.</li><li><strong>Preserve the relationship.</strong> A “no” today may be a “yes” in the future — feedback should keep that door open.</li></ol><h3>Why It Matters</h3><p>Respectful feedback benefits both sides. Candidates leave the process feeling valued, even in rejection. They are more likely to:</p><ul><li>Stay open to future opportunities</li><li>Speak positively about the company</li><li>Reflect constructively on their growth</li></ul><p>It also strengthens the employer brand, helping attract stronger talent over time.</p><h3>Closing Thought</h3><p>Hiring is about evaluating signal, not labeling people as good or not good. When feedback is framed around the signal collected — and not hidden behind company policies — it keeps the process honest, respectful, and human. That approach builds trust, preserves relationships, and creates a hiring culture worth being proud of.</p><p>Hiring is about evaluating signal, not labeling people as good or not good. When feedback is framed around the signal collected — and not hidden behind company policies — it keeps the process honest, respectful, and human. That approach builds trust, preserves relationships, and creates a hiring culture worth being proud of.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d35f76afc28c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Five Attributes of an Engineer]]></title>
            <link>https://artemkholodenko.medium.com/five-attributes-of-an-engineer-38d32ba2be15?source=rss-92fb9640317------2</link>
            <guid isPermaLink="false">https://medium.com/p/38d32ba2be15</guid>
            <category><![CDATA[engineering-culture]]></category>
            <category><![CDATA[engineering-career]]></category>
            <category><![CDATA[performance-management]]></category>
            <dc:creator><![CDATA[Artem Kholodenko]]></dc:creator>
            <pubDate>Wed, 05 Jun 2024 21:37:20 GMT</pubDate>
            <atom:updated>2024-06-05T21:43:00.215Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/600/0*2lwN35H-39eNfC8R.jpg" /></figure><p>It is easy to argue that an engineer has one attribute: rockstar, or 1,000 attributes. Having thought through and applied the following methodology over a number of years, I believe the following five do an effective job of comprehensively covering the role of an engineer from most critical facets.</p><p>The five attributes of an engineer represent groups of skills and abilities that are expected at each level of career progression. The overarching theme is magnitude of impact and ability to multiply others.</p><p>Impact starts with self. As an engineer professionally matures, the impact expands beyond self and to other team members. Reaching beyond a senior member of a team, impact grows to multiple teams, before achieving organizational level. At the highest pinnacle of impact, a technical leader (whether individual contributor or people leader) impacts the company as a whole.</p><p>Multiplying others starts first with the ability of senior technical leaders being able to leverage engineers to multiply the leader’s impact. During the course of a career, an engineer shifts from multiplying others, to leveraging others to multiply themselves.</p><h3>Tech Skills</h3><p>A foundational piece of defining an engineer are technical skills. The skills aren’t solely represented as a current snapshot, but in pairing with the ability to quickly pick up new skills to accelerate knowledge growth and magnitude of impact. The magnitude grows from small tasks and features at the start of a career to driving the planning and execution of major critical systems that lead to significant business impact as an executive-level technical individual contributor.</p><h3>Delivery</h3><p>While the joy of learning new skills and solving problems is part of the journey, in a professional world, the most critical aspect is the destination. A major aspect of impact is underscored by the ability to deliver a technical solution to a business problem within a predictable time frame and a high bar for quality. Delivery is supported by three main pillars: planning, execution, and last mile. In more detail, delivery involves the ability to absorb requirements, picture the project end-to-end and breakdown with effort estimation, execute on the derived plan, and push over the finish line through typical hurdles like code reviews, QA, UAT and a deployment plan.</p><h3>Ownership</h3><p>While notably more complex to quantify, ownership starts to get into the soft skills of a technical professional. A key aspect is being proactive, an unblocker and a loop-closer. In the question of who’s responsible for <em>this</em>, the answer is always <em>you.</em> The best philosophy that highlights ownership is the concept of <a href="https://www.amazon.com/Extreme-Ownership-U-S-Navy-SEALs/dp/1250067057">Extreme Ownership</a>.</p><h3>Soft skills</h3><p>The success of growing tech skills through learning from others, being able to collaborate on delivery, and having a successful level of ownership heavily depends on soft skills. As an engineer grows their impact, the ability to communicate beyond the technical team becomes a must have. Understanding the needs and points of views of product managers, business stakeholders, and external partners becomes a must-have skill. Setting expectations and proactively keeping all needed parties in the loop defines the reliability level of an engineer.</p><h3>Leadership</h3><p>Early on in a career an engineer is focused on developing the above attributes. As an engineer approaches a senior level, leadership starts to take a more center stage. Early areas of focus support code standard and best practices enforcement. This progresses to mentoring other engineers, setting technical roadmaps, and leveraging others to multiply yourself.</p><p>Each of the attributes can easily be a lengthy write up of their own. No doubt there’s the sixth attribute on the bench that will play a critical role down the road.</p><p>Whether it’s these five or others, the important piece is not to share expectations once and simply include in an onboarding handbook. Any expectation is only effective when connected to individuals, their expected and current performance levels, with examples of operating at or next-level challenges that they should be striving for.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=38d32ba2be15" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Solving Problems at the Root]]></title>
            <link>https://artemkholodenko.medium.com/solving-problems-at-the-root-4dbd67dbaa?source=rss-92fb9640317------2</link>
            <guid isPermaLink="false">https://medium.com/p/4dbd67dbaa</guid>
            <category><![CDATA[job-search]]></category>
            <category><![CDATA[job-hunting]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[agtech]]></category>
            <category><![CDATA[solving-hard-problems]]></category>
            <dc:creator><![CDATA[Artem Kholodenko]]></dc:creator>
            <pubDate>Sat, 20 Feb 2021 11:07:09 GMT</pubDate>
            <atom:updated>2021-02-22T03:28:29.955Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*e8I6p7b5WGxWRoAfQtMDAQ.png" /><figcaption><a href="https://www.toddklassy.com/">https://www.toddklassy.com/</a></figcaption></figure><p>During my time at Instacart, underscored by the Covid-19 pandemic, the need for reliable and affordable access to food was boldly highlighted as an ongoing problem to solve. The logistics of virtual shopping and real-world delivery are the final tip of the iceberg for a supply chain that starts all the way back at the farm.</p><p>The agriculture industry is age-old and the market size measures in the hundreds of billions. <a href="https://en.wikipedia.org/wiki/Agricultural_technology">Ag-tech</a> however, is currently in its infancy. Helping farmers run more efficient and sustainable businesses will help produce a reliable and affordable food supply for generations to come. To help solve problems closer to the root, I am joining <a href="https://www.fbn.com/">Farmers Business Network (FBN)</a> to lead their financial and insurance engineering efforts.</p><p>While many granular attributes went into my decision making process, they all roll up to three main areas.</p><h3>People</h3><p>This is the number one attribute when deciding to professionally align myself with an organization. Not being on the same wavelength as colleagues and leadership leads to frustrating and fruitless results.</p><h3>Impact &amp; market size</h3><p>Understanding the impact of the problem being tackled is key in determining if it’s the most critical issue to solve for the industry. Sizing the market is directly aligned with defining business impact.</p><h3>Product market fit</h3><p>While many success stories have come from dreamers tackling problems with seemingly impossible solutions, it’s important to be able to evaluate and understand what the path to success and failure looks like. This includes risk assessment and how it overlaps with your personal risk tolerance.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4dbd67dbaa" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Conveying urgency through data]]></title>
            <link>https://artemkholodenko.medium.com/conveying-urgency-through-data-a34d02e5cc51?source=rss-92fb9640317------2</link>
            <guid isPermaLink="false">https://medium.com/p/a34d02e5cc51</guid>
            <category><![CDATA[project-management]]></category>
            <category><![CDATA[urgency]]></category>
            <dc:creator><![CDATA[Artem Kholodenko]]></dc:creator>
            <pubDate>Fri, 07 Feb 2020 22:47:04 GMT</pubDate>
            <atom:updated>2020-02-07T22:47:04.688Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/960/0*Z_aywMB162CMBoRc.png" /></figure><p>One of the most common frustrations professionals face in growing organizations is the increased turnaround time on deliverables. Whether it’s an incident that wasn’t addressed fast enough, or a blocking project by another team that took longer than it should have, the perception is things move slower.</p><p>The perception of a decreased pace is not necessarily false. When there’s more people, more features, and more code, getting alignment across all facets takes more talking, thinking, and understanding than before. However, a gap in communication that can lead to an incorrect priority ranking of a to-do for a team or an individual.</p><p>It’s not uncommon for an engineer to get pinged by the boss with a message of “This feature is broken! It needs to get fixed ASAP!”. The priority is set by the boss: <em>I have an exclamation point in every sentence — this must be important</em>. The engineer will drop everything and focus on the issue at hand. This earns great respect and perception of understanding of what really is important.</p><p>But why? How many users does the issue impact? How much money is the company loosing? How many users and how much revenue does the work the engineer dropped to focus on this issue impact? What’s the cost of the context switch?</p><p>These are all great questions and the answers are excellent data points to convey urgency and get multiple individuals and teams on the same page.</p><p>I recently had a chat with a fellow engineering leader, who was having trouble conveying urgency to parallel teams responsible for implementing blocking components of a system that his team needed to resolve an issue impacting thousands of users. While the immediate issue was patched up, the band-aid solution was not going to hold for long.</p><p>We went through the above questions:</p><ul><li>the number of users impacted?</li><li>resulting hit to revenue and the time the work would take?</li><li>opportunity cost: what projects the teams were prioritizing above the blockers?</li><li>how long it did it take to obtain the growth matching the impacted users and revenue?</li></ul><p>It was very clear that the best thing the teams could be doing as their top priority was implementing the needed support to resolve the patched-up issue with a long term solution. Working on regaining that many users and that much revenue would take significantly longer.</p><p>An additional consideration that may be relevant in scenarios involving external clients is the potential of unlocking future opportunities. Will addressing a minor issue quickly build the trust and loyalty from customers to drive bigger commitments?</p><p>With this information in hand, the engineering leader was able to get all the teams on the same page by focusing on impact. Data is great at driving consensus and setting urgency. If you believe an individual or team is misaligned, make effort to understand what is being prioritized over what you believe to be most urgent. Then quantify the impact between the conflicting priorities. An apples-to-apples comparison leads to clarity in stack-urgency.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a34d02e5cc51" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Define Career Ladders Early]]></title>
            <link>https://artemkholodenko.medium.com/define-career-ladders-early-ed7cf094e4a0?source=rss-92fb9640317------2</link>
            <guid isPermaLink="false">https://medium.com/p/ed7cf094e4a0</guid>
            <category><![CDATA[careers]]></category>
            <category><![CDATA[hiring-for-startup]]></category>
            <category><![CDATA[career-ladder]]></category>
            <dc:creator><![CDATA[Artem Kholodenko]]></dc:creator>
            <pubDate>Wed, 15 Jan 2020 23:35:22 GMT</pubDate>
            <atom:updated>2020-01-15T23:37:34.632Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/0*VMkA36e3WzXDN7pa" /></figure><p>One thing that is definitely absent from the lengthy to-do lists on day one of a company’s founding are career ladders. At the inception of a company, there are only the founders. The title of <strong>founder </strong>(if one) or <strong>co-founder </strong>is all that exists. Titles don’t matter because each person involved knows how they can contribute. Getting things off the ground is the most important thing.</p><p>As the founders build something that may justify a round of outside investment, they hustle to get a foot in the door with <a href="https://en.wikipedia.org/wiki/Venture_capital">VCs</a> and <a href="https://en.wikipedia.org/wiki/Angel_investor">Angel investors</a>. These conversations involve clarification of the role of each co-founder: who’s the business one, who’s the technical one and who else does what. Prior to terms sheets, investors may request a more classic org-chart. They want a single point of contact — most commonly the CEO.</p><p>Now there is the founding team with titles like CEO, CTO, and COO. There’s money in the bank. The next stage of the company will be reached with more than just the co-founders on the team. First hires are typically technical. The product must go from prototype / v1 to something that would attract the masses and eventually the wallets. <strong>Engineer #1 </strong>is hired. Titles are still not important. It’s very clear what the CTO can’t do alone and the first engineer comes with the skillset needs to augment the CTO. Aspects of all engineering fall under the domain of this individual. Salary is fairly low regardless of experience level because that seed round can’t cover market rate. Equity is generous to compensate for the salary. <strong>Software Engineer</strong> covers the role very well.</p><p>The first engineer may have been recruited from within a close network, but for the next 3–10 the CTO will need to compete with other startups and well-financed tech companies. Creativity becomes the name of the game and diamonds in the rough the prize. Fresh college and coding academy grads are a solid choice. Yes, a lot of effort will go into finding the perfect candidates, but the budget can’t afford those looking to maximize their paycheck for their expertise. With some luck, there is a small pool of candidates passionate about the problem the company is solving, who prioritize that over high salaries. Between the grads and the passionate crowd, titles still don’t matter. Most are <strong>software engineers</strong>, perhaps an extra cherry on top for the more seasoned hires is a <strong>senior software engineer</strong> title.</p><p>A couple of years go by and the company is now a solid Series A/B-funded business. While tough, recruiting has gone well and the engineering team is now at 10–15. Most engineers are within the first 1–3 years of their career. There is a decent onboarding process to make sure the roughness is polished off the diamonds quickly and they start contributing to the engineering roadmap effectively. After 1–2 years, those same diamonds are able to do the full breadth of projects the company requires. Based on everything they read online describing the role of a senior software engineer, they fit the bill. The CTO is now sitting on a potential time bomb: a significant number of engineers on the team believe they deserve a promotion and the next title up is <strong>senior software engineer</strong>. There are plenty of companies who are willing to pay more and give fancier titles to get the polished diamonds to join.</p><p>Should the CTO promote several hires with 2–3 years experience to senior roles?</p><p>This problem is not new. It has been solved by many late-stage startups and large tech companies. The majority of the time this problem has been solved reactively. Defining a career ladder proactively is not a herculean task. While many companies will have their own nuances, an example of a basic career ladder is as follows:</p><h4>Level 1 — Intern I</h4><p>Intern with no prior software engineering internship experience.</p><h4>Level 2 — Intern II</h4><p>Intern with at least one relevant software engineering internship.</p><h4>Level 3 — Software Engineer I</h4><p>Someone who recently graduated with an undergraduate or Master’s degree. Takes 1–2 years to get to the next level.</p><h4>Level 4 — Software Engineer II</h4><p>Someone with 2–6 years of experience after graduation. Takes 2–5 years and to demonstrate impact on tasks of sufficient difficulty to get to the next level.</p><h4>Level 5 — Senior Software Engineer I</h4><p>Someone with 6–10 years experience, who is primarily autonomous and takes on tasks without excessive detail, while being able to figure out what to do and execute on it. Takes 2–3 years to get to the next level.</p><h4>Level 6 — Senior Software Engineer II</h4><p>Someone who in addition to L5 attributes can demonstrate leadership on projects. There is no concrete timeline to get to the next level.</p><h4>Level 7 — Staff Software Engineer</h4><p>Someone who demonstrates a track record of substantial contributions to complex and large projects. Proposals for quality solutions, planning, execution and delivery become key. Working closely with cross-functional partners to define the roadmap is common.</p><h4>Level 8 — Senior Staff Software Engineer</h4><p>Someone who drives technical strategy in large product areas. This role is rare at a company and is focussed on management and leadership.</p><h4>Level 9 — Principal Software Engineer</h4><p>Someone who is a peer to VP of Engineering and leads large initiatives across the organization, including areas outside their core expertise.</p><p><em>Anything above L9 is very company-specific.</em></p><p>Let’s apply the career ladder to the initial problem. The recent grads would move up from L3 to L4 after 1–2 years. Then after another 2–5 years to L5. The total 3–7 year runway gives time to truly master the skills needed at each level, while having a clear vision of where the career is going. Of course, if the diamonds are getting polished faster, there is no need to artificially throttle.</p><p>A career ladder may seem like overkill in the early stage companies. Yet, it is very straight forward to define and sets up the engineering organization and its members for long term success and understanding of their path.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ed7cf094e4a0" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Attributes of a great Product Manager from an engineer’s perspective]]></title>
            <link>https://artemkholodenko.medium.com/attributes-of-a-great-product-manager-from-an-engineers-perspective-787609c54c5b?source=rss-92fb9640317------2</link>
            <guid isPermaLink="false">https://medium.com/p/787609c54c5b</guid>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Artem Kholodenko]]></dc:creator>
            <pubDate>Thu, 12 Dec 2019 18:27:37 GMT</pubDate>
            <atom:updated>2019-12-13T04:47:36.692Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/600/0*ekk4y2HAXq4vLVgl.png" /></figure><p>No doubt the topic of what makes for a great professional in any role invokes heated debate, based on the experiences of the individuals involved. The following key attributes of a great product manager are based on my experience, dominantly in early-to-mid stage start-ups, from the perspective of an engineer.</p><h4>Vision</h4><p>Whether you’re taking on building an entirely new product or taking over an existing one, vision is a must. What is the longterm purpose of the product? What’s beyond v1? What’s beyond polish? If all goes well, what does the product look like in five years? If all doesn’t go well, what are the core pillars to continue in the direction of your vision? What unique position will the product assume to make it a market leader?</p><p>A great PM is able to articulate inspiring answers to all these questions.</p><h4>Conviction</h4><p>Having a great vision is important, but a PM is going to have a hard time getting engineers to believe in the vision if conviction is lacking. Do you believe in your vision? Why? Why should others? What are the trends and data points you’re seeing or generating that will make your vision a success?</p><p>Excellent communication skills are needed to convey the conviction. This is not about being the loudest in the room. It’s about making the strongest case to support the validity of the vision.</p><h4>Technical comprehension</h4><p>For a PM to be technical means having a certain depth of knowledge in software development and data analysis.</p><p><em>Software</em></p><p>Being technical on the topic of software allows for the ability to properly prioritize roadmaps and take feedback from engineers. Understanding why a seemingly simple feature is going to take weeks to implement and work with engineers to chisel out the best bang-for-the-buck alternative will earn the respect of the engineering team.</p><p><em>Data</em></p><p>Conviction needs to be supported by evidence. Whether it is historical trends, which foreshadow direction or user behavior that drives a roadmap, being able to dig in to analyze and understand data is key. A great PM is familiar with analytics/BI tools, has the ability to query a database, and the statistical background to understand the data to unlock the insights that lead to product success.</p><h4>Methodical</h4><p>Putting together specs, ironing out the nuances in designs, scheduling kick-off meetings, and more are all part of keeping the ball smoothly rolling in a product development lifecycle. Engineers often get frustrated with half-baked specs or designs that solve for the “happy case”. Staying sharp, with attention to detail, will draw much respect from an engineering team.</p><h4>Empathetic</h4><p>The role of a PM is at the center of an organization, bridging sales, business development, customer support, finance, design, engineering, data science, research, customers and more. The only way this ecosystem works well is through great working relationships. Great working relationships are built through the ability to understand and share the feelings of another — empathy.</p><p>No doubt there are many additional granular attributes that make for a great PM. Please share in the comments.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=787609c54c5b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Don’t copy culture fit — define your own.]]></title>
            <link>https://artemkholodenko.medium.com/dont-copy-culture-fit-define-your-own-8b4fe5c2cb25?source=rss-92fb9640317------2</link>
            <guid isPermaLink="false">https://medium.com/p/8b4fe5c2cb25</guid>
            <category><![CDATA[culture-fit]]></category>
            <category><![CDATA[hiring]]></category>
            <dc:creator><![CDATA[Artem Kholodenko]]></dc:creator>
            <pubDate>Sun, 24 Nov 2019 17:27:04 GMT</pubDate>
            <atom:updated>2019-11-24T17:27:04.935Z</atom:updated>
            <content:encoded><![CDATA[<h3>Don’t copy culture fit — define your own.</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/920/0*VfVkMvLhMjh7GVbn.png" /></figure><p>The phrase <em>culture fit</em> has become a common bookend in job posting descriptions over the last two decades.</p><p>At first it was a fluke. Growing companies gaining momentum would be hiring at a neck-breaking pace. This pace did not allow for the proper time to vet candidates, nor setup new hires for success in their new roles. Many never found their rhythm or burnt out, while some succeeded and thrived. Consequent waves of hiring at these companies aimed to find candidates similar to those who were able to fight the odds and flourish.</p><p>A wave of successful companies became the benchmark for the next wave of buddying entrepreneurs. They began to emulate the behaviors of previous successes, assuming that what worked for others, will work for them. This included the approach to hiring and filtering criteria for candidates, including the now coined <em>culture fit</em>.</p><p>The mistake is sifting through candidates, looking for those that would be successful based on the criteria of other companies. Take two examples of companies, both of which require hard-working and intelligent technologists: Facebook and SpaceX. At the very core of Facebook is the phrase “break things and move fast”. The only downside when FB is down due to a bug is ad revenue lost. SpaceX is moving faster than any space program in the history of humanity. Yet, with the potential of launching humans into space in 2020, the company needs a reputation of stability and reliability. It takes very different personalities and interests to succeed at Facebook vs. SpaceX.</p><p>Simon Sinek’s book <a href="https://www.amazon.com/gp/product/1591846447/ref=as_li_tl?ie=UTF8&amp;camp=1789&amp;creative=9325&amp;creativeASIN=1591846447&amp;linkCode=as2&amp;tag=adk06a-20&amp;linkId=1a6dd07b9b402348ac1621ba6116d2a7"><em>Start with Why</em></a> touches on culture fit from the perspective of having a common “why”. A successful company has a “why” (mission) to focus what it does and how it does it. Similarly each person has a “why”. A professional culture fit becomes a match between a company’s and an individual’s “why”. Avoid matching candidates to a different company’s “why”.</p><p>To hire the right people for an organization, it is critical to identify the attributes that will make a new hire a success at this organization. Turn the potential fluke into a sure bet.</p><p>The next step, after identifying the attributes that definite a good culture fit for a company (or a team, in a bigger organization), is to determine which of those attributes is defined by nature vs. nurture. Nature can’t be altered. It’s a constant and you will fail trying to change someone’s nature. Nurture is coachable. Both, <a href="https://www.amazon.com/gp/product/1591846404/ref=as_li_tl?ie=UTF8&amp;camp=1789&amp;creative=9325&amp;creativeASIN=1591846404&amp;linkCode=as2&amp;tag=adk06a-20&amp;linkId=9627f3a024d31946763f7debad76afca"><em>Turn this Ship Around!</em></a> by L. David Marquet and <a href="https://www.amazon.com/gp/product/1250183863/ref=as_li_tl?ie=UTF8&amp;tag=adk06a-20&amp;camp=1789&amp;creative=9325&amp;linkCode=as2&amp;creativeASIN=1250183863&amp;linkId=e41bdd011d39f214c56ef8b7564f741b"><em>Extreme Ownership</em></a> by Jocko Willink and Leif Babin, discuss altering team behavior through distribution of ownership and decision making.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8b4fe5c2cb25" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[End-to-end: How to publish a React component with typescript as an NPM package]]></title>
            <link>https://artemkholodenko.medium.com/end-to-end-how-to-publish-a-react-component-with-typescript-as-an-npm-package-d8883076bc18?source=rss-92fb9640317------2</link>
            <guid isPermaLink="false">https://medium.com/p/d8883076bc18</guid>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[typescript]]></category>
            <category><![CDATA[react]]></category>
            <category><![CDATA[npm]]></category>
            <dc:creator><![CDATA[Artem Kholodenko]]></dc:creator>
            <pubDate>Mon, 11 Nov 2019 22:03:43 GMT</pubDate>
            <atom:updated>2019-11-11T22:07:51.742Z</atom:updated>
            <content:encoded><![CDATA[<h3>End-to-end: How to publish a React component with TypeScript as an NPM package</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/880/0*QTe47eof0dQSEDFe.png" /></figure><p>I recently wanted to learn what it takes to publish a <a href="https://reactjs.org/">React</a> component, written in <a href="https://www.typescriptlang.org/">TypeScript</a>, as an <a href="https://www.npmjs.com/">NPM</a> package. I found a number of great tutorials covering different part of the work and workflow. Having needed to piece together several guides, I’m putting it all together in one place.</p><p>One of the most complete guides I came across (minus the TypeScript setup) was <a href="https://medium.com/recraftrelic/building-a-react-component-as-a-npm-module-18308d4ccde9"><strong>Building a React component as an NPM module</strong></a> by Manoj Singh Negi. This post covers setting up the module to be published and a sample app to use / test the module.</p><p>I then came across another great guide, which focused on development with TypeScript. A very clearly named post, <a href="https://www.pluralsight.com/guides/react-typescript-module-create"><strong>How to Create a Typescript and React Module</strong></a> by Eli Yukelzon. This post also covers Jest testing, a great bonus nugget.</p><p>At this point, I had the component I wanted to publish to NPM setup. I had a sample app using the component. Yet the workflow had many manual steps. I needed to build the package, then stop the sample app; run <strong>yarn</strong> in the sample app to get the latest version of the package; then <strong>yarn start</strong> to start the sample app.</p><p>To solve workflow efficiency problem, following a <a href="https://yarnpkg.com/lang/en/docs/cli/link/"><strong>guide on symlinking</strong></a>, I connected the module’s build output to the sample app’s package repository.</p><p>The last step was to use <a href="https://www.npmjs.com/package/watch"><strong>Watch</strong></a>, via a <a href="https://flaviocopes.com/package-json-watch/"><strong>guide on automatically running any command</strong></a> when files changes occur. With this enhancement, the workflow was complete. The future NPM package can be developed and automatically built and synced with the sample app. One challenge yet to overcome is the ~5 second delay between saving changes to the module to building to hot-reloading of the sample app.</p><p>The last step is to publish to NPM using <strong>npm publish</strong>, with detailed instructions in the first linked guide.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d8883076bc18" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to successfully estimate software projects]]></title>
            <link>https://artemkholodenko.medium.com/how-to-successfully-estimate-software-projects-3a2ead543ddb?source=rss-92fb9640317------2</link>
            <guid isPermaLink="false">https://medium.com/p/3a2ead543ddb</guid>
            <category><![CDATA[agile]]></category>
            <dc:creator><![CDATA[Artem Kholodenko]]></dc:creator>
            <pubDate>Tue, 05 Nov 2019 01:11:38 GMT</pubDate>
            <atom:updated>2019-11-05T01:11:38.163Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/620/0*ppMa0_OnesAVmbUF.jpg" /></figure><p>One of the most common mistakes, which derails the timely delivery of software engineering projects is the lack of thorough breakdowns and estimations of the implementation details.</p><p>In a junior world, engineers dive into implementation first, peeling away one layer at a time. Each layer presents its own challenges, which may have been minimized if all layers were understood ahead of implementation. Architectural decisions made in the first layer can lead to major refactoring a few layers into the project.</p><p>In a senior world, planning time is spent on system architecture and high-level design, with many of the implementation nuances assumed to be trivial. Those nuances are not always trivial and take significantly longer than an engineer initially expects.</p><p>A great approach, which I have seen successfully work for delivering many projects, within reasonable margin of chronological error, is to break down all the work into the smallest possible tasks: target having no task estimated to take longer than one hour; a task should also be no smaller than 15 minutes. If a task is estimated to take longer than one hour, it should be broken down into smaller sub-tasks. Estimating the time to complete each small task becomes significantly simpler and more precise. While the entire project may be new territory, chances are, the small tasks have been completed for previous projects.</p><p>Let’s go through an example of breaking down and estimating a basic user sign-up form. We will not worry about scalability or advanced security in this scenario.</p><p><strong>Product Requirements: </strong><em>build a sign-up form, which takes in a user’s first name, last name, email, and password, to create a user account and be logged into the application.</em></p><p>The most common approach to breaking this down is:</p><ul><li><strong>Front-end (1/2 day)</strong> … because how long does it really take to make a simple form that calls an API?</li><li><strong>Back-end (1/2 day)</strong> … because how long does it take to make a simple API that takes in user info and stores to the DB</li></ul><p>So the quick estimate for the project is 1 day.</p><p>What does a detailed breakdown look like?</p><p><strong>Front-end (9 hours)</strong></p><ul><li>routing for sign-up page (30 min)</li><li>generic template layout (1 hour)</li><li>first name form field (1 hour) <em>// with reusable styling for other fields</em></li><li>last name form field (15 min)</li><li>email form field (15 min)</li><li>password form field (15 min)</li><li>submit button (15 min)</li><li>client-side input validation: general logic (30 min)</li><li>client-side input validation: first name (15 min)</li><li>client-side input validation: last name (15 min)</li><li>client-side input validation: email (30 min)</li><li>client-side input validation: password (30 min)</li><li>integration with API (1 hour)</li><li>handle success case for API response (30 min) <em>// confirmation UI</em></li><li>handle failure case for API response (1 hour) <em>// identify errors and present to user</em></li><li>redirect user to logged-in dashboard (30 min)</li><li>QA time (30 min)</li></ul><p><strong>Back-end (8.5 hours)</strong></p><ul><li>DB migration to create users table (1 hour)</li><li>User model (1 hour)</li><li>routing for API url (30 min)</li><li>controller with stub action method (1 hour)</li><li>create user via model using API inputs (15 min)</li><li>server-side input validation: general logic (30 min)</li><li>server-side input validation: first name (15 min)</li><li>server-side input validation: last name (15 min)</li><li>server-side input validation: email (30 min)</li><li>server-side input validation: password (30 min)</li><li>create user session (1 hour)</li><li>successful response (15 min)</li><li>failed response (1 hour) <em>// simulating various test scenarios creating user takes time</em></li><li>QA time (30 min)</li></ul><p>The detailed breakdown adds up to 17.5 hours, which makes this roughly a 2-day project. Many of the listed items may take less than the estimated time, yet any one of them has the potential of taking significantly more.</p><p>In the real world, this estimate is in <em>engineering time</em>. This means it’s the time to actually do the work. Add to this distractions and context switches that come up during a typical day for an engineer and its safe to double <em>engineering time</em> to get the <em>calendar time</em> for a project. The project above will take four calendar days. Add to this the time needed to code-review, merge, and deploy. Now you’re looking at a week of time from breaking ground to getting the project into production — a big gap between the quick estimate of 1 day and the reality of 1 week.</p><p>If you don’t have the luxury of time, then the work needs to be parallelized and the context switching explicitly minimized. The above project can be worked on by two engineers in parallel (front-end and back-end). Though be careful — not all projects can be sped up by more resources. Two engineers can do two days of engineering work in one day. Eight engineers will not be able to do same work in two hours.</p><p>The user sign up project can be worked on by two engineers, be code-complete by end of the first day; integrate, QA, and iron out the issues by end of the second day; code review, merge in, and release by end of the third day.</p><p>The key takeaway is to think through all the details and nuances first. Estimating small tasks is significantly more precise than ball-parking a full project.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3a2ead543ddb" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[When to give candidates a deadline to accept an offer]]></title>
            <link>https://artemkholodenko.medium.com/when-to-give-candidates-a-deadline-to-accept-an-offer-8e0b36198748?source=rss-92fb9640317------2</link>
            <guid isPermaLink="false">https://medium.com/p/8e0b36198748</guid>
            <category><![CDATA[startup-lessons]]></category>
            <category><![CDATA[hiring]]></category>
            <category><![CDATA[recruiting]]></category>
            <dc:creator><![CDATA[Artem Kholodenko]]></dc:creator>
            <pubDate>Tue, 29 Oct 2019 18:34:51 GMT</pubDate>
            <atom:updated>2019-10-29T18:34:51.368Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/788/0*X968oHZtrcdaa5Sf.jpg" /></figure><p>When you’re hiring in an early stage startup, you’re looking to fill strategic roles. You’re not looking to build out a marketing team; you’re trying to hire the one marketing super star, who can take on the responsibility one of the founders has been handling until that point. You’re not looking to build out an engineering org; you’re looking for the one senior data engineer who can take the needed data work from amateur to pro level. Even when hiring for junior roles, it’s one or two at a time.</p><p>While extremely limited on open headcount, you’re still trying to go through as many candidates as possible because hiring for the roles is crucial to the success of the business. You may find yourself in a position where a successful wave of recruiting simultaneously lands a number of great candidates, at different stages of their interview process. One may be in final rounds with a number of companies, the second has more on-sites over the next couple of weeks, and the third just started looking.</p><p>The first to come in does great and you’re ready to give her an offer. You’ve been interviewing for the role for a couple of months and this is the best candidate you’ve seen. You don’t know if others will match this caliber and want to make sure the offer is accepted. You present the offer, everything goes well and the candidate asks for time to think about it. You’re a startup, you’re flexible, you tell her to take her time. She’s in final stages and promises to get you a response by end of the week.</p><p>In three days, a second candidate does great on the phone screen and has a fantastic on-site a week later. Some pros and cons over the first candidate, but overall, a solid alternative. The candidate has other on-sites yet to come, so you don’t feel the pressure. You follow up with an email, conveying how impressed everyone is and how great the on-site went, while asking for a few days to get back with next steps. You’re trying to buy time for the first candidate to respond.</p><p>The end of the week rolls around. You haven’t heard from the first candidate. You reach out, she responds with excitement, asking for a few more days to make the decision. You’re keeping the second candidate on hold, hoping you can have the needed information to extend an offer or decline.</p><p>As luck would have it, a third candidate, who had rescheduled the initial call a few times, does well on the phone screen and, to make sure you speak with all great candidates, is invited on-site. This is starting to get interesting. Three potential candidates. You’ve got the upper hand in these negotiations. Let’s start to put pressure on the first candidate — flexibility has outlived its welcome. You email the first candidate, now two weeks after the initial offer presentation, giving her two days to make a final decision. You schedule a call with the second candidate three days in the future. Even if you have to turn him down, you’ll give great feedback and convey how good they were — you’re doing great!</p><p>Two days goes by, you hop on the phone with the first candidate. She tells you how great everything was, how tough the decision is, and how she’s going to accept an offer with a company she found closer aligned with her passion. That’s okay. No problem. Now you can focus on the other two candidates. Next day, you’re on the call with the second candidate. You tell him the great news! In response, he tells you that he’s accepted an offer from a different company a couple of days ago, as he was waiting too long to hear back. He wanted to hop on the phone, to directly convey how good the interview experience was and how he enjoyed the process. Well… that’s not what you had in mind, but fine — last but not least, here we go.</p><p>The third candidate interviews just as well. You’re ready to give an offer, but you’re not going to make the same mistake again. You’re not getting strung along nor loosing a potential fourth candidate. You present your offer, give a reasonable one week deadline, and feel like you’ve really grown from the experience. A week later, the candidate accepts your offer and is starting in three weeks. #Winner.</p><p>Two weeks later the same candidate emails you, thanks you for the great experience and informs you that he has decided to go a different direction with his career, and thus will be joining a different company.</p><p>You’ve got none in the hand. You’ve got none in the bush. You’re just confused on what went wrong and how three great candidates slipped through your fingers. You’re tough and will keep pounding the pavement … but with what takeaway?</p><p>To sum up what happened:</p><ul><li>Candidate #1 was late in her process and was holding off on accepting your offer because she was already waiting for offers from other companies. She eventually got the details and decided one of the other offers / roles was better.</li><li>Candidate #2 was mid-process, and had some time to spare. You took too long, even with the available buffer. He accepted another offer due to low confidence that an offer was ever going to come from you.</li><li>Candidate #3 was earlier in the process, and your offer was the first. Because of your deadline, he accepted before hearing back from other companies. In the next couple of weeks a better offer came along, and he changed his mind, with little remorse, since you forced his hand in the first place.</li></ul><p>The timing with the first two candidates can be better mitigated, yet still not fully in your control. The third candidate scenario is a direct reaction to an offer deadline. More commonly, the candidate will turn down the time-pressured offer.</p><p>What could have been done differently? Here’s an alternative approach to the same timeline:</p><p><strong>Candidate #1 is presented with an offer</strong></p><p>After restating the uniqueness of the opportunity and summarizing the details, ask the candidate to provide expected timing for getting a response. If the timing is too far out (more than two weeks), work toward getting an earlier commitment. Regardless, be sincere and transparent: explain that you are interviewing other candidates for the role; underscore that the candidate is your top choice, yet you can not hold the position for her indefinitely. Schedule a follow up phone call during this conversation. The follow-up should be at the midway point between now and the date of expected response. As a reason for the check-in call, explain that it is to answer any potential questions that may come up.</p><p><strong>Candidate #2 does well on the phone screen</strong></p><p>It’s been half a week since candidate #1 received offer details. It’s another half a week until your check-in call with her. You schedule the on-site with candidate #2 a week into the future, knowing that by then you will have additional data points about the first and be a few days from her self-set response date.</p><p><strong>Check-in call with candidate #1</strong></p><p>It’s half a week after the successful screen with candidate #2. You’re trying to figure out what’s going through the first candidate’s mind. You ask if she has any questions. There may not be any questions of substance. You ask if she understands the offer details, discuss any bonus or equity details, work from home policy, etc. Then dive into practical questions:</p><ul><li>Does the candidate have concerns about the location?</li><li>Is the family excited about the opportunity?</li><li>Based on the reasons they are looking, does the opportunity match her goals?</li><li>How many companies are in the running and what the pros / cons are?</li></ul><p>Read the answers directly and between the lines. Pay attention to tone, pauses, and hesitations. Don’t press if the candidate doesn’t feel comfortable answering.</p><p><strong>Candidate #2 comes in for the on-site</strong></p><p>The second candidate comes in and does a great job. You’ve spoken with candidate #1 half a week ago and have a good understanding of where she is in her process: final stretch, but deeply analyzing her options. In another half a week you will have an answer. You can reasonably ask candidate #2 to give you 3–4 days to get back to him. You ask one of the interviewers from the on-site to send a follow-up email in two days, with a brief note about how much that interviewer enjoyed the conversation the two had. This creates a check-in point and keeps the candidate engaged.</p><p><strong>Candidate #3 does well on phone screen</strong></p><p>It’s the day after candidate #2 was on-site. You schedule candidate #3 for an on-site a week into the future. You have a call in two days with candidate #1 to get a final response. Then you will either stop the process with candidate #2 and #3 or make an offer to candidate #2. The timing works well, with another 1-week check-in call and 2-week response call.</p><p><strong>Response call with candidate #1</strong></p><p>The candidate asks for more time. You reiterate everyone’s excitement about her joining the team. You then summarize the fact that she had two weeks already, you agreed on a timeline, and as you mentioned there are other candidates you are holding off on. You ask again if there are any questions and what is causing the hesitation. This is where the candidate will most likely bring up wanting to have all her options in front of them to make a decision, while not having yet had heard back from some of the other companies. You convey that you completely understand, yet you cannot hold the position for more than another 24 hours and ask the candidate to email you the decision by same time tomorrow. The email option is good because the candidate will not be sleeping much that night. If she decides then, it’s an opportunity to email you any time, unlike a scheduled call.</p><p><strong>Candidate #1 declines the offer</strong></p><p>It’s almost end of the next day. You keep staring at your inbox. Finally, an email from candidate #1 pops up. It’s a no go. You ask for feedback about your interview process: what went well, what could have been done differently, and overall aim to understand the deciding factor.</p><p><strong>Candidate #2 is presented with an offer</strong></p><p>It’s been four days since candidate #2 was at the on-site. It’s been two days since one of your team members checked in with him. He’s excited and engaged. You send an email, conveying you have great news and ask for the next available time for a quick call. The candidate is free that evening. You go through the same playbook: offer details, agree on response timeline, schedule a mid-way check-in call.</p><p><strong>Candidate #3 comes in for the on-site</strong></p><p>It’s been half a week since candidate #2 received his offer details. Half a week until the check-in call. The on-site with candidate #3 goes well. You follow the same playbook: 3–4 day buffer, with a post-2-day interviewer check-in.</p><p><strong>Check-in call with candidate #2</strong></p><p>Same playbook: what new questions does the candidate have? Looks like you’re toward the top of the list. He’s since had more on-sites and is leaning toward accepting your offer. The candidate negotiates the offer details. You convey that you can definitely have that conversation, but if you were able to get him the numbers he wants, is he ready to accept the offer? The candidate confirms. You schedule a follow up call toward the end of the next day.</p><p>You may have already had a budget to play with or needed to get approval, either way, the ask is reasonable and you’re able to meet the request. You get on the call with the candidate and share the good news. He’s in! The candidate verbally accepts the offer and you agree on a start date. You send a formal offer letter, which the candidate signs by the next day.</p><p><strong>Declining candidate #3</strong></p><p>It’s been five days since the third candidate was on-site. Three days since an interviewer has check-in with him. Not ideal. You send an email, explaining that while the candidate did well on the interview, a candidate who was earlier in the process has accepted an offer and the role is now filled. You offer to get on a call, if the candidate is interested in receiving feedback. You put in great effort into getting useful and constructive feedback to a candidate, who’s already doing well. Most companies don’t give feedback and most of those that do, give fluffy responses about alignment / fit, which a candidate can’t use to improve. This is a great opportunity to stand out. The world is a small place. You’ll probably be hiring again at some point and this will make you stand out among all the competition.</p><h3>Takeaways</h3><p><strong>Don’t pressure, but control the timeline.</strong></p><ul><li>get the candidate to propose the response timeline</li><li>set a mid-point check-in</li><li>hold the candidate accountable for getting a response within agreed upon timeline</li></ul><p><strong>Create a sense of care and empathy.</strong></p><ul><li>understand and address the decision points for the candidate</li><li>touch on tangible topics impacting the decision (family opinion, location, offer details)</li></ul><p><strong>Every candidate deserves an awesome experience.</strong></p><ul><li>keep in touch at well paced intervals</li><li>be transparent with the candidate</li><li>provide feedback</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8e0b36198748" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>