Job Description
Kindly share your updated resume at your earliest convenience, along with a suitable time for us to connect over a call.
\n
I would appreciate the opportunity to understand your current situation, career goals, and specific preferences regarding your next opportunity.
\n
\n
Full Stack Associate Developer
\n
Location: Dallas, TX / Jersey City, NJ / Tampa, FL
\n
Interview Process: 2 rounds – Second round in person
\n
Pay Range : $45 to $50
\n
Role Expectations
\n
1. Overall Experience & Mindset
\n
- \n
- Early career to developing engineer with ~2-4 years of Hands on experience in full stack application development.
- Demonstrates strong fundamentals, willingness to learn Client standards, and the ability to grow with guidance from senior engineers.
- Comfortable working in Agile teams, taking ownership of assigned stories and tasks.
- AI tool exposure like GitHub copilot is a plus but not required.
\n
\n
\n
\n
\n
2. Backend Development (Primary)
\n
- \n
- Solid understanding of Java and Spring Boot fundamentals.
- Experience building or modifying RESTful APIs.
- Basic knowledge of microservices concepts (service boundaries, configuration, logging).
- Familiarity with messaging concepts (Kafka/JMS) is a plus, but deep expertise is not required at this level.
- Uses structured logging and understands basic error handling.
\n
\n
\n
\n
\n
\n
3. Frontend Development
\n
- \n
- Working knowledge of Angular or React (components, services, state basics).
- Ability to build simple UI features and integrate them with backend APIs.
- Understanding of basic UI/UX principles and accessibility awareness (at least at a conceptual level).
\n
\n
\n
\n
4. Database & SQL
\n
- \n
- Ability to write basic to intermediate SQL queries:
- SELECT, JOINs
- WHERE clauses
- GROUP BY / ORDER BY
- Understands relational database concepts (tables, indexes, primary/foreign keys).
\n
\n
\n
\n
\n
\n
5. Development Tools, Testing & Deployment
\n
- \n
- Comfortable using an IDE (IntelliJ, VS Code, or Eclipse).
- Familiar with Git (branching, pull requests, resolving conflicts).
- Exposure to unit testing (JUnit / Jest or similar).
- Basic understanding of CI/CD pipelines and deployment workflows.
- General familiarity with cloud environments (AWS or similar).
- High level understanding of containers (Docker) and platform concepts (OpenShift/Kubernetes) is sufficient.
- No expectation to design infrastructure independently at this level.
\n
\n
\n
\n
\n
\n
\n
\n
6. Technical Demonstration & Interview Expectations
\n
Must be able to:
\n
- \n
- Explain actual project work they have contributed to (academic, personal, or professional).
- Walk through code they have written . There should be sample projects in their IDE and should be good enough to showcase his/her skills. A Hello world program is not acceptable.
- Answer basic Java, SQL, and frontend questions without relying on memorized answers.
\n
\n
\n
\n
Should be prepared for:
\n
- \n
- Screen sharing
- Demonstrating problem-solving using an IDE
- Deep system design is not expected, but clarity of thought and fundamentals are required.
\n
\n
\n
\n
7. Behavioral & Professional Expectations
\n
- \n
- Communicates clearly with team members and mentors.
- Open to feedback and actively incorporates suggestions.
- Understands the importance of quality, security, and reliability in a regulated financial environment.
- Shows accountability for deliverables and timelines, even for smaller assignments.
\n
\n
\n
\n
\n
8. What Is Not Expected at Associate Level
\n
- \n
- Designing complex distributed systems independently.
- Owning architectural decisions end-to-end.
- Advanced Kafka tuning, cloud cost optimization, or complex performance engineering.
- Leading squads or mentoring others formally.
\n
\n
\n
\n
\n
\n
Only candidates with strong practical understanding and real project exposure will be considered
\n
\n
Feel free to apply on this position or DM me for the role assistance. Also, if this isn’t for you, kindly like or share to help spread the word.