As a Product Manager, Would You Shut Down an Engineering Project Started By a Technical Lead?

Let’s imagine you are a product manager who recently paired with a new engineering team. You come across a project initiated by a technical lead that you would rather shutdown than watch continue. What would you do in such a scenario? Even if you feel that shutting down the project is best for the company, there is a right way to go about the process.

Are You Sure the Project Needs to Go?

Before you decide you need to put the brakes on an ongoing engineering project, make sure you are on the right track. Some tell-tale signs of a project being in trouble include:

• The team has no detailed project plan.
• There is no clear hierarchy in the team.
• No one from the company’s senior management is backing the project.
• There has been no customer involvement in product definition.
• The customer has not provided any feedback on deliverables.
• There is no use of suitable project tracking tools.
• The team is overworked.
• Team members have ideas about how to provide simpler solutions.
• There has been little to no testing.
• There is no clarity on exactly what’s expected from the final product.

Shutting Down a Project

Every once in a while, there comes a time when a product manager needs to shut down a project started by a technical lead (TL). If you are worried this might reflect poorly on your own performance, don’t be. Here are measures you may follow to make the process go as smoothly as possible.

• Include the TL in your talks with other stakeholders, which include feedback calls. This gives you an opportunity to get a first-hand perspective. For all you know, the TL might also feel that the project needs to go.
• Determine how aligned the project is to your company’s goals, because shutting it down might be easy if it is down the priority list.
• If you can get the project into a beta or minimum viable version (MVY) state with little effort, you may track its adoption (or lack of).
• Begin user-involvement at an early stage, simulate possible results, get required feedback, and make your decision accordingly.
• Speak with stakeholders who wanted the project implemented and find out their reasons. Share with them why you feel moving forward might not be a good idea.

The Alternatives

While you might want to take a firm decision of shutting down a project, think hard in case other stakeholders do not provide their complete support. If you have been tasked with recovering an engineering project, start by looking for signs of over- engineering. In some cases, you might be able to pivot projects by adding capabilities that provide value to end-users. Pay close attention to numbers when justifying a product’s level of automation, be it the number of users or the time saved.

Conclusion

When caught in a dilemma about whether or not to shutdown a project that a technical lead holds close to the heart, determine what’s best for your company. Thinking about sunken costs will do no good, because there’s a good chance you will need to rebuild anyways. Cutting your losses short - and even starting over if you have to - might be in your best interest.

How to Avoid Burnout in a Software Engineering Job?

Consider this – you embark on a new project with much gusto, and end up building something of value that finds several takers. Then, you start getting overwhelmed because of technical issues and support requests. Burn out follows. While this is not the only scenario of burnout in software engineering jobs, it goes to highlight that the problem is all too real.

Fortunately, identifying early signs of burnout in your job can be easy. Once you do, you may take the required measures to steer clear of any such situation.

Symptoms of Burnout at Work

Overworking and stress often play a role in burnouts. Once on this path, a developer soon loses interest in coding and anything else that might be work-related. While symptoms of burnout vary from one person to the next, here are signs that warrant your attention.

Lack of passion or motivation
Having a sense of self-doubt
Feeling ineffective in your current role
Poor performance
Feeling fatigued (mentally or physically)
Feeling isolated or disconnected
Suffering from anxiety, depression, or insomnia
Suffering from headaches, dizziness, shortness of breath, or chest pains
Experiencing mood swings
Not being able to pay attention
Noticeable change in appetite

What Causes Burnout?

Instances of burnouts in the software industry are fairly common because this field is very challenging and highly demanding. Instead of having to work for a fixed number of hours each day or every week, software engineers are often found pushing boundaries because of seemingly unrealistic management-driven deadlines. Some of the common causes for burnouts in software engineering jobs include:

Under-resourcing by employers
Sitting in front of computers for extended durations
Monotony
Mental fatigue
Poor physical health
Cynicism and indifference
Weak culture of programming at the work place
Having to make personal sacrifices
No relief in sight

How You May Avoid Burnout

Avoiding burnout at your software engineering job so you may retain your passion for coding requires self-control. You need to start by asserting that you are in charge of what happens with your life. You should avoid saying yes to every project that comes your way because quality matters more than quantity. In addition:

Set non-negotiable boundaries and make them known to all involved stakeholders.
Learn to distinguish between what you want to do and what you don’t.
Let your boss know what you need in order to succeed – be it more time or additional resources.
Work for no more than eight hours per day.
Don’t work on weekends.
Don’t check work-related emails and messages after work hours.
Eat and sleep well.
Get enough exercise.
Consider meditating.
Avoid too much caffeine.
Assess your energy levels regularly.
Pursue hobbies that take you away from programming.
Be kind to yourself.
Limit the use of social media.
Take at least one vacation every year.

