Hard to give good feedback, because we don't know what the software is trying to accomplish. Enterprise is all about form following function.

• It's clean visually, but as others have said the angle makes it hard to critique
• Contrast is not accessible in the nav and possibly other areas
• Consider a humanist sans (Roboto, Open Sans etc) typeface, which is more readable than geometric sans.
• Use real titles, esp in your main nav. Long words won't fit there
• A lot of vertical space is used on the right for whatever is in light gray. Technical users typically prefer compact UIs

It is not as accessible for some sight-impaired individuals.

Yes. I did an email deck and an in-person deck. I don't have time to code up a new portfolio site (though I've had one in-progress for like 6 months). Downside is less visibility. You are depending on active recruiting to get your deck in front of the right people. A deck is also slightly higher friction for the hiring manager to go through. (Protip: short link or domain that redirects to your deck link)

You will likely still need to do a design challenge.

Do you work for Netlify per chance?

HP Z27 4K is a fantastic monitor. Just got one, alongside my old Displayport Cinema display. I'm probably going to replace the Cinema display with another Z27.

That was a joke

What is this "digg" thing?

Hype is pretty great for what you're describing as complex animations.

Transitions between pages is a different beast. The CSS is straightforward, but the javascript is very framework dependent. This is a good overview of the challenge and the options out there for static content.

It's great that you got one done in your company!

Sprints are for solving big problems, not for run of the mill feature work. I don't think there's any company that operates regularly on that schedule. We've run 20+ sprints with different teams in our company over the past 1.5 years. No two sprints are the same, and we almost never use the entire GV playbook. Rather, we tailor exercises from GV, IDEO, and Luma to fit the needs of the problem we're trying to solve and the design maturity of the product team.

The point of sprints and "design thinking" in general is to get product teams out of the Gartner magic quadrant / feature-train mindset, and instead to approach the challenge from a problem-first perspective.

The important thing is to use sprints as another tool that you can pull at the right time to solve the right kind of problems. They aren't a substitute for long-term discovery/research projects, design iteration, data science, or usability testing.

UXPin is doing some interesting work here. Then there's the old standby – Axure, which has had this for years.