As a Software Engineer, Do I Move to the East Coast From San Francisco? What’s the Difference?

Are you thinking about moving from San Francisco to the East Coast to pursue your career in software engineering? If so, know that there are several aspects that need your attention, and they don’t limit just to your salary. If you plan to make this move, it is best that you determine its pros and cons well in advance.

Where Do You Plan to Go?

Making the decision becomes considerably simpler if you already have a job offer. In case you don’t, you need to identify your options ahead of time. This is because software engineers tend to serve distinct sectors across different East Coast cities.

• Most software engineering jobs in New York relate to servicing the finance industry, which includes names such as Citadel, Jane Street Capital, and Goldman Sachs. 
• Jobs in Washington D.C. are mostly government-based.
• Hartford’s software engineers largely cater to the insurance sector.
• In Greenwich, they are typically found working around hedge funds.

What you can notice here is that while software engineering jobs in San Francisco revolve around technology, technology serves as an add-on feature in cities along the East Coast.

The Money

How much money you stand to earn and save as a software engineer might depend on the city to which you move. In a list of 21 cities that find favor with software engineers, Seattle and San Jose take the top two spots when it comes to real earrings. This accounts for income and expenses, while paying due attention to the cost of living. For example, gas is more expensive along the West Coast, and so is the typical cost of home ownership. Washington D.C., Boston, and New York find themselves at the bottom of the list.

When it comes to highest paying salaries, San Francisco takes the lead, followed by San Jose, and New York comes third.

The Weather

Weather across both coasts can vary significantly because of what the Atlantic and Pacific oceans bring. If you’re in New York, you can expect long and very cold winters followed by blazingly hot summers. You can experience all four seasons here in all their glory, with fall making way for some beautiful landscapes.

Weather along the West Coast is typically milder. For instance, South California is warm and sunny almost all through the year, whereas even the northern part does not get very cold in the winters. If you go further north on the West Coast, you’ll experience no more than the occasional snowstorm.

Recreation

The West Coast offers great diversity when it comes to taking a break. You get to choose from a plethora of beaches, driving routes, national parks, and hiking spots. While the East Coast is mainly mountainous, it still has some great national parks. 

The Other Differences

Here are some other differences that might warrant your attention in case you plan to move eastward.

• The West Coast is more politically liberal than the East Coast.
• New York City beats San Francisco when it comes to public transportation.
• The West Coast is better at recycling its waste.
• The East Coast is typically more fast-paced than the leisurely West Coast.
• Cities in the east are more compact than their western counterparts – think New York.
• If New York has theatre and fashion, San Francisco is famous for its music and museums.

Conclusion

You can make the most of moving to the East Coast from San Francisco if you know exactly what you’re after. However, determining just how your move might affect your future prospects is crucial. Switching back from a government-based tech job that involves little innovation to a completely tech-based company later in life might not be easy, after all.

As a backend engineer, will Apple M1 work for me?

 

Introduction

Apple divorcing from Intel was about as expected as the collapse of Kim Kardashian’s marriage to Kanye West. For years we have been watching all the major cell phone manufacturers ditching Qualcomm as fast as you can say “SIM Card” and, as was expected, the PC manufacturers have decided it was their turn. As with people, the only one you can really trust is yourself, and that is the same for massive technological empires. Beyond that, software's, languages, and all other things follow one steady path through this journey of life, and that is, after being taxed disproportionately, at some point they die. x86 has been getting caught up to for years. Intel has slowly become a 21st century case study in the Innovator’s Dilemma as ARM is showing x86 the door with lower power draw and higher performance.  AMD, which for the record still makes x86 chipsets, is eating Intel for breakfast as their chips feature a 7nm die size; something obtained after a summer of ditching the pizza parlor for the running trails. This article could go on and on about how Intel is suffering in the short-term to the new obsession with ARM processors, and quite frankly, everyone else, but this is just to state why Apple has switched from Intel to in-house silicon. Because of the switch, I know many readers like you are wondering if M1 silicon will work for your job as a backend engineer. 

Disclaimer

I must start by disclosing I have worked professionally in a full-stack and embedded engineering role using Macintosh products. Some of you will read this and assume I am a paid fanboy for the team they have assembled in Cupertino, so let me start by saying that I will use my experience with the products to paint an accurate picture of Macintosh and not some glowing review of the greatness of Tim Cook and his cadre of scientists and engineers. I think Windows has many viable options for backend engineers, and at better price points. Linux is a viable option too, and thank the geniuses at the Raspberry Pi foundation for making Linux the OS of my favorite computer. However, this is simply to answer the question, as a backend engineer, will the Apple M1 work for me. 

