Skip to content
aitrainer.work - AI Training Jobs Platform
Engineering Full-Time
micro1

Software Engineer (Principal), Eng-wide Architecture

micro1 • Remote • Lead

Company

micro1

Annual salary

$450k – $700k/yr

Location

Remote

Listed

2d ago

Level:
Lead
Apply at micro1 →

Join the talent pool

Set up a profile and we'll consider you for roles at labs like micro1.

Set up your profile →

About this role

We’re looking for an exceptional, hands-on Principal Software Engineer to serve as the most senior individual contributor in our engineering organization. You’ll develop a deep understanding of our entire technology ecosystem, shape the long-term technical architecture, and establish the engineering practices that enable teams to build reliable, scalable systems at speed.
You'll dedicate approximately half your time to advancing agentic engineering, transforming how we develop, review, test, and ship software through AI-powered automation. The remaining time will focus on solving the most critical engineering challenges across the organization, wherever your expertise can create the greatest impact.

What you'll do

  • Own Technical Architecture: Develop a comprehensive understanding of our platforms, infrastructure, and engineering ecosystem to shape long-term architectural direction and guide critical technical decisions.
  • Lead Agentic Engineering: Design and implement AI-driven engineering workflows, autonomous coding agents, and intelligent automation across the software development lifecycle.
  • Transform Code Review & Delivery: Drive an initial goal of making 30% of pull requests eligible for automated approval within the first 3 months, through reliable AI-powered reviews, automated validation, and clearly defined quality gates.
  • Solve Critical Engineering Challenges: Take ownership of the organization's highest-priority technical problems, from complex architectural bottlenecks and reliability issues to platform scalability and urgent cross-team initiatives.
  • Establish Engineering Excellence: Define and champion engineering standards across system design, code quality, testing, observability, reliability, security, and maintainability.
  • Build Developer Infrastructure: Improve CI/CD pipelines, developer tooling, automated testing, and internal engineering workflows to increase velocity and reduce manual overhead.
  • Drive Cross-Platform Alignment: Identify architectural inconsistencies, reduce technical debt, and introduce reusable patterns and shared infrastructure across engineering teams.
  • Stay Deeply Hands-On: Write production-grade code, build prototypes, review complex implementations, debug critical issues, and lead by example through direct technical contributions.
  • Provide Organization-Wide Technical Leadership: Mentor senior and staff engineers, influence technical strategy, and raise the engineering bar without relying on formal management authority.

What you need

  • 12+ years of software engineering experience, with a proven track record of operating at Staff, Principal, or equivalent technical leadership levels.
  • Exceptional hands-on engineering expertise in Python, TypeScript, or similar languages, with extensive experience building and operating complex production systems.
  • Deep systems architecture experience across distributed systems, microservices, APIs, cloud infrastructure, databases, and large-scale platform engineering.
  • Practical experience with agentic engineering, including AI coding agents, LLM integrations, tool calling, orchestration, automated code review, and autonomous development workflows.
  • Strong understanding of software quality and delivery, including automated testing, CI/CD, code review systems, observability, security, and production reliability.
  • Proven ability to drive technical strategy across multiple teams, establish engineering standards, and influence architectural decisions at an organizational level.
  • Experience improving developer productivity through engineering automation, internal tooling, infrastructure improvements, and measurable process optimization.
  • Exceptional problem-solving and execution skills, with the ability to rapidly understand unfamiliar systems, navigate ambiguity, and resolve high-impact technical challenges.
  • Strong technical communication and mentorship skills, with the ability to align engineering teams, challenge assumptions, and drive adoption of better engineering practices.

Nice to have

  • Experience in AI research labs, AI-native companies, or high-growth technology startups.
  • Hands-on experience with AI coding agents and autonomous development systems, including tools such as Claude Code, Codex, Cursor, or similar technologies.
  • Experience designing agentic software development pipelines, including automated PR generation, code review, testing, validation, and deployment workflows.
  • Familiarity with agent orchestration frameworks, MCP, tool-use architectures, context engineering, and evaluation frameworks.
  • Experience leading organization-wide architectural transformations, platform modernization, or developer productivity initiatives.
  • Background in AI/ML infrastructure, data-intensive systems, or human data platforms supporting model training and evaluation.
  • Experience defining and measuring engineering effectiveness metrics, including deployment frequency, change failure rate, review cycle time, and automation coverage.
About micro1 and legal notices

Compensation & Benefits Notice

The national pay range for this full-time position is base salary of $260,000 –$320,000. All employees are eligible for equity compensation, and employees may also receive performance-based bonuses, dependent on role and subject to company policies. micro1 provides a comprehensive benefits package, including up to 100% reimbursement for health-insurance premiums, paid time off, a 401(K) plan with a company match, and additional benefits designed to support a high-performing, remote-first workforce.
micro1 is an equal opportunity employer. All qualified applicants will receive consideration for employment without regard to race, color, religion, sex (including pregnancy, sexual orientation, or gender identity), national origin, age, disability, genetic information, veteran status, or any other characteristic protected by applicable local laws, regulations and ordinances. If you need assistance and/or a reasonable accommodation during the application process, reach out to [email protected].
Our hiring process utilizes artificial intelligence tools to assist in candidate screening and assessment. Our AI tools are designed to complement, not replace, human decision-making.

Skills and categories

STEMPythonTypeScript System Architecture & Distributed SystemsAgentic Engineering & AI-Driven DevelopmentTechnical Leadership & Engineering ExcellenceComplex Problem-Solving & Technical ExecutionCodingExpert AI TrainingSpecialistSoftware Engineering

Common questions

How do I apply for the Software Engineer (Principal), Eng-wide Architecture role at micro1? +

Use the Apply button on this page. It opens micro1's own application form, so you apply directly with them.

What does this micro1 role pay? +

micro1 lists $450k – $700k/yr.

Is this role remote? +

The listing is remote. Check micro1's posting for any country or time zone requirements.

Software Engineer interview prep

Questions Software Engineer interviewers often ask. They aren't taken from this listing.

How do you approach designing a system when the requirements are still likely to change?

I design around the parts of the problem I'm confident are stable, like the core data model, and keep the parts most likely to change, like specific business rules, isolated behind clear interfaces. Over-engineering flexibility everywhere just adds complexity to parts of the system that were never going to change.

What's your process for debugging an issue that only reproduces in production, not locally?

I add targeted logging around the suspected area and compare production data or configuration against my local setup, since an issue that's environment-specific usually traces back to a real difference between the two rather than a fundamentally different bug. I avoid making speculative changes without first confirming where the divergence is.

How do you decide when a piece of code needs a test versus when it's low-risk enough to skip?

I prioritize tests for logic with real business consequences if it breaks, or code that's likely to be touched again later by someone unfamiliar with it. Simple, rarely-changed glue code gets less coverage, since the cost of a thorough test there often exceeds the risk it's protecting against.

How do you evaluate a proposed technical solution's trade-offs, like performance versus maintainability?

I start from the actual constraint that matters for this specific system, whether that's genuinely performance-critical or whether maintainability is the bigger long-term cost, rather than defaulting to whichever trade-off I personally prefer. Optimizing for performance the system doesn't need just adds complexity nobody benefits from.

See all 10 Software Engineer interview questions →

This listing mentions these tools. Brush up before a technical screen:

Related roles

micro1

More full-time jobs at micro1

micro1 builds AI-native infrastructure and employs a globally distributed team of engineers, researchers, and operations professionals.

See all micro1 roles →