πŸ‘”

How we Hire

If you are excited to join One2N, this page is for you. The intention of this page is to let you know how and why we do what we do.
First, we’d like to explain the kind of work we do. This drives the kind of roles we are hiring for and the skills needed for these roles. Finally, we’ll cover our interview process and how we assess these skills.
You can also find out more about the benefits and perks of joining One2N. The perks or benefits are a byproduct of our values and culture. So join us for the values and culture, not for perks. Those will follow anyway. πŸ™‚

Some history

We are in business since Dec-2019, have had 100% YoY growth in revenue and team size since our inception. In the short time we’ve been around, we have partnered with 15+ startups to provide them with reliable, timely software solutions. So much so, that our business has now started growing through referrals.
The primary reason:
We care about our craft. And that is a non-negotiable quality we expect our people to have.

So what do we do?

We primarily work on the back end of software systems, making them scalable, reliable and maintainable through our engineering expertise. The typical tech stack we use is statically typed languages (Go, Java) and ecosystems around these languages. Our work is typically of two types:
  • Backend Architecture and Engineering
  • Site Reliability Engineering
While we treat these as separate roles as of now, we would eventually want to champion the mindset that these are skills that anyone can pick up. Anyway, as engineers grow in experience and seniority, they are expected to contribute to both of these areas, and more.

How we work

When we engage with our clients, we look forward to
  • Work on production system
    • We believe in building something people want and will use. It’s as simple. Even when we work on designing systems from scratch, our focus is on building features incrementally and making sure our code goes to production. After all, the iteration really starts when people use the software we build. What good is a Mona Lisa painting if it’s not seen by anyone?
  • Work with decision makers
    • We work with decision makers to ensure our efforts are always aligned to what the business wants. We strive to create meaningful business impact with our work and shy away from buzzword driven development. Technology is an enabler; we want our work to either make money or save money and time for our clients. We work with decision makers to understand the context and build pragmatic solutions that are maintainable, scalable and reliable.
  • Long term focus
    • Almost everything in software is a short-term vs long-term trade off. Refactor vs pile on more tech debt, deployment automation vs manual deployments that take days, automated testing vs lot of manual verification - these are all long-term vs short-term trade offs. We strive to build software that’s easier to change. Period. After all, change is the only constant.
We believe in becoming a T or a ∏ shaped individuals, where we can excel at one or two things while still having a broad understanding of other things. Our philosophy is:
Go deep in a couple of areas instead of going shallow in all areas.
This requires deliberate practice and repetition in solving similar problems. Thankfully, we get to do that at One2N. For more details about our work, refer our past case studies.
Here’s everything you need to know about our values, hiring processes, team, work etc. before you apply to work with us.

Where to go from here

πŸ€„
Hiring Philosophy
πŸ”¦
One2N Values
πŸ“
Interview Process
🍫
Benefits and Perks
🏏
Open Positions