The Wrong Reasons why you should buy M1

So, in a world of good and bad reasons, I find it best to bring you the worst first. If you choose to sip on silver-tinted Kool-Aid, and ask Siri sage questions such as “how do I fry an egg”, you have probably fallen into the camp of the Mac faithful, and well, we are going to get eviscerated in the comment section, but nobody will get our diamond hands off of our favorite plug and play machines. Sure, we may outspend our Windows brethren, and we may not be as in-touch with the spirits of computer science as our friend on Linux (because you are allowed one, no more, no less), but we are also spending our time actually doing our job rather than installing drivers. This brings me to my first wrong reason:

You Don’t Know Anything Else

You have been bellying up to the bar of Macintosh for long. You actually know how to use homebrew without looking up commands. Debian and Red Hat sound like secret societies (which, to be fair, they kind of are). Bill Gates has not found a way to spy on you yet. Apple is quickly becoming a part of your dependency list. As someone who has worked in Windows, Macintosh, and Linux as a professional, I am saddened if you are stuck with Mac. But I get it. It’s okay, we all have that thing we cling tightly to; the thing which we watch every update to see when it will finally go away. I have woken up with a cold sweat imagining the day they sunset CoolTerm. I think such concerns are far off for Apple, so fret not, you are more than safe hitching your career to that wagon. That being said, if you are making this decision because you couldn’t fathom using any other OS, perhaps this is the time you branch out a little, and I promise, this will go better than that time your mom told you to try out for the soccer team. 

One Word - PowerPC

Tim Cook reassured an audience of non-technologists by saying that Apple would support their Intel-based Macs for “years”. Well, some remember the transition from PowerPC to x86, and let me tell you, those “years of support” looked more like “long enough to let the existing staff learn the new chip” than “we stand behind what we make”. So if you are a backend engineer, and you are going to stay with Macintosh, I would definitely recommend against buying a Mac until you can get your hands on an M1. In fact, including all my good reasons, this bad reason is probably the best reason for you to buy an M1 as a backend engineer if you NEED a Mac. 

It Is the Shiniest Toy

Being on the forefront of any major technological change is always going to be difficult, and that is true whether you are one of those types that lives a step or two beyond stable releases or even just buying the newest cell phone. Early reports show that there are already performance bugs that are present in some of our favorite software's like Chromium, Docker, Edge, and Firefox. These will subside as time goes on, and it is up to worthy pioneers to blaze a trail. Then again, do not rush to the frontier if you are doing it for the cowboy hat. Beyond that, as a Mac buyer for years, I know that you can save considerably when you wait for the first refurbs to come back. 

The Right Reasons why you should buy M1 as a backend engineer

The Battery and The Fan

ARM used to be reserved for micro-controllers, cellphones, and other things which could afford to slow down a little bit in the name of consuming less power. Well, I for one am glad to see x86’s skinny cousin getting his time in the gym, and coming back to school this fall as a lean mean fighting machine. Initial reviews say that the new M1 silicon is a beast when it comes to battery life, and you are going to need that for when you are actually going places again and not firmly affixed to wherever your Mac charger is plugged in. I have heard reports of eight hours of active development with no need for plugging in, and that is frankly impressive. A quieter fan is a welcome sound to my ears. As a software engineer, I have enough people that whine at me over the tasks I ask them to perform, my computer doesn’t need to as well. 

SSD

On the Mac, a lightning fast SSD is essential to executing database queries and subsequently file accesses quickly. Whether full-stack, backend, frontend, business-end or the end, you are going to find that a fast SSD is going to make you faster, and therefore better at your job, and happier with your productivity. The write speed between the previous version of the MacBook Air and the M1 has gone from 1007MB/s to 2190MB/s. Color the computer engineer in me impressed, and you can cash in those performance increases with a marked improvement in what you get done during the workday.

GPU and RAM

I know this affects the front-end engineers more, but the GPU is becoming ever so important in the world of block chains as well. And everyone always wants more RAM, I mean, you might be using this to game after work, and that is important too. The new M1 architecture has less RAM than the Intel versions of the computer, however, the new integrated architecture means a lot more bang for your buck with the RAM that you do have. For example, the 8GB and 16GB Mac’s with M1 have reported very little difference in performance, so it is debatable if the RAM difference is significant. That being said, some of the Intel offerings by Mac do currently have 64GB of RAM, so if that is of dire urgency, by all means. Then again, iPhone users with 4GB of RAM are getting performance numbers on par with Android devices with over 8GB, so it may just be a matter of time for these laptops with less memory to catch up, if they have not already. 

