Web Developer
Veradigm (company site, opens in a new tab)PuneOn-siteDirect career pageEst. 5–12 LPA
Posted 14h ago
Reach people at Veradigm
People at this company you can reach
Log in to see who works here
Create a free account or log in to see the people at Veradigm you could write to:
- Recruiters & HR
- People in this function
- Work addresses
Your match
Against your primary resume
Log in to see your match score
Create a free account or log in to unlock your CV match score across:
- Role fit
- Experience
- Industry relevance
Protocol Intelligence
How competitive this role is
Competition
Background fit
Strictness
Log in to see why each signal reads the way it does.
Job description
Structured overview of role & requirements
About This Role
- Own the upkeep and continuous development of a Jekyll-based website, including content, templates, performance, security, testing, and monitoring.
- Administer GitHub repositories and documentation; use Claude Code and Cowork to develop, test, deploy, and host web properties.
- Manage web integrations and data connections, translating stakeholder requirements into technical solutions and communicating project status and risks.
Minimum Requirements
- Work Experience Required: Not explicitly mentioned in the JD.
- Technical requirements: Proficiency with Jekyll or a comparable static site generator; working knowledge of HTML, CSS, Markdown, and Liquid templating; ability to use Claude Code and Cowork professionally.
- Git and GitHub experience, including repository administration, branching, pull requests, and issue tracking.
- Pune-based in-office role with a hybrid night shift, Monday–Friday, 7:30 PM–4:30 AM IST.
Ideal Candidate Profile
- Has a strong fit for static-site development and repository ownership, with the ability to maintain code quality, testing, and thorough technical documentation.
- Can independently manage multiple web workstreams, including deployment, performance, security, and integrations; CI/CD, hosting, APIs, and web security are preferred signals.
- Comfortable translating requirements between non-technical stakeholders, designers, and vendors, and proactively communicating technical decisions and risks.