503 karma · joined October 5, 2016
It takes luck, skill, and a personal match between you and a set of people at a company. At the end of the day both parties must feel like they have a good match.
Re: Tech interviews, unless you pore time into things like leet code and "cracking the code interview" tech screen will always just be psudo random.
I can imagine its somthing along the lines of needed to move data 1 time between 2 systems for an export/import and got lazy with permissions.
The other I had to build for a startup with millions of monthly uniques but only seed funding (cant do a 30+k a month data eng bill).
Went with custom event emission->kenisis->(druid & S3) and used imply (https://imply.io/). Easy real time data analytics, auto "enrichment with druid lookups from a RDBMS, and a simple ui for slice/dice investigation metrics. All in all costed lest then the cheapest looker license.
You look at my examples as negatives... its the wrong way to look at it... thoes other managers of other departments? Are the bad people? No... but they have a job and responsibility to represent their departments and do from their point of view whats best for their team and the company.
I feel like there is a segment of workers in engineering has this weird self damaging hatred for leaders/managers other departments do not have... then thoes same people get pissed when they dont have a leader and their department is glossed over because no one represents them when/where some of the most important decisions are made.
No one, its done by committee and/or senior leadership, the team/department with no seat at the table is always at a disadvantage.
>Who will take direct credit for the work of others?
A managers job is to distribute credit and shield blame/failure. This may sound generic but its true... a managers true strength/power/greatness or what ever other BS comes from the strength of their reports. Its extremely short sited to not pass on credit and grow those under you.
>Who's going to write a bad performance review of someone they don't like that much?
A good manager tries to be very objective and doesn't bring personal opinion into reviewing performance. I have had people who I did not like personally who i brought though multiple jobs... good managers respect effective people not people they can get a drink with after work.
- Whos going to push back and sales and marketing for harassing you directly or taking direct blame for failures?
- Who will represent the engineering team in leadship meetings to make sure policies/decisions are made with their needs in mind?
- Who's going to fight for your raises and promotions?
- Who's going to make sure that there is budget for what engineering needs to do and keeps a proper record to keep finance happy?
Please thing about it... any company that grows to 30-50 people (even startups) need to have management and processes that eventually lead to (even unintentional) politics. The other departments will have leaders/managers defending/supporting them... its foolish to not understand or respect competent leaders.
An Engineering Manger/Director/VP/CTO's main job is 2 things.
- To be the over arching intermediate between engineering and other business units (note: this does not mean walling off engineering, engineers SHOULD understand and work with business units when it makes sense).
- To support, mentor, shield, and basically do what ever is necessary for their team/department/org to be as successful as possible.
This sounds VERY self centered and I honestly believe product and engineering managers need to be to most selfless people possible to actually be effective. I would call it backwards even... a leader/manager needs to tailor himself and his approach to both his people and his cross-department equals in order to be the most successful.
They are lottery tickets and I treat them as such. I was a c level at my last position and had a percentage ownership... no difference.
I treat salary and bonus as my only comp, equity is just a lottery ticket of x size.
So you could also argue for that savings it may not be worth it. 100k is less then 1 engineer in most places (especially including TOTAL hire costs like equipment, office space, benefits, ect).
You can also argue it is much harder to hire golang engineers (or invest time/money into training engineers in go) so that that savings may not be worth it depending on the time it takes to rewrite plus the gamble of failure.
Also you need to ask could those engineers doing the rewrite have been working on up-sell features or other products that could make more money?
Would the investors (especial new growth oriented investors) care more about a increase in margins or a even larger multiple in ARR?
-I did x yesterday and am doing y today. - I am blocked/need a (answer, code review, dependency completed, ect). -reminder of OOO or WFH.
This minor message keeps everyone in the loop and takes little time. If you feel pressure to deliver because of standup I would say that's a cultural issue... or a self performance one (aka why have you been working on x for 2 weeks).
If your only issue is the other guy then in theory this could workout better for you as when the CTO's replacement comes in you all have nearly equal footing.
Who is your boss post his departure the CEO? If so be proactive and set time up with them to ask questions and voice concerns. You could possibly carve yourself a comfort zone.
I wonder if having wework on your resume is a good or bad thing.
(Disclaimer: I work for such a platform)
I picked up the vibe that none of their engineering endevors will drive any profits and basicly "sounds/look cool". I dont like being part of engineering teams that are cost centers and not value ads.
As someone whose spent nearly 13 years in the startup world my advice is this. Expect your cash comp to be your only comp and negotiate cash comp separately from equity.
Most startups fail... and even those who do succeed? The VC's get first payout... then founders... then maybe what's left for you...
Also there many other situations a company can pull to invalidate or take equity away from employees (think Zynga).
There is alot to gain in working at startup, just dont think the equity is the main reason to.
Note: do have some stuff in lambda but its package size restrictions limit us.
Revenue and business impact are ALL that matter.
Good, clean, scaleable, and testable code only exist to rapidly support the above. The moment you choose tech value over buisness you are a risk not asset to a company.
I sware sometimes I see so many delusional software "engineers" who care more about building technically excellent systems that are either delivered late or dont solve a/the real problem... it disgusts me.
It took me all of 4 days to come up with a CI/CD pipeline/production environment using ECS and fargate for the startup I was the cto for.
We are now looking at kuberneties or reserved instances to save some money as we have scaled to angel->seed->series A. Though tbh its looking like the extra cost is worth it given the out of the box 1 click scaling, blue/green deployments and "conatiner as a server" level monitoring and logging.
Node for the backend will also use javascript.
That could take you a very long way if you want to just hack out a product.
One key thing though is making sure everyone on the team understands our culture, and applies is somewhat fairly.
Personally I define "culture" as following the values set by the company and the department.
At my current place what are the core culture concepts we look out for (in a nutshell):
- Valuing the delivery of functional & sustainable products over checking boxes or coming up with impressive/resume-building solutions
- Everyone is expected to support, teach, and grow one another and everyone has something they can teach.
- Valuing receiving & giving honest, direct, and valuable feedback.
Many engineers would NOT fit this culture and in some interviews that becomes very apparent. We also send our values to our interviews before we bring them on site and reiterate them strongly before giving an offer letter... Thoes who have ignored this have never lasted to 6 months due to clashes with deliverables and with other team members.
The reality is there is two types of engineers:
- those how give zero shit about there company or product and use their currtent job as a platform the jump the their next job with zero care given about how it trufly effects the person paying them. (aka we NEED kubrentes, SPA, mircoservices, ect).
- and engineers who care about being REAL engineers... and providing the best technical solutions to the companies issues and/or problems.
One track leads to lead, manager, director, VP, CTO, and the other leads to a dead end bitching how management (aka those who give a fuck about hitting business goals) have more power then the spoiled self centered engineers who are mad the company wont pick the next flavor of the month tech stack to help them into their next job.
edit: wow down voted into oblivion over this... I came for a reasonable debate. Its super clear now why "rude" people rule and all the passive aggressive do is down vote me over a reply.
If your a team lead with no hire/fire power you need to go to your department head (and rally those whoa agree with you to do the same) and be blunt. "X is is not performing to expectations on top of that the way X is not performing is disrupting, impeding, and alienating other members of the team and its now become not just a performance issue but one of employee attrition".
This makes it about X vs the rest of the team/department and allows him to clearly see what is actually at risk. Its very unlikely 1 person is so valued that a manager would accept major turnover in their department.
How would those 7 top performers act if placed alone in a situation of failure? Where its obvious the company is failing and is clear is certain individuals? Is it not "rude" to point that out? Or are we defining being rude or assholity differently?
I personally seen many times people who push back or raise justified criticism of anything be labeled as "rude"/"toxic"/"assholish".