> Markdown version of [/jobs/ext/739566-staff-software-engineer-boston](https://www.wearedevelopers.com/jobs/ext/739566-staff-software-engineer-boston). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md). --- # Staff Software Engineer - Boston - **Company:** Perk Company, Inc. - **Location:** Boston, MA, United States - **Salary:** $174,000.0 - $205,000.0 - **Contract:** Permanent contract - **Skills:** Artificial Intelligence, Amazon Web Services, Code Review, Python (Programming Language), Backend, Front End Software Development - **Published:** June 29, 2026 - **Apply:** https://www.indeed.com/viewjob?jk=9b1568574d804871 ## About the Role * Product engineering mindset: you work end to end - from understanding customer problems alongside product, through to deployment and measuring impact. Technical skill alone isn't enough; you need to be able to own a problem fully. * Cross-team technical leadership: proven experience coordinating significant, multi-team technical initiatives where you've had to manage dependencies, align stakeholders, and keep a longer-horizon project moving. * Architectural judgment: ability to design scalable, evolvable systems and articulate a clear technical roadmap - balancing long-term thinking with pragmatic, near-term delivery. * "You build it, you run it" experience: you've run your own services - monitoring, testing, rolling out, and operating them in production. The tools may differ; the mindset shouldn't. * Domain complexity: experience working in a domain with significant underlying complexity - ideally flights or travel, but also fintech or any industry where you've had to build reliable, customer-facing products on top of messy, constrained underlying systems. * Backend-heavy, full-stack comfortable: our stack is roughly 80% backend, 20% frontend. You should be comfortable across both, with the depth in backend systems. We use Python and AWS; we're open to people who've used different tools, as long as they can demonstrate they learn quickly. * Operational maturity: experience leading observability and reliability practices; defining SLOs, handling incidents, and conducting blameless post-mortems. * Mentorship and influence: a track record of levelling up engineers around you through mentorship, design reviews, and by modelling what great engineering looks like. * AI-driven development: experience with - or a strong interest in - modern AI-augmented workflows, including agentic coding and AI-assisted code review. ## Description * You'll work across multiple teams to coordinate a shared technical direction. This means contributing to the creation of annual and quarterly plans in collaboration with product managers, engineering managers, and other engineers - and translating that into clear, actionable priorities that teams can work to today. * Be hands-on, with purpose. * Staff engineers at Perk are mostly hands-on - spending the majority of their time actively contributing within one or two teams, and the rest mentoring engineers, unblocking delivery, and working with dependent teams to move shared projects forward. You won't be pulled into excessive meetings or committees with a focus on impactful collaboration. * Shape how we work, not just what we build. * You'll take higher-level business goals and turn them into engineering approaches. That means proposing the shape of annual objectives, identifying architectural changes needed for scale, and making sure the team is investing its energy where it counts most - not just staying busy. * Raise the bar for everyone around you. * Staff engineers are mentors and multipliers. You'll support engineers through direct mentorship, design reviews, and pairing. You'll help explain technical complexity to the wider business - including why certain things take the time they do - and help the whole team level up their skills to better apply them to the domain. * Lead across boundaries. * Your influence won't stop at your own team. You'll coordinate across squads, contribute to engineering initiatives, and drive alignment across the broader organisation. When there are dependencies or blockers, you'll be the one connecting the dots. ## Related Videos - [Shipping Faster with Less: Render on Cloud Hosting, AI Workloads, and the Future of DevOps](https://www.wearedevelopers.com/videos/1894-shipping-faster-with-less-render-on-cloud-hosting-ai-workloads-and-the-future-of-devops) - [Containers in the cloud - State of the Art in 2022](https://www.wearedevelopers.com/videos/410-containers-in-the-cloud-state-of-the-art-in-2022) - [Are Code Reviews Worth It? Insights from 16 Years of Review Data](https://www.wearedevelopers.com/videos/1135-are-code-reviews-worth-it-insights-from-16-years-of-review-data) - [Developing the Backend with Stefan Lingler, CTO at Shpock](https://www.wearedevelopers.com/videos/100360-developing-the-backend-with-stefan-lingler-cto-at-shpock) - [Developer Experience in the Age of AI](https://www.wearedevelopers.com/videos/1118-developer-experience-in-the-age-of-ai) - [Reliable scalability: How Amazon.com scales on AWS](https://www.wearedevelopers.com/videos/983-reliable-scalability-how-amazon-com-scales-on-aws) ## Related Articles - [Dev Digest 120 - Apple and peers](https://www.wearedevelopers.com/magazine/455-dev-digest-120-apple-and-peers) - [Navigating the AI Shift](https://www.wearedevelopers.com/magazine/629-navigating-the-ai-shift) - [What is Software Engineering in the Age of AI?](https://www.wearedevelopers.com/magazine/640-what-is-software-engineering-in-the-age-of-ai) - [Dev Digest 121 - AI goes offline](https://www.wearedevelopers.com/magazine/456-dev-digest-121-ai-goes-offline) - [The Prompt Engineer ✍️](https://www.wearedevelopers.com/magazine/216-the-prompt-engineer) - [Dev Digest 137 - AI'm not sure about this](https://www.wearedevelopers.com/magazine/485-dev-digest-137-ai-m-not-sure-about-this)