"Why Omnesoft / Why this role?"

It's less about something missing and more about scale of ownership. At Artlist I work on one part of a large product with a large team. The architectural decisions get made at higher levels and I implement against them. At an earlier stage, I'd be making more of those decisions myself — picking patterns, defining structure, raising the bar on the team. That's the experience I want to build in my next chapter.

It's also true that I've been there for a while. Sometimes the most growth happens when you change context.

I haven't worked in ERP directly. What appeals to me is the combination of a traditional industry — manufacturing, fabrication — with a product-led modern approach. Vertical SaaS into a domain that hasn't been fully transformed yet means the customer pain is real, the workflows are concrete, and the impact of a good interface is measurable. That's a different kind of satisfying than building yet another social or content app.

And technically, the frontend challenges — large grids, complex state, performance at scale, accessibility for daily-use enterprise tools — are exactly the kinds of problems I enjoy.

From your site and the careers page: you're building a modular ERP — Omne — focused on discrete manufacturing, with modules for inventory, production, scheduling, and partner management. You position yourselves as the modern alternative to legacy ERP systems that are slow and outdated. You're remote-first, global team, and you're hiring across roles right now — six open positions including this one — which suggests you're scaling.

I also noticed you exhibited at FABTECH 2025, which tells me you're not just a stealth startup — you're actively in the market with paying customers or close to it.

What I'd love to learn from you: where you are in terms of stage and traction, and what the frontend looks like today versus where you want to take it.

Timing-wise, I'm at a point where I want to make my next move intentionally rather than waiting for circumstances to push me. So I'm being selective and looking for a few specific things: earlier stage, real product, real customers, technical depth in the frontend. This role hits all four. The stack is also a good match — modern React, TypeScript, Tailwind, plus complex data interfaces. There aren't a lot of roles that combine all of that.

Honest answer: I've worked in monorepo setups and I'm familiar with the architectural patterns Nx solves — module boundaries, affected commands, computation caching, library isolation. I haven't shipped a production Nx app, but the conceptual model is familiar and I'd ramp quickly.

For AG Grid specifically — I've worked with virtualized data grids and the patterns around them, but haven't shipped AG Grid in particular. That's something I'd dig into early. I'm not going to claim deep familiarity I don't have.

What I do bring is the underlying skills these tools require: React performance, large-data rendering, working with complex column-based UIs. Those transfer.

I'm having early conversations with a few teams to understand what's out there. I'm not committed to any particular process and I'm not trying to manufacture a bidding war — I just want to make a thoughtful decision. If the fit is right with Omnesoft, I'd move forward seriously.