Conclusion

You need to understand that your productivity will take a nosedive if you suffer from a burnout, and all the efforts you have put into any process until now might end up going in vain. If you feel passionately about your work, or want to again, it is important to do what’s required in order to avoid a burnout.  Remember that you are in control of your life. Besides, even though you might have no control over what others think, your actions may have an influencing effect.

How to Deal With a Biased Boss?

Do you think your boss showers one or more employees in your team with special treatment, while the efforts of others go in vain? If so, understand that the workplace is almost never a level playing field because bosses and employees are all too human. Work place favoritism has probably existed since the dawn of workplaces, and most people find themselves at one end of the spectrum or other at some point in time.

While dealing with a biased boss might seem daunting, you need put your foot down at some stage in order to move forward professionally. Fortunately, finding a solution might be simpler than you think.

Signs of a Biased Boss

You need to be sure if your boss is biased so you may take effective corrective actions. Here are signs that mark bias in a boss.

• A particular employee is constantly showered with praise for no apparent reason.
• Others in your team get better career development opportunities.
• You feel micromanaged all the time.
• You don’t get feedback.
• Your request for a raise is rejected without a valid reason.
• You’re not included in important meetings.
• You receive criticism even when you do a good job. 

Are You Really a Victim?

Are you sure that your boss is biased or might you have perceived a situation incorrectly? One way to determine if you’re thinking straight is to ask your colleagues if they feel the same way. Pay attention to conversations between your boss and those who you feel receive undue praise. Could it be that the people you who feel are being favored are actually more adept at handling tasks assigned to them? Remember that an incorrect assumption can lead to drastic consequences.

Act Normally

Pretend that you have no inclination about your boss playing favorites. You definitely don’t want your boss to see you in bad light, which is why you need to keep all adverse reactions at bay. While you might not be your boss’ favorite, you don’t want to end up at the bottom of the ladder either. Bear in mind that emotions can cloud your vision. Determine what the favored employee is doing right, because two can play the game.

Know Your Performance Metrics

Seek clarity about the performance metrics that apply on your team. Ask for your key responsibility areas (KRAs) so you can identify the basis of your evaluation. With a clear picture of your targets and expected standards, you know just what you need to do to get your boss’ attention. However, this also requires that you put your best foot forward consistently, and work on improving your skills.

Find a Mentor

If you feel that no matter what you do your boss is just not giving you your due, consider finding a mentor. A mentor can guide you in exploring other possible roles within your organization based on your skill set. In addition, you may also receive guidance surrounding what you need to do to improve your skills and how to get noticed by other leaders in your organization.

Document All That You See and Hear

Once you’re sure that your boss is biased, start documenting all that you might see or hear about him/her, because this is crucial when it comes to establishing a pattern of biased behavior. However, this step requires that you be honest and objective. You might make use of this documentation at a later stage, if higher ups or the HR department enters the picture.

Talk to Your Boss

You might consider bringing your reservations up with your boss directly. However, make sure you are subtle, as opposed to being accusatory. In some cases, highlighting clear data points instead of making generic statements helps bring to the surface some unconscious biases.

Explore Other Options

When all else fails, you might want to look for other opportunities, either within your organization, or elsewhere. Some organizations give employees the ability to make lateral moves to other managers or projects. At this stage, affecting a positive change is basically up to you.

What You Need to Do If You Face Discriminatory Bias

The U.S. Equal Employment Opportunity Commission (EEOC) states that it is illegal to discriminate against employees based on race, religion, color, sex, age (40 or older), national origin, disability, or genetic information. It is also illegal to retaliate against anyone who has complained about discrimination, filed an official complaint about discrimination, or taken part in an employment discrimination lawsuit or investigation.

If you find yourself in any such situation, consider filing a complaint with your organization’s HR department. You might also think about contacting a lawyer and/or the EEOC.

Conclusion

There is no reason for you to go out of your way to please your boss as long as you’re good at your work. What you need to bear in mind, though, is that your boss is simply trying to provide value to his/her boss. Favorites typically help managers look good in front of their bosses, so there’s no real bias there. If you can think of a way to make your boss’ life easier, you might find yourself becoming the next favorite. If things seem beyond your control and the bias is real, reporting it might be your best bet.

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.

What is an SRE?

Introduction

