What is a Software Engineer at Research Foundation of CUNY?
As a Software Engineer at the Research Foundation of CUNY (RF CUNY), you are stepping into a role that bridges complex technical development with the expansive mission of public higher education and research. You will be building, maintaining, and scaling applications that directly support students, faculty, researchers, and administrative staff across the City University of New York network. Your work ensures that critical educational platforms, research administration tools, and internal systems operate seamlessly and efficiently.
The impact of this position is deeply tied to the user experience of the academic community. Whether you are developing features for a Learning Management System (LMS) or architecting robust databases to handle complex research grants, your code facilitates the core operations of one of the largest public university systems in the United States. You will tackle challenges related to scale, data integrity, and cross-platform responsiveness, ensuring that end-users have reliable access to the resources they need.
Expect a role that balances technical rigor with a strong sense of purpose. The environment is collaborative and highly professional, offering a unique opportunity to apply modern software engineering practices—such as advanced JavaScript frameworks and complex SQL database management—within an academic and research-driven context. You will be expected to take ownership of your projects, advocate for best practices, and continuously improve the technical foundation that supports CUNY’s diverse initiatives.
Common Interview Questions
See every interview question for this role
Sign up free to access the full question bank for this company and role.
Sign up freeAlready have an account? Sign inPractice questions from our question bank
Curated questions for Research Foundation of CUNY from real interviews. Click any question to practice and review the answer.
Design a CI/CD system for Airflow, dbt, Spark, and Kafka pipelines with automated testing, staged releases, rollback, and SOX-compliant auditability.
Explain a structured debugging approach: reproduce, isolate, inspect signals, test hypotheses, and verify the fix.
Explain the differences between synchronous and asynchronous programming paradigms.
Sign up to see all questions
Create a free account to access every interview question for this role.
Sign up freeAlready have an account? Sign inGetting Ready for Your Interviews
Thorough preparation is the key to navigating the interview process at Research Foundation of CUNY. The hiring team is looking for candidates who not only possess strong technical fundamentals but also understand how to apply them to real-world, user-centric problems.
Technical Proficiency – You must demonstrate a deep understanding of the core technologies used by the team, particularly JavaScript and advanced SQL. Interviewers will evaluate your ability to write clean, efficient code and your capacity to design complex database queries that handle substantial academic or research data.
Project Ownership and Experience – The team heavily indexes on your past work. You will be evaluated on your ability to articulate the architecture, challenges, and outcomes of your previous projects. Strong candidates will provide detailed, specific examples of their contributions, rather than vague overviews.
Problem-Solving and Architecture – You will be assessed on how you approach building responsive, scalable applications. Interviewers want to see your methodology for designing systems like a Learning Management System (LMS) or handling cross-device responsiveness, focusing on your structured thinking and user-first mindset.
Collaboration and Professionalism – Working within a university research foundation requires navigating diverse stakeholder needs. You will be evaluated on your communication skills, your receptiveness to feedback, and your ability to work collaboratively across technical and non-technical teams.
Interview Process Overview
The interview process for a Software Engineer at Research Foundation of CUNY is designed to be thorough but respectful of your time. You can expect a structured progression that typically begins with a comprehensive resume walkthrough and behavioral screen. During this initial phase, the team will dive deeply into your background, asking you to unpack specific projects, your role in them, and the technical decisions you made.
Subsequent rounds blend technical assessments with deeper behavioral evaluations. You will face targeted questions regarding your technical stack, particularly focusing on JavaScript and advanced SQL queries. The interviewers are known for being exceptionally professional, understanding, and supportive, creating an environment where you can showcase your true capabilities. Even if you are a junior candidate or a recent graduate, you will be treated with a high level of professional respect.
What makes this process distinctive is the heavy emphasis on practical, applied experience rather than abstract whiteboard algorithms. The team wants to know exactly how you handled responsive design in a past application or how you approached building educational tools.
This visual timeline outlines the typical stages of your interview journey, from the initial resume deep-dive to the final technical and behavioral rounds. Use this to pace your preparation, ensuring you are equally ready to discuss your soft skills and your technical architecture. Note that while the core stages remain consistent, the depth of the technical drill-down may vary slightly depending on whether you are interviewing for an Application Developer or a Senior Software Engineer position.
Deep Dive into Evaluation Areas
Resume Walkthrough and Past Projects
Your past experience is the strongest predictor of your future success at Research Foundation of CUNY. Interviewers will ask you to walk through your resume line by line, expecting you to defend your technical choices and explain the business impact of your work. Strong performance here means speaking confidently about the "why" behind your code, not just the "how."
Be ready to go over:
- End-to-end project lifecycle – Explaining how you took a feature from concept to deployment.
- Overcoming technical roadblocks – Discussing specific bugs or architectural flaws you identified and resolved.
- Stakeholder communication – How you translated business or academic requirements into technical specifications.
- Advanced concepts (less common) –
- Refactoring legacy systems without disrupting active users.
- Implementing CI/CD pipelines for your specific projects.
Example questions or scenarios:
- "Walk me through the most complex project on your resume. What was your specific contribution?"
- "Tell me about a time you had to pivot your technical approach on a project midway through development."
- "How do you ensure that the documentation for your past projects remains accurate and useful for the next developer?"
Front-End Development and Responsiveness
Because the applications built here serve a wide demographic of students and faculty accessing tools across various devices, front-end responsiveness is a critical evaluation area. You will be tested on your modern JavaScript knowledge and your approach to building fluid, adaptable user interfaces.
Be ready to go over:
- Responsive design principles – Media queries, flexbox, grid, and mobile-first development.
- JavaScript fundamentals – ES6+ features, asynchronous programming, and DOM manipulation.
- UI/UX collaboration – How you ensure your technical implementation matches the intended user experience.
- Advanced concepts (less common) –
- State management in large-scale single-page applications.
- Web accessibility (a11y) standards crucial for public educational institutions.
Example questions or scenarios:
- "Give me a specific example of how you implemented responsiveness in one of your recent projects."
- "How do you handle cross-browser compatibility issues in your JavaScript code?"
- "Explain your approach to optimizing the load time of a visually heavy web application."
Database Management and Advanced SQL
Data is at the heart of the research foundation. You must prove your ability to interact with complex relational databases. Interviewers will look for your proficiency in writing advanced SQL queries, optimizing database performance, and ensuring data integrity.
Be ready to go over:
- Complex queries – Joins, subqueries, window functions, and aggregations.
- Database design – Normalization, schema design, and indexing strategies.
- Data manipulation – Safely updating and migrating large datasets.
- Advanced concepts (less common) –
- Query execution plan analysis and bottleneck identification.
- Designing databases specifically for educational technology or LMS platforms.
Example questions or scenarios:
- "Describe your experience writing advanced SQL queries. Can you give an example of a particularly complex query you had to write?"
- "How would you design the database schema for a system tracking student enrollments and grades?"
- "Tell me about a time you had to optimize a slow-performing database query."
Domain Experience: Educational Technology
While not always a strict prerequisite, experience with or a strong understanding of Learning Management Systems (LMS) and educational technology is highly valued. The team evaluates your ability to conceptualize the unique workflows of educators and students.
Be ready to go over:
- LMS architecture – Understanding how content delivery, assessments, and user roles interact.
- User role management – Handling permissions for administrators, teachers, and students.
- System integration – Connecting external tools or APIs to an existing educational platform.
- Advanced concepts (less common) –
- SCORM compliance and educational data standards.
- Real-time collaboration features within an educational platform.
Example questions or scenarios:
- "Discuss your experience with developing or integrating a Learning Management System."
- "How would you approach building a feature that allows faculty to bulk-upload grades securely?"
- "What do you consider the most important technical feature of a successful educational platform?"
