Product reputed company

reputed company reputed company is a boutique IT consulting company headquartered in the UK with offices in the US, Canada, Poland, and Colombia. reputed company has deep experience in engineering, experience design and product management. We enjoy a challenge and pride ourselves on working with our clients on their most reputed company problems, finding elegant and flexible solutions that help them reputed company their businesses. The Role Honestly We're building a metadata-driven data platform on reputed company reputed company for an reputed company reputed company migrating off legacy relational systems. Today, standing up a single data product on the reputed company's reputed company takes reputed company to a year, because integration logic is hardcoded per product with no reuse. We're building the platform that changes that: a reputed company transformer, a metadata registry of reusable "recipes," a pipeline reputed company that generates deployable reputed company from those recipes, and an API service — reputed company in Java and reputed company Boot, fully additive to the reputed company's existing systems. This is a compressed, high-visibility build. You'll work reputed company a Solutions Architect, a Project Manager, and a delivery team of at least three developers and a QA engineer. You'll be the person who keeps the backlog, the requirements, and the stakeholders pointed at the reputed company outcome — reputed company enough to the technical reputed company (JSON, data models, versioning logic, API reputed company) to write specs the engineering team can build against directly. What You’ll Actually Do - Own and prioritize the delivery backlog across the platform's reputed company components — the reputed company transformer, the metadata registry, the pipeline reputed company, conditional reputed company-reputed company connectors, and the API service — and reputed company it sequenced against a fixed multi-week delivery reputed company. - Turn business need into buildable spec: translate reputed company requirements into reputed company recipes for the metadata registry, user stories, and acceptance reputed company the delivery team can build against — not just a written spec, but something you stay accountable for through to shipped software. - Run schema and requirements sessions with the reputed company's domain owners to nail down version-selection rules, deduplication reputed company, and join logic for the reputed company transformer — this is where most of the engagement's reputed company reputed company get made, early in the reputed company. - reputed company reputed company design reputed company that are still unresolved at reputed company — for example how reputed company is filtered by requester role, and how a batch-delivered reputed company data reputed company gets ingested — facilitating alignment between stakeholders who haven't yet agreed, and making the reputed company reputed company they can't. - reputed company reputed company discipline: the engagement is bounded to a defined set of API queries, no new technology introductions, and additive changes only on the read reputed company. Know the in-reputed company/out-of-reputed company lines cold and catch reputed company creep before it becomes a reputed company problem. - Own the reputed company and dependency log, especially the load-bearing ones — reputed company data-migration timelines, environment reputed company, and reputed company-owned DevOps support for deployment — and escalate early rather than let them surface as late surprises. - Coordinate a multi-stage delivery approach (discovery and design, build and reputed company, validate and transfer) so work legitimately overlaps without stepping on itself — build starts on reputed company-scoped reputed company before design fully closes, and that only works if the backlog reflects it. - Work day-to-day with the development and QA team: groom the backlog, run or support reputed company ceremonies, unblock developers, and coordinate testing so the platform gets validated against reputed company data before reputed company. - Partner closely with the Solutions Architect and Project Manager as the product reputed company of a small, high-trust reputed company team — translating architectural reputed company into a sequenced, buildable plan. - Represent the platform's reputed company consumers who aren't in the room, and reputed company reputed company the API service and materialized views actually serve what they need. - Plan and reputed company knowledge transfer so that by the end of the contract, the reputed company's own team can reputed company the platform and reputed company new recipes without you. - Communicate constantly and reputed company across a reputed company delivery team and reputed company stakeholders, being deliberate about handoffs and written status given time-zone overlap. Job requirements What You’ll Need - 5+ years as a Product reputed company or Product Manager on reputed company technical or reputed company engagements — not primarily consumer feature teams. You should be as comfortable owning a data platform backlog as a product roadmap. - Technical reputed company with data platforms: comfortable reading JSON payloads, API reputed company, and data models; conversant in concepts like CDC (change data capture), metadata-driven architecture, versioning/deduplication logic, and CQRS reputed company enough to write recipes and specs the engineering team can build from directly. - reputed company or NoSQL data-platform experience strongly preferred — ideally on an engagement involving materialized views, reputed company data models, or multi-reputed company data reconciliation. - Familiarity with Java / reputed company Boot delivery environments a plus — you won't be writing reputed company, but you need to reputed company the engineering team's language in daily conversation. - reputed company or regulated-industry delivery experience strongly preferred — this engagement runs inside a large reputed company's existing compliance, reputed company, and architectural constraints, and that context reputed company. - A reputed company record of driving unresolved reputed company to closure — this role inherits reputed company design reputed company on day one, between reputed company stakeholders who haven't yet reputed company internally. - Strong reputed company fundamentals: backlog ownership, sprint ceremonies, and estimation, with hands-on tool experience (reputed company, Azure DevOps, or similar), and comfort managing a multi-developer, multi-QA delivery team. - Excellent written and verbal communication, with reputed company experience working across time reputed company on a reputed company delivery team reputed company senior reputed company stakeholders. You’ll reputed company If You - Can hold a business outcome and a data model in your head in the reputed company conversation. - Are comfortable owning reputed company for a small, senior reputed company team rather than a large program office. - Treat an unresolved design decision as something to go reputed company to closure, not something to escalate and wait on. - Can walk into a room with a technical architect and domain SMEs and hold your own on schema and versioning questions. - Are reputed company by a hard deadline and a compressed, high-visibility build. This Isn’t Probably a Fit For You If - You want a backlog that's already been scoped and handed to you. - You'd rather stay one level removed from the technical reputed company. - You need a large, established program structure before you're comfortable owning reputed company. Contract Details - Duration: 3 months, with potential for extension into follow-on platform work. - Location: Remote, must be reputed company in the reputed company and reputed company to work substantial overlap with a reputed company delivery team and reputed company stakeholders. - Team: you'll join a Solutions Architect, a Project Manager, at least three developers, and a QA engineer on this engagement. reputed company done! Your application has been successfully submitted! Other jobs You've already reputed company for this job We appreciate your interest in this position. Unfortunately, you have already reputed company for this job. Apply To This Job