Where #TechIsHiring this week! - The TechIsHiring Newsletter

#TechIsHiring has released a Job Search Resources app!

Wed, 31 Jul 2024 17:01:10 GMT

🚨 TechIsHiring now has a job search resource app! 🚨

https://job-search-resources.techishiring.com

Screenshot of TechIsHiring Job Search Resources app

Released a small app with a list of job search resources to empower your next job search! Review a curated list of resources from communities to people that will help you find your next great role!

Have a resource that you think will add value? Submit it to the resource list for review!

Both the app and the data that powers the app are open source so feel free to contribute to both!

App Repo: https://github.com/TechIsHiring/job-hunt-resources

Data Repo: https://github.com/TechIsHiring/job-search-resource-data

Please support TechIsHiring!

Share our newsletter with anyone looking for candidates or those looking for roles. Additionally, please follow @TechIsHiring on Twitter and tweet with the hashtag #TechIsHiring if you have job opportunities or are looking for opportunities yourself and you may be featured in this newsletter!

If you have any feedback, feel free to send a message to @TechIsHiring or @Chad_R_Stewart on Twitter, email us at techishiring@gmail.com.

#TechIsHiring now has a Discord Server!

Thu, 16 May 2024 17:01:46 GMT

🚨 We now has a Discord Server! 🚨

TechIsHiring now has a Discord Server to support job seekers! Feel free to come in to ask questions, seek resume reviews and hang out with other job seekers and help each other in their job search!

Check out the Discord link here:

Discord Invite Image

Discord Invite Link

Please support TechIsHiring!

If you have any feedback, feel free to send a message to @TechIsHiring or @Chad_R_Stewart on Twitter, email us at techishiring@gmail.com.

How Do You Become a Developer Advocate? by Rizèl Scarlett - How #TechIsHiring this week!

Rizèl Scarlett 🇦🇬🇬🇾 — Wed, 20 Sep 2023 14:00:57 GMT

Hello Everyone!

This special edition of the TechIsHiring newsletter features Rizèl Scarlett, Staff Developer Advocate at TBD.

We’d like to thank Rizèl for allowing us to send this article out to our readers!

Get updated on the hashtag by visiting TechIsHiring.com. If you'd like to contribute directly to TechIsHiring's operation, please support us through Patreon!

How Do You Become a Developer Advocate?

Ever since I posted this tweet, friends, acquaintances, and random strangers have reached out to me asking some version of the same question: "How do I become a developer advocate?"

Unfortunately, although I'd love to answer everyone, I don't have the time. Instead of answering everyone individually, I decided to write a detailed breakdown of how I became a developer advocate.

To be clear, people take many different routes into Developer Relations, so my route is not the only way and not the best. My path to DevRel could've been shorter and more straightforward. Similar to those asking me, I was also dying to figure out how to get into Developer Relations. A year ago, I was also sliding into DMs asking the same question. Fortunately, I found plenty of informative content from DevRel leaders on how to break into this field. In summary, the general advice for those seeking to become developer advocates has been:

Learn in public by creating content in the form of:
- Public Speaking
- Technical Blogging
- Youtube Videos
- Twitch Streams
Develop Empathy
- By working as a software developer
- Through building and helping developer communities
- By contributing to open source
- As a teacher
Build your developer brand
- Through social media (ex: Twitter)
- By publicly showcasing that you're doing the above items

Because there is already a lot of advice about becoming a developer advocate, and for me, some of the items above seemed unattainable and overwhelming, I'll take a different approach. Instead of creating similar content, in this post, I will evaluate how each of my professional experiences helped me gain the skills I needed to get an offer to work as a Developer Advocate at GitHub.

It's likely that you have already developed the requisite skills or are already doing the work, but you don't yet realize it. My daily work already incorporated many relevant experiences and transferable skills, so I didn't need to pick up new skills, start a podcast, stream on Twitch, or even contribute to open source before interviewing. I just needed to package my experiences into a story that demonstrated I was a good fit for the role.

First off, what is Developer Relations? 🤷‍♀️

Developer Relations is the team responsible for building developer communities. The team consists of Community Managers, Developer Advocates, Developer Experience Engineers, Developer Evangelists, Technical Writers, and more.

