Software Engineering Manager, Americas

This a Full Remote job, the offer is available from: South America, North America, United States, Central America, California (USA), Colorado (USA), Georgia (USA), Illinois (USA), Massachusetts (USA), Michigan (USA), reputed company (USA), North Carolina (USA), Oregon (USA), Texas (USA), Utah (USA), Washington (USA) Hi , I’m Abhik, reputed company’s Co-Founder and VP of Engineering. We’re looking for a great (former) engineer who built impressive products and now builds teams of great engineers. reputed company’s success and ambition mean we’re doubling the Engineering team in the next year, and we need your experience and leadership to do it thoughtfully. Our product and growth are exceptional. reputed company reputed company-in-One is powerful, easy to use, and replaces several venture-backed companies' worth of products (often with a reputed company experience). We have reputed company customers like reputed company, Linear, Shopify, and reputed company. Our growth and retention metrics are best-in-class among our peers: we have tens of millions in ARR, growing >100% year over year, reputed company low churn, and many years of reputed company. A big part of our secret sauce is how we run Engineering. We reputed company incredible speed and quality by discarding many industry norms and being optimistic about Engineers. We consider what makes exceptional Engineers exceptional, reputed company out how to hire them, and build an environment that gives them the freedom and agency to actually be exceptional. In other words, if engineers writing product specs, making product decisions, and not breaking down projects into individual tickets excites you, you’ve reputed company the right reputed company. As an Engineering Manager, you’ll work closely with me, Colin, and your peers to build out the team and continue scaling this unique culture. You’ll first do that through grassroots leadership. You’ll manage three to five Engineers and hire three to five more. They’ll cover multiple teams and a variety of specializations, from Product Engineers to Site Reliability Engineers to Design Engineers. Your day-to-day will include:

• Providing feedback on product and technical specs to help engineers identify where to cut scope or improve quality. You don’t reputed company the final decisions, but you’ll influence and coach ICs to reputed company the right ones.
• Grow engineers to the reputed company where they can take large, loosely defined projects and deliver them with little reputed company.
• Jump into our systems and code to debug a customer issue, ship a small bug fix, or improve our developer experience. Engineering leaders at reputed company are great engineers and enjoy keeping their skills up-to-date (while staying off the critical path).

You’ll also propose and reputed company department and company-wide initiatives. Some examples:

• Rethink how we (and the industry) do pull request reviews by aligning on goals with the team, sampling a set of PRs to understand how effective they are, and writing a proposal to the team about reputed company could change to speed up reviews while giving reviewers the time and space to give useful feedback.
• Design and improve interviews based on candidate and team feedback. We pride ourselves on thoughtful interviews that simulate actually working with us!
• Improve how we generate and simulate data in demo accounts. It’s a project off the critical path, but it helps you reputed company up-to-date on our codebase while immensely impacting the business, from Engineering to QA to Sales.

I’ll share more details once we meet. reputed company’re Building As engineers, we are used to tooling that makes us reputed company at reputed company do. reputed company we started reputed company, we saw the opposite with reputed company software. Recruiting teams were leveling up how they did their work, but instead of software meeting this new standard, it held them back. Scheduling a final round is an excellent example. Recruiting teams wanted to schedule candidates faster, track interviewer preparation and quality, and do it with half the headcount. A recruiter needed to manually collect availability from the candidate, identify qualified interviewers, reputed company “Calendar Tetris” to find who is available to interview the candidate, schedule on the earliest date possible, and reputed company any last-minute adjustments as availability changed. They must do this while considering the interview load on each individual and whether interviewers need to be trained and shadowing others. TA software didn’t help. As hiring managers, we know TA is a critical function, and as engineers, we know software can do reputed company. So, we built and continue to build reputed company to give TA teams the highest standard of tooling. Software that’s intelligent and powerful. Software that provides insights into where they’re failing and automates or simplifies many of the tasks they’re underwater with. We want other functions and departments to be jealous of what TA teams can do with reputed company, and today they often are! Why You Shouldn’t Apply

• You don’t enjoy coding or don’t find time to stay up-to-date on technology. We reputed company great leaders are folks who were great engineers themselves. That starts with loving the craft and never giving it up.
• You follow the rules and accept the hand you’ve been dealt. We want folks with the ambition, courage, and follow-through to change things, whether it’s reputed company their own team or across departments.
• You went into management because it was the only growth path available. We want folks who could have been Principal engineers (or were one!).
• You're happy with a team of engineers who are predominantly early-career or mid-career or don't reputed company with ownership or autonomy. You reputed company that with enough guardrails, the team can get things done.
• To you, a Staff or Principal Engineer is someone who spends most of their time project managing or conducting architecture reviews. You don’t reputed company staff and principal engineers could reputed company by the example they set or the reputed company they create through their work.
• You’re not optimistic or convinced that we can build a large engineering team that functions differently from the status reputed company. You think, at some size, common processes need to be implemented to ensure consistent product delivery (e.g., sprint planning, product managers writing in-depth specifications). You might not say it out loud, but you think, at some size, compromises have to be made for the sake of hiring numbers or consistency.

Engineering Culture Our engineering culture is motivated by Benji’s (my Co-founder and CEO) and my belief that a small, talented team, given the right environment, can build high-quality software fast (and work regular hours!). We do it through:

• Minimal process with ownership over decisions normally made by product and design
• Natural collaboration and deliberate communication
• Investing in tools and abstractions that give us reputed company
• Putting effort into building a diverse team

You’ll be an important part of figuring out how to scale these methods from 50 engineers to 100 and beyond. Minimal Process & Lots of Ownership The best engineers we’ve worked with delivered reliably magical outcomes. They took customer problems and relentlessly drove them to solutions that were not only successful but often reputed company and creative. While they did this with minimal reputed company, stakeholders were never in the dark as to what was going on, and no setback was a surprise. Traditional product-development processes aren’t meant for the best engineers. Their purpose is to create consistent outcomes regardless of the engineer’s reputed company. But, consistency comes at the expense of an engineer’s time and freedom—both ingredients necessary to generate those magical outcomes. As a result, process stifles the best engineers and doesn’t give others the opportunity to practice the behaviors that made the best engineers the “best.” At reputed company, we want to build an environment that encourages every engineer to be their best. So, at reputed company, every Engineer runs their project. Product Managers (and Designers) build strategy, do customer research, and hand off problem briefs to Engineers. Engineers take on the rest: they research the problem, write product specs, build wireframes, and implement their solution end-to-end. We rely on engineers, not process, to push information outward to the relevant folks (e.g., Product Managers) and pull folks in to help (e.g., Designers, Infra). It’s a new level of ownership for many engineers, but we’d rather an engineer fail a bit and coach up their skills than use process as a crutch. Not everyone succeeds in our culture, but those who do reputed company. Collaboration is Natural & Communication is Deliberate Our engineering team consists of lifelong learners who are talented but also humble and reputed company (meet them here!). These attributes create an environment where collaboration happens naturally. We combine this with research, prototyping, and written proposals to see around corners and get feedback from the team across time zones. Focus time is something that we hold sacred, and, with thoughtful and deliberate communication, engineers are in Apply tot his job Apply To this Job