Make Our Team
Your Team
DevLift is built by ReGoBs, a small DevSecOps company in Kochi that runs production infrastructure for fintech and SaaS companies. These are ReGoBs roles, spent building the product. If owning real systems early matters to you, this would be a good fit.
Current openingsCurrent Openings
4 roles, all based in Kochi and all employed by ReGoBs Technologies Pvt. Ltd. Apply even if you match most of a role rather than all of it.
Product engineering (2)
Role brief
What you would own
- The Next.js application DevOps teams use every day: the studio, the approval flow, the FinOps views
- The path from a natural-language request to a reviewed pull request, end to end
- Performance and correctness on a dashboard that renders other people's infrastructure
- The UI for humans to say yes or no to what an agent proposes
What we look for
- TypeScript and React in production, and opinions about state you can defend
- You have shipped something engineers depend on, and been paged for it
- Enough Terraform or Kubernetes to read what the product generates
- A habit of writing the thing down before building it
Role brief
What you would own
- The engine that turns intent into Terraform and Terragrunt across many AWS accounts
- Plan analysis: catching a destructive change before a human is asked to approve it
- The MCP surface that lets an assistant provision infrastructure safely
- Drift detection and the reconciliation that follows it
What we look for
- Deep Terraform, and the scars from running it at scale
- AWS IAM, networking and state handling you could explain to an auditor
- Python or Go for the parts that are not HCL
- A view on where an AI agent should be allowed to touch production, and where not
Customer engineering (1)
Role brief
What you would own
- Getting DevLift running inside a customer's AWS accounts, CI and approval flow, and staying until it is theirs
- The first ninety days of every rollout: what their platform team needs, what breaks, what we did not anticipate
- Turning what you see on site into product changes, with the engineers who will build them
- Being the person the customer's platform team calls, and the person who tells us what they are not saying
What we look for
- Production AWS and Terraform, enough to work inside an account you did not build
- You have shipped something and then supported the people using it, and you liked the second part
- You can explain a plan diff to a CTO and to a junior engineer in the same meeting
- Comfortable in a customer's Slack at six in the evening, and honest about what that costs
Security (1)
Role brief
What you would own
- Security review of what DevLift generates and applies, before a customer ever sees it
- OAuth, token handling and audience validation on the MCP server
- Penetration testing of the product and the client platforms it operates on
- Findings written so an engineer can act on them, with a fix, not just a severity
What we look for
- Hands-on offensive experience: engagements, CTFs, bug bounty, or all three
- Fluency in the OWASP classes of issue and why they recur
- Comfort reading Terraform and IAM policy as attack surface
- OSCP, OSWE or equivalent is welcome and not required
The Values
We Work By
Not a poster on a wall. Three things that decide how work gets done at ReGoBs, and that you will feel in your first week on DevLift.
01
Ownership
ReGoBs owns the stack so founders do not have to. On DevLift that means owning a feature from the request to the reviewed pull request it becomes, and being the person who answers for it.
02
Rigour
The infrastructure DevLift touches is audited. SOC 2, ISO 27001, PCI DSS, SLSA 3. Every change the product proposes has to survive that, which is why the engineering here is careful in ways that are hard to learn elsewhere.
03
Candour
We tell customers what is actually wrong with their infrastructure, and we tell candidates what is actually hard about the job. A product that guards production has to be built by people who say the uncomfortable thing early.
Life @ ReGoBs
The team that builds DevLift, in Kochi. Mostly quiet concentration, occasionally an incident call, and a lot of arguing about the right way to do something before doing it.
Why Engineers Join
Six facts about the work rather than lines from a benefits deck.
Your code runs in production for real companies
DevLift is not a demo. It generates and applies infrastructure for fintech and SaaS teams under an uptime commitment. What you ship on Monday is running somewhere by Friday.
Seniors who have actually done it
The people reviewing your work have run production for platforms handling billions in transactions, hold OSWE, and have spoken at Defcon, BlackHat and OWASP.
Audit-grade by default
SOC 2 Type II, ISO 27001, PCI DSS and SLSA 3 are the everyday standard at ReGoBs, not a special project. That experience is rare and it travels with you.
The product and the practice, side by side
ReGoBs runs infrastructure for clients and builds DevLift to do it better. You sit between the two, and the feedback loop is a hallway, not a quarterly survey.
Wide scope, not one slice
In a month you might ship a UI, change how plans are analysed, read a pentest report and sit on an incident call. If you want breadth, there is nowhere better to get it.
A shared rotation, honestly described
Production is under an SLA, so there is a pager and sometimes it is yours. It is shared across the team and we say so here rather than in month three.
You Will Probably Like It Here
Nothing on this page fits but you want to build DevLift? Write anyway. Tell us what you have built, what you would want to own, and what you are trying to get better at. Include something real: a repository, a write-up, an incident you handled.
Write to us
How Hiring Works
Four steps and about two weeks. No unpaid take-home, no panel of six.
A reply, either way
Someone reads your application and answers it. If it is a no, you get the no.
Within 5 working daysA conversation
With an engineer, about what you have built and what went wrong with it.
45 minutesReal ground
A plan to review, a component to critique, a system to break. No algorithm puzzles.
90 minutesThe trade
Money, the rotation, growth on a small team, and anything you want to ask. Then a decision.
Offer within 3 working daysReady to apply?
A reply within five working days, either way.