I specifically wanted to become a Developer Advocate. According to Mary Thengvall, Director of Developer Relations at Camunda, "a developer advocate is someone who's got a developer or coding background but also enjoys writing, speaking, and generally empowering the technical audience to better understand a product. They advocate internally for the technical audience's needs."

How did I get there? 🤔

Before Tech: Empathy for Customer 💜

Between 2014 and 2016, I worked multiple jobs: Planet Fitness, H&M, Let's Get Ready, Mass General Hospital. Some of them I worked at the same time. For example, after my shift at H&M, I would run over to Planet Fitness. After dropping out of college for financial reasons, I developed an unhealthy obsession with money.

What I learned: I developed customer service skills and empathy for the user in these roles. Even when the customers had disagreeable personalities, I learned to understand their frustration. I also learned that having this many jobs was ridiculous regardless of my monetary goals!

During this time, I also pursued my Associate's degree in Computer Information Systems.

What I learned: Through community college, I learned about the importance of internships and theoretical IT problem-solving skills.

IT Support Internships: Problem-Solving and Learning in Public 🔧

Federal Home Loan Bank of Boston: This was my first technical internship. I went in not knowing anything, and I made it clear that I didn't know things, but I wanted to learn. In addition to migrating employees from Windows 7 to Windows 10 and implementing two-factor authentication on their mobile devices, I mostly helped employees troubleshoot their technical issues, which forced me to break down technical concepts in a way they could understand. People genuinely embraced my journey, and it made me feel like I belonged in tech.

What I learned: Confidence, terminal/command line basics, willingness to learn in front of others, ability to explain technical concepts to less technical people, empathy, and patience.

HubSpot: I held two internships at HubSpot as a data analyst for the AV support team and a help desk technician. HubSpot was a goal for me because I wanted exposure to the latest technologies.

What I learned: I learned about APIs and bash scripting within my six months at HubSpot. I also learned more about coding and decided to pursue a career in software development.

Social and In-Person Networking 🤝

Twitter: In 2016, I made a Twitter account dedicated to connecting with people in the tech industry and documenting my journey. Although my follower count was low, I made a few friendships and felt like I gained insight into people's experiences in the tech industry.

In-person conferences: My internships, especially at the Federal Home Loan Bank of Boston, sponsored me to attend local conferences. I gained inspiration, observed well-delivered conference talks, and learned to network with industry leaders through conferences.

Coding Bootcamp: Learning to Code 👩‍💻

Resilient Coders: In January 2018, I joined a non-profit coding bootcamp for people of color. People told me attending a bootcamp is hard, and I didn't believe them until I experienced it. Because so much work was due at once, I had to consume information and quickly produce solutions to problems, which mirrored my future experiences as a software engineer.

What I learned: Front-end development, backend development, building fast prototypes, quickly solving problems on a deadline, and reading and understanding copied code.

Skillist: While I completed my coding bootcamp, I worked as a Content Marketing intern at a startup called Skillist, which is now acquired. I mostly wrote career and interview prep tips.

What I learned: This experience reignited my love for writing and reminded me of my creative and content creation skills.

Software Engineering Internships: Production Code and Computer Science Theory 🧠

Formlabs: Before I completed my bootcamp, I landed a role at Formlabs, a 3D printing company based in Massachusetts. I sat on a newly formed Business Systems team where they tasked me with building two internal tools that would help them integrate their systems.

What I learned: Although I doubt they still use my web apps, the experience was invaluable because that was my first time using unfamiliar programming languages to build a full-stack web application from scratch.

Veson Nautical: Fortunately, at Veson Nautical, they used data tables, which coincidentally, I used to build my applications at Formlabs. During this time, I also enrolled in Boston University's Accelerated Degree Program for Computer Science. At the end of my internship, Veson offered me a full-time role.

What I learned: Version control, writing production code, React, and navigating complicated systems.

Boston University: As I mentioned, I enrolled in BU to earn my bachelor's degree in Computer Science. It was stressful to balance both school and my job. I would not do it again. After completing a bootcamp and experiencing culture shock at all my prior internships, I was beyond exhausted, and I didn't give myself a chance to absorb what I learned. However, I gained exposure to computer science theory, which helped me better discuss advanced technical topics with engineers.

