GOMO Group — Round 1 Interview Prep

Role: Senior Full Stack Developer (Web, Applications & Integrations) Format: 30 min call — this is almost certainly a screening round with a recruiter or hiring manager, not a deep technical round. Expect fit, background, and breadth-of-skills questions, not live coding.

---

0. The gap you need a story for, before anything else

You'll get asked why you left CloudEQ (separation April 2026, and your resume lists "Aug 2025 – April 2026" for SE II which is likely a typo — check this before the call, it should probably be Aug 2024/2025 range consistent with "3 yrs 4 months"). Fix the resume date issue tonight — if a recruiter notices Aug 2025 to April 2026 is 8 months but you wrote 3 yrs 4 months total tenure, that's a red flag they'll clarify or silently judge.

Answer for "why did you leave CloudEQ / are you currently working":

"I was at CloudEQ for about 3.5 years and grew from SE I to SE II, owning some fairly large systems — a Saga-orchestrated automation platform and enterprise ITSM integrations. My role ended in April this year, and I've used the time since to sharpen my system design and interview depth, and to build out a personal project — StreamSync — that let me work hands-on with real-time streaming and AI transcription, which is close to the kind of integration-heavy, ship-fast work GOMO does. I'm looking for a role where I can own projects end-to-end again, ideally somewhere with more direct client/product ownership, which is what drew me to this posting."

Keep it forward-looking, no negativity about CloudEQ, no over-explaining.

---

1. Likely question categories for a 30-min GOMO screen

Given the JD's emphasis (agency environment, end-to-end ownership, CMS/e-commerce, integrations, stakeholder management), expect roughly this split:

1. Walk me through your background / resume (5-7 min)
2. Technical breadth check — CMS, e-commerce, cloud, integrations (8-10 min)
3. Ownership & project-delivery scenarios (5-7 min)
4. Agency-fit / soft skills — juggling multiple projects, client-facing work (5 min)
5. Logistics — notice period, location (Chandigarh vs Pune — this matters, see below), compensation, availability (3-5 min)
6. Your questions for them (2-3 min)

---

2. The single biggest risk area: CMS & e-commerce

Your resume has zero CMS or e-commerce experience — no WordPress, Sanity, Strapi, Contentful, Storyblok, Payload, Shopify, or WooCommerce. This is explicitly called out as a required skill ("2-3 platforms"). Do not try to bluff depth here. The credible move is: acknowledge the gap honestly, bridge it with adjacent experience, and show you can ramp fast.

Likely question: "Have you worked with any headless CMS or e-commerce platforms?"

Interview-ready answer:

"Direct hands-on CMS/e-commerce shipping isn't in my last three roles — my depth has been backend systems, integrations, and internal tooling. But conceptually I'm very comfortable with the pattern: content modeling, API-driven content delivery, and decoupling presentation from data — that's the same mental model as the event-driven, API-first systems I've built, just with a CMS as the data source instead of Salesforce or an ITSM tool. I've used Next.js extensively for the frontend side, which is how most modern headless setups render content anyway. Given a sprint or two I'd expect to be productive in something like Sanity or Strapi — the learning curve for me is usually the platform's data modeling conventions, not the underlying concepts."

If pushed further, mention you're comfortable evaluating platforms and would default to whichever the team already uses.

---

3. Technical breadth questions (map to your real experience)

"Tell me about a project where you owned something end-to-end."

Use the Saga Orchestrator project — it's your strongest, most senior-sounding story.

"At CloudEQ I architected an automation platform triggered by Salesforce CDC events. I designed the whole pipeline: a stateless Node.js ingestion layer, a Redis/BullMQ queue partitioned by opportunityId so related events processed in order, and a MongoDB-backed Saga Orchestrator handling compensating transactions and idempotency guards so retries never created duplicate resources. I also built human-in-the-loop approval gates via Jira webhooks for steps that needed sign-off. It processed 500+ events a month at 99% reliability with zero data loss, and cut manual project-intake overhead by 75%. I owned this from architecture through production — including the failure-mode design, like scoping exponential backoff to only transient 5xx errors so we didn't retry things that would never succeed."

This answers "architecture," "scalable/secure/maintainable systems," and "ownership" all at once.

"Have you worked with REST APIs / GraphQL / webhooks?"

"Heavy REST API experience — building and consuming them across the CloudEQ integrations (Jira, Halo ITSM, ServiceNow, Microsoft Graph), plus webhook-driven architectures for the approval-gate system. I haven't shipped GraphQL in production, but I understand the resolver/schema model well and have worked with TanStack Query on the client side, which overlaps conceptually with GraphQL's declarative data-fetching approach. I'd be comfortable picking it up quickly if a project called for it."

"Talk about a third-party integration you built."

Use Halo ITSM ↔ Jira / ServiceNow ↔ Jira or Microsoft Graph / Teams+SharePoint.

"I built event-triggered AWS Lambda integrations syncing Halo ITSM and Jira bidirectionally — this cut manual ticket synchronization by about 80% and sped up ticket resolution by 25%. Separately I integrated Microsoft Graph API to automate Teams channel creation and SharePoint file migration for over 2,000 documents, which is directly relevant to the kind of business-system integrations — CRM, ERP, identity providers — this role touches. The common thread is designing for idempotency and graceful degradation, since these integrations run unattended and have to survive upstream outages."