CPU

I am going to just leave these scores from Cinebench and GeekBench here: 

	M1	Intel i7 1185G7
Single Core Cinebench	1516	1548
Multi-Core Cinebench	7698	6263
Single-Core Geekbench	1778	1518
Multi-Core Geekbench	7518	6097

Considering that the Intel offering listed is the current industry leader, and that the M1 won in all categories except the single-core test by Cinebench, you could at least say that the M1 was a worthy competitor. And you would be right. Consider the fact that the fans never turned on for the M1 tests due to the lower power consumption of the ARM chips, and I will leave it to you to figure out who is leaving who in the dust. 

The Reasons why you should NOT buy M1 as a backend engineer

GPU and Graphics

You can not have an external GPU, and are limited to one external monitor. I don’t know about you, but following the rule of 5 (every five years of development experience can and must be cashed in for another monitor in your dev environment), this is simply not allowed. For that matter, Minecraft is going to run horribly without the external Apple eGPU, so anyone who wants to game on this machine after work, good luck. I have heard the GPU is on par with competitors outside of these limitations, but this is listed first, because this is of dire importance to anyone envisioning impressing their coworkers at the after-hours LAN party. Without the external GPU, who knows, maybe you won’t even be invited. 

Dual-Boot

As I said, some professionals need this to work with multiple OS’s, and as a backend engineer, that may be the case. You must remember that there is less RAM on this laptop and not all VM’s are ready to use the integrated memory efficiently… You may find yourself working with 8 total gigs of RAM on a Windows machine and although going back to 2014 to avoid COVID is alluring, I am very much a fan of the increased processing power the past six years have brought us technologically. 

IDE’s and other software

If you use XCode, and nothing else, skip this section. You already are optimized, you don’t have to consider this at all. If you don’t, well, at best your favorite apps will perform at the same level of performance they have been. Rosetta2 may be bridging the gap, and some like VS Code are announcing a plan to get with the times, but like I said earlier, being the first means you’re usually paying a larger price than the premium of being the first to have something. JetBrains and Eclipse have also announced plans to make adaptations for the Mac silicon, but these things take time. For that matter, consider that some of your favorite tools that are not already optimized are going to need to be, and not all of them have the backing that products like Visual Studio do. 

You are happy with your computer

If you are not currently a Mac user, you are probably in the camp that should wait for the pioneers to figure M1 out, and that includes all the software out there that is going to need to eventually break out of Rosetta2. If you have a Mac that can extend you another couple years, well, you will see the price of M1 and won’t be caught bagholding when inevitably the Intel support falls away. It is exciting to be on the cutting edge, but sometimes you get cut and it hurts. 

The Answer

As a backend engineer, you are more than likely going to be just fine with the M1 silicon in the long-run. You are going to be caught in the awkward growing pains of Apple’s new hardware, as you watch your instances of Windows slow down, and you run into problems with some of your favorite applications like has been reported with Docker as of the time of this article. The graphics limitations could be a concern, but if you are all work, no play, and you don’t even know how to pronounce Adobe, you are probably fine working with the graphics card that ships with that. However, also consider that blockchains and scientific computing are intensive on the graphics card as well, so you are not only going to be limited in how many frames you can mine Redstone at. I personally love Mac and do full-stack development with it, and I am waiting for refurbs and the software ecosystem to catch up, but for those of you that NEED to be on the cutting edge, I think this is going to be a very solid machine. Now excuse me while I ssh into my Pi from my MacBook Pro and play Pong. 

Written By: Grant Udstrand, writer for copperlunatic.com

My manager does not let me take up more responsibility

A number of engineers and coders fail to get more roles or responsibilities from their managers despite having years of experience, being good at their jobs, and being important team members. Fortunately, following a few simple measures might work in their benefit.
Further down this page, you will get to identify the common problems that employees tend to face in this situation, as well as whet you can do to work your way around.
If you wait for things to get better without taking proactive actions, you might find yourself in a state of stagnation, getting out of which may become a challenge at a later stage.

Speak With Your Manager

