openashbyhqarsenalgrowth
Staff Software Engineer, Engineering AI Team
Second Nature
LocationRemote, USA
WorkplaceRemote
EmploymentFullTime
Posted2026-04-22T16:05:41.787+00:00
Last observed2026-06-13 05:23:59.903142
Job idarsenalgrowth-second-nature:ashbyhq:ce8bb758-f58a-4800-8a6d-dff88c82ea50
TODAY, WE LIVE IN A WORLD WHERE EVERYTHING HAS BECOME CONVENIENT. NOW YOU CAN GET A RIDE ANYWHERE, BUY ANYTHING, AND GET AN ANSWER TO YOUR QUESTION WITH JUST A COUPLE CLICKS ON YOUR PHONE. CONVENIENCE ISN’T A LUXURY, IT’S AN EXPECTATION. SO WHY NOT RENTING? IT’S STILL A CHORE TO GET UTILITIES SET UP, BUY RENTERS INSURANCE, GET AIR FILTERS CHANGED, HANDLE PEST CONTROL, AND MORE. THAT’S WHY WE’VE BUILT THE WORLD’S FIRST RESIDENT EXPERIENCE PLATFORM THAT MAKES RESIDENT ONBOARDING, RESIDENT SERVICES, AND ANCILLARY REVENUE EFFORTLESS FOR PROPERTY MANAGERS. WE’RE PASSIONATE ABOUT TURNING FRICTION INTO TRIPLE WIN EXPERIENCES FOR RESIDENTS, INVESTORS, AND MANAGERS. THAT WAY RENTING CAN BE EASY AND REWARDING FOR EVERYONE. AND NOW YOU CAN JOIN US. APPLY TODAY TO JOIN 275+ PASSIONATE, CREATIVE PEOPLE WHO STRIVE TO MAKE A DIFFERENCE EACH DAY SO RESIDENTS, PROPERTY MANAGERS, AND INVESTORS ALL WIN. About The Role We are looking for a high-agency staff software engineer to help accelerate both platform development and real-world experimentation. This isn’t a typical "build features from a Jira ticket" role. You will operate with high autonomy, owning full loops without handing work off across layers. You will act as a builder, an experiment owner, and a reality check, ensuring that everything we develop is grounded in practical, everyday engineering workflows. About the Team We are a small, fast-moving team focused on transforming the software development lifecycle (SDLC) using AI-driven, agentic workflows. Our work sits at the cutting-edge intersection of AI-powered development, rapid experimentation, and robust platform building. We are rethinking how engineers ship code by developing remote coding agents, automated iteration loops, and workflow orchestration. We build and test simultaneously—ensuring that our platform evolves alongside real-world experiments that actually improve engineering velocity. How We Work We don't just build AI tools; we walk the walk. This team builds 100% of our software utilizing AI coding agents (e.g., Claude Code) and integrates AI across our entire development and support processes (leveraging Gemini, Claude Cowork, and dogfooding our own platform). We are a team of professionals who recognize a fundamental truth: quality code helps AI agents produce quality code. To that end, we maintain a tight "human-in-the-loop" development cycle, ensuring we cultivate an opinionated codebase with solid abstractions that continuously accelerate our velocity. Key Responsibilities - Build Core Platform Infrastructure: Design, develop, and ship core platform components, including workflow orchestration, third-party integrations, and sandboxed execution environments for AI agents. - Drive End-to-End Experimentation: Own the full lifecycle of rapid experiments (hypothesis → build → measure → iterate) to discover what meaningfully improves engineering velocity. - Maintain High-Quality AI Dev Loops: Leverage AI coding agents to write, refactor, and review code, maintaining the strong abstractions and opinionated architecture required for AI to be effective. - Ground AI in Reality: Act as the technical bridge between experimental AI capabilities and real-world engineering workflows, ensuring our tools solve actual pain points. - Full-Loop Ownership: Operate autonomously to take concepts from 0 to 1, delivering tangible improvements and clear signals on AI workflow efficacy without over-engineering the solution. Key Outcomes (first 90 days) - Master our AI workflow: Integrate our AI tooling while rigorously auditing and refining AI-generated code and tests to meet our quality bar. - Ship rapidly and reliably: Consistently deliver high-impact PRs with minimal rework by ensuring thorough local testing and CI/CD readiness before review. - Plan with pragmatism: Adopt our norm of writing lightweight plans (outlining phases, trade-offs, and "good enough" criteria) for non-trivial work before coding. - Own a full experiment: Drive at le
This page is generated from the committed OpenOpps static snapshot. Use the source posting or apply link for the employer's current canonical posting state.