Remoat Teams
Website:
remoatteams.com
Job details:
This is not an engineering role where you push tickets through sprint cycles. This is an engineering role where you build the company.
Our client is an AI-powered services company scaling from 700 to 1,000+ people. We serve unicorn fintechs and data infrastructure providers used by the Mag-7. The stakes are high, the pace is unreasonable for most, and the standards are binary: the system works, or it doesn't.
We're looking for an engineer who thinks like a founder. You'll sit inside the Founder's Office — the CEO's SWAT team — and rotate through every department in the company on 2–3 month sprints. Your job is to look at how each function operates, identify where systems are broken or missing, and build the technical solutions that make the entire organisation run faster. You won't be building product features. You'll be building the company itself.
Think of it as: what would happen if an engineer joined every department for a quarter and rebuilt their infrastructure from first principles — using AI, automation, and code? That's the role.
THE TRADE-OFF
What you give:
- Your full focus, 6 days a week
- Your ego (you will be corrected often and challenged to improve your business acumen).
- Your comfort zone (you will architect solutions for problems you've never seen before — across departments you've never worked in)
What you get:
- A PhD in Scaling. You will sit in executive meetings, see how technical decisions drive business outcomes, and learn exactly how a $100M company is built from the inside. You'll understand why the CEO made that call, how the ops team broke down, where the GTM motion stalled — and you'll be the one who builds the fix.
- You will gain more operational, technical, and business skill in 12 months here than in 5 years at a normal engineering job. This is direct exposure to enterprise clients in financial services, building systems that power a company serving Wall Street's biggest data providers.
- Access to proprietary learning resources — paid masterclasses, executive advisors (who've advised Twitch, Patreon, YouTube), AI workflow training, and frameworks from the best operators in the business. We invest heavily in the people we believe in.
THE SCOPE (What you will actually build)
1. AI Engineering & Systems Architecture (60%)
- LLM Implementation & AI Workflows: You build AI-powered systems that replace manual processes across the company. This means designing prompts, building agents, creating AI colleagues that handle real work — not demos. When the CEO says "our QA process takes too long," you don't hire more people. You build an AI system that handles it, with humans in the loop where it matters.
- Vibe Coding & Rapid Prototyping: You live in Claude Code, Cursor, and whatever ships next. You build internal tools in days, not sprints. You prototype three versions and ask which one ships. If the tool doesn't exist, you build it. If the API doesn't have a wrapper, you write one.
- Workflow Infrastructure: When the CEO says "Fix Recruitment," you don't make a Trello board. You build the pipeline — intake forms, automated routing, status dashboards, Slack notifications, AI-powered screening, and a reporting layer. You connect Notion, Slack, Airtable, Make, internal APIs, and whatever else the business runs on. If a process is manual and repeatable, you automate it.
- Data & Dashboards: You build dashboards that executives actually use. You write SQL when needed. You don't wait for "the data team" because you are the data layer for the Founder's Office.
2. Department Sprint Operator (30%)
- Rotational Deep Dives: Every 2–3 months, you embed in a different function — GTM, Operations, Client Success, Product. You audit how the department runs, identify the highest-leverage technical problems, and build the systems that solve them. You leave each department with infrastructure they didn't have before.
- Shadow & Synthesise: You sit in high-level discussions. Your output is not "notes" — it's a structured Action Plan with dependencies mapped, blockers flagged, and a technical implementation path for every decision that requires one.
- AI-First Documentation: Every meeting is recorded and transcribed. You build systems where AI colleagues can parse meeting outputs, generate follow-ups, and create institutional memory that scales. You design processes as if your team members are AI agents — because increasingly, they will be.
3. Intersectional Product-Engineering (10%)
- Internal Product Design: You identify where the company needs an internal tool and you design and build it — from the user experience to the backend logic. This isn't product management. This is one person seeing a problem, sketching the solution, and shipping it.
- AI Colleague Architecture: You help design and build the framework for how INFLXD deploys AI agents across the organisation — what they handle, how they escalate, how they learn. This is early-stage, greenfield work. You're building what most companies won't figure out for years.
THE DNA (Who survives here)
- Builder, Not Ticket-Pusher: You see a broken process and your instinct is to build the system that fixes it — not file a Jira ticket and wait for the next sprint. You default to shipping over delegating.
- Engineer Who Gets Business: You don't just write code. You understand why the code matters. You think in terms of revenue impact, operational leverage, and scaling bottlenecks. You'd rather automate a CEO's workflow than build a feature nobody uses.
- AI-Native: You use LLMs to 10x your speed. Prompting, automation, agent design, code generation — AI is your co-pilot, not a novelty. You've already built things with Claude Code or Cursor that made people's jaws drop. You think about AI colleagues as a real architectural pattern, not a buzzword.
- High Speed, Low Drag: You don't ask "How do I do this?" You say "I built three versions — which one ships?" Speed of iteration is your competitive advantage.
- Data Over Feelings: Direct feedback is a gift. You don't take correction personally; you take it as a system update. When your solution gets torn apart, you rebuild it better.
- Discretion is Currency: You will see cap tables, client contracts, and internal performance data. A single breach of trust is a single-strike exit.
THE PROFILE
Two archetypes thrive here:
- The Engineer Who Wants to Be a Founder: You can ship software, but you're bored building features no one uses. You want to understand the whole business — GTM, ops, finance, client success — and you want to build the technical systems that connect them all. You see this as a 12-month accelerator for becoming the kind of technical founder who actually knows how businesses scale.
- The Ops Person Who Codes Like an Engineer: You've been running operations or consulting, but you taught yourself Python and started building automation because you got tired of waiting on engineering. You see business problems first, then build technical solutions. You've shipped internal tools that replaced entire manual workflows.
Both share this: You are the person your friends call when they need to "figure something out." You are in a season of life where building skills, gaining exposure, and compounding your capabilities matter more than a comfortable title. You'd rather join a rocketship at the ground floor than coast at a company where your impact is invisible.
YOU'VE PROBABLY BUILT...
- The v1 of a product feature (or full product MVP) that you built from concept to deployment and saw its first users or internal traction.
- The foundational data pipeline or system of record that the entire company still runs on.
- An AI agent or automation system that eliminated a high-cost, high-headcount manual workflow.
- A monitoring dashboard that became the single, essential source of truth for executive decision-making.
- Something you built in a day or a weekend (using tools like Claude Code or Cursor) that immediately solved a critical business problem.
- A core system or integration that required you to reverse-engineer a garbage API — and you shipped it anyway because the business needed it.
If three or more of these describe you, keep reading.
THE TECHNICAL ENVIRONMENT
You won't be limited by a tech stack — you'll choose and build it based on the problem. That said, here's what the landscape looks like:
- AI & LLMs: Claude (primary), Gemini, OpenAI, Grok, open-source models. You'll design prompts, build agents, and architect AI-augmented workflows across the company.
- Dev Tools: Claude Code, Cursor, Codex GitHub Copilot — whatever accelerates your shipping speed.
- Languages: Python, JavaScript/TypeScript, SQL, Apps Script — whatever gets the job done. You're not religious about languages.
- No-Code/Low-Code: Make (Zapier), Replit, Retool, Airtable — when speed matters more than customisation. But you're never limited by them. If the tool can't do it, you build it yourself.
- Infrastructure: Notion, Slack, internal APIs, client delivery systems. You connect the dots between all of them.
COMPENSATION
- Base: Competitive monthly salary (disclosed during screening)
- Performance: Bonuses tied to quarterly deliverables, automation coverage, and operational milestones
- Growth: This is a track to Head of Engineering Operations, Technical Chief of Staff, or VP-level. Survive 2 years, and you will have the skills to run a department — or a company.
Click on Apply to know more.