People who complain about not getting enough responsibilities or not getting assigned more roles by their managers have typically already made some efforts on their own. These can include asking to working on a new project, mentoring an intern, or interviewing possible new hires.
If you have asked your manager for more to do, there is a good chance you have been told that you need to make more contributions and exercise patience.
At this stage, ask your manager what he or she thinks you need to do to move to next level of responsibility. Try to get specific and actionable feedback. After all, who better to tell you what your manager expects than your manager?

Identify What’s Holding You Back

You might be in your current situation because you overestimate your contribution, because your manager favors other team members, or even because your manager dislikes you.
If you have overestimated your contribution, you need to keep putting your best foot forward and delivering consistently.
If you think you are not in your manger’s good books, you might be fighting a tough battle. In this case, you can think about fixing any apparent problem, or leaving the team/organization. It is important that you do not demand too much because it might worsen the situation. On the other hand, you might get desired results by doing more for the organization, the team, and your manager.
If you find yourself in a situation where your manager does not meet your advocacy requirements, let go off your expectations. Then, work on finding another advocate. This might come in the form of a direct supervisor, a manager from another department, or even a mentor from outside your organization.

Identify Possible Roles

When you talk with your manager about taking up more roles, you need to present solutions instead of highlighting problems. You need to be clear about what roles you would like to take on, because asking for more responsibility without offering suggestions makes your appeal rather ambiguous.
For instance, do you want to develop a new product, do you want to lead a project, do you want to partake in an existing project, or do you wish to manage others? Try to identify overwhelmed teams or bottlenecks that typically slow processes down, and then suggest how you can address them effectively.
When identifying opportunities, your focus should be on ones that benefit your business as well as clients. Then, you need to articulate how your new responsibilities or role can help deliver positive results.

Take Ownership and Provide Updates

Once you evaluate your own performance, determine if you have been scraping by or have been exceeding your goals. If you have ideas about how you can improve a process or a product, bring them up in team meetings. Consider summarizing your ideas and sending them via email, while copying the same to different stakeholders.

As and when you get to take on any new roles or responsibilities, make sure you provide timely updates about your progress. Moving forward, ask your manager if you are on the right track.

Conclusion

Know that how your manager feels about you or your work today is subjective, and can change with time. So, a no today might change to a yes tomorrow. Timing may play a role too, because your manager might simply be too swamped with work at this time. If push ends up coming to shove, start building your network inside and outside your organization. This way, you will have leads to openings when the time arrives.
If you have questions about this blog post, please ask by using the corresponding comments section. If you found it to be beneficial, please share it with others. To access more useful content related to careers in software, follow us now.

Is there any point of a PMP certification?

What is PMP?

PMP is an abbreviation for Project Management Professional. It is a professional certificate that is awarded to certain individuals who pass the Project Management Body of Knowledge exam. The certificate is awarded by the Project Management Institute PMI, which is located in the United States of America and is recognized internationally. There are over one million PMP certified and active individuals around the globe. It is awarded to individuals who demonstrate skill, knowledge, experience and competency that are required for the project manager to manage various projects and lead teams from different backgrounds to achieve the project's goals. PMP gains its importance for being imperative and essential in almost every industry. The demand for PMP certificate varies from one industry to another. The demand comes from the need to have individuals who are able to handle system reorganizations, develop strategic plans, manage outcomes, handle issues and ensure system effectiveness. Being recognized globally, the PMP certification is considered an unbiased endorsement of the individual’s project management experience and knowledge.

Skills tested in a PMP exam

The project management professional exam tests five different skills for the project manager. The first skill tested is the individual’s ability to understand the project goal and problems. This tests the individual’s ability to identify the key issues in the project and clearly be able to have an idea about the end project result. Another skill is the ability to plan the project. This checks whether the candidate has the ability to create a long-term plan that would be followed throughout the entire project, unless there are changes or unexpected variables that might be introduced later on in the project resulting in plan changes and adjustments. Again, to be able to develop a successful plan, the candidates need to show an understanding of the project’s goals and key elements. A third skill is the ability to run and execute the project according to the developed plan. This tests the candidate’s team management and leadership skills represented by distributing and assigning tasks to the right people according to a set period of time. This skill is considered a crucial skill in the PMP exam. The fourth main skill tested is the candidate’s ability to manage, monitor and control the project. The project management professional should be able to handle delays, monitor tasks and conduct adjustments accordingly. The candidate should be able to notice and identify issues that the project might run into and tackle them. Finally, the candidate is tested for his project closure skills. This tests his ability to meet goals and deliver the project according to the assigned time frame.

