Life at IntelliconnectQ
Trekkers, bikers, farmers, swimmers, runners, artists, polyglots, cricket enthusiasts, yoga practitioners — building decision infrastructure for enterprises around the world.
Meet the team →The whole person
The best practitioners we know are whole people. The patience a farmer applies to growing things, the discipline a marathon runner builds before dawn, the eye an artist trains over years — these don't stay outside the door when the work starts. They walk in with the person.
We don't separate who someone is from how they work. The diversity of what our team pursues outside technology is part of what makes the team effective inside it.
See the full roster →Curiosity is the thread. What each person is curious about varies — and that range of perspective is part of what makes the work better.
Our culture
We hold ourselves to the same standard we build into our clients' systems: decisions get made, information gaps get closed, progress is measured by outcomes — not hours logged or screens watched. The sports team analogy on the team page isn't decoration. Defined roles, shared accountability, one goal — and everyone knows the score.
Missing information gets a call — not an email thread. If something is unclear, whoever notices it surfaces it immediately. We don't wait for the next scheduled meeting.
The idea that works wins, regardless of who brings it. Seniority earns trust, not automatic authority. Feedback travels in every direction.
No time tracking. No screen monitoring. Accountability lives in scrum calls and delivery — not keystroke logs. We hire adults and trust them completely.
Teams take ownership the way a sports team does — you know your role, you execute, you're accountable for the result. Recognition follows performance, not tenure.
Teams help each other — not because it's policy, but because the work demands it. When one person is blocked, it's the team's problem. That's the model.
If something slows us down, we fix it — a tool, a script, an automation. Six internal tools in three years, because we don't live with friction when we can engineer past it.
Continuous learning
Every team member — not just engineers — has access to AI tools and the space to find where they genuinely make the work better. It's not mandated; it's adopted because it works. Each person discovers their own leverage points.
Anyone can recommend a tool. If it improves the work, we adopt it. Airbyte, coding assistants, IDE extensions, and several frameworks currently in use came from team recommendations — not top-down decisions.
Team members write on Medium and publish to GitHub under their own names. What we learn from real deployments — tools built, problems solved, architectures deployed — goes back to the practitioner community. Contributing beyond the client relationship is part of how we work, not an afterthought.
Tools we build for customers are published on GitHub, credited to the engineer by name — on LinkedIn and in the repository. Your name goes on what you build. Recognition that's visible, not buried in a delivery note.
Working here means seeing the full deployment cycle — not just design or planning. Manufacturing, logistics, managed services, financial infrastructure — across countries and company sizes. Most engineers go deep in one vertical. Here you build working systems across many, and you understand the decision patterns that make or break each one. That breadth is the career asset.
Internal infrastructure
We use the same technology we build for clients — internally, every day. The AI analysis agent running our customer workflows is built on the OpsGrid framework we ship to enterprises. Internal friction is product feedback, not a support ticket.
When customers reach out with queries and documents, an AI agent — built on the same framework that powers OpsGrid — handles initial triage and analysis instantly, routing to the right team with context intact. We are our own first OpsGrid customer. When we ship an update, we feel it before any client does.
SMB clients communicate via WhatsApp. Our team runs on MS Teams. Previously an analyst relayed messages between them — summarising, forwarding, sometimes losing detail. Now customer messages, documents, and images arrive directly into the right Teams channel. The right person picks up. No relay, no loss.
Creating change requests used to mean navigating multiple screens in the PM tool. Now a Teams bot accepts a single command — create CR, add comment, update status — from wherever the team is already working. No screen switching. No context lost between the conversation and the ticket.
This one came from our own frustration. The team was spending hours searching documentation — for each other, for customers, during onboarding. The answer existed somewhere in the wiki; finding it was the friction. We don't file tickets for problems we can build our way out of.
So we built QHub. Type a question in the browser tab, get the answer from the company knowledge base instantly. No context switching, no browsing. Self-hosted, unlimited users, Apache 2.0 — now deployed at multiple client sites too.
Every morning, the bot posts each team member's to-do for the day directly into the scrum channel. Through the day it surfaces updates and comments automatically. The PM has full visibility without chasing anyone. Everything is in the channel — no ambiguity
Teams focus on doing the work.
Our teams operate across multiple GitHub organisations — customer repos, our own, partner companies. Adding or revoking access manually across all of them was a recurring burden on the IT Infra team: org-by-org navigation, missed revocations, unnecessary dependency on engineering.
The engineering team built an internal tool that hands control directly to Infra — add or remove users across any organisation from a single interface, without filing a request or touching each org separately.
Practitioners first, people always. See who builds the systems — and what they've shipped.