At a Glance
- Tasks: Design and build complex systems while writing production code regularly.
- Company: Innovative tech company focused on impactful engineering work.
- Benefits: Unlimited leave, open salaries, and a collaborative environment.
- Other info: Dynamic projects with high ownership and minimal process overhead.
- Why this job: Join a team where your coding skills make a real difference.
- Qualifications: Strong coding skills and a passion for mentoring others.
The predicted salary is between 70000 - 90000 £ per year.
We are looking for someone who has raised the bar for ten years. The people around you write better code because you are there. You mentor through pairing and feedback, not hierarchy. You have gone deep enough to hold strong opinions, and are humble enough to change them. You still build regularly in production. This role isn’t for everyone; it’s for engineers who want to stay close to the code, go deep, and do meaningful work. If that sounds like you - apply.
What the work looks like:
- Redesign a ClickHouse schema so an ad buyer can query 85 billion rows in under two seconds.
- Keep a vehicle telemetry platform moving billions of messages a day without the Kafka consumers falling over.
- Build the engineering spine of a mobile wallet used by more than two billion people across four continents.
- Ship the data product behind peer-review submissions for one of the world's largest scientific publishers.
The list changes every quarter. The pattern doesn't: data-heavy, distributed, and often sitting on top of something that already exists and isn't perfect.
What you will actually do:
- Design and build systems that deal with real-world complexity (not toy problems).
- Write production code frequently, not just review or direct.
- Work across languages when needed, not just your comfort zone.
- Break down messy problems into clean, maintainable systems.
- Push back on bad ideas, including ours.
You won’t be:
- A people manager.
- A “review-only” architect.
- Someone removed from the code.
How we think about engineering:
- We care about code that is simple, testable, and built to change.
- Engineers who can explain their design decisions clearly.
- TDD, refactoring, and continuous improvement - not as rituals, but as tools.
- Choosing the right technology, not the fashionable one.
We don’t care much about:
- Buzzwords.
- Framework loyalty.
- Whether you’ve used our exact stack before.
Tech (context, not a checklist): TypeScript, Java, Scala, Kotlin, Go, Elixir, Python, .NET, Node.js, Rust. You don't need to have shipped all of these. You do need the ability to learn what the problem demands.
What you’ll get:
- A place where Principal Engineers still write code - daily.
- One designation across the company: Solution Consultant.
role = "PRINCIPAL ENGINEER" if raises_bar(team) and depth >= LEGENDARY and ships_code else "SENIOR" employer: Sahaj Software
At Sahaj, we pride ourselves on being an exceptional employer that fosters a culture of innovation and collaboration. Our Principal Engineers are empowered to write code daily, engage in meaningful projects, and enjoy the flexibility of unlimited leave, all while contributing to a transparent and open salary structure. With a focus on personal growth and minimal process overhead, we create an environment where engineers can thrive and make a significant impact.
StudySmarter Expert Advice🤫
We think this is how you could land role = "PRINCIPAL ENGINEER" if raises_bar(team) and depth >= LEGENDARY and ships_code else "SENIOR"
✨Tip Number 1
Network like a pro! Reach out to your connections in the industry and let them know you're on the hunt for a role. A personal recommendation can go a long way, especially when it comes to landing that Principal Engineer position.
✨Tip Number 2
Show off your skills! If you’ve got a portfolio or GitHub with projects that demonstrate your ability to raise the bar, make sure to highlight them during interviews. We want to see how you tackle real-world problems, not just theoretical ones.
✨Tip Number 3
Prepare for technical interviews by brushing up on your coding skills. Practice solving complex problems and be ready to explain your thought process. Remember, we’re looking for engineers who can break down messy problems into clean solutions.
✨Tip Number 4
Don’t forget to apply through our website! It’s the best way to ensure your application gets seen by the right people. Plus, it shows you’re genuinely interested in being part of our team at StudySmarter.
We think you need these skills to ace role = "PRINCIPAL ENGINEER" if raises_bar(team) and depth >= LEGENDARY and ships_code else "SENIOR"
Some tips for your application 🫡
Show Your Impact:When you're writing your application, make sure to highlight how you've raised the bar in your previous roles. We want to see specific examples of how your presence has improved the code quality and team dynamics.
Be Authentic:Don’t just list your skills; share your journey! We’re looking for engineers who are humble yet confident. Tell us about your deep dives into tech and how you’ve evolved your opinions over time.
Keep It Relevant:Tailor your application to reflect our focus on real-world complexity. Share experiences where you’ve tackled messy problems and turned them into clean, maintainable systems. We love seeing that problem-solving mindset!
Apply Through Our Website:We encourage you to apply directly through our website. It’s the best way for us to get your application and for you to stay updated on the process. Plus, it shows you’re keen on joining our team!
How to prepare for a job interview at Sahaj Software
✨Show Your Impact
When discussing your experience, focus on how you've raised the bar for your team. Share specific examples of how your mentorship and feedback have improved code quality and team performance.
✨Demonstrate Depth of Knowledge
Be prepared to discuss your strong opinions on engineering practices and technologies. Show that you're humble enough to adapt your views based on new information or insights, highlighting your commitment to continuous learning.
✨Talk About Real-World Problems
Prepare to discuss complex, real-world challenges you've tackled in your previous roles. Use examples that showcase your ability to design and build systems that handle messy problems, rather than just theoretical scenarios.
✨Stay Close to the Code
Emphasise your hands-on coding experience. Be ready to share recent projects where you wrote production code regularly, demonstrating your passion for staying engaged with the technical side of engineering.