Software Engineer _ KE
Reports
Administratively to the Scrum Master for day-to-day task allocation (“What” to
do and “When”) and functionally to the Head of Engineering on technical matters
(“How” of the work)
Job Summary:
Key Responsibilities:
- Development
of small to medium software modules assigned by the Software Engineer II /
Senior Engineer.
- Write
clean, efficient, and well-documented code.
- Participate
in peer code reviews and technical discussions.
- Conduct
basic unit testing and contribute to automated test cases.
- Help
maintain project documentation and contribute to internal tools and
utilities.
- Learn
and apply team development practices, including version control and coding
standards.
- Actively
participate in sprint planning and team stand-ups.
Requirements
Required Qualifications:
- Bachelor’s
degree in Computer Science, Software Engineering, or related discipline.
- 1–2
years of professional experience (internships or entry-level roles
acceptable).
- Proficiency
in at least one programming language (e.g., Python, Java, JavaScript, C#).
- Familiarity
with source control systems (e.g., Git).
- Basic
understanding of object-oriented programming and software development
lifecycle.
- Eagerness
to learn and improve technical and soft skills.
Preferred Qualifications:
- Exposure
to front-end or back-end frameworks (e.g., Angular, Java Springboot.
- Experience
working in an Agile or Scrum team environment.
- Familiarity
with development tools and development environments (e.g., VS Code,
IntelliJ).
- Basic
knowledge of REST APIs and database interactions.
Core Competencies:
Technical Learning
- Quickly
learns new tools and technologies and applies them to tasks.
Team Collaboration
- Works
effectively under the guidance of more experienced engineers.
- Communicates
progress and blockers clearly to Software Engineer II.
Problem Solving
- Breaks
down tasks and approaches problems methodically.
- Seeks
help when necessary and demonstrates initiative.
Attention to Detail
- Produces
quality code that meets standards and passes tests.
- Follows
established practices for documentation and versioning.
Communication
- Communicates
clearly in team discussions and written documentation.
- Receptive
to feedback and willing to adjust based on guidance.