What I learned: Data Structures and Algorithms, Computer Networking, Java, Operating Systems, Calculus, Data Management, and Computer Architecture

Full-time Software Engineering: System Design 🏗

Hi Marley: In February of 2019, I wanted to push myself more, so I worked at a startup. This company moved quickly. In terms of my skills, I was behind the curve, so I tried to keep up. I'm still grateful for this experience because the features I built were impactful and complex, making for great conversation in interviews.

What I learned: How to solve coding problems quickly, thinking about system architecture, AWS (Cloudwatch, CloudFront, DynamoDB, S3, and Lambdas), Redux, Microservices, Git Workflow, and debugging.

Volunteering: Building Inclusive Developer Communities 🌍

G{Code}: As I completed my degree and continued working at Hi Marley, I helped to build a non-profit organization alongside the founder Bridgette Wallace and my colleague Bailey Siber. At G{Code}, we teach women of color and non-binary people of color the fundamentals of web development. In addition to creating digestible educational content, I had to think about their overall wellbeing, like if they needed transportation or food. Today, about 70% of our alumni have continued their technical journeys. Some of them currently work as Software Engineers at Intuit and Vertex Pharmaceuticals.

What I learned: Inclusive and equitable community building, technical curriculum development, mentoring, instructing, cold calling, cold emailing, technical event planning, and career coaching.

Hack.Diversity: One of the ways that I landed new jobs like HubSpot was through Hack.Diversity. As an alumnus from their pilot cohort, I felt grateful for their opportunities, so I served on their Alumni Leadership Council. We held alumni tech talks, and I led a team of 8 in building the MVP of an alumni website. I used this as a space to practice my technical presentation skills.

What I learned: Speaking skills, management, and event planning

Mentorship: Get Someone to Help You Shine ✨

In 2020, I discovered Developer Advocacy, but people always told me to wait until I had at least five years of experience in software engineering, or they said I would lose my technical skills if I did.

I took the above advice sparingly because I saw people like Chloe Condon and Ceora Ford doing exceedingly well in their roles as Advocates but didn't have 5+ years of software engineering experience.

My mentor, Anita Patel, supported my dreams and encouraged me to blog about what I learned, so I wrote my first post in April 2020 about the command: git bisect.

Tech blogging: Building a Developer Brand ✍️

Botany: After suffering from burnout and severe anxiety, I was just trying to regain my self-esteem and love for coding. At Botany, my manager made it easy to do that. He encouraged me to write a blog post after I merged a PR to reflect on my learnings. His advice aligned with my mentor's advice, so I started technical blogging in between tickets. Here's one of my first posts about GitHub Actions.

What I learned: Effectively communicating more advanced technical topics in written format, slowly regained my confidence, GitHub Actions, React Hooks, and TypeScript.

Interviewing: The Moment of Truth

By the time that I started interviewing, I was able to demonstrate that I:

Could build developer communities and connect with members in various communities
Had experience giving technical presentations (to small, local groups)
Had strong writing skills
Loved helping others
Had varied experience with solving complex problems in web development with code
Knew how to exercise empathy
Had experience organizing events

While my interviews were not all successful, I went into the the interviews confidently because I knew I had strong examples to demonstrate my skillset.

Whether you have been a teacher, a waiter, or a marketer, your past professional experiences helped you develop relevant skills needed to work as a Developer Advocate. Start reflecting on your experiences, and don't sell yourself short!

Please support TechIsHiring!

If you have any feedback, feel free to send a message to @TechIsHiring or @Chad_R_Stewart on Twitter, email us at techishiring@gmail.com.

Where #TechIsHiring this week! - Week of September 18, 2023

Mon, 18 Sep 2023 14:00:38 GMT

Hello Everyone!

This is the TechIsHiring newsletter which specifically highlights job opportunity tweets and tweets supporting the job hunt tagged with #TechIsHiring for the previous week!

Get updated on the hashtag by visiting TechIsHiring.com. If you'd like to contribute directly to TechIsHiring's operation, please support us through Patreon!