What is the main role of a Developer?

A developer is the person who works in software development. Developers are responsible for designing the software and identifying the main goals of the software that is yet to be created. They are also responsible for creating, developing and testing the software to meet the design requirements. The final step involves maintaining and adding features to the developed software. As you might have noticed, the developer’s work is similar to that of a project manager. Developers can develop software to different companies for different purposes, so they are not limited to computer manufacturing companies, but they can rather work for different companies involving different industries. This is again similar to a project manager working on different trades in one large project. A developer is responsible for understanding the problem to be solved, designing a solution, developing and programming the solution, testing the developed solution and finally releasing the software to the client.

What Project managers do?

As previously mentioned, a successful manager is an individual who is capable of achieving a successful project initiation, planning, implementation, monitoring, development and closure. A successful project manager should be able to identify key project elements, detect unstated assumptions, lessen uncertainties and risks, manage the project process and finally deliver the project. The PM should listen to feedback from the project’s team members and act accordingly. A crucial role that is played by the project manager – independent of the working environment or industry – is making critical decisions. The project manager is the one responsible for the project’s success. Accordingly, key decisions taken by the project manager are crucial to control risks, handle issues and minimize uncertainty.

Is PMP certification enough to switch from being a developer to project manager?

The short answer is not much. It is clear that there are obvious differences between being a developer and being a project manager. Despite the similarities in some of the job duties, a developer is yet to possess some of the skills that a project manager needs to lead a team, plan, implement and manage a project throughout the whole project phase. Obtaining a PMP certificate is not enough to do the career shift from being a developer to being a project manager. The certificate is used to test the way you are going to handle different situations that a project manager might face. In most cases, a good project manager develops his skills from previous experiences. He might rely on the concepts that he learned during his studies towards PMP certification, but still, it is not simple to mimic real life situations and complexities on paper. In addition, there is no theoretical way that you can use to run a project, but rather it comes with lots of practice, job shadowing and experience. Being a developer with a PMP certification is not enough to convince any company that you are capable of running a project and leading a team of different backgrounds and skills that are much broader. According to some of the people who receive job applications for project management position, possessing a PMP certificate makes no to little difference and does not give the candidate the edge he/she might have in mind.

Is engineering PM an over-saturated role ?

Do you think that the role of a project manager (PM) is overrated? Do you feel it is hyped, oversaturated, and maybe, even elitist? If so, you probably need a reality check. The competition that one has to deal with to become a PM, after all, is often worth the effort.

In this post, you will find out why the role of a PM is relevant, especially in today’s times.

Start by understanding that many seemingly great products would not have found the success they have if not for competent PMs. However, the role is such that the number of PM openings is typically lower when compared to completely engineering or technical roles.

What Does a Project Manager Do?

Businesses that require PMs do so with good reason. While they have engineers and developers to focus on software and mechanical specifics of getting products going, PMs play a vital role in understanding customer requirements and communicating with all stakeholders.


In a nutshell, a PM needs to understand customer requirements, identify tools or processes that can be of use, and oversee the creation, execution, and delivery of any project.


A good PM would also be adept at:

• Identifying and resolving issues
• Budgeting
• Time management and approval
• Team-building

One of the biggest challenges that PMs face is influencing people without exercising an air of authority. This can be particularly difficult when they have to deal with people who don’t report to them directly.

Project Managers vs. Product Managers

While both are PMs in their own right, and both come from predominantly engineering backgrounds, they have different responsibilities.


Project managers need to ensure that tasks are assigned to the right people, while also making sure of timely delivery. Their focus is on driving the development of products. A project manager would typically:

• Oversee the workload of multiple engineers
• Have at least basic technical knowledge about products being developed
• Solve management and scheduling problems
• Coach and offer advice
• Resolve disputes

A technical product manager, on the other hand, is responsible for making tech-based decisions after considering different metrics, as well as for overseeing the execution of development plans.

The "Worth" of a Project Manager

As a project manager, you should have the required knowledge about your realm, failing which you don’t stand a very good chance of earning your peers’ respect. Being able to influence without authority is also important.


You should be able to get through roadblocks faced by your engineers and bring plans to fruition. For instance, if your engineers are waiting for information from a product owner who is slow to respond, you should be able to deliver in a timely manner.


