Not the original scores fortunately.
1,793 karma · joined September 24, 2007
Not the original scores fortunately.
That said, with startups it is always wise to assume your equity will be worth nothing. You can’t compare the compensation on equal terms with big tech RSU packages. It’s really about whether you will like the work and the startup environment better.
In practice, my experience has been that a typical engineering manager has to work in varying degrees across several dimensions of management:
- People management: performance evaluation; career development; keeping people happy; being a "first responder" to deal with issues before HR needs to get involved; resolving interpersonal issues to prevent them from affecting team performance; managing team morale.
- Project management: figuring out (by negotiating with non-technical staff and within the technical team) who should do what when; and making sure it gets done.
- Technical leadership: guiding design and architecture of the system; deciding / influencing the tech stack; setting and maintaining standards and best practices. Staying reasonably close to hands-on work, avoiding the critical path but staying informed enough to make the high-level decisions effectively.
- Product management: If the dedicated PM staff are not effective at defining the requirements, or are not technical enough to properly communicate them in a way the engineers can act on, an engineering manager often has to step in and fill the gap.
- Managing up / sideways: keeping higher-ups apprised of status and roadblocks, and feeding relevant information back to the team; depending on the manager's level and the size / structure of the organization, working with other functions in the company (sales, marketing, accounting, legal, ...) to the extent that these functions interact with engineering.
- Hiring: identifying what the team needs; working with HR/recruiting to find the right talent; being the first line of screening so that the engineers don't waste their time interviewing bad candidates.
All that is to say: yes, your sense that something is off with engineering management in your organization might be correct. "Might", because you might not actually be seeing all the activities they are doing. One thing I would say is that if your manager does not do a regular 1:1 meeting with you, focused on the people management aspect, that is a red flag.
Your comments about ineffective sprint planning and the siloing of backend vs. frontend teams ring true. I have seen "agile" processes done well and done badly. Having cross-functional / "vertical" teams generally works better. But it can be harder to organize things that way in large companies where there is a perception that functional specialization (e.g. grouping all the backend engineers under a backend manager) is more efficient.
Having a public GitHub profile is not a requirement, and most GitHub profiles I see are worthless. They're either large open source repos where the candidate contributed a few trivial changes among thousands; or personal repos that are just them working through some cookie-cutter online tutorial. The most useful repos from a screening perspective are where you created a non-trivial project from scratch. It doesn't have to be anything ground-breaking or truly novel. It just has to show evidence that you identified a problem worth solving, and spent some meaningful amount of time solving it, so that the code you wrote is a faithful representation of your ability to build and evolve a software system over time.
A lot of people just post "student code", which is badly organized, badly formatted, sparsely commented, and untested. This gives me no positive signal. Putting in the time to apply professional software engineering standards, even to a personal project, is much more likely to give me a positive impression of your capabilities.
Aside from the repo question: this just seems to be a difficult time for job-seekers. Lots of companies are doing layoffs and slowing hiring, is my perspective on the situation.
Other resume signals:
* A degree from a top 10 or top 20 university may help you stand out; top 50 is nothing special (but not a negative either).
* Sad as it is to say, if you've been hired at a well-known tech company with fairly high standards, that does provide a positive signal. If the only companies you've worked at are small startups I've never heard of, it's a bit harder for me to justify spending 30-45 minutes on a phone screen.
That said, the #1 thing I look for is whether you've done the previously done the kind of work I need to have done, and done it successfully (e.g., you stayed a while at the same company and the company didn't fail). (Obviously I can't attribute that to you individually, but I might at least give you a chance to demonstrate your depth of knowledge and ability in a phone screen.)
This was just me interacting through text prompts. I could imagine some kind of more integrated solution where you can provide some basic test cases, and the system would run those cases through code proposed by the LLM could go a long way towards improving this.
For now it seems mainly useful as a way of getting a quick first draft of some code which I then have to fix up and get fully working myself.
2. How much would you pay?
Previous discussion: https://news.ycombinator.com/item?id=29481061
Hilfinger?
In the US, it's common for schools to start at 8:00 or even 7:30. Recently there has been a push to start later to give kids more time to sleep. So pushing it back to say 8:30 or 9:00 (but not shortening the day, so basically everything just gets pushed back, and the kids stay up later, and need more time to sleep...).
noun, 3c: "a person who carries through an enterprise by skillful or artful contrivance"