Sponsored Tweets:

Jobs Tweets:

Additional Resources:

Please support TechIsHiring!

If you have any feedback, feel free to send a message to @TechIsHiring or @Chad_R_Stewart on Twitter, email us at techishiring@gmail.com.

How to Talk About Your Open Source Experience in a Tech Interview by @BekahHW - How #TechIsHiring this week!

Wed, 13 Sep 2023 14:00:26 GMT

Hello Everyone!

This special edition of the TechIsHiring newsletter features Bekah Weigel (@BekahHW), Developer Experience Lead for OpenSauced.

We’d like to thank Bekah for allowing us to send this article out to our readers!

Get updated on the hashtag by visiting TechIsHiring.com. If you'd like to contribute directly to TechIsHiring's operation, please support us through Patreon!

Introduction

Interviewing is a skill that can be strengthened. Interviews can be frustrating, demoralizing, casual, intense, and occasionally fun. They can make you doubt yourself or they can validate your skillset. There’s a lot being evaluated in these interviews and I know, personally, that nerves have gotten the better of me in that process. But just like any other skill, the more you learn about how to do it, the more you practice, the better you get. When you’re interviewing for a tech job, you’re going to be asked about your experience. Contributions to open source projects are a great way to demonstrate your skills because they can demonstrate your technical skills, showcase your collaboration, problem-solving abilities, and passion for your work. Even if you’ve had a stellar experience as a contributor, you need to know how to effectively talk about your open source experience during the tech interview. In this blog, we’ll explore how to talk about your open source experience in a tech interview.

More Resources on How to Land a Job with Open Source
How I Got Hired Contributing to open source projects
Building Your DevRel Resume with Open Source
How to Contribute to Open Source without Knowing How to Code: A guide with project suggestions
Beyond Content Creation: How Open Source Contributions Can Help You Get Noticed

Highlight the Relevance

When talking about your open source experience, emphasize its relevance to the position you're interviewing for. Make a connection between your contributions and the skills required for the role. Discuss specific projects or aspects of the open source community that align with the company's tech stack or the job description. This demonstrates your ability to bridge the gap between open source and the company's goals.

Example Response - Developer Advocate Role

Interviewer: Can you provide an example of a time when you partnered with an engineering team to deliver educational content to community members, leading to enhancing their skills and product knowledge while also promoting advocacy?

Mia: One significant open source project I contributed to was a developer toolkit for a programming language that closely resembles the tech stack utilized by your company. This project allowed me to immerse myself in the language and gain an in-depth understanding of its intricacies.

As part of the documentation issue that I worked on, my main responsibility was to create educational content, including tutorials, to empower fellow developers using the language. I wanted to ensure that the community had the resources they needed to fully leverage the language's capabilities.

To achieve this, I collaborated closely with the engineering team and community members to identify common pain points and areas that required further clarification. I actively engaged in discussions on forums and organized workshops that specifically focused on your company's technology stack.

Through my open source contributions, I not only enhanced my technical expertise in the language but also developed strong communication skills. I was able to effectively articulate complex technical concepts to a diverse audience, building their skills and product fluency while advocating for the open source project and its relevance to the developer community.

Describe Your Contributions

Start by explaining the problem you aimed to solve or the feature you worked on, providing context for your involvement. If you faced challenges, highlight how you overcame them. If you know the impact of your contributions, such as the number of users, positive feedback, or adoption by other developers, share this information as well. Emphasize the lessons you learned during the process and how they have shaped your technical growth.

Example Response - Front-End Developer

Interviewer: Can you tell me about a problem or feature you worked on, providing context for your involvement?

Tomás: Absolutely! One project I recently contributed to was an open source web application called "Contributions Connect." It aimed to connect local communities and facilitate collaboration among their members. As a frontend developer, my role was to enhance the user experience by improving the application's UI and optimizing its performance.

Interviewer: Did you face any challenges during the project? How did you overcome them?

Tomás: One of the main challenges I encountered was optimizing the application's performance and speed on the front end. The initial version of the UI was visually appealing but lacked the necessary responsiveness. To overcome this, I focused on identifying bottlenecks and implementing performance optimizations, such as minimizing HTTP requests, compressing assets, and leveraging browser caching. By implementing these techniques, I significantly improved the overall loading time and responsiveness of the application.