Consider this example – you are responsible for handling a team that is working on a completely new product. You need to start by determining if it is a good idea. Then, you need to look into existing competition, as well as address aspects related to costs and revenue. You also need to collaborate with the marketing team so it can help you get your product off the ground. To do all this effectively, you need more than just engineering skills.

As you can see, the role of a project manager is rather wide-ranging, and calls for high levels of soft skills as well as business skills.

Conclusion

Getting back to whether the role of PMs has become oversaturated, the answer remains an obvious no. However, what should go without saying is that not having a PM at all is better than having a bad one. A good PM should not only have technical knowhow and analytical skills, but should also be able to distribute accountability and ownership of key aspects to the core team.

If you can manage to double up as a project and product manager, there’s nothing like it, because you’re then responsible for executing your own suggestions.

What Happens to Your Software Career When You Turn 50?

Have you reached that stage in your software career where you are wondering how relevant you might remain once you turn 50? Are you worried about finding a job that matches your existing skill set? If so, know that there is plenty of light at the end of this tunnel.
This blog post addresses all the aspects that need your attention in keeping your software career going way beyond your 50s, should you so desire.
You need to start by understanding that just your years of experience might not serve the purpose. This is because whiling away in your existing job without taking on new challenges, while simply waiting for the years to pile, will do little good for your prospects in the future. Therefore, what happens to your software career in your 50s and later is basically up to you.

What Does the Existing Scenario Look Like?

There are several programmers over 50 years of age who have managed to do rather well for themselves, be it in the form of responsibilities or financial growth. Some have found great roles with leading names such as Google and Amazon, some are playing important roles at startups, and some others have found success as independent consultants.
Names such as Jon Skeet, Linus Torvalds, Jeff Dean, John Cormack, and Doug Cutting have gone on to show that age is just a number when it comes to keeping a career in software going great guns. It is also interesting to note that not many end up going toward management.

What You Need to Do

If you are looking at continual growth in your software career, it is important that you remain ambitious and continue improving. Adding to your skill set along the way is crucial. For instance, if you have been programming for two or more decades, it is fair to assume that you have moved from COBOL to VB4 to Oracle to Java.
Going forward, the progression needs to continue. You may also need to reinvent yourself at some stage. Might you, for instance, consider a switch to AI- or IoT-related technology?
With a strong foundation of coding and database architecture in place, learning new technologies is fairly straightforward and takes little time. This is because you start seeing patterns that are repeated and reapplied in different domains.
Depending on how good you are and the value you bring to the table, you can end up being mediocre, while still retaining a good job, or become highly sought after by market leaders.

Roles You Might Get to Play

Depending on your skill set and areas of interest, you may consider taking up different roles in the later stages of your career.
Engineers can look for roles in technical management.
Coders can take up leadership roles related to product strategies.
You may work as a distinguished engineer, who is nothing short of an influencers’ influencer.
You can become a technology advisor for a large company that is working its way around the legalities of software development and use.
You can voice your opinion on controversial software-related topics such as the use of AI, cybersecurity, dark patterns, and software ethics.

What You Should Not Do

Several people try to rush their careers in a hurry to become product or people managers. This is usually with the aim of wanting to stop coding or getting a hike in salary. Most experts opine that getting an initial thrust in a software career can make you replaceable not far down the line. Besides, if you don’t pay attention to your technical skill set, and also indulge in office politics, you stand the risk of someone younger coming in and taking on your role more effectively.
The bottom line is that focusing on the technical side while continually upgrading your knowledge and skill set is bound to hold you in good stead no matter whether you are 50 or older. As long as you manage to stay relevant and have the fire in your belly going, there is no stopping you from shining in your software career even as the years go by.
If you have questions related to this write-up, please ask by using the comments section. If you’ve found this post to be helpful, please hit the like button. If you’re looking for more great content related to careers in software, follow us now.

No interview calls? Your resume is probably not getting past any SWE recruiter.

Several SWEs experience difficulty in getting interview calls for software engineering jobs. Wondering what they might be doing wrong and what they can do to increase their chances follows. If you find yourself in the same boat, going through this post in its entirety will give you a fair indication of what you need to do to land an interview call that can change it all.

What have you been doing wrong ?

Start by determining what you’ve been doing wrong so far. Answering these questions will help.

• Have you been using the same resume to apply for all the jobs you come across?
• Have you been over selling yourself?
• Is your job search limited to a few resources?

