Founding Engineer Web & Mobile Apps Architecture

BUILDING THE EXECUTION LAYER FOR WORK

We're building the brain that runs a company's work... not another app, the reasoning layer above all of them. It senses what's happening across every tool, remembers, and acts. The hard part isn't the UI; it's making an AI reason over a live work-graph and be trusted to act. That problem is wide open, and it's ours to win. Small team, real product, huge scope. You'd own a piece nobody's solved yet.

Every productivity app on your screen is individually excellent and collectively blind. They don't share a mind, so you become the integration layer carrying context between tools in your head, paying for it in attention every day. WorkElate is the AI-native Work Execution OS: one organism wearing eleven faces, One Brain that remembers everything, sees across everything, and acts with provenance.

The body is built. The brain's substrate is laid. The hard part the memory-and-deep-context engine that compounds with use and flattens its own cost curve is the work ahead. That's the part that turns a category-leading product into a generational company. That's the part we're hiring for.

We'd rather earn your conviction with what's true than your applause with what isn't. So here's the honest version of who we are.

What we run on: MAGIC

M_Momentum. We ship, measure, and ship again. In one recent build session, the team wired an entire app into the orchestrator, proved it with live end-to-end tests, and caught three real bugs mocked tests would've hidden because momentum without verification is just motion.

A_Ambition & Accountability. We aim at a trillion-dollar category, and we own the gap between vision and reality in public. Our own whitepaper marks what's shipped vs. roadmap, line by line. Ambition writes the check; accountability makes it cashable.

G_Grit & Growth. We do the unglamorous, load-bearing work: multi-tenancy, durability, the cost curve. The hard middle is boring, and it is exactly where moats get built. If you only want the demo-friendly parts, this isn't the room.

Innovation & Initiative. We build the thing nobody else is building: optimal memory instead of the thing everyone's racing to ship: more memory. Initiative here means you see the load-bearing problem and take it, unassigned.

C_Commitment to Customer-Centricity. We meet operators where they are — on email, not a portal and we solve the pain no incumbent will touch: chasing the client for them. The customer's real day is the spec.

Who we're looking for

• Engineers who reach for the hard, unglamorous middle tenancy, durability, work surface that screenshots well.
• People who state trade-offs out loud and commit, instead of hedging every claim.
• Builders who verify. "It compiled" isn't done; "I drove it end-to-end and watched it work" is.
• Anyone who'd rather own one load-bearing problem than touch ten shallow ones.

How we don't work

• No theater. We don't ship status updates to prove we worked — the work emits its own signal.
• No demo-driven development. If a test passes on mocks and fails on reality, the test lied.
• No poster values. If a value here can't change a real decision, it's not a value; it's décor.

So

The AI-native rewrite of office productivity will be won by whoever owns the execution layer, the context graph plus the action loop across an organization's work. It's winner-take-most, because context compounds and switching cost grows with every memory. We intend to own it: surface by surface, memory by memory, by being the team that tells the truth, builds the hard part, and never confuses a demo with a moat.

If that's the company you want to build, come build it.

What you'll own

• The core document model and CRDT/OT architecture across all editing surfaces.
• Real-time multiplayer infrastructure: presence, cursors, conflict resolution, offline-first sync.
• The plugin/block architecture that lets every surface (doc, sheet, slide, board) compose from shared primitives.
• Performance and reliability budgets every keystroke, every collaborator, every device.
• The interfaces AI agents use to read, mutate, and reason over documents.
• Production frontends for 2–3 surfaces at any given time (Docs, Mail, Tasks, Hub, etc.).

Bonus signals

• Experience at Notion, Figma, Linear, Google Docs, Coda, Airtable, Quip, or similar.
• Open-source contributions to editor or sync libraries.
• You have an opinion about why Google Docs' editor architecture has held it back for the AI era.
• Built or contributed to a popular UI library, framework, or developer tool.
• Experience at companies known for frontend craft (Linear, Vercel, Stripe, Figma, Arc, Raycast, Notion, etc.).
• Comfortable in WebGL/Canvas useful for the Whiteboard surface.
• First 90 days
• Day 30 - Clean Architectural spec for the unified WorkElate document model, all apps operating smoothly for a small team of 20.
• Day 60 - Multi user 5-6 apps surface working end-to-end with concurrent editors and offline reconciliation.
• Day 90 - Implement second surface in all apps running on the same model, demonstrating the architecture's leverage.

Compensation

Founding equity: up to 2%. Finalized during the interview process. Monthly salary will be between (INR ₹30k–45k/month). We intend to be the highest-equity, highest-leverage one.

How to apply

• Fill out the form with the intent and various work exposures you have
• Send a 60–90 second Loom answering: "What's the one decision in editor architecture that most teams get wrong, and why?"
• Include a link to code, a system you've designed, or a write-up that shows how you think.

Email: teams@workelate.com

Subject line: "Founding Engineer"