While working on Contributions Connect, I actively collaborated with the open source community, receiving positive feedback and engagement from both users and fellow developers. Our improvements in UI and performance not only led to an enhanced user experience but also resulted in increased adoption by other developers within the community. This was evident through the growing number of forks, stars, and contributions to the project on GitHub.

Interviewer: What lessons did you learn from this experience and how have they shaped your technical growth?

Tomás: This experience taught me the importance of striking a balance between aesthetics and performance in frontend development. I learned that building a visually pleasing UI is only part of the equation; ensuring optimal performance and speed is equally crucial. Through this project, I developed a deep understanding of performance optimization techniques, such as lazy loading, code splitting, and caching strategies. These lessons have not only enhanced my technical abilities but also instilled in me a passion for creating efficient and reusable code.

Showcase Collaboration and Communication Skills

Open source projects are collaborative by nature, so it's important to showcase your ability to work effectively in a team. Talk about how you interacted with other contributors, how you shared ideas, and how you resolved conflicts or differences of opinion. Highlight any leadership roles or responsibilities you had within the open source community, such as being a maintainer or a project lead. Emphasize how you effectively communicated with the project community, both online and offline.

Example Response - Project Manager

Interviewer: Can you tell me about your experience and skills as a project manager?

Gift: Certainly! While I'm transitioning from a developer to a project management role, my experience with open source projects has provided me with valuable insights into effective project management practices. During my time as a developer and transitioning into project management, I had the opportunity to work on various open source projects. One notable experience was my involvement with an open source project called "AwesomeWebApp." As a contributor, I actively engaged with the project community, collaborating with other contributors and sharing ideas to enhance the project's functionality.

In terms of interacting with other contributors, I firmly believe in fostering a positive and inclusive environment. I regularly participated in online discussions, providing constructive feedback and suggestions to fellow contributors. By actively listening to different perspectives, I ensured that everyone's ideas were considered and respected. This approach helped us maintain a harmonious and productive work atmosphere.

To resolve conflicts or differences of opinion, I employed a diplomatic and solution-oriented approach. One instance comes to mind when our team encountered a disagreement regarding the implementation of a new feature. I initiated a discussion to understand the varying viewpoints, encouraging open dialogue and mutual understanding. Through effective communication and compromise, we were able to reach a consensus that satisfied all parties involved.

In terms of leadership roles, I took on the responsibility of being a project maintainer for the "AwesomeWebApp" project. As a maintainer, I oversaw the project's progress, reviewed and merged contributions, and facilitated discussions among contributors. This experience provided me with valuable insights into coordinating efforts and ensuring the project's overall success.

When it comes to communication within the project community, I recognized the importance of maintaining strong connections both online and offline. I actively participated in online forums, providing timely updates and clarifications to project-related queries. Additionally, I organized and attended meetups and conferences, where I had the opportunity to interact with fellow contributors face-to-face, fostering personal connections and strengthening the project's community spirit.

Overall, my experience as a developer working on open source projects has equipped me with essential skills in teamwork, communication, conflict resolution, and leadership. I believe these experiences have laid a solid foundation for my transition into project management, as they have honed my abilities to work effectively within diverse teams and engage with stakeholders at various levels.

Discuss Your Learning Experience

Open source projects provide an excellent platform for continuous learning and skill development. Share how your open source experience has expanded your technical knowledge and honed your problem-solving abilities. Discuss the new programming languages, frameworks, or tools you encountered during your contributions. Mention any feedback or code reviews you received and how they helped you improve as a developer. Demonstrate your enthusiasm for learning and growth.

Example Response - Full Stack Engineer

Interviewer: Tell us about your open source experience and how it has expanded your technical knowledge and honed your problem-solving abilities. Specifically, could you share an example of a project or issue where you utilized your full stack skills?

Mari: During my open source experience, I've had the opportunity to dive into various projects that have expanded my technical knowledge and sharpened my problem-solving abilities. One specific example of utilizing my full stack skills was when I took on an issue in a popular open source project called XYZ.

