Meadow - Senior Software Engineer

• This is a full-time position reporting to Mike, Meadow's Engineering Manager. • 5+ Years of Experience in Product Engineering • You have experience building and operating production systems at scale. • Builder Mindset: You demonstrate High Agency x High Urgency. • You own problems end-to-end. • You make consequential decisions that impact outcomes. • Agency: You make bigger calls on your own. You own the scope, approach, and tradeoffs for your projects without needing sign-off, and default to action when the path is ambiguous. • Decisions: The team trusts your call, as you are usually right. You estimate accurately and credibly, rarely make the same mistake twice, and correct fast when wrong. • Operational Excellence: You make operating our system a top concern. You instrument and document proactively, so things are debuggable and supportable before they break. • Empathy: You keep a steady rhythm of contact with your users, external or internal (IE, CX), across your area: support tickets, integration issues, calls, telemetry. You understand the desired outcomes and surface patterns worth acting on. • Creativity: You form opinions on what to build, not just how. You generate and propose solutions to problems worth solving, including ones beyond their assigned work. • Taste: You judge which options actually move the needle on user outcomes and back them. You help teammates see defects and product-sense gaps, raising the bar around you. • Technical Depth • Design & Architecture: You are trusted to lead engineering design on any project. You understand the why behind the architecture and see second-order effects, including how a component behaves as usage grows, and make calls that are not obvious to others. • Problem Solving: You anticipate the failure modes in your own designs and handle ambiguous, underspecified problems. • Tooling & Verification: You continuously encode your expertise for an agentic context with context files, evals, and patterns that keep generated code correct and on-spec. • Tech Debt: You identify systemic debt across your components. You write the spec/proposal for the whole project, get it prioritized, and lead execution. • You default to AI-first approaches where appropriate and have built workflows, tooling, or practices that improve output beyond just themselves. • You demonstrate strong judgment about tradeoffs and failure modes by choosing tools intentionally, validating outputs, and building review, testing, or mitigation into the workflow. • Communication & Collaboration • You speak cross-functionally without jargon, making sure non-engineers understand. You balance technical, product, and CX tradeoffs in the moment and drive buy-in from all stakeholders.