The limitations of traditional online coding tests in assessing real-world skills.
The importance of pair programming in evaluating candidate fit and communication skills.
The impact of interview processes on company reputation and candidate experience.
Strategies for implementing realistic pair programming sessions during interviews.
Cost considerations in traditional versus modern interview approaches.
Hiring the right talent is crucial for the growth and success of any tech company. The process, however, is fraught with challenges, especially when relying on traditional methods like online coding tests. These tests, often found on platforms such as LeetCode and HackerRank, primarily assess a candidate's ability to solve algorithmic problems under time pressure. While these are valuable skills, they are not the sole indicators of a candidate's potential and fit for a team.
Online coding tests typically focus on a narrow set of skills, primarily algorithms and data structures. Candidates are often asked to solve problems like reversing a linked list or traversing a binary search tree, which are not common tasks in a typical software development role. This creates an imbalance, as these tests do not adequately reflect the day-to-day challenges and skills required in the industry.
Moreover, these tests can be stressful and do not allow candidates to showcase their true potential. They often lead to false positives, where candidates who are good at these tests but not necessarily at real-world problem-solving are hired, or false negatives, where potentially great candidates are overlooked.
Company reputation can also suffer due to these traditional interview processes. Candidates often share their experiences with peers, and a cumbersome or unenjoyable process can deter top talent from applying. It's crucial for companies to be perceived as having fair and enjoyable hiring processes, which can simultaneously serve as a networking opportunity.
To address these issues, pair programming has emerged as a more effective way to assess candidates. This approach involves working on a real-world problem together, using a collaborative coding environment. It's not about scribbling on a whiteboard under intense scrutiny but engaging with a practical task in a way that mirrors actual work scenarios.
Pair programming allows both the interviewer and candidate to interact naturally, providing insights into the candidate's communication skills, problem-solving approach, and fit with the team. It offers a realistic glimpse into the candidate's day-to-day work environment, which is invaluable for both parties.
During a pair programming session, the candidate is evaluated on their ability to understand the problem, articulate their thought process, and respond to feedback. This approach reveals much more about a candidate than a traditional coding test, as it reflects their ability to collaborate, adapt, and think critically.
Implementing pair programming requires thoughtful preparation. The problem should be realistic and relatable, something that the candidate might encounter in their actual work. Using a real coding environment, such as CodeSandbox or VS Code's LiveShare extension, ensures that the assessment is as close to real work as possible.
It's also essential to consider the cost implications of the interview process. While traditional tests may seem cost-effective initially, they can lead to costly rehiring processes if the wrong candidate is selected. Pair programming, though potentially more time-consuming upfront, can lead to better hiring decisions and long-term savings.
Adjusting the pair programming approach based on the candidate's experience level is also beneficial. For junior candidates, the focus might be on communication and willingness to learn, while for senior candidates, it could be on leadership and the ability to mentor others.
Incorporating additional stages, like architectural design interviews for higher-level candidates, can further enhance the process. This ensures a comprehensive evaluation of a candidate's abilities, from technical skills to leadership potential.
By shifting from traditional coding tests to pair programming, companies can improve their hiring processes, reduce costs, and enhance their reputation. This approach not only evaluates the candidate more holistically but also ensures that the interview experience is mutually beneficial and enjoyable.
We’ve all experienced the job application which required us to do an online coding test. You have to brush up on your algorithms, data structures, time complexity, and by the end of it you’re cramming as if it was a university exam! Now that we’re the ones usually interviewing candidates, a good question to ask is: “are online coding tests the best indicator of a candidate’s proficiency and competence?” In this talk, we’ll explore:
- The pitfalls of Leetcode-like tests
- What we should be looking for in candidates
- How pair programming is the best way to see how a candidate would work with the team
- Plus a little mini demo on a remote pair programming interview
This talk has been presented at TechLead Conference 2023, check out the latest edition of this Tech Conference.
The talk focuses on the issues with traditional online coding tests, the inefficacy of platforms like LeetCode, and the benefits of integrating pair programming interviews into the hiring process to enhance the selection of candidates.
Muhammad believes that pair programming interviews offer a more realistic assessment of a candidate's coding skills and teamwork capabilities, as they simulate actual work environments and problem-solving situations, which leads to better hiring decisions.
Traditional online coding tests are criticized for focusing too narrowly on a candidate's ability to solve algorithmic and data structure problems under time pressure, which may not accurately reflect the skills needed for day-to-day software development.
Theodo, where Muhammad works, incorporates pair programming interviews that involve realistic coding tasks and environments to better assess the practical and collaborative skills of candidates.
Muhammad's decision to join Theodo was significantly influenced by his positive experience during a pair programming interview, which he found enjoyable and representative of the actual work environment at Theodo.
Theodo looks for candidates who can write maintainable and understandable code, solve problems effectively, and work well within a team, emphasizing practical skills over just theoretical knowledge.
Muhammad recommends using tools like CodeSandbox or Visual Studio Code's LiveShare extension, which allow for real-time collaborative coding in a realistic environment that mimics daily work settings.
A tennis scoring kata is a coding exercise used during interviews to simulate real-world programming tasks. It involves implementing the scoring logic for a tennis game, serving to evaluate a candidate's coding and problem-solving skills in a practical scenario.
The Talk discusses the problems with online coding tests and the benefits of pair programming interviews. It emphasizes the importance of hiring and growth, including creating a positive interview experience and considering the cost of hiring. The job of a software developer extends beyond coding and requires multiple skill sets. Pair programming provides a more accurate assessment of skills required for software development. The Talk also covers implementing a tennis scoring system and customizing pair programming interviews for different roles and levels.
Hello everyone. Today, we'll discuss the problems with online coding tests, the benefits of pair programming interviews, and the importance of hiring and growth. We'll also explore the ideal candidate traits and the mismatch between online coding platforms and required skills. I'll share my personal experience with pair programming interviews and their impact on my career. Let's dive in.
2. Importance of Hiring and Growth
Having an effective hiring system is crucial for hiring the right candidates and avoiding false negatives. The hiring process can impact a company's reputation, so it's important to create an enjoyable and positive experience for applicants. Additionally, the cost of hiring, including the pay for candidates and the time spent by interviewers, should be taken into consideration. When looking for candidates, it's important to focus on their ability to write maintainable and understandable code, as code is read more often than it's written.
3. Job of a Software Developer
The job of a software developer is multifaceted and goes beyond just coding. They need to identify and break down problems, design efficient solutions, work in cross-functional teams, and be pragmatic in their approach. For higher-level positions, coaching, managerial skills, and the ability to maintain code quality across projects are important. Hiring a candidate requires considering multiple skill sets.
4. Online Coding Tests and Pair Programming
Online coding tests primarily assess a candidate's knowledge of algorithms and data structures. They follow similar patterns and require familiarity with classic computer science concepts. These tests also evaluate the ability to implement solutions quickly under pressure. However, they may not effectively assess skills required for day-to-day software development. Pair programming, on the other hand, involves realistic problems and coding environments, providing a more accurate assessment.
5. Realistic Coding Environment and Demo
Encapsulate logic and knowledge in a relatable problem for testing candidates. Use a realistic coding environment, like CodeSandbox or VS Code's LiveShare extension, to simulate day-to-day coding. In a pair programming interview, focus on collaboration and problem-solving. Provide candidates with a demo of working within your team. Use real-world problems from GitHub repos for testing in interviews.
6. Implementing Tennis Scoring System
We'll be implementing the scoring system for tennis, focusing on the bare logic without UI or data validation. During the interview, observe the candidate's problem-solving approach, their interaction with you, their receptiveness to feedback, and their preference for simple solutions. We have a live share environment set up and will follow the TDD programming style. Let's move on to the next test for handling a win.
7. Representing a Win in Code
To represent a win in code, we can either use a value above the highest score or have some sort of state in the class. Using a flag would require checks in multiple places and if-statements to prevent score incrementing. Although using a fake value deviates from the actual logic, it provides a quicker solution for this test.
8. Refactoring the Score Function
Let's choose a value over 40, like 60. If both players have a score of 60, return Player1Wins. Otherwise, check if the second player has won and return Player2Wins. We've reached the refactoring stage. Inside the score function, let's refactor the code that calculates the index of the next score. Let's name it 'getNextScoreIndex' and pass in the score. While Sadiq works on that, it's a good sign that he's comfortable asking for suggestions.
9. Final Thoughts and Wrap-up
Sadiq's comfort in asking for help is a good sign. We refactored the code and made it more efficient. Our tests are passing, and we're in a good state. The tennis problem is interesting, especially with deuces and advantages. Thank you, Sadiq, for your time. Let me share some final thoughts.
10. Creating a Positive Interview Experience
Don't jump straight into the exercise. Take time to get to know the candidate and create a better environment for the interview. Review the solution together and encourage the candidate to critique their own work. Ask for feedback to improve the process. A positive experience can make the interview worthwhile.
QnA
Coding Tests and Pair Programming
Most people have abandoned coding tests, but they still play a substantial role in the hiring process. The cost of interviews should be considered, especially in consultancy backgrounds. The coding exercise mentioned in the talk is called tennis scoring kata. Pair programming is effective for assessing communication skills and the ability to pick up concepts. For higher-level positions, the candidate's ability to explain topics and fit into a leadership role is important.
Customizing Pair Programming Interview
You can customize the pair programming interview to fit different roles and levels. It's important to assess architectural choices and integration skills. Consider asking candidates about handling complex problems before starting the interview. Tweak the process to make it specific to each role and team. Adapt to the changing tech scene to find the perfect fit for candidates.
This Talk explores the concepts of impact and growth in software engineering. It emphasizes the importance of finding ways to make the impossible possible and the role of mastery in expanding one's sphere of impact. The Talk also highlights the significance of understanding business problems and fostering a culture of collaboration and innovation. Effective communication, accountability, and decision-making are essential skills for engineers, and setting goals and finding sponsors can help drive career growth. Feedback, goal setting, and stepping outside of comfort zones are crucial for personal development and growth. Taking responsibility for one's own growth and finding opportunities for impact are key themes discussed in the Talk.
The role of a Tech Lead involves shaping the roadmap, helping the team be more effective, and working on important projects. Lessons learned include encouraging idea sharing, avoiding taking on all the work, and focusing on delegation. Tech Leads focus on the outcome, involve the team in decision-making, and make plans based on how different pieces will interact. The role of a Tech Lead is to focus on engineering and guide the team in figuring out how the whole system should fit together. Architecting can become problematic when it loses touch with the coding part, resulting in implementation issues.
Software engineer, lecturer, podcast host, author — is there something Emma Bostian hasn't done? She moved from America to Sweden, started working at Spotify, and took up a few challenges along the way. And now she has some career tips to share. What led you to software engineering? I was raised in the ecosphere of tech because my dad is a software engineer at IBM, and my mom was a designer there, too. My dad always encouraged me to join STEM and take a look at computer science — however, I was convinced I wanted to be a medical doctor. In my first year of college, I declared a biology major and quickly realized I was not too fond of it. In my second semester, I switched to an actuarial science major where I took Introduction to Computer Science, and the rest is history. In my second year of college, I declared a computer science major and began my journey from there. What is the most impactful thing you ever did to boost your career?Writing blog posts and documenting my learning journey on Twitter has far been the best career boost. I wrote purely for myself to reference the things I learned over time, and I even utilized my design skills in Figma to create custom graphics depicting difficult concepts like CSS specificity. By sharing my blogs on Twitter and engaging with the people reading them, I was able to grow an audience extremely quickly. I began receiving conference speaking opportunities, podcast requests, and course invitations to teach with LinkedIn Learning and Frontend Masters. Ultimately, I landed my job at Spotify through Twitter, too, when a friend and follower of mine asked if I would be interested in interviewing. Now I live in Stockholm working my dream job. It still blows my mind how tweeting about my blog led me to some of the most amazing career opportunities. What would be your three tips for engineers to level up their career? First, be patient. I often see posts on Twitter or LinkedIn about developers who were promoted to a senior position after a year. And while this is wonderful, I think we forget that each company has a different standard for what constitutes a senior developer, and everyone's journey will be different. Second, don't be afraid to ask questions. If you try your best to solve a problem or answer a question you have, but you can't figure it out after a reasonable amount of time, ask a team member or mentor for help. And lastly, invest in the right resources for learning. When I started my journey, I didn't know which platforms worked for me to learn. Now, I have a few trusted platforms such as Frontend Masters, Free Code Camp, or Level Up Tutorials that I go to when I need to learn a new skill. You're currently working as a software engineer at Spotify. What does a typical day of yours look like there?I begin my day answering emails. Then we have a team breakfast and a standup remotely as we're all still remote at Spotify. After that, we might have a web tech sync with the other squads in our business unit. The day usually includes some form of pair or mob programming, depending on the work stream. My team always has Fika, a traditional Swedish coffee break, scheduled every afternoon. Every couple of Fridays, we have team games planned to release some stress. Also, I tend to have a lot of free time to focus, which is nice but makes for a boring answer to this question! Do you have some rituals or tools that keep you focused and goal-oriented?I'll admit that I've been struggling with staying motivated in the time of remote work. I've been remote with Spotify since onboarding a year ago, but my team is wonderful, and they help me when I'm down. Apart from that, I use Todoist to keep track of my tasks, and, naturally, I listen to Spotify while working. But other than that, not really. Maybe I should adopt some new tools to keep me on track! My current favorite Spotify playlist is Brand New Chill: https://open.spotify.com/playlist/37i9dQZF1DX6uQnoHESB3u?si=380263b3c853442e I also love Chillout Daily: https://open.spotify.com/playlist/7ozIozDp260fjNOZy1yzRG?si=66d6c839ec9b458a You wrote a book called De-coding the Technical Interview. What was the impulse to do it?I wanted to give the community a manual of the essentials of computer science knowledge to ace the technical interviews. The book covers data structures like stacks, queues, or linked lists, tackles algorithms, and deals with systems design. You'll also learn about the interview process from start to finish, get tips on how to submit an amazing take-home project, or understand how to problem solve. You'll also gain knowledge on the frontend coding skills needed to excel at a frontend interview. If you could stress one piece of advice on surviving a technical interview, which would it be?Do not lie your way through an interview. If you don't know the answer to something, just admit it. There's no shame in admitting you don't know the answer to something. There is shame in faking it and pretending like you do know the answer. What's the single best practice everyone who writes code should follow?Remember that while you are technically writing code for computers, you're also writing it for humans. Your code should be readable and have as little complexity as possible without sacrificing accessibility or performance. In addition to the book, you co-host the Ladybug Podcast. What inspired you to enter this field, and what are the podcast's main topics?We talk about everything tech and career on the podcast, from Java and GraphQL to how to start a business and cross-cultural communication. The podcast is a way for me and my co-hosts to share our experiences in tech, having taken different paths. And I'm really glad for doing it — it has allowed me to meet so many incredible people, learn many new things, and support my dream of teaching. What pieces of your work are you most proud of?My technical interview book was a huge feat for me as well as my courses with LinkedIn Learning on building a tech resume. I enjoy creating things that help other people advance their careers, so I'm also proud of my courses with Frontend Masters on design systems and CSS.
Even though his bio offers quite a hefty reading, he only applied for one job in his career. The rest came along as he was building his name as a renowned speaker, teacher, and a prolific figure of the open-source community. How did Kent do it? “Commit to creating high-quality content,” he says. What led you to programming?I had a friend when I was a teenager who was really into it, and he tried to teach me. But I just couldn't get it — it didn't make any sense to me. So I never really thought I'd get into programming, but I liked computers a lot, and I ended up going to school for electrical engineering. Well, that didn't work because I'm not good at math. But right when I started the program, I got a job at a company uploading videos to YouTube and that sort of thing. The work was tedious, so I decided to write a computer program to automate lots of the work I was doing with the knowledge I had about programming. And that was the first spark of things for me to use programming to solve real-world problems. What is the most impactful thing you ever did to boost your career? Committing to creating high-quality content. That might sound obvious because I'm a full-time educator now, but I would not have gotten my job at PayPal if I hadn't been so active with my blog. In fact, lots of my jobs came out of me being involved in the community around meetups, conferences, or open-source projects. How do you choose topics for the content you create, be it for your blog or podcast?I don't think too much about the content other people are creating. And I don't often consume it. My ideas come from the things that I'm working on, things that I'm learning myself, or — when I was working with a team of developers — the things that I had to remind people of in code reviews regularly. Anytime that I would have a code review comment that was pretty long to describe my position, that was an excellent opportunity for a blog post. Also, if people ask me about a topic regularly, I'll make a blog post rather than answer that question multiple times. What would be your three tips for engineers to level up their career? The number one thing I tell people is to be a nice person. I know that sounds fluffy or silly, but it cannot be overstated. You will get so much further in your career and just in life in general if you're a nice person. That doesn't mean that you take people being jerks lying down, but how you interact with others is out of kindness. You could be the best engineer in the entire world, but if you're not a nice person, you will not reach your full potential or accomplish your goals, whatever they may be. Second, it's just as important to decide what you are not going to learn as it is to decide what you are going to learn. You could jump into countless things — and there are successful people who are polyglot programmers, but I can't speak to that a whole lot. All I can tell you is that in my experience, focusing on specific things that I want to be truly good at has worked out great for my career. That doesn't mean that I closed myself off to other things. With my website rewrite, I have been doing a lot of dev ops-related work and a lot of back-end stuff that I've typically not been involved in. You want to keep your head up on what's going on outside of what you're doing so that you know what direction to go in when you come across problems you need to solve. However, finding a focus on what you want to be good at has helped me a lot. That way, you feel a little less stressed. And the third one? Learn how to learn effectively. It's a three-step process: you consume, build, and teach. The consumption of newsletters and Twitter and whatever inspires you, but you don't want to spend too much time doing that — implementing it into actually building something matters. This happens naturally if you work at a company, but maybe you're not making the things you want to learn, so you may want to start a side project. The building phase is where you get experience, but you also want to solidify that experience. How? You start teaching. You don't necessarily have to teach it to people, it could be stuffed animals. The goal of the teaching is to retain in your mind what you've learned through the building process. What are you working on right now? The big thing I'm working on right now is a rewrite of my website. It'll be much more than just a developer portfolio — I'll have user accounts, and there'll be fun things that you can do with it. And because it's more than just a website, I'm using Remix, a new cool framework in the React ecosystem. I'm also working on updating my material on TestingJavaScript.com and a TypeScript course as well. So, whatever I'm working on, it ends up resulting in lots of opportunities for content. Do you have some rituals that keep you focused and goal-oriented? I have a notepad where I keep all of my notes of what I'm going to do for the day so that when I'm checking things off, I'm not distracted notifications. I've tried apps for that, and that does not work well for me. I also am a firm believer in inbox zero. I have my work inbox and my personal inbox, and I keep them both at zero. And I kind of use that as a to-do list. And if I'm not feeling excited about working for some reason, I will often hop on my Onewheel, which is an electric skateboard that only has one giant wheel in the middle. It's just a total blast, and I'll hop on that with my backpack and a charger, and I'll go to a Starbucks or a park just to declutter my mind. What things in the React universe are you excited about right now?React version 18 is coming out soon. The experimental version is out there, and it's fun to play with. I'm just really thrilled that it's no longer a concurrent mode but concurrent features that you can opt into. Cool things like that will enable React server components in the future. But the biggest thing I'm excited about is Remix. That's huge. It eliminates a lot of problems that are solved well other tools, but when I'm using Remix, I don't have those problems, so I don't need those clusters. You already said that teaching is an integral part of the learning process, and you stand your word since you're also a full-time educator. What inspired you to enter this field?I have been a teacher for as long as I can remember. I grew up in a church where you talk in front of your peers from a very young age, and my mom was an elementary school teacher, so teaching has just always been a part of me. I really just enjoy sharing what I'm learning with others. As far as teaching technical topics, I gave my first workshop when I was still a student at Brigham Young University. With my fellow, we taught how to use AngularJS, and I got Firebase to sponsor pizza so they would show up, and that was pretty fun. Then I started teaching on the side at egghead.io right after I'd graduated. That was when I first got a paycheck for teaching. And I realized that teaching could be quite lucrative and support my family and me as a full-time endeavor. So I did it — I quit my job. I'm a very risk-averse person, so I'd done teaching as a side hustle for four years just to verify that I could make this work. When TestingJavaScript was released, and I got that paycheck, I realized that I didn't need my PayPal salary anymore. I could just focus my daytime on teaching and give my evenings back to my family, which was a nice trait. Apart from that, how has teaching impacted your career? Earlier I mentioned that pretty much all of my jobs came because I was perceived as an expert. After the first job, where I was an intern and then converted into full-time, I never applied to another. I worked for four different companies, and they wouldn't have recruited me if they didn't know who I was and what I was doing. My content is how they knew who I was — I just made it easy for them to find me. Teaching made that impact. It made my career. We talked about React and Remix. Are there any other open-source projects that you'd recommend keeping an eye on or contributing to?I have some myself. React Testing Library is probably the biggest one that people are familiar with. And if React isn't your jam, then other framework versions of the testing library. React Query is also really popular. If you're using Remix, you don't need it, but if you're not, I strongly advise using React Query cause it's a stellar, fantastic library, and Tanner Linsley, the creator, is a stellar and fantastic person. What pieces of your work are you most proud of? Probably the biggest thing I've ever done is EpicReact.Dev. It has helped tens of thousands of people get really good at React, improve their careers and make the world a better place with the skills that they develop. My whole mission is to make the world a better place through quality software, and I feel like I've done that best with Epic React. There are things that I've built at other companies that are still in use, and I'm proud of those cause they've stood the test of time, at least these last few years. But of everything, I think Epic React has made the biggest impact.
Today's Talk covers the four building blocks of communication: people, message, context, and effective listening. It emphasizes the importance of considering the perspective of others and tailoring messages to the recipient. The Talk discusses different types and channels of communication, and the need to align them with the intended message. It also highlights the significance of soft skills in communication and provides techniques for effective communication and assessing soft skills in tech interviews. Cross-cultural communication and the impact of bluntness are explored as well.
Code will be imperfect and perishable, so testing and debugging are crucial. Building relationships and being generous with code reviews are important for teams. Code ownership should belong to the team, not individuals. Prioritizing functionality over consistency can lead to more efficient development. Growing into a tech lead role requires building relationships and coaching skills.
Transitioning from an individual contributor role to a leadership position, especially in the fast-paced tech industry, is hugely challenging. Most new leaders don't receive any training at all in the first 10 years of their new responsibilities.Our comprehensive workshop is designed to assist new and emerging tech leaders in understanding their new roles and gaining the skills to make them confident, happy and effective leaders.
A Developer’s Guide to Communicating, Convincing, and Collaborating Effectively With Stakeholders It’s a tale as old as time - collaboration between developers and business stakeholders has long been a challenge, with a lack of clear communication often leaving both sides frustrated. The best developers can deeply understand their business counterparts’ needs, effectively communicate technical strategy without losing the non-technical crowd, and convince the business to make the right decisions. Working at a consultancy, I’ve both failed and succeeded in architecting and “selling” technical visions, learning many lessons along the way.Whether you work at a product company, are a consultant/freelancer, or want to venture beyond just being a developer, the ability to convince and clearly communicate with stakeholders can set you apart in the tech industry. This becomes even more important with the rise of GenAI and the increasingly competitive developer market, as problem-solving and effective communication are key to positioning yourself.In this workshop, I’ll share real-world examples, both good and bad, and guide you through putting the theory into practice through dojos.
Ready to kickstart your freelance career or just getting started on your freelance journey? You’re in the right spot. Learn from the world’s largest fully distributed workforce in the world. The independent talent movement is the future of work. If you’re considering leaving full-time employment for a career as a freelancer, now is the time to find your successful space in the independent talent workforce. More people are working freelance today than ever before, with the freelance marketplace now contributing $1.2 trillion to the US economy. Some of the most in-demand roles for freelancers right now are senior developers with professional experience in React, Python, Blockchain, QA, and Node.js. This workshop will help you design a sustainable and profitable full-time (or part-time) freelancing/contracting career. We will give you tools, tips, best practices, and help you avoid common pitfalls. At the end of the workshop there will be a Q&A session with a Freelance Developer who can answer your questions and provide insights and tips into their own success. During the Workshop break, we will be running a speed-coding challenge! At the end of the workshop, we will award a prize for the winner and display the leaderboard. We will have you login to our portal and complete the challenge as fast as you can to earn points. Points are assigned based on difficulty and the speed at which you solve the tasks. In case you complete all tasks, you get extra points for the remaining time. You’ll see your score, ranking, and the leaderboard once you complete the challenge. We will be giving away three Amazon Gift Cards ($200, $100, $75) for the top three winners.
Would you like to pursue your passions and have more control over your career? Would you like schedule and location flexibility and project variety? Would you like the stability of working full-time and getting paid consistently? Thousands of companies have embraced remote work and realize that they have access to a global talent pool. This is advantageous for anyone who has considered or is currently considering freelance work.>> Submit your interest on becoming a freelance engineer with Toptal and get a call with Talent Acquisition specialist <<
Freelancing is no longer an unstable career choice.
This workshop will help you design a sustainable and profitable full-time (or part-time) freelancing career. We will give you tools, tips, best practices, and help you avoid common pitfalls. Table of contents
Module 1: Dispelling common myths about freelancing Module 2: What does freelancing look like in 2021 and beyond Module 3: Freelancing choices and what to look for (and what to avoid) Module 4: Benefits of freelancing from a freelancer + case study BREAK Module 6: How to get started freelancing (experience, resume, preparation) Module 7: Common paths to full-time freelancing Module 8: Essentials: setting your rate and getting work Module 9: Next steps: networking with peers, upskilling, changing the world Module 10: Freelancer AMA
Renaud Bressant (Head of Product), Nathanael Lamellière (Head of Customer Success and Solution Engineer), Nouha Chhih (Developer Experience Manager) will be looking at the different developer jobs that you can accounter when looking for your next developer role. We'll be explaining the specifics of each role, to help you identify which one could be your next move. We'll also be sharing tips to help you navigate the recruitment process, based on the different roles we interviewed for as recruiters, but also as candidates. This will be more of an Ask Us Anything session, so don't hesitate to share your thoughts and questions during the session.
Onboarding to a new project can be difficult, no matter your background and experience. But it can be especially challenging for new developers straight out of school or a coding bootcamp. Drawing on personal experience as a bootcamp grad and JavaScript consultant, this talk will discuss tips and strategies for managers to help the new developers on their teams get their bearings in an unfamiliar codebase, so they can make more of an impact, faster!
Comments