Full Stack Software Engineer - AI Applications

Who You Are An agent orchestrator, not a typist. You don't want to be a faster keyboard. You want to be a manager of agents — handing off the heavy lifting, reviewing the output, and keeping your hands on the architecture. The IDE is a cockpit for orchestration, not a text editor. Productively lazy.

Your dream workflow:

describe the requirement, let the agent build it, verify, ship, next. You automate anything a human shouldn't be doing twice. Your biggest bottleneck should be deciding what to build — while AI executes the how . Fundamentals first. Data structures, algorithms, distributed systems, networking — you understand the machine, not just the library that wraps it. When a framework breaks, you fix it. When AI gives you the wrong answer, you catch it. Orchestrating agents only works if you can tell good output from garbage. First-principles thinker with vision. You break problems to their core, question the assumptions, and rebuild. A software engineer's job is to architect solutions, not wrestle with syntax. You don't copy an architecture because "that's how it's done" — you ask why and decide if there's a better way. High agency. You don't wait for perfect specs or permission. You find a path, propose it, and move. Large organizations have walls; you figure out which ones to go through, around, or remove — and you do it constructively. Bias for action. Requirements will be messy and priorities will shift. You ship v1, learn, and iterate instead of living in design review.