Find your next opportunity
Browse fresh openings from leading companies and apply with a resume tailored to the role.
Browse fresh openings from leading companies and apply with a resume tailored to the role.
12764 openings
3313-3320 of 12764Apptegy
Free to start · No card · 5 credits the moment you sign up
As a Senior Full Stack Engineer on Apptegy’s Platform Engineering team, you will help build and evolve the shared foundations that power our products at scale, including authentication, identity, access, platform services, and the operational guardrails that keep our systems secure, observable, and reliable.
This is a hands-on senior engineering role for someone who enjoys solving cross-cutting technical problems, especially the ones that make the entire product ecosystem stronger for other engineers and safer for end users. You will work across the stack using Vue.js and Ruby on Rails, but your focus will go beyond feature delivery. You will design and own platform capabilities that application teams depend on, such as secure sign-in experiences, shared service patterns, access controls, rollout safety mechanisms, and monitoring that helps us detect and resolve issues early.
This role is ideal for an engineer who can move between product context and platform architecture with ease, bringing a strong sense of ownership, sound engineering judgment, and a bias toward systems that are scalable, maintainable, and secure by default.
Design, build, and maintain platform capabilities that support multiple product and engineering teams, with a strong emphasis on authentication, identity, session management, and access control.
Lead the architecture and implementation of secure, scalable full-stack systems using Vue.js and Ruby on Rails, ensuring performance, reliability, and maintainability across shared platform surfaces.
Improve authentication and sign-in experiences across the platform, including flows that require district-aware routing, subdomain-aware login behavior, SSO compatibility, and clear separation of session boundaries.
Build and evolve shared services that act as reliable sources of truth for platform-critical data and workflows, enabling consistency across applications and teams.
Create systems and patterns that other engineers can build on confidently, reducing duplicated effort and raising the baseline for security, performance, and developer experience.
Make thoughtful technical decisions that align with long-term platform strategy as well as near-term business priorities.
Establish and improve observability across platform-owned areas, including instrumentation, dashboards, alerting, and monitoring for authentication flows, platform latency, and failure patterns.
Design with security in mind from the start, ensuring platform behavior enforces clear access boundaries and reduces opportunities for incorrect or unauthorized access.
Use feature flags, progressive delivery, and well-defined rollback procedures to launch safely and reduce risk when introducing platform changes that affect multiple user types or systems.
Identify platform bottlenecks and failure modes early, then drive pragmatic solutions that improve resilience and reduce support burden over time.
Contribute to engineering standards and architectural patterns that make platform changes easier to test, operate, and evolve.
Partner closely with product, design, and application engineering teams to translate complex platform needs into clean technical solutions and well-scoped implementation plans.
Work across team boundaries to support initiatives where entitlement logic, shared services, or authentication behavior impacts multiple product areas.
Mentor engineers through design reviews, code reviews, and day-to-day collaboration, helping the team write high-quality, maintainable code and make sound technical tradeoffs.
Break down large, ambiguous platform problems into manageable, well-sequenced work that can be executed reliably.
Communicate clearly with stakeholders about risks, dependencies, timelines, and technical decisions, especially when changes have broad platform impact.
Significant professional experience building and shipping production software across the full stack.
Strong hands-on experience with modern frontend and backend development, ideally including Vue.js and Ruby on Rails.
Experience working on platform, infrastructure-adjacent, or shared systems that support multiple teams or products.
Deep understanding of authentication and authorization concepts such as SSO, session management, identity flows, access control, and secure service boundaries.
Experience designing APIs, backend services, and internal abstractions that are reusable, reliable, and easy for other engineers to adopt.
A strong operational mindset, including comfort with monitoring, alerting, rollout planning, incident response, and performance tuning.
Ability to balance speed and quality while making durable architectural decisions in a fast-moving environment.
Proven ability to mentor others, influence technical direction, and raise engineering standards through collaboration.
You have experience owning or materially improving authentication, identity, or access-management systems in a multi-tenant SaaS environment.
You have built shared platform services, internal tooling, or foundational capabilities that multiple product teams depend on.
You bring strong judgment around observability, rollout safety, and incident prevention, especially for changes that affect sign-in, permissions, or other critical user flows.
You are comfortable navigating ambiguity and defining scalable patterns where no clean precedent exists.
You combine deep technical skill with a product-minded approach, understanding how platform decisions shape user experience, security, and team velocity.
You are the kind of engineer who raises the bar for the people around you through mentorship, clarity, and durable engineering practices.
Originally posted on Himalayas
Start with a role or skill you want to use in your next job. Use the location and role filters to narrow the results, then open a listing to review the description. A title alone rarely explains the level of responsibility, working arrangement, or experience a team needs. Compare those details before deciding which opportunities deserve a tailored application.
Employers use different titles for similar work. If an exact phrase produces no results, try a shorter title, a core skill, or an alternative name for the role. Remove one filter at a time to understand which requirement is narrowing your search. A broader search can reveal suitable work without asking you to change your actual qualifications.
For each promising listing, read the responsibilities and separate essential requirements from preferences. Note the location, schedule, employment type, and compensation when provided. Missing details are questions to confirm with the employer. A remote opening may still require a particular country, work authorization, or time-zone overlap, so check the full posting before treating it as a location-independent opportunity.
Choose a few examples that demonstrate the skills this employer names. Explain your contribution and its outcome, using accurate numbers where available. Put the most relevant experience first and keep your resume easy to scan. Avoid adding technologies, qualifications, or achievements simply because they appear in a description. Your application should make your existing strengths easier to understand.
Follow the employer’s instructions for resumes, cover letters, work samples, and screening questions. Review the exported file before submitting it: confirm that contact details are correct, text can be selected, and links reach the intended pages. A resume check can help you spot unclear writing before you apply. Its feedback is advisory and does not predict a hiring decision.
Listings are collected from external sources and may change after they appear here. The employer or recruiting destination controls whether applications are open. If an original link is unavailable, check the company’s careers page for the title or move to another opening. An employer website link is a place to check current vacancies, rather than confirmation that a particular job is still accepting applications.
Keep a simple record of the company, role, job reference, application date, and documents you sent. Record any follow-up instructions and the next action you plan to take. This makes it easier to prepare for interviews, compare opportunities, and avoid applying repeatedly to the same opening through different boards. Review your shortlist as employers update their listings and prioritize opportunities with clear requirements that match the work you want to do.