Skip to main content

Current and fake IT position presented by employees

By
Today post will not be about a technical problem or technology. It will be about IT people and their fake positions (the ones that are presented by them)
More and more often I see a lot of discrepancies between the real passion of a person in a company and the one that they share on LinkedIn, different events and meetings or on mail signature.
Before going deeper let’s see some example:

Current position | “Dream (fake) position”
Junior Developer | Software Consultant
Junior Developer | Solution Provider
Software Developer | Team Lead
Software Developer | Software Architect
Senior Developer | Technical Lead
Senior Developer | Project Manager

This are only a small part of the fake positions that I discover in the last 2-3 months. The list could continue, but you got the idea.
From my perspective, lying in your business card is a pretty big problem, which shows to me how reliable and honest is that person. For this kind of persons, the position is the most important thing for them and usually this dream is destroyed when you start to talk with them and you realize that they don’t have the knowledge and seniority level from their “business card”.
It is good to have a dream, but you need to work to reach it.
Why all of this is so important?
Because when a client see in specific position of a person, they expect to get a person at the level, not a ‘fake copy’. For example if you present yourself as a Team Lead and you start to discuss with clients about how you need kick off a project and organize the team, it is pretty clear that the client will be disappointed. He will realize that you are a junior and have the sensation that the company is selling untrained people.
Another example is when a junior say that he is a technical consultant, but without knowledge related to this position. The client end up with the same image: people from that company are not well train, WTF.

As we already saw, the biggest problem will not be on the people themselves. The company image will suffer. And because we live in a small world, you can imagine how fast other companies will know about that. The funny part of this story is that the company itself was no fault. This was made without
their knowledge or agreement.

Is better to have an extremely good junior than a mediocre (moron) senior in the end.

Comments

Post a Comment

Popular posts from this blog

Windows Docker Containers can make WIN32 API calls, use COM and ASP.NET WebForms

By
After the last post , I received two interesting questions related to Docker and Windows. People were interested if we do Win32 API calls from a Docker container and if there is support for COM. WIN32 Support To test calls to WIN32 API, let’s try to populate SYSTEM_INFO class. [StructLayout(LayoutKind.Sequential)] public struct SYSTEM_INFO { public uint dwOemId; public uint dwPageSize; public uint lpMinimumApplicationAddress; public uint lpMaximumApplicationAddress; public uint dwActiveProcessorMask; public uint dwNumberOfProcessors; public uint dwProcessorType; public uint dwAllocationGranularity; public uint dwProcessorLevel; public uint dwProcessorRevision; } ... [DllImport("kernel32")] static extern void GetSystemInfo(ref SYSTEM_INFO pSI); ... SYSTEM_INFO pSI = new SYSTEM_INFO(...
Post a Comment
Read more

ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded

By
Today blog post will be started with the following error when running DB tests on the CI machine: threw exception: System.InvalidOperationException: The Entity Framework provider type 'System.Data.Entity.SqlServer.SqlProviderServices, EntityFramework.SqlServer' registered in the application config file for the ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded. Make sure that the assembly-qualified name is used and that the assembly is available to the running application. See http://go.microsoft.com/fwlink/?LinkId=260882 for more information. at System.Data.Entity.Infrastructure.DependencyResolution.ProviderServicesFactory.GetInstance(String providerTypeName, String providerInvariantName) This error happened only on the Continuous Integration machine. On the devs machines, everything has fine. The classic problem – on my machine it’s working. The CI has the following configuration: TeamCity .NET 4.51 EF 6.0.2 VS2013 It see...
8 comments
Read more

Navigating Cloud Strategy after Azure Central US Region Outage

By
 Looking back, July 19, 2024, was challenging for customers using Microsoft Azure or Windows machines. Two major outages affected customers using CrowdStrike Falcon or Microsoft Azure computation resources in the Central US. These two outages affected many people and put many businesses on pause for a few hours or even days. The overlap of these two issues was a nightmare for travellers. In addition to blue screens in the airport terminals, they could not get additional information from the airport website, airline personnel, or the support line because they were affected by the outage in the Central US region or the CrowdStrike outage.   But what happened in reality? A faulty CrowdStrike update affected Windows computers globally, from airports and healthcare to small businesses, affecting over 8.5m computers. Even if the Falson Sensor software defect was identified and a fix deployed shortly after, the recovery took longer. In parallel with CrowdStrike, Microsoft provi...
Post a Comment
Read more