"Experience with authentication/SSO/OAuth?"

"Yes — I implemented SSO via Azure AD for about 450 enterprise users at CloudEQ, and separately built OAuth 2.0-secured Node.js backend services at InfoHub. I've also used Clerk for auth in my personal project, StreamSync, so I've worked across both the enterprise-identity-provider pattern and the modern managed-auth-service pattern."

"Cloud experience — AWS, GCP, Vercel?"

"Strong on AWS — Lambda and API Gateway have been core to most of my integration work — plus some Azure (Functions, VMs, ACI, and I hold the AZ-900 cert). I haven't used GCP or deployed on Vercel professionally, though Vercel is a natural fit given how much Next.js I've written, so that'd be a quick adjustment, not a new paradigm."

"Databases — MySQL, PostgreSQL, MongoDB?"

"PostgreSQL and MongoDB are both daily-driver for me — Postgres with Prisma on the relational side, MongoDB as the source of truth for the Saga Orchestrator's state. I don't have direct MySQL experience but it's close enough to Postgres that it's not a real gap."

"CI/CD, GitHub workflows?"

Be honest and brief if this is thinner than the rest — pivot to what you do know (Git workflows, code review practices) rather than overclaiming pipeline-authoring experience unless you actually set up CI/CD pipelines at CloudEQ — if you did, use specifics; if you mostly consumed them, say so plainly.

---

4. Agency-fit / ownership / soft-skill questions

"This is an agency environment — multiple projects, tight timelines, direct client exposure. How do you handle that?"

"The closest parallel is running the Saga Orchestrator project alongside the Halo-Jira integration work at the same time, each with different stakeholders — engineering leadership on one, IT ops on the other. What worked was being upfront early about scope and tradeoffs rather than letting ambiguity sit, and building in observability so I wasn't firefighting blind when something broke across projects. I like this kind of variety, honestly — going from a backend orchestration problem to a frontend performance problem keeps me sharp."

"Tell me about a time you had to push back on scope or manage a stakeholder."

Prep a specific 60-90 second story from CloudEQ (the human-in-the-loop approval gates are a natural example — you presumably had to negotiate what needed human sign-off vs. full automation). If you don't have a crisp one memorized, pick the strongest real example tonight and rehearse it once out loud.

"Where do you want to be in a few years?"

Tie to GOMO's ownership model — senior IC who owns projects concept-to-launch, not necessarily a management track answer unless that's genuinely true for you.

---

5. Practical / logistics questions — prepare real answers, don't wing these

• Location: JD lists Pune (WeWork Raheja Woods, Kalyani Nagar). You're in Chandigarh. You need to proactively address this — ask upfront whether the role is remote, hybrid, or requires relocation, since it's not stated as remote. This is honestly a question you should ask them early in the call if they don't clarify it.
• Notice period: You're already off CloudEQ's payroll since April, so you can likely say "immediately available."
• Compensation expectations: Have a number/range ready. Don't dodge if asked directly in a screening call — recruiters usually want this early to confirm alignment.
• AI-assisted dev tools (Cursor, Claude Code, Copilot): This is explicitly in the JD and plays to your favor.

  "I use Cursor and Claude regularly in my workflow — for scaffolding, debugging, and speeding up boilerplate — and I've also gone deeper into how MCP works, since I did Anthropic's course on it. I think being fluent with AI-assisted tooling is table stakes for shipping fast in an agency context, so this is genuinely a strength, not a checkbox for me."

---

6. Questions to ask them (pick 2-3, don't ask all)

1. "Is this role remote/hybrid, or is on-site in Pune expected? How is the team currently distributed?"
2. "What does a typical project look like end-to-end — is it usually one engineer owning a client project solo, or small pods?"
3. "Which CMS and e-commerce platforms does the team standardize on today?"
4. "What does success look like in the first 90 days for whoever takes this role?"
5. "What's the next step after this round, and roughly what's the full process?"

---

7. Quick-reference cheat sheet (glance at this right before the call)

Their ask	Your strongest proof point
Architecture/scalable systems	Saga Orchestrator (BullMQ, MongoDB, compensating transactions)
Integrations (CRM/ERP/identity)	Halo↔Jira, ServiceNow↔Jira, MS Graph/Teams/SharePoint, Azure AD SSO
Frontend/React/Next.js depth	Custom budget-vs-variance table (no library, windowed loading, expandable rows)
Performance/SEO optimization	800ms page-load cut, LCP +10%, CLS 0.23→0.12
End-to-end ownership	Saga Orchestrator, StreamSync personal project
AI tooling fluency	Cursor, Claude Code, MCP course
Gap to own honestly	No CMS/e-commerce — bridge via API/headless conceptual overlap
Gap to clarify	Pune location vs. your Chandigarh base — ask, don't assume

Good luck tomorrow — this role plays well to your integration and systems-architecture strength. The CMS gap is real but minor if you handle it with the honest-bridge answer above rather than dodging it.