Individual contributor role. 3-5 years of hands-on coding.

Compensation isn’t determined by the salary band in the job posting. It’s determined by the value you bring. We pay top-of-market compensation to top-of-market talent.

Who we are

LiveSwitch builds real-time video and communication technology for small businesses: virtual estimates, on-site documentation, and AI built for the trades. We help David slay Goliath. Our products help small businesses save money, make money, and serve their customers better.

The company is owned and led by Brian Hamilton, who has built major companies before. The model here is simple: small teams of exceptional people, moving fast, obsessed with customers. We are growing our engineering team in Bangalore, and you would build on our SaaS products (systems paying customers use every day), working directly with the leadership.

Read this before you apply

We recruit the way we'd want to be recruited: everything on the table, first date. Here is the part most companies save for after you join.

The hours are long. 60+ hour weeks are normal here. We are trying to build a very large company and there is a cost to that. If you want balance right now in your life, that is a completely legitimate choice, and this is the wrong job for it.
Deadlines are assumed to be now. We don't do status meetings and long email threads. You get an objective, you own it, you move.
Everyone tests the product. Including you. Engineers at LiveSwitch use our products the way customers do, find what's broken, and fix it. "Works on my machine" doesn't exist here.
Feedback is direct. We are brutal about facts so we can be fast about fixes. If your code has a problem, someone will tell you plainly, and you're expected to do the same.
Titles mean nothing. Respect is earned by shipping. Our senior-most people write code and close deals. Nobody is above the work.
You will talk to customers. Every team member gets close to real users every year. Empathy here is an activity, not a value statement.

If that list made you tired, please don't apply, sincerely and with respect. If it made you lean forward, keep reading.

What you'll do

Build and ship features end-to-end across our products: backend, frontend, deploy, monitoring. You own what you build, in production, permanently.
Solve whatever problem matters most right now: frontend, backend, data, infrastructure. We are deliberately not hiring specialists at this stage; we're hiring problem solvers.
Improve the product relentlessly: small, compounding gains shipped quickly beat big-bang releases.
Work directly with founders and senior engineers who've built companies before.

Who you are

3-5 years writing production code, and still an IC by choice. You committed code this week. You have no interest in becoming a manager yet.
You've shipped real systems at real companies, software that paying customers depended on, and you can walk us through every layer of it and defend every decision.
You're a problem solver first. The best engineers we've met all say the same thing: they don't care whether the problem is frontend or backend; they love the challenge itself. That's who we're hiring. If you see yourself as a specialist in one layer, this is the wrong role.
Top of your class from a top-tier school, with a record to show it.
You learn fast, with proof. Tell us about the last time you went from zero to shipping in something unfamiliar.
You come with answers. Asked how to fix something, you give a position, not a menu of options.

The process

Fast: measured in days, not months.

Screen with a member of the Product team (45 min).
Work session: live coding on a real problem + a deep dive into something you've shipped (90 min).
Conversation with Brian Hamilton, owner of LiveSwitch. Yes, really, and yes, early. He meets candidates himself.
Engineering deep dive with a senior engineering leader.
Offer, with a written, explicit summary of exactly what you're signing up for. No surprises. That's the whole point.

Software Engineer

Recommended Jobs