With the incorporation of software in almost every industry and the huge dependency on programming and computer science, it was just a matter of time before a new discipline was introduced. According to Ben Treynor Sloss, who is Google’s engineering vice president, “A site reliability engineer is a software engineer who is responsible for developing an operations function”. Site reliability engineering (SRE) uses the versatility of software to handle regular IT operations such as server management and other computer operations by establishing reliable software systems. SRE task forces usually utilize and develop software to handle project issues and problems, increase project autonomy and manage the entire project’s process with minimum manual intervention and manpower. Despite being a commonly used term in classifying work teams, the majority of the people working in both software and project management industries are still not fully aware of the underlying concept behind site reliability engineering. This article is an attempt to clarify what does an SRE do, how is an SRE important to business and projects, how are SRE teams different from DevOps and what kind of tools and technologies that an SRE utilize.

What does a site reliability engineer do?

SRE work can be divided into two main tasks. About half the time is spent on developing and programming new features, increasing system autonomy and project scaling. The rest of the time is spent on operations related work including tasks that require personal intervention and on-call duties. So an SRE should have a balanced mix of system administration skills and software programming, automation and engineering. Among the duties of an SRE is the code deployment, configuration and monitoring in addition to responding to emergencies and managing production service capacities.

How important are site reliability engineers?

SRE makes the project management process of large projects easier by developing complicated codes and algorithms that handle most of the regular and daily tasks. The software developed can be expanded to administer a huge spectrum of machinery and equipment within a company. As I mentioned earlier, SRE’s work can be divided into two main sections, standardization and automation. It is the goal of an SRE to improve a system’s reliability and features while automating operations tasks. The unique role of an SRE requires programming skills and operations management experience. SRE teams are particularly important for startups. Due to its small scale and inability to hire large groups of developers at large scale, having SRE teams would be extremely beneficial for the startup. After understanding how important are SRE teams to a company and what kind of work do they handle, we now need to discuss how do SRE teams work within a development team. 

How different are DevOps from site reliability engineers?

Site reliability engineering implements the idea of DevOps at its core. But what are DevOps? DevOps simply denotes development and operations, where developers are responsible for writing codes, which are then passed on to the operations team for installation and support. However, due to the separation between both teams, developers were not responsible for how the software or features would be used, leaving the operations team in a bad position. This led to problems because the goal of the developers is to keep introducing new features for the customers with new pieces of code, whereas the operations teams are seeking a steady system with stable and steady changes. However, by combining both teams and helping them understand each other’s duties and responsibilities, introducing new features will not only be based on developing the code for the feature itself but also on the consequences and fallout this new introduction might lead to. DevOps and site reliability engineering are often confused because of their similarity in many aspects and properties. Both DevOps and SRE seek high quality and fast services delivery as well as life cycle development, by optimizing business value and responsiveness through automation, platform operation enhancement and integrating both development and operations teams. Now, let us see how is SRE different from DevOps. First of all, SRE teams take to their own hands the duty to eliminate communication and workflow issues. SRE teams’ main goal is to achieve site reliability while adding novel ideas and features, whereas DevOps are mainly concerned with efficient development of operation using platforms such as Kubernetes and microservices. Unlike DevOps, SRE teams split their working time between operations and development tasks such as systems scaling and automation implementation, which is a crucial aspect in the site reliability engineer’s role. A key component for SRE teams is to achieve that balance between both operations and development work. 

What kind of technology supports a site reliability engineer?

In order to determine the type and time of features to be launched, SRE teams use Service Level Agreements (SLAs), which are used to determine the necessary system reliability depending on Service Level Indicators (SLIs) such as availabilities, rate of error, requested latency and systems throughput, and Service Level Objectives (SLOs), which are based on specified goal values and budget error. Due to the fact that an integral aspect of SRE’s work is automation, unified software containers usually provide teams with a common development environment facilitating work integration, automation and delivery.

Conclusion

Incorporating site reliability engineers can be handful especially for startups. They can assist developers by solving some of their general issues, hence providing them with more time to handle programming specific issues. They can also improve the capabilities of the tools used by developers to help them become more productive. In addition, the customer will be provided with a product that has high reliability and security. It is important to mention that finding an SRE to join the team is not quite simple due to the fact that they are looking for a person who are able to multitask and handle both operations and software engineering at a high level. It is always a pleasure to answer all your questions and see you in the next one.

**Note: All the attached photos are royalty free and not copyrighted. 

Facebook – Solution Engineer vs Software Engineer

**Note: All the attached photos are royalty free and not copyrighted.

Introduction

