Scrum Master – Guwahati (Ganeshguri)
A part-time, on-site Scrum Master role is open in Ganeshguri, Guwahati, paying up to ₹39,000 a month. The team's looking for someone to keep their development sprints running smoothly and their Agile process actually working, not just documented somewhere and ignored. Part time scrum master jobs in Guwahati at this pay level don't come around often, so it's worth a look for anyone already living in or near the city.
What you'd actually be doing
- Facilitate sprint planning, daily standups, and retrospectives for the development team
- Clear blockers that are slowing the team down, whether that's a dependency on another team or a decision stuck waiting on approval
- Coach the team on Agile and Scrum practices, adjusting the process as the team's needs change rather than enforcing a rigid textbook version of Scrum
- Work with product owners and developers together to keep sprint priorities realistic given the team's actual capacity
- Step in when disagreements come up within the team and help work through them before they slow down delivery
That last point matters more than people expect when they walk into this role. A good chunk of what makes a Scrum Master useful isn't process knowledge; it's being the person who can read a tense standup and know when to pull two people aside afterward. Ceremonies run on schedule easily enough once a team's used to them; what actually separates a strong Scrum Master from a mediocre one shows up in the quieter moments between meetings.
What the role calls for
A bachelor's degree is the baseline education requirement, and it doesn't need to be a technical one specifically, though understanding software development well enough to follow technical conversations helps considerably. Candidates should be comfortable with the tools this team's Agile process runs on day-to-day, things like sprint boards and backlog tracking software, since a Scrum Master who can't navigate the team's own tooling loses credibility fast.
Forty-two months of relevant experience is expected, ideally spent actually running Scrum ceremonies rather than just participating in them as a developer or product person. There's a real difference between sitting through years of standups and being the one responsible for making them useful. A candidate who's led Scrum for a smaller team for a shorter stretch, but did it well, is worth more here than someone who's attended years of ceremonies without ever owning the facilitation.
Core skills
- Solid grounding in Agile and Scrum practices, beyond just knowing the vocabulary
- Sprint planning, including realistic capacity estimation for the team
- Team facilitation, keeping meetings on track without shutting people down
- Conflict resolution, since disagreements within a development team are normal and need a steady hand rather than avoidance
These skills tend to show up together in a single stretch of any given day. A sprint planning session might start smoothly, hit a disagreement over scope between two developers, and require the same person to shift from facilitator to mediator without missing a beat.
Good to have
A Certified Scrum Master credential or similar Agile certification will strengthen an application, though plenty of strong candidates have learned the role through direct experience rather than formal certification. Some exposure to Kanban alongside Scrum is useful too, since many teams end up running a hybrid of the two rather than a textbook Scrum implementation. Neither is required, but both make the first few weeks a little easier to navigate.
Pay and benefits
Scrum master salary in Guwahati for this part-time role tops out at ₹39,000 monthly. The position includes pro-rated paid leave, flexible in-office scheduling that fits a part-time arrangement, and performance-based incentives. Since it's on-site, relocation assistance and accommodation support are available to candidates moving to Guwahati for the role.
Working in Ganeshguri
Ganeshguri has a decent concentration of small and mid-sized IT companies for a city like Guwahati, and this team operates out of an office there. Naukri Mitra has listed a handful of similar Agile and software development roles from teams in the same area recently, and this one follows a comparable pattern: a small development team, a part-time schedule built around flexible hours rather than a fixed shift, and a Scrum Master who's genuinely embedded with the team rather than floating between several groups.
Because the team is on the smaller side, this Scrum Master will likely know every developer's working style personally within the first month or two, which makes facilitation easier than it would be on a larger, more anonymous team. That familiarity cuts down on much of the guesswork facilitation usually involves; knowing that one developer tends to go quiet when overloaded, or that another needs a direct nudge to speak up, makes reading the room much faster.
Who tends to succeed here?
People who naturally notice team dynamics, who they haven't heard from in standup lately, who seem quietly frustrated, tend to do well in this kind of role. It also suits someone who's comfortable being the person who says no to unrealistic sprint commitments, even when that's an uncomfortable conversation to have with a product owner pushing for more. Candidates who prefer staying entirely behind the scenes, without much direct people-facing responsibility, may find this a harder fit than a project coordination role with less day-to-day human friction. The role rewards someone who genuinely likes people, messiness and all, more than someone who prefers process for its own sake.
Applying
Send a resume that spells out which teams and projects you've run Scrum for, along with team sizes and how long each engagement lasted. The interview process typically includes a conversation about how you've handled a specific team conflict or blocked sprint in the past, since that tends to reveal more than a general description of Scrum knowledge would. Candidates should come ready with a real example, not a hypothetical one, since the specifics of how a situation actually got resolved say more than the general approach described.