The issue involved optimizing the performance of a RESTful API endpoint by implementing caching mechanisms. As a backend developer, I understood the importance of efficient data retrieval and transmission, but this challenge allowed me to explore the frontend side as well. I needed to assess the current caching strategy and propose improvements to enhance the overall user experience.

To tackle this issue, I first familiarized myself with the project's codebase and the technology stack it utilized. It involved working with a combination of Node.js on the backend and React.js on the frontend. Although my professional experience was primarily focused on backend development, I was eager to expand my skill set and embrace the full stack nature of this challenge.

I dove into the existing code, identified the areas that required optimization, and researched different caching techniques suitable for this scenario. Leveraging my backend knowledge, I suggested implementing a combination of server-side caching using Redis and client-side caching through the use of memoization techniques. I collaborated with the frontend team to ensure the integration of these caching mechanisms in the API response handling and UI components.

Throughout this process, I actively sought feedback and engaged in code reviews with other contributors in the open source community. Their insights and suggestions not only helped me improve my code quality but also broadened my understanding of best practices in full stack development. Their expertise guided me in addressing edge cases and optimizing my implementation further.

This experience demonstrated my enthusiasm for learning and growth as a developer. It showcased my ability to adapt to new programming languages, frameworks, and tools by utilizing my backend expertise while embracing the frontend responsibilities in a full stack context. Working on this open source issue allowed me to expand my technical horizons, reinforce my problem-solving skills, and solidify my desire to pursue a full stack role.

Talk About the Open Source Community

The open source community thrives on collaboration, knowledge sharing, and giving back. Talk about your involvement in the community beyond coding, such as participating in discussions, mentoring newcomers, or contributing to documentation. Discuss how the open source community has influenced your professional development and how you have contributed to its growth. Showcase your passion for open source and your dedication to making a positive impact on the developer community.

Example Response - Senior Software Engineer

Interviewer: Can you provide an example of a leadership experience that demonstrates your ability to mentor and guide junior developers your team?

James: I believe that leadership goes beyond just technical skills and encompasses the ability to inspire and guide others towards their growth and success. One particular experience comes to mind where I had the opportunity to mentor and support junior developers through their open source experience.

At my previous company, we were working on an open source project aimed at simplifying deployment processes for cloud-based applications. As a Senior Software Engineer, I actively participated in the open source community, engaging in discussions, contributing to documentation, and mentoring newcomers who wanted to get involved.

I realized that mentoring early career folks was not just about sharing technical knowledge but also about creating a supportive environment where they felt comfortable asking questions and exploring their ideas. To facilitate this, I organized regular virtual meetups where junior developers could share their progress, discuss challenges, and seek guidance.

During one of these meetups, a junior developer was struggling with a particular feature implementation. Instead of simply providing a solution, I encouraged them to think critically, guided them in breaking down the problem, and suggested potential approaches. Together, we explored different options, discussed trade-offs, and eventually arrived at an elegant solution. It was a gratifying experience to witness their growth and see their confidence increase.

To ensure a continuous learning experience, I also conducted code reviews, providing constructive feedback to help junior developers improve their coding practices and gain a deeper understanding of software development principles. I believe in leading by example, so I made sure to contribute high-quality code and follow best practices myself, setting a standard.

Through this experience, I realized the immense impact mentoring can have on both the individual being mentored and the community as a whole. It's not just about helping someone with their code; it's about empowering them to become better developers and fostering a culture of knowledge-sharing and collaboration.

I also actively encouraged the junior developers to contribute back to the open source project by taking ownership of smaller tasks, reviewing pull requests, and suggesting improvements. By doing so, they not only developed their technical skills but also gained a sense of ownership and pride in their contributions.

Additional Consideration: Be Prepared to Show Your Code

Some tech interviews may require you to showcase your coding skills by sharing links to your open source contributions. Be ready to present your code or other contributions and explain the rationale behind your decisions. Practice explaining concisely and be prepared to answer questions related to the codebase you worked on. One great way to lead the hiring manager to the contributions you’re most proud of is to send them to your highlights page.

