LyzrArchitect 2.0 / hiring

Technical Product Manager · Architect

Build your own vibe-coding platform

One assignment. If you're shortlisted, direct interview.

Start here

Check out architect.new, the platform you'll be building the next version of.

Open architect.new ↗

What to do

1Explore

Take reference from these platforms:

architect.newReplitLovableEmergentVercel v0Rocket.newCursorCodexClaude Codeor any other coding agent / vibe-coding platform

Understand every feature of each one:

  • What makes each one different?
  • Why are people using it?
  • What features does each platform have?
  • The UI, the UX, the user flows, everything

2Build

Build Architect 2.0: a vibe-coding platform for both technical and non-technical users, where a user can:

  • Build an entire agentic application just by prompting
  • Import an existing project and keep working on it in Architect
  • Build agents in any framework
  • Connect GitHub to their app
  • Deploy the app
  • …and anything else you think it needs

Keep in mind:

  • Architect 2.0 should have all the features of the current Architect. But today's Architect only caters to non-technical folks. The new version should also cater to technical folks, like developers. Think about what additional features it needs to serve both audiences.
  • Focus more on the UI/UX and the flow of the entire app, from authentication to deploying the app, and how every feature flow would look for the user.
  • All the features you're adding to your application don't need to be fully functional. You can just create dummy flows to show how the user flow would look for each and every feature you add.
  • If you can make some basic functionality work, like authentication and the database, that's a plus point. Otherwise, dummy flows are good enough.

3Ship

Deploy it and share the live URL with all the major features in place, along with the GitHub repo, in the Submit tab.

How we'll judge it

In order of importance

Design, UI/UX & flows

Most important

Good design and product sense are a must for our product. Think through everything from the user's perspective, down to the small things: where each button sits, which pages and sections exist, the layout, and how one step leads to the next.

Think from first principles. Don't copy the current Architect's UI/UX, or any other platform's. We want to see first-principles thinking: start from what the user needs, then design the flow. If you think of something better, or want to experiment, go for it.

Feature coverage

High

Cover every feature a platform like this needs. Dummy flows are fine, as long as each one shows your product thinking and design.

  1. 01Authentication
  2. 02Homepage
  3. 03Chat window
  4. 04App preview
  5. 05Agent section
  6. 06UI getting built
  7. 07GitHub integration
  8. 08Deploying the app
  9. + anything else you can think of

Don't stop at this list. These are just a few examples. Think holistically from the user's perspective: what would technical folks need, and what would non-technical folks need?

Working functionality

Plus points

Not required. But making a few basic things work, like a database or Google sign-in, earns plus points. This is just to test your technical capabilities and how many things you can actually make functional.