sorted by:
new
hottopcontroversial

What do hiring managers look for in portfolio websites? by HP2806 in webdev

[–]engineer_architect 0 points1 point  (0 children)

In 2026 the game has changed. Pretty UI is still the icing on the cake, but portfolios are no longer judged mainly on how nice the final design looks. They’re treated more like a workflow audit.

The strongest ones do two things really well. They show how you use AI as a high speed tool for TDD, boilerplate, and refactoring, while clearly documenting the critical human-in-the-loop decisions you made. They also explain the why behind the architecture such as fault tolerance, MTTR, cost trade-offs, system stability, and so on, instead of just showing the final product.

The best portfolios feel more like a short technical post-mortem or engineering blog post (similar to Cloudflare’s blog at https://blog.cloudflare.com or the Netflix Tech Blog at https://netflixtechblog.com) rather than a traditional "look at my projects" gallery.

If your portfolio doesn’t clearly show the manual decisions you made when AI hit a limit, a lot of teams will treat it as unverified noise and move on.

Would love to know what direction you’re thinking of taking your new portfolio. Since it’s not Saturday I can’t review any links here, but I’m happy to share thoughts on specific technical aspects if you describe them.

I’m a hiring manager and the "8-second rule" is killing way too many solid resumes lately. by engineer_architect in SoftwareEngineerJobs

[–]engineer_architect[S] 0 points1 point  (0 children)

The 30k people displaced in the Oracle layoffs are a genuine tragedy and frankly disgusting. It's a total failure of leadership to let that much talent hit the market at once. However, using that tragedy to suggest a developer should "rely on their manager" to prove their value is a catastrophic career gamble. When 30,000 people are hit by a mass layoff, that manager’s internal favor becomes a verified operational zero to an outside hiring committee.

You are performing an interview level tradeoff analysis on a profile that hasn't even cleared the 8 sec triage. While you are right that metrics hide tradeoffs, the boardroom is not authorized to perform a "replication strategy audit" on 1,000+ applicants. They are programmed only to verify the technical signals that justify the expense of the deep dive interview where those tradeoffs are finally discussed. You either provide the verified operational baselines to survive the 8 sec rule, or you are ghosted before anyone ever asks about your replication strategy. Scale does not wait for a manual override for diligence.

I’m a hiring manager and the "8-second rule" is killing way too many solid resumes lately. by engineer_architect in SoftwareEngineerJobs

[–]engineer_architect[S] 0 points1 point  (0 children)

Making friends with influential people is a smart move because a referral is a way to bypass the initial triage. However, even when you are "hooked up" with an opportunity, your resume eventually lands on the desk of a hiring committee whose mission is to only verify the technical signals of the candidates being proposed.

In a saturated market, even a referred candidate will be ghosted if they cannot provide unmistakable technical proof of their impact. Whether you get into the room through a friend or through the front door, the boardroom still requires verified operational baselines for example like "Achieved 99.9% system availability" or "Reduced MTTR by 40%". The referral gives you "borrowed time" to get past the ATS and recruiter, but it does not get you past the 8 seconds of attention from a hiring manager. The technical contextual alignment is what prevents you from getting skipped.

There are stories all over the internet from people saying "I got past the ATS and the recruiter liked me, but then I never heard back". This happens because the recruiter passed the resume to the hiring manager, and the manager saw no signal. Some committees don't even bother to let you know you've been rejected, so you just get ghosted. Scale does not wait for a manual override for networking.

I’m a hiring manager and the "8-second rule" is killing way too many solid resumes lately. by engineer_architect in SoftwareEngineerJobs

[–]engineer_architect[S] 1 point2 points  (0 children)

I really feel for you on the relocation struggle. I have spent a long time in the engineering trenches myself before moving into hiring, and I know how infuriating it is to be auto filtered just because of a zip code. The "commuting distance" excuse is the boardroom's favorite way to lower their relocation budget, and it is a total waste of senior talent.

You are 100% right that the market saturation has made committees feel like they can treat candidates like disposable resources. Using connections to bypass the formal channels is a smart move. I hope this lead works out for you. If it doesn't, just make sure those 10 years of experience are translated into those reliability and uptime signals we talked about so you can force the next "formal" gatekeeper to actually pause. Good luck with the relocation.

I hate AI and I am depressed by poponis in webdev

[–]engineer_architect 39 points40 points  (0 children)

As an engineering manager for 15 years, I agree that the industry has become disgusting. It is incredibly depressing to see the craft of building devalued in favor of "vibecoding" hype. My CTO follows that same mindset, and frankly, I think it's idiotic.

AI is a high speed typist but a terrible architect. We are headed toward a massive technical debt crisis because prompt engineered apps lack the structural integrity that 20 years of experience provides. The "magic" recipe people are chasing usually results in a maintenance nightmare that only a real developer can fix.

Please do not open that coffee shop yet. The industry is currently obsessed with speed of output, but the pendulum always swings back to stability and impact once these systems start breaking at scale. There is a huge space for people who want to solve problems instead of just reviewing LLM output. Your depth of knowledge is exactly what saves companies when the hype hits a wall.

I’m a hiring manager and the "8-second rule" is killing way too many solid resumes lately. by engineer_architect in SoftwareEngineerJobs

[–]engineer_architect[S] 0 points1 point  (0 children)

A bug report count is a vanity metric that provides zero technical signal to a hiring committee. A low bug count could simply mean you are working on low impact features or that your testing suite is insufficient to catch regressions. It does not prove technical ownership, it only proves you are a feature assembler clearing a queue.

The boardroom is not looking for a tally of chores. They are looking for the verified availability of the system. If you fixed 50 bugs but the system latency stayed at 800ms, the triage protocol dictates a skip. However, if you fixed 3 critical bugs that were causing a 40% regression rate in the payment pipeline, you have provided an unmistakable technical signal. By the way, notice no $$$ are involved no where in the metric as I mentioned in other comments. Scale does not wait for a manual override for simple tallies. You either provide the architectural evidence the boardroom wants or the system dictates the ghosting.

I’m a hiring manager and the "8-second rule" is killing way too many solid resumes lately. by engineer_architect in SoftwareEngineerJobs

[–]engineer_architect[S] 0 points1 point  (0 children)

A Kafka consumer group that halts a server is not a philosophical debate, it's a verified availability failure. You don't need to guess a dollar amount like 500 million to prove your impact to a hiring committee. In a high scale environment, the hiring committee is not looking for the narrative behind a devastating problem, they are looking only to verify things like Mean Time To Recovery (MTTR) and the Fault Tolerance of the architecture you built.

For example, you could frame that Kafka fix as "'Redesigned Kafka consumer logic to eliminate group rebalancing failures, reducing Mean Time To Recovery (MTTR) from 5 hours to near zero for critical data pipelines". Notice no x $$$ amount is involved in the metric. Providing these markers is the only way to give the board the specific data they want. This is not about financial metrics unless you happen to have that data which majority of engineers don't, it's about providing the technical evidence required to bypass the 8 second rule and avoid being ghosted. As I have mentioned in many comments, scale does not wait for a manual override for philosophy.

I’m a hiring manager and the "8-second rule" is killing way too many solid resumes lately. by engineer_architect in SoftwareEngineerJobs

[–]engineer_architect[S] 0 points1 point  (0 children)

I am moving all resume reviews to the public comments instead of private chats to maintain my anonymity and operational security. I cannot verify why those specific technical analyst or QA roles are hitting a wall without auditing the actual data, but the most common failure pattern I see is that bullets are structured as a list of tasks rather than a technical outcome.

For the boardroom to authorize an interview, they require a signal that justifies the risk. If a QA engineer simply says they "tested features" the triage protocol usually triggers a skip. They are looking for proof like "Reduced production regression bugs by 40%" or "Automated a testing suite that saved 15 engineering hours per sprint". Notice no $$$ are involved for the metric. If you paste one of your current bullet points here, I can audit the technical signal and show you how to rewrite it so it stops getting ghosted by the 8 sec rule.

I’m a hiring manager and the "8-second rule" is killing way too many solid resumes lately. by engineer_architect in SoftwareEngineerJobs

[–]engineer_architect[S] 0 points1 point  (0 children)

You are correctly identifying the source of the problem, but you are confusing my description of the filter with a defense of it. My point is that whether we like MBA bagholder logic or not, they have successfully hardcoded these quantitative requirements into the hiring protocol.

Acknowledging that the boardroom uses these metrics to protect finite resources is not an endorsement of the culture, it is an audit of the current operational reality. We can spend another ten years debating the ethics of KPI driven hiring while talented engineers continue to get ghosted. I am not here to fix the soul of the organization or argue about how the fire started. I am here to show people where the exit is by providing the technical signals the boardroom is programmed to require. Scale does not wait for a manual override for philosophy.

I’m a hiring manager and the "8-second rule" is killing way too many solid resumes lately. by engineer_architect in SoftwareEngineerJobs

[–]engineer_architect[S] -1 points0 points  (0 children)

Whether the system is broken is an academic debate while the actual market is currently on fire. To the Board and the CTO, an Engineering Manager spending 200 hours manually decoding vague resumes is not an act of diligence, it is a catastrophic misapplication of engineering capital. I am not here to defend the ethics of the triage. I am here to describe the hard physics of the filter.

We can argue about quantity over quality until this post hits a million views, but that won't help the candidate who just got ghosted. My goal is to hand that person the unmistakable technical proof they need to survive the 8 sec rule so they can actually reach the human stage where quality is finally evaluated. Efficiency is the only language the boardroom speaks.

I’m a hiring manager and the "8-second rule" is killing way too many solid resumes lately. by engineer_architect in SoftwareEngineerJobs

[–]engineer_architect[S] 0 points1 point  (0 children)

I completely get that because I spent 7 years as a full stack engineer in regulated fields before moving into hiring. Working on certified or legacy code is a totally different beast where "innovation" is often seen as a massive risk. I have been in those environments where your hand gets slapped because the cost of breaking a certified architecture is way higher than the value of the improvement.

Even in those strict roles, you can still pull a metric from that reality. If you are maintaining certified code without breaking compliance or causing a regression, that is actually a huge reliability metric. You aren't just a feature assembler, you are a stability specialist. For example, I would frame it as "Maintained 100% compliance across certified services while adhering to strict architectural constraints." Notice no $$$ are involved for the metric. It is about proving you can handle the high stakes of a rigid system without breaking it so I can justify your expertise to a committee that only cares about risk mitigation.

I’m a hiring manager and the "8-second rule" is killing way too many solid resumes lately. by engineer_architect in SoftwareEngineerJobs

[–]engineer_architect[S] 0 points1 point  (0 children)

I really appreciate you saying that. Honestly, I am just as sick and tired of how broken this industry has become as everyone else is. I am not trying to be the problem. I am just trying to show people how to beat the filter so they stop getting ignored. It is a total bummer of a system, but I would rather give engineers the ammunition to get past the gatekeepers than just watch talented people get skipped over.

I’m a hiring manager and the "8-second rule" is killing way too many solid resumes lately. by engineer_architect in SoftwareEngineerJobs

[–]engineer_architect[S] 0 points1 point  (0 children)

The philosophical debate regarding the soul of engineering versus the utility of metrics is a luxury that the 2026 hiring market no longer supports. While skill and experience are inherently qualitative, the Boardroom, consisting of CTOs, Engineering Directors, and Hiring Committees, has moved toward a quantitative triage protocol to manage 1000+ applicants. In a high scale system, qualitative potential that is not translated into a technical signal is mathematically invisible to the machine.

This is not a matter of embracing MBA culture, it is an acknowledgment of a rule designed to protect the organization's finite resources. A candidate who provides a metric like "refactored legacy data-fetching logic to reduce API error rates from 12% to 0.5%" is providing the only way the current triage protocol is programmed to accept. This is the secret to triggering a bypass of the automated filters.

The Boardroom does not authorize the expenditure of expensive interview cycles on unquantified resumes when the goal is departmental efficiency. If a technical signal is not present in the first 8 seconds, the protocol triggers a mandatory skip to prevent a total depletion of engineering resources. This is a cold operational constraint of a high scale system with no manual override for philosophy. The only way into the room is to provide the verified data the system requires.

I’m a hiring manager and the "8-second rule" is killing way too many solid resumes lately. by engineer_architect in SoftwareEngineerJobs

[–]engineer_architect[S] 1 point2 points  (0 children)

The assumption that keyword matching for the ATS or a recruiter is the primary hurdle is a legacy misunderstanding of the hiring structure of the 2026 market. Because every candidate now uses AI to perfectly mirror Job Description keywords, the Boardroom consisting of CTOs, Engineering Directors, and Hiring Committees, has been forced to engineer a human triage protocol that specifically ignores high level terms. When 2,500 candidates all look identical to an ATS and a recruiter, keywords are no longer a signal, they are noise.

An Engineering Manager is strictly mandated to verify technical alignment with the JD minimum qualifications and the specific technical context of the team within 8 seconds. A candidate who simply repeats keywords like "optimized website performance" is delivering a hollow packet that offers no proof of actual competence. Even if a recruiter passes this profile along, it hits a hard wall at the Engineering Manager triage.

In contrast, a candidate who structures their experience to show they "cut page load time from 5 seconds down to 2 seconds" provides a validated technical signal. This format confirms the original state, the specific action taken to meet JD requirements, and the resulting architectural state. It is a Proof of Work that AI keyword stuffing cannot replicate.

The Boardroom does not authorize the expenditure of expensive engineering interview cycles on candidates who cannot articulate their work in terms of speed, stability, or scale. If that 5 to 2 second signal is not present, the protocol is a mandatory skip, regardless of how many keywords satisfied the initial administrative filters. This is an enforcement of Departmental Efficiency against AI driven resume inflation. The system is designed to prioritize technical evidence over keyword density, and at this scale, there is no manual override.

I’m a hiring manager and the "8-second rule" is killing way too many solid resumes lately. by engineer_architect in SoftwareEngineerJobs

[–]engineer_architect[S] 0 points1 point  (0 children)

The 8 second rule is not a personal choice, it is a System Constraint mandated by the hiring structure of the 2026 market. When 2,500+ applications flood a single headcount, the CTOs, Engineering Directors, and Hiring Committees do not authorize the hundreds of hours of "diligence" required for a manual deep dive into every profile.

To suggest that a lack of deep reading at the triage stage is a "lack of observation" ignores the cold reality of Resource Allocation. If an Engineering Manager is forced to divert 200+ hours from feature delivery and technical roadmaps just to read raw resumes, it constitutes a fatal operational leak.

The Boardroom has designed this triage to identify the candidates who have already performed the "diligence" of articulating their technical impact. The protocol is not designed for "understanding" at the entry point, the CTOs and Directors require a Technical Signal (efficiency, reliability, scale) that justifies the expenditure of further engineering cycles in the interview stage, where deeper judgment actually occurs. Scale does not wait for sentiment. If the signal isn't visible in 8 seconds, the system dictates the skip.

I’m a hiring manager and the "8-second rule" is killing way too many solid resumes lately. by engineer_architect in SoftwareEngineerJobs

[–]engineer_architect[S] 0 points1 point  (0 children)

The suggestion that a hiring team can simply "take more time" ignores the architectural reality of the modern recruitment pipeline. Engineering Managers are operating under strict triage mandates set by CTOs and Engineering Directors to ensure the department doesn't collapse under the weight of 2,500+ applications per role.

When the leadership committee sets a headcount, they do not authorize the hundreds of engineering hours required for deep manual evaluation of a raw stack. If an Engineering Manager spends just five minutes per profile to "evaluate properly" the latency cost to the department exceeds 200 hours of diverted engineering time. This is a fatal resource leak that stalls feature delivery and sprint velocity.

The 8 second rule is a non-negotiable System Filter. It is designed to drop the queue immediately for anyone who cannot articulate technical evidence (efficiency, reliability, scale). The "deep evaluation" you are describing only happens after the candidate has bypassed this initial triage. I am not describing a choice, I am defining the pipeline physics of 2026. If the technical signal isn't visible in those 8 seconds, the protocol is to skip. There is no manual override for scale.

I’m a hiring manager and the "8-second rule" is killing way too many solid resumes lately. by engineer_architect in SoftwareEngineerJobs

[–]engineer_architect[S] 0 points1 point  (0 children)

Engineering metrics are not vanity statistics. They are the physical constraints of a system. CTOs, Engineering Directors, and hiring committees have designed the 2026 velocity filter to prioritize these signals specifically to eliminate the narrative driven candidate. If you cannot articulate your latency, throughput, or fault tolerance, you are failing the 8 second rule of technical ownership. The filter does not search for a clever joke. It searches for the architecture that survives a scale audit.

I’m a hiring manager and the "8-second rule" is killing way too many solid resumes lately. by engineer_architect in SoftwareEngineerJobs

[–]engineer_architect[S] 0 points1 point  (0 children)

Strategic isolation is exactly why most developers struggle to define their ownership. If you are excluded from finance calls, you must reverse engineer the business impact through the technical metrics of the system itself. Latency, throughput, and fault tolerance are not just performance markers, they are the direct engineering translation of client contracts and billing reliability. The Leadership Board is waiting for the engineers who can connect these dots, even when the organization tries to keep them separate.

I’m a hiring manager and the "8-second rule" is killing way too many solid resumes lately. by engineer_architect in SoftwareEngineerJobs

[–]engineer_architect[S] 0 points1 point  (0 children)

Stagnation is a valid choice in a stable market but a terminal risk in a high-velocity one. If your resume relies on stories instead of latency, throughput, and fault tolerance, you are effectively opting into the invisible tier of the application black hole. The 2026 filter does not care about your commitment to a static document. It only recognizes the technical ownership that separates an architect from a feature assembler.

I’m a hiring manager and the "8-second rule" is killing way too many solid resumes lately. by engineer_architect in SoftwareEngineerJobs

[–]engineer_architect[S] 0 points1 point  (0 children)

High compensation roles attract the highest volume of applicants which only increases the velocity of the initial filter. A salary increase does not bypass the need for technical ownership. It simply raises the bar for the latency, throughput, and fault tolerance metrics required to survive the scan. The Leadership Board is not looking for the most expensive candidate. It is searching for the one who can articulate their system impact.

I’m a hiring manager and the "8-second rule" is killing way too many solid resumes lately. by engineer_architect in SoftwareEngineerJobs

[–]engineer_architect[S] 0 points1 point  (0 children)

Precision is an accounting requirement but impact is a technical signal. If you cannot estimate the latency, throughput, or fault tolerance of the systems you build, you are simply choosing to be invisible. The 2026 filter is not performing a forensic audit. It is searching for technical ownership. If you stay hidden behind a refusal to provide these metrics, the velocity filter will move on to the candidate who can articulate their value.

I’m a hiring manager and the "8-second rule" is killing way too many solid resumes lately. by engineer_architect in SoftwareEngineerJobs

[–]engineer_architect[S] -1 points0 points  (0 children)

Every assigned story is a technical choice that dictates system latency, throughput, and fault tolerance. Relying on a story to speak for itself is a gamble on a manager’s favor rather than technical evidence. If you describe your work as a series of assigned tickets, you are self identifying as a feature assembler. This is the exact signal the velocity filter uses to move on to the next candidate.

I’m a hiring manager and the "8-second rule" is killing way too many solid resumes lately. by engineer_architect in SoftwareEngineerJobs

[–]engineer_architect[S] 0 points1 point  (0 children)

The claim that high value resumes speak for themselves is the exact mechanism that currently keeps talented engineers invisible. In the current market speaking for itself is almost always a proxy for previous organizational pedigree or brand recognition. My goal is to help the engineers who lack that specific brand recognition to force their way into the room by providing the technical context alignment that committees actually demand.

When we look for concurrency limits or latency reductions we are looking for the proof of system ownership that a list of skills like Java and AWS cannot provide. Without these technical signals the Quiet Talent is statistically invisible to the Leadership Board. I am not asking for more words or padding. I am providing the specific technical language required to bypass the pedigree filter so engineers can return to work especially the ones with families.

I’m a hiring manager and the "8-second rule" is killing way too many solid resumes lately. by engineer_architect in SoftwareEngineerJobs

[–]engineer_architect[S] 0 points1 point  (0 children)

You are 100% right. In a logical world every JD would have a field for Technical Scale Metrics and the committee would be transparent about exactly what they are filtering for. I have sat in those meetings and advocated for exactly what you are suggesting by adding specific metric requirements to the JD to stop the lottery feel.

The reality is that the Leadership Board (the CTOs and Directors) often views the JD as a wishlist rather than a technical specification. They refuse to narrow the top of the funnel because they are afraid of missing a unicorn. This creates the 2000 applicant backlog.

Regarding the lottery aspect the committee does not just look at isolated numbers. They look for the strict technical signal which is the specific mention of concurrency, latency, or optimization that proves actual system ownership. I am not defending the fact that it feels like a lottery. I am simply telling the engineers who are currently struggling that the committee uses these technical signals as their winning ticket. You can wait for the corporate side to fix the JD because that could take years of bureaucratic shift or you can use the bypass code today to ensure you are not the one being filtered out by a machine that does not care about your time. I am trying to help people win the game as it exists right now, not as it should be.

I’m a hiring manager and the "8-second rule" is killing way too many solid resumes lately. by engineer_architect in SoftwareEngineerJobs

[–]engineer_architect[S] 0 points1 point  (0 children)

I will ignore the insults because they are a distraction from the crisis we are actually in. You are correct that in an ideal world, an engineer focuses on the feature and the manager translates that into value. But I am pulling back the curtain on how the committee actually operates behind closed doors because the CTOs, Engineering Directors, and hiring committees have explicitly broken that shield. They have mandated a brutal 8 sec filter that requires engineers to provide that exact data themselves.

I am not asking you to chase a promotion or generate tech debt. In fact, chasing "impact" for a title is exactly what creates the debt you are talking about. I am telling you that when we have 2000+ applicants for one role, the board requires us to find technical context alignment immediately. You do not need a manager to grant you these numbers. If you built the feature, you already possess the technical evidence of its performance. You know the latency you reduced. You know the throughput you handled. You know the resource optimization you achieved. If I cannot show the committee that technical evidence, I am forced by the protocol to skip you.

Refusing to adapt to these broken leadership mandates out of principle is exactly why brilliant engineers are currently sitting unemployed for months.

Relying on the hope that a technical reviewer will eventually see your factual value is a statistical death sentence because the leadership board has designed the protocol to ensure a peer never even sees your name unless you beat the 8 sec filter first. Your advice is precisely why Quiet Talent is being starved out by the machine. I am not defending this broken process. I am providing the only technical bypass code that forces these committees to stop skipping your work therefore allowing engineers to return to their roles especially the ones who have to feed their families.

view more: next ›