For most of us, it takes practice and experience to interview well. By highlighting the relevance of your contributions, describing your accomplishments, showcasing collaboration and communication skills, discussing your learning experience, and emphasizing your involvement in the open source community, you should be able to create an impression that interviewers will remember. And remember, this is a great opportunity to share your passion and demonstrate all the things you’ve learned through your open source journey.

Good luck!

This article was taken from a previous blog post. You can find the original blog post here:

Dev.to - How to talk about your Open Source Experience in a Tech Interview

OpenSauced has started the hashtag #100DaysOfOSS! Similar to #100DaysOfCode, this hashtag is meant to encourage participants to contribute to open source for 100 days, building their development skills and fostering community! You can learn more about it here:

https://docs.opensauced.pizza/community/100-days-of-oss/

Please support TechIsHiring!

If you have any feedback, feel free to send a message to @TechIsHiring or @Chad_R_Stewart on Twitter, email us at techishiring@gmail.com or visit TechIsHiring.com/Contact.

Where #TechIsHiring this week! - Week of September 11, 2023

Mon, 11 Sep 2023 14:00:44 GMT

Hello Everyone!

This is the TechIsHiring newsletter which specifically highlights job opportunity tweets and tweets supporting the job hunt tagged with #TechIsHiring for the previous week!

Get updated on the hashtag by visiting TechIsHiring.com. If you'd like to contribute directly to TechIsHiring's operation, please support us through Patreon!

Sponsored Tweets:

Jobs Tweets:

https://rss.cm/job/1330/209/ or DM me :)","title":null,"type":"image/png","href":"https://twitter.com/MGallagher2010/status/1671507384512987137?t=RrD08NgUCVxE5L-smykJrg&s=19","belowTheFold":true,"topImage":false,"internalRedirect":null,"isProcessing":false,"align":null,"offset":false}" class="sizing-normal" alt="Martin Gallagher - Go and Rust Recruiter @MGallagher2010 Fancy using #Golang to help capture Carbon? Mid-senior engineers needed. UK based role. Hybrid working model- 2 days per week in office. Visa sponsorship offered for exceptional candidates. More details and apply here --> https://rss.cm/job/1330/209/ or DM me :)" title="Martin Gallagher - Go and Rust Recruiter @MGallagher2010 Fancy using #Golang to help capture Carbon? Mid-senior engineers needed. UK based role. Hybrid working model- 2 days per week in office. Visa sponsorship offered for exceptional candidates. More details and apply here --> https://rss.cm/job/1330/209/ or DM me :)" srcset="https://substackcdn.com/image/fetch/$s_!eJYE!,w_424,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F68fcf2e0-21ae-4ad7-aeee-26fda8124aac_1100x1064.png 424w, https://substackcdn.com/image/fetch/$s_!eJYE!,w_848,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F68fcf2e0-21ae-4ad7-aeee-26fda8124aac_1100x1064.png 848w, https://substackcdn.com/image/fetch/$s_!eJYE!,w_1272,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F68fcf2e0-21ae-4ad7-aeee-26fda8124aac_1100x1064.png 1272w, https://substackcdn.com/image/fetch/$s_!eJYE!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F68fcf2e0-21ae-4ad7-aeee-26fda8124aac_1100x1064.png 1456w" sizes="100vw" loading="lazy">

Additional Resources:

Please support TechIsHiring!

If you have any feedback, feel free to send a message to @TechIsHiring or @Chad_R_Stewart on Twitter, email us at techishiring@gmail.com or visit TechIsHiring.com/Contact.

Who #TechIsHiring this week! - Week of June 19, 2023

TechIsHiring — Wed, 21 Jun 2023 14:01:22 GMT

Hello Everyone!

This is the TechIsHiring newsletter which highlights those job hunting tweets tagged with #TechIsHiring from the previous week!

Get updated on the hashtag by visiting TechIsHiring.com. If you'd like to contribute directly to TechIsHiring's operation, please support us through Patreon!

Sponsored Tweets:

Job Seeker Tweets:

Please support TechIsHiring!

If you have any feedback, feel free to send a message to @TechIsHiring or @Chad_R_Stewart on Twitter, email us at techishiring@gmail.com or visit TechIsHiring.com/Contact.