Founding Engineer Rust (Full remote)

Other Jobs To Apply

No other job posts for this day.

Our client is building the operating system for autonomous businesses.<br><br>They build autonomous AI agents that run entire parts of a business. Not workflow automations, agents that learn, adapt, recover from errors, and make decisions. Built in Rust.<br><br>In just weeks of beta, over 100,000 AI agents have been deployed on their platform - automating trading systems, service businesses, workflows, and internal operations. Backed by a $10M seed round, they are redefining how companies run: AI agents connected to Slack, email, CRMs, payments, calendars, and beyond.<br><br>This is not incremental innovation. This is infrastructure for the next generation of digital companies.<br><br>They are moving fast. Very fast.<br><br><strong>Job Description<br><br></strong><strong>What we're looking for<br><br></strong>We're hiring a <strong>founding engineer</strong> with entrepreneurial experience. You've built and shipped a product of your own as a founder, co-founder, or solo technical lead of an early-stage venture. You carried it: architecture decisions, production debugging, shipping under pressure, wearing every hat. Whether it was acquired, wound down, or is behind you for other reasons, you came out of it with deep judgment and the drive to build again.<br><br><strong>Profile / Requirements<br><br></strong><strong>What matters to us<br><br></strong><ul><li> Strong systems programming skills in Rust, Go, or C++, used regularly in your current or recent work</li><li> Production experience — you've built and operated systems used by real people, not just prototypes or demos</li><li> Active builder — you're currently shipping work we can look at (open-source contributions, personal projects, public repos)</li><li> End-to-end ownership mindset — you think about product outcomes and business impact, not just code</li><li> Comfort with ambiguity — you've made architectural decisions without a spec and lived with the consequences<br><br></li></ul><strong>Domains We Care About<br><br></strong>AI agents, browser automation, LLM infrastructure, distributed systems, developer tooling. If you're building in one of these, we're especially interested.<br><br><strong>What The Role Looks Like<br><br></strong>You own systems end-to-end — architecture, implementation, production, and consequences. Small team, high intensity, minimal process. You define the approach rather than waiting for direction. Remote-friendly<br><br><strong>How We Evaluate<br><br></strong>No algorithmic puzzles. We assess four things:<br><br><ul><li> Systems-level depth — real concurrency, async, memory and performance awareness</li><li> Shipped work — production systems used by real people</li><li> Autonomy under ambiguity — evidence of independent architectural judgment</li><li> Product ownership — you care about what the system does for users, not just how it's built<br><br></li></ul><strong>Benefits<br><br></strong><ul><li> Equity</li><li> 40 hours per week</li><li> 100% Remote</li><li> Direct exposure to cutting-edge AI infrastructure</li><li> Work alongside product and engineering teams shaping autonomous systems</li></ul>

Back to blog

Common Interview Questions And Answers

1. HOW DO YOU PLAN YOUR DAY?

This is what this question poses: When do you focus and start working seriously? What are the hours you work optimally? Are you a night owl? A morning bird? Remote teams can be made up of people working on different shifts and around the world, so you won't necessarily be stuck in the 9-5 schedule if it's not for you...

2. HOW DO YOU USE THE DIFFERENT COMMUNICATION TOOLS IN DIFFERENT SITUATIONS?

When you're working on a remote team, there's no way to chat in the hallway between meetings or catch up on the latest project during an office carpool. Therefore, virtual communication will be absolutely essential to get your work done...

3. WHAT IS "WORKING REMOTE" REALLY FOR YOU?

Many people want to work remotely because of the flexibility it allows. You can work anywhere and at any time of the day...

4. WHAT DO YOU NEED IN YOUR PHYSICAL WORKSPACE TO SUCCEED IN YOUR WORK?

With this question, companies are looking to see what equipment they may need to provide you with and to verify how aware you are of what remote working could mean for you physically and logistically...

5. HOW DO YOU PROCESS INFORMATION?

Several years ago, I was working in a team to plan a big event. My supervisor made us all work as a team before the big day. One of our activities has been to find out how each of us processes information...

6. HOW DO YOU MANAGE THE CALENDAR AND THE PROGRAM? WHICH APPLICATIONS / SYSTEM DO YOU USE?

Or you may receive even more specific questions, such as: What's on your calendar? Do you plan blocks of time to do certain types of work? Do you have an open calendar that everyone can see?...

7. HOW DO YOU ORGANIZE FILES, LINKS, AND TABS ON YOUR COMPUTER?

Just like your schedule, how you track files and other information is very important. After all, everything is digital!...

8. HOW TO PRIORITIZE WORK?

The day I watched Marie Forleo's film separating the important from the urgent, my life changed. Not all remote jobs start fast, but most of them are...

9. HOW DO YOU PREPARE FOR A MEETING AND PREPARE A MEETING? WHAT DO YOU SEE HAPPENING DURING THE MEETING?

Just as communication is essential when working remotely, so is organization. Because you won't have those opportunities in the elevator or a casual conversation in the lunchroom, you should take advantage of the little time you have in a video or phone conference...

10. HOW DO YOU USE TECHNOLOGY ON A DAILY BASIS, IN YOUR WORK AND FOR YOUR PLEASURE?

This is a great question because it shows your comfort level with technology, which is very important for a remote worker because you will be working with technology over time...