If your answers to these questions are in the affirmative, getting that interview call you crave might continue to remain a pipe dream. Fortunately, taking a few relatively simple measures can set you on the right track.

Get your resume in order

The first filter your resume needs to cross is that of a recruiter. Here’s what you need to do to get past this roadblock.

• Don’t add summary and objective sections because most recruiters tend to skip these.
• Keep your resume to one page, unless your experience stretches to beyond two decades.
• Your resume doesn’t need you complete address – the city and state are enough.
• If you need to email your resume, send it as a PDF and not a Word file, because the latter can lose its formatting on other machines.
• Include genuine interests because these can help recruiters connect with possible interviewees.
• Read through your resume in 10 to 15 seconds, and identify key take away points. That’s typically how long recruiters take for initial screenings.
• Get someone from within the industry to review your resume.

Try to get referrals

Referrals give job aspirants easy means to land interview calls. This is typically a win-win situation because, from a recruiter’s point of view, a referral is nothing short of gold.

If you have former colleagues who work with companies that interest you, ask them for referrals. However, don’t give them your resume straightaway. Mention that you’re interested in what the company might have to offer and give them your contact details along with a link to your LinkedIn profile.

Don’t hesitate to ask for referrals from anyone you feel might be able to help. These can include friends, relatives, and even acquaintances. Using platforms such as Teamblind and Reddit might prove to be beneficial as well. When asking for referrals, remember that you need to be polite, not overbearing.

Quantify your work

Try to quantify your experience. For example, instead of saying, “Maintained a crucial piece of internal marketing tool meant for corporate users”, go with something like, “Maintained a 5,000 line code, fixed 300 bugs, and delivered 50 change requests for a marketing tool deployed by around 200 users over a six-month period”.

Highlight the work experience they need

As clichéd as this might sound, getting the work experience right is crucial. Adding volumes about mundane details serves little to no purpose. Seasoned recruiters will not attempt to find what they need in your sea of fluff. Neither do they have the time, nor do they care.

While your resume needs to reflect what you have worked on in the past, it’s important that you read job postings carefully, and use the core words you find there in your own resume.

For example, if a job requires five years work experience in AngularJS framework, do not assume that a recruiter will get the required information from your brief mention of, “10 years experience in JavaScript frameworks”. Highlight and underline what they are looking for, while using just the right jargon. Do away with, or provide little focus on, aspects that don’t matter to a recruiter.

Do not lie about your work experience. Remember that the verbiage you use in this section speaks a lot about your existing and future potential as a candidate. Trained eyes tend to know just what to watch out for when it comes to this aspect.

Accept it, your resume may not be the best

Bear in mind that the companies you have worked for in the past matter, because recruiters view FAANG, unicorn companies, and regular bodyshop IT consulting companies differently. Be comfortable in knowing that there are other candidates who might appear more appealing on paper, and that your resume is probably at the bottom of the pile. Set your expectations accordingly. It’s best not to have a dream company in mind.

Your visa status may be, unfortunately a factor

If you’re in the U.S. on a work visa, remember that many companies view the process of getting a visa transferred as cumbersome. If you’re here on a student visa, the company you wish to join would have to apply for a work visa on your behalf.

If you have declared that you need visa support, probable employers may choose to ignore your resume. There is nothing much you can do about this, especially if they do not disclose their preferences ahead of time.

Have you tried adding a cover letter?

Most online application methods give you the ability to add an optional document in the form of a cover letter. Use this opportunity to highlight how your work experience will benefit the organization in question. Mention important points that don’t find room in your resume.

A farfetched yet effective idea would be to write a critique about something that is well known, or even about the organization’s website, tool, or process - while offering suggestions for improvement. For example, if you’re applying for the position of a frontend engineer at food delivery startup, you may provide ideas about how to improve UI experience without the need for extensive redesigning.

Look for openings through different platforms

Several recruiters use LinkedIn to find probable candidates. When updating your LinkedIn profile, follow the mantra of “Less is More”. For instance, you don’t need to add details about all the projects you’ve worked on, or the teams you manage.

• If your career has progressed well, make sure you add your job titles.
• Change your profile’s settings to reflect that you’re open to new opportunities.
• Add all relevant skills that you might have.

Check postings on Hacker News’ Who is Hiring. These are updated each month. In several cases, hiring managers add these posts, so you get the ability to bypass Human Resources. Attending hackathons and meet ups might also be fruitful.