As we all know, Facebook is one of the largest tech companies in the world in the meantime. It ranks in the fifth place according to brand value compared to other tech companies in 2020 with a whopping 147 Billion Dollars. Facebook Inc. has also acquired multiple tech companies in the last decade such as WhatsApp, Instagram and more. Without a doubt, it is mesmerizing to be part of Facebook, whether as a software engineer, a solution engineer, or at any other position. However, if it is an option that you can choose between a software engineer and a solution engineer, then there are some points that you will have to consider before taking the decision. In this article, I am going to point out the major differences between both roles, and hopefully help you pick the one that is more suitable for your preferences. 

What does a Software Engineer do?

A Software Engineer utilizes his/her knowledge and expertise about computer science to write codes using programming languages, in addition to servers, databases and frameworks that are used to create computer or mobile applications, operating systems … etc.

The software engineer’s responsibilities can vary from one job to another and there are many career paths for a software engineer other than coding jobs. Here are some examples: web developer, mobile developer, test & quality assurance engineer, machine learning engineer, data scientist/engineer and much more. 

What does a Solution Engineer do?

A Solution Engineer is like a job description and not a field of engineering. It also requires a bachelor in software engineering or computer science just like the software engineer. Nonetheless, a Solution Engineering role can be considered the interface between the development team and the client or the customer. The solution engineer also makes use of computer science principles to make sure that every component of the product or the software is running seamlessly as it should be, without any glitches or lags. The solution engineer is not only responsible for the software part of the product; however, he/she is responsible for the integration with the hardware components of the system. Not to forget that another major role of the software engineer is to familiarize the client with the product; that includes operating demo presentations and some technical meetings explaining the product or the system. 

Major differences between both roles

One of the qualifications that should be found in the solution engineering role and not in the software engineer is the fair knowledge of sales. The solution engineer is the one responsible for outlining the client’s needs and delivering it to the development team making sure that the client is satisfied with the outcome solution. As mentioned earlier, the solution engineer is more of a client-facing role while the software engineer is more of a back of house role that is not felt by the customers. 

Responsibilities of a Software Engineer at Facebook

Just similar to any software engineer, they are working on creating new products and systems that run the Facebook Group’s apps and services. The software engineering force at Facebook is divided into multiple teams, which are Products and Services Teams, Infrastructure Teams and the team of Specialists. The first team is focused on utilizing new technologies to create new features and improving the existing ones. The second team works on ensuring the stability and efficiency of the infrastructure of Facebook such as servers, data storage, system resources and more. The final team, which is the team of specialists, usually work on integrating the new technologies with the complete structure of Facebook. 

Responsibilities of a Solution Engineer at Facebook

A solution engineer at Facebook, his/her time is divided 50/50 between two main sorts of tasks. The first one is to code and develop new products and services just like other software engineers. The other sort of tasks is actually a combination of activities such as dealing with support requests, performing adoption of new products to be able to comply with Facebook’s technologies, interacting with clients and partners, doing public speaking or even writing some blogs. 

Conclusion

Assuming that you have the opportunity to choose between the two positions, your choice should be based on multiple factors. The most important one is to choose the role you are more passionate about. You will perform better if you’re enjoying what you are doing. The second factor is the career future. As discussed earlier, the major difference between a software engineer and a solution engineer is how deep you are involved with coding. Software engineers purely write codes, on the other hand, solution engineers are more client facing with some sort of involvement in code writing. It is totally up to you to choose the track you want to take. Specifically, at Facebook, code writing is highly integrated in the tasks of a solution engineer. Accordingly, you will not miss the benefit of being into coding on a regular basis with the addition of gaining experience from clients’ interaction and sales tasks. The third factor is the salary; both roles are paid roughly close figures. The average annual salary of a software engineer is around $92,000. For the solution engineer, the average annual salary is around $100,000. The common qualification that you must have to work at Facebook is to have brilliant developing skills; hundreds of millions or even a billion users are testing your output every month so any mistake will be very costly. 

References:

https://www.reddit.com/r/cscareerquestions/comments/bmer6i/solutions_engineer_vs_software_engineer/

https://www.quora.com/Is-it-better-to-be-a-solutions-engineer-or-a-software-engineer-With-respect-to-future-growth-and-salary

https://www.quora.com/Is-solutions-engineering-at-Facebook-a-fancy-term-for-tech-support

https://www.quora.com/What-does-a-solution-engineer-do

https://codingnomads.co/blog/what-does-a-software-engineer-do/

https://www.glassdoor.com/Job-Descriptions/Solutions-Engineer.htm

https://www.facebook.com/careers/areas-of-work/engineering/?p[teams][0]=Software%20Engineering&teams[0]=Software%20Engineering

https://www.facebook.com/careers/life/solutions-engineering-at-facebook