Principal Software Engineer
Principal Software Engineer
Posted 5 days ago
SENIORITY
Manager
About the role
- Own: Own from end to end the short and long term technical vision of your team
- Design & Revamp: Design, implement and improve critical systems and components powering ServiceTitan stack; improve the security, availability, reliability, and performance of our products; drive/participate in all major architectural and strategic decisions especially those relating to scale
- Improve Efficiency: Build tools to increase efficiency of all our engineers; improve performance, processes, and quality across the whole engineering team
- Discover: Identify opportunities to extract or develop systems beneficial for multiple teams
- Empower: Mentor and guide Engineers across engineering as a whole 60% development / 40% working on everything else
- Teambuilding: Work closely with Recruiting — in particular, interview candidates and co‑own activities related to lead generation (e.g. tech talks) and screening (HackerRank tests)
- Strategy: Contribute to the roadmap and resource planning
- Measure Success: Determine metrics for success and constantly measure them
- Collaborate: Communicate effectively with cross‑functional teams, engineers, Product Managers, customers, and partners
- 8+ years of industry experience, including with large scale enterprise web/saas applications 3+ years of experience in senior engineering roles (designing APIs, abstractions, and tools used by other engineers)
- Microsoft .NET technology stack (C# / .NET, ASP.NET MVC, Web APIs) and SQL databases (Microsoft SQL Server or any other)
- Taking existing monolithic applications to a domain based, service‑driven paradigm
- Experience with large scale 3rd party integrations
- Basic Microsoft Windows administration skills including IIS administration
- Performance / reliability monitoring tools (e.g. New Relic, DataDog, Application Insights)
- Log / Metric collection and analysis tools (e.g. Elasticsearch‑Logstash‑Kibana, DataDog, Interana)
- Git, unit testing, debugging, profiling, Visual Studio, JIRA and other tools that are typically used by developers on Microsoft technology stack
- Continuous integration and continuous delivery methodologies and tools (TeamCity or similar)
- Administration and building automation for Azure, AWS or other public cloud technology
- Ability to empathize with our users and champion for their experience.
- Strong communication and technical writing skillsB.S., M.S. or PhD in Computer Science, Physics, Engineering or a related technical field.
Before you apply
Applying takes about a minute. These four things decide how fast it moves after that.
Your profile is current
It's what we read first. Occupations, seniority and locations matter more than a long history.
Two examples you can talk through
Not a portfolio — just two pieces of work where you can explain the decisions and what you'd change.
A number in mind
What you're on now and what would make you move. We negotiate better when we know both.
Your notice period
Employers plan around it, and it's the question that stalls offers most often.
Once you apply, someone reads it and calls you before anything reaches the employer — usually within two working days.