While the going might seem tough at the beginning of your search for a new job, you can make the process easier by paying attention to the aspects mentioned herein. Getting through an interview, then, becomes your next challenge. 

If you have any questions about this blog post, please feel free to ask by leaving a comment. If you’ve found the content to be helpful, please share it with others who you feel might also benefit. Follow us for more relevant content that might help you find your dream job.

Feeling lost at your programming job ? You are not alone.

Introduction

Maybe you are let to believe that you are either not doing so well in your programming career or want to excel beyond your colleagues in the market or even have no purpose in your job and want to be motivated. In this article I will be offering some help on that.

First of all, you have to assess the situation, you can be unmotivated by your manager, or you can be falling behind your co-workers and need extra effort to cope with them, or maybe you are not feeling challenged in your work … and so on and so forth. After assessing the situation, it is time to take an action that suites you personally. Remember, there can be more than one solution to any given problem … it differs from one person to another. Let me in the following paragraphs propose some possible solutions to the scenarios I mentioned earlier. 

Scenario #1 to be unmotivated by your manager

We all know how positively or negatively a manager can influence the employees without even noticing. The most important thing is to never let anyone affect your self-confidence or make you question your capabilities. 

In programming obviously, you can write tens or even hundreds of codes to do the same task. It doesn’t mean that you were wrong and your manager was right if you didn’t deliver the results your manager wanted. You can solve that by having 1:1 conversation with your manager explaining how you feel. Maybe you need training on something. Maybe you are burned out solving issues that are of lesser priority and loosing focus on the bigger tasks. These are non-technical management things to focus on. If that doesn’t help, find a senior team member or a mentor to seek advice from. Or raise the issue in your workplace to a higher level.

Scenario #2 falling behind your co-workers in terms of performance

Let it be clear that it is not always a good idea to compare yourself with others because everyone has his own circumstances. However, we are living in a very competitive world that will create comparisons out of nowhere especially in a tech/programming job.

It is possible that you are not actually 100% sure of your interest in your current job. Maybe you as a web developer, find robotics interesting or as an embedded systems engineer is fascinated by web development. Put aside some hours per week to try them out, without forming close opinions. I have been there myself, but I had taught myself how to experiment before settling with what I want to do. It is possible that the new thing you picked up might become stagnant in 5 years, but then you already know how to repeat the cycle. You are older and wiser by now.

You are comparing yourself with much experienced friends. Ambition is a great thing but a negative feedback along the way is demoralizing. Know how to get positive feedback and keep yourself motivated along the way by gaining some perspective by doing freelancing or contributing to open source in your spare time. I’m sure most of the known names in programming have been there at the beginning of their career. You don’t have to be perfect to those, all you need to start is to be able to do things others can’t. One step after another you will improve faster than you can imagine. That way you can also dedicate some time in your week to learn and practice new things. You can do that by taking online courses or attending group workshops. Create dummy projects and try new techniques and tools. Remember, practicing a trade helps you sharpen your skills and a no-pressure hobby project is a great option to achieve that.

Scenario #3 not feeling challenged in your work. 

It is easy to feel bored if you keep doing the same tasks over and over … day after day. You are pretty good at what you do and it doesn’t push your intellectual limits any more – like production support job in a pretty stable environment where the most stressful moments of your job is handhold users to get their password reset. There is no development in repeating your job duties with little to no changes every single day. You can solve that by thinking outside the box, as cliché as it may seem, but this strategy actually works. Let the computer do the boring stuff by automating manual processes as much as you can in your code. By that, you will have time to work on your self-development. Re-visit old tools and try to improve them or even create new tools that will help you and others afterwards. That may provide some edge to eventually grow out of the grunt and maybe offer a distinction in the eyes of your manager. If a promotion doesn’t pan out as a result, you now have something to talk about in your resume for your next job.

Bonus Tips

At the end let me give you some bonus tips. The first and most important tip is to get out of your comfort zone. Keep challenging yourself to do things you never thought you could do. For example, involve yourself in a project written in a new programming language that you are not expert in yet. “Magic happens outside your comfort zone” I believe that if you adopt this saying in your life, you will really witness the magic. The second tip is to review your progress on a monthly basis. Make sure that you are heading towards the right direction, re-visit your goals and reflect on your outcomes. 

Conclusion

Finally, be sure that to set reasonable goals with achievable steps and don’t overload yourself with a lot of things at the same time. Small consistent steps on the right track will lead you to a better future and you all know the famous quote “The journey of a thousand miles begins with one step.”