Website:
intribe.ai
Job details:
About intribe
intribe is building identity infrastructure for the long arc of a person's life — a digital record of who someone is, owned by them, verified by the institutions that touched their life.
The platform is built in full compliance with India's Digital Personal Data Protection Act, 2023. We are in stealth, preparing for our first pilot deployment in late 2026.
This is the first engineering role at intribe outside the founder. The person who takes it will own a complete vertical of the platform from day one.
The role
Many of the institutions intribe will work with run their core operations on on-premise enterprise software — typically Windows-based, typically backed by Microsoft SQL Server, often unchanged for a decade.
We do not have the luxury of asking them to migrate. We meet them where they are.
This role builds the integration layer that lets these on-premise systems talk to our cloud platform reliably, securely, and without disrupting their day-to-day operations. Specifically, you will build:
• A .NET 8 Windows Service that runs alongside a partner institution's existing software on their premises
• A SQL Server Change Data Capture (CDC) consumer that detects relevant updates in real time
• A durable local queue with at-least-once delivery semantics, resilient to network outages
• A signed webhook publisher that pushes verified events to the intribe cloud
• Comprehensive observability — logs, metrics, traces — for systems we do not always have direct access to
Bounded scope. Clear edges. Real users from day one. You will work directly with the founder on architecture and own every line of integration code we ship.
Who you are
Required
• 6–9 years of professional .NET experience, with at least 3 in production .NET 6/7/8
• Deep, demonstrated experience with Microsoft SQL Server — schema design, query optimisation, and especially Change Data Capture
• Windows Service development — process lifecycle, installation, service-account permissions, the realities of running long-lived processes on Windows servers
• Hands-on experience with at least one durable queue (MSMQ, RabbitMQ, Azure Service Bus, or equivalent) and the patterns around at-least-once delivery
• Comfortable writing testable code — unit tests, integration tests against real databases, and good judgement about where each is worth it
• Strong instinct for reliability — knows what can fail in a distributed system and writes code that survives it
• Clear written communication — you will be debugging issues with partners over email more than over Zoom
Nice to have
• Experience with legacy .NET Framework codebases — you will encounter them
• Familiarity with Visual Basic .NET (legacy systems often use it)
• Cryptographic signing experience — HMAC, RSA, certificate-based authentication
• Familiarity with cloud-based message bus systems (AWS SNS/SQS, Kafka)
• Working knowledge of Indian data protection regulation (DPDP Act)
• Open-source contributions, especially to .NET libraries
Who you are not
• Someone who has only worked on greenfield projects — this role lives at the interface between legacy and modern, and that is the point
• Someone uncomfortable with on-premise software — this is not a pure-cloud role
• Someone who needs a large team around them — you will be the first integrations engineer, then build the team
Compensation and structure
Compensation
₹10 LPA, based on experience and interview performance
Employment type
Full-time
Probation
6 months
Leave
12 days as per company calendar along with 6 days medical.
Equipment
MacBook Pro or Windows equivalent of your choice, monitor, peripherals
Reporting line
Direct to founder
Location and work mode
• Preference: Chennai-based
• Time zone: Indian Standard Time working hours
•
Interview process
Four stages. Designed to give you a clear read of us as well.
Stage 1 — Screening call (30 minutes)
Conversation with the founder. We talk about your background, what you are looking for, and what we are. No technical questions. We share the broad shape of the role and what intribe is doing in stealth, without revealing specifics.
If we both want to continue, you sign a candidate NDA. Full role details, pilot context, and architecture overview are then shared.
Stage 2 — Technical conversation (60 minutes)
Founder-led. Deep dive into SQL Server CDC, Windows Service patterns, durable queueing, and reliability engineering. We discuss real engineering tradeoffs you have made. No leetcode.
Stage 3 — Take-home (3–4 hours)
A small, realistic build task representative of the work — designed to take an experienced engineer 3 to 4 hours over a weekend. We pay ₹5,000 for completed take-homes regardless of whether you receive an offer.
Stage 4 — Take-home review and culture fit (60 minutes)
We walk through your take-home together. You ask any remaining questions. We discuss compensation, equity, start date.
Offer follows within 48 hours of Stage 4, or a clear explanation of why not.
How to apply
Email careers@intribe.ai with:
• Your CV
• A short note (under 200 words) on why this role interests you and one production reliability problem you have solved that you are proud of
• LinkedIn profile URL
• Earliest you could start
We respond to every serious application within five working days, including declines with reasons.